6/20/2023 0 Comments Perl warning setting locale failedLocale: Cannot set LC_ALL to default locale: No such file or directory Perl: warning: Falling back to a fallback locale ("en_US.UTF-8"). Perl: warning: Please check that your locale settings:Īre supported and installed on your system. The error looks something like this: perl: warning: Setting locale failed. Locales are a framework to switch between multiple languages and allow users to use their language, country, characters, collation order, etc. Thanks for the reference to the ubuntu docs, quite worthwhile I'll be reading what it has to say about postfix, too.In case you’re running Ubuntu 18.04 ( or earlier versions as well, such as 16.04, 14.04 ), you may be encountering a locales warning or error while trying to update your package index or installing a package.Īs the locales package configuration states: So if you have the patience I'd like to get postfix back up, too. logwatch used to work ok and it isn't like I'd intentionally do anything to alter that. Looks like a permission issue, but I don't see how this came about. Nov 4 17:01:37 cl28810 postfix/master: fatal: bind: private/lmtp: No such file or directory Nov 4 17:01:37 cl28810 postfix/postfix-script: starting the Postfix mail system Nov 4 17:01:36 cl28810 postfix/postfix-script: warning: not owned by postfix: /var/spool/postfix/private/maildrop Nov 4 17:01:36 cl28810 postfix/postfix-script: warning: not owned by postfix: /var/spool/postfix/private/scache Nov 4 17:01:36 cl28810 postfix/postfix-script: warning: not owned by postfix: /var/spool/postfix/private/lmtp Nov 4 17:01:36 cl28810 postfix/postfix-script: warning: not owned by postfix: /var/spool/postfix/private/anvil Syslog shows this: Nov 4 17:01:15 cl28810 postfix/master: fatal: bind: private/lmtp: No such file or directory The VM UI status page shows this and restarting in either the UI or the commandline, using service postfix start both fail, although the command line version returns It develops that postfix is not running although dovecot is. The logwatch command still fails, though not with locale errors and still at line 870 as above. But often what is actually the case is that there are several problems. It is always tempting when the computer misbehaves to think that there is a problem with the computer. So far so good and I have no more locale errors. Likewise with setting a default locale to GB worked fine after I read the manual about having to re-login for changes to take effect. But locale IS already installed and your suggestion to try installing english language support got lots of action and seems to have worked out ok. Running apt-get install locale tells me there is no locale available to install. In the interval from my last post the failcount on that line has increased to 13 for unknown reasons running logwatch again does not alter the value. I have not tinkered with the installation and would much appreciate advice or pointers. I know that this is not a perl support site, but perl was installed as a part of installation of VM. System 'cat '/var/log/messages' | /usr/bin/perl /usr/share/logwatch/scripts/shared/expandrepeats ''| /usr/bin/perl /usr/share/logwatch/scripts/shared/removeservice 'talkd,telnetd,inetd,nfsd,/sbin/mingetty,netscreen,netscreen'| /usr/bin/perl /usr/share/logwatch/scripts/shared/applystddate ''>/tmp/logwatch.85OCq98X/messages' failed: 35072 at /usr/sbin/logwatch line 870. Perl: warning: Falling back to the standard locale ("C"). When I do this is the result: # logwatch warning: Setting locale failed. Periodically I'd like to be able to send myself a logwatch report. I have a VM GPL install under openvz on Ubuntu 10.04.2.
0 Comments
Leave a Reply. |