![]() According to man run-parts, you can pass -verbose to cause it to print the name of each script before running it, or use -report to print only for scripts which produce output. According to /etc/anacrontab, cronie uses run-parts to run its scripts. I didn't know how to solve this when you asked, but I looked into it for you. There doesn't seem to be anything in the man page to indicate this. Is there a way that I can get cron to display the name of the script if it produces output? I seem to remember that the default cron in Debian is able to do this. I am aware that the cron job is likely to be in /etc/cron.daily. Any thoughts about the cronjob issue?Ĭronie is reporting that the job is one of the anacron daily tasks, meaning it is probably a job in /etc/cron.daily. I am no longer getting the error messages. That should be fixed before we tackle the cronjob issue. It's important that 'locale' prints valid locale settings and that it doesn't print error messages. Posted: Sun 10:23 am Post S: have you seen my last post about the locale output? PS - does anybody know how to get cronie to report the name of the script that the error occurred in? I had to add the second line to get rid of the error messages (locale: Cannot set LC_CTYPE etc) when I ran `locale -a': ![]() Last edited by mike155 on Sun 10:01 am edited 1 time in total Which init-system do you use? OpenRC or Systemd? ![]() You can find a list of valid entries in /usr/share/i18n/SUPPORTED. You can see list of all localisation in /etc/locale.gen using the cat command: cat /etc/locale.gen OR more /etc/locale.gen Another option is to use grep command to search for specific locales. no output file produced because errors were issued How to fix Perl: warning: Setting locale failed in Debian and Ubuntu Type the following commands to fix it. There's no indication of which script produces the messages. In response to the second answer, the subject of the message in my cron job is Quote: Locale: Cannot set LC_ALL to default locale: No such file or directory Locale: Cannot set LC_MESSAGES to default locale: No such file or directory Locale: Cannot set LC_CTYPE to default locale: No such file or directory Incomplete set of locale files in "//usr/lib/locale/en_AU.utf8" no output file produced because errors were issued character map file `C.UTF-8' not found: No such file or directory * Bad entry in locale.gen: 'UTF-8 ' skipping * Generating 1 locales (this might take a while) with 4 jobs From there you can check the crontab of that user to see any relevant environment variables, or to disable the job if you don't want it to run at all. The subject line of the cron e-mail should tell you the command that was run, and for which user. Posted: Sun 3:20 am Post subject: Re: perl: warning: Setting locale failed.įrom an unidentified cron job (maybe spamassassin update?) Perl: warning: Falling back to the standard locale ("C"). Perl: warning: Please check that your locale settings:Īre supported and installed on your system. I've started getting these messages on my system - from an unidentified cron job (maybe spamassassin update?) Posted: Sat 11:03 pm Post subject: perl: warning: Setting locale failed. Gentoo Forums Forum Index Portage & Programming Even changing repo to official + purge and manual installation locales doesn't solve my problem, which manifests itself on each fresh installation of Debian 7.Gentoo Forums :: View topic - perl: warning: Setting locale failed. Here is what shows locale: root:~# locale The same with dpkg-reconfigure locales + setting pl_PL.UTF-8, pl_PL.ISO-8859-2 or even en_US: Įxport LC_ALL=pl_PL.UTF-8 (even on root): -bash: warning: setlocale: LC_ALL: cannot change locale (pl_PL.UTF-8).Generating locales myself - update-locale LC_ALL="pl_PL.UTF-8" - shows:.Everything works fine, except locales - any attempt to install anything shows: I've installed Debian 7 i386 on my VPS (OpenVZ).
0 Comments
Leave a Reply. |