search for: 0logwatch

Hi all, Last week I have migrated 5 CentoS 6.2 servers to CentOS 6.3. In all of them, I receive every day problems with logwatch: /etc/cron.daily/0logwatch: Can't exec "sendmail": No such file or directory at /usr/sbin/logwatch line 1040, <TESTFILE> line 1. Can't execute sendmail -t: No such file or directory It is really strange, because I am using default config ... On the other side, I have three CentOS 6.2 servers and th...

...tem pull in the following selinux updates: Jan 07 21:39:14 Updated: selinux-policy-2.4.6-255.el5_4.3.noarch Jan 07 21:39:31 Updated: selinux-policy-targeted-2.4.6-255.el5_4.3.noarch This machine has SELinux set to Enforcing. This morning, I see I got the following email from Cron: /etc/cron.daily/0logwatch: sendmail: warning: premature end-of-input on /usr/sbin/postdrop -r while reading input attribute name sendmail: fatal: root(0): unable to execute /usr/sbin/postdrop -r: Success Frankly, this error message means little to mean... in the course of troubleshooting, I tried this: # setenforce Permi...

...roblems with my system email or specifically my logwatch reports showing up in my inbox. I got most of those issues figued out except one now when i get an email from my system it has a title of this Cron <root at localhost> run-parts /etc/cron.daily with this message /etc/cron.daily/0logwatch: Recipient names must be specified I have my aliases set right and have been googling for an answer and just cant seem to find anything pointing me in the right direction. But this has been going on for awhile now and i would like to get my normal reports back that i used to get. I have never ha...

...itely been applying updates from base, no other changes have happened on this box. I ran logwatch at the command line: logwatch --detail medium --mailto root at fqdn.example.com but still no email. As expected, /etc/cron.daily has the following entry: lrwxrwxrwx 1 root root 39 Jul 30 2008 0logwatch -> /usr/share/logwatch/scripts/logwatch.pl Where should I start looking to figure out why logwatch seems not to be doing its thing? Thanks in advance, -Ray

Hello I am trying to get logwatch working on CentOS 8. System is fully updated. Usually install minimal version and then add only necessary with yum. On CentOS 7: install logwatch and get daily logwatch report on mail. On CentOS 8: install logwatch but no way to get mail. Am I doing something wrong? Or miss something? Thanks in advance Blaz

...32-bit servers, delivering the report by mail to my root account once a day sometime around 3:30am. On the 64-bit systems, no mail is occurring. From the "cron" log on a 64-bit system, there are lines like: cron-20110821:Aug 21 03:36:23 XXX run-parts(/etc/cron.daily)[9727]: finished 0logwatch (where "XXX" stands for the server name) but no report is sent. If I run logtwatch manually, by simply typing logwatch as root, I get the mail. Is this a known issue? Is there some information I could supply that would help identify the reason? To the best of my knowledge, I made...

...lled. I need some help to try to solve this problem, because is a production server and I can't uninstall many working packages that depends on perl* ones. I read about similar problem in CentOS forums, with no sucess. Many thanks to all!!! Here is the report from logwatch: /etc/cron.daily/0logwatch: Errno architecture (i386-linux-thread-multi-2.6.9-42.0.3.elsmp) does not match executable architecture (i386-linux-thread-multi-2.6.18-53.1.14.el5pae) at /usr/lib/perl5/site_perl/5.8.8/Errno.pm line 11. Compilation failed in require at /usr/lib/perl5/5.8.8/File/Temp.pm line 138. BEGIN failed--com...

.../cron.daily) Aug 18 04:02:01 xen-B1 anacron[25037]: Updated timestamp for job `cron.daily' to 2008-08-18 Aug 18 04:06:06 xen-B1 crond[2963]: (CRON) STARTUP (V5.0) the last line seems to be the reboot. here the content of my cron.daily folder. [root at xen-B1.blab:/etc/cron.daily]# ls 0anacron 0logwatch cups logrotate makewhatis.cron mlocate.cron prelink rpm tmpwatch I had also heartbeat running on the machines, after the last crash I thougt it was heartbeat that rebooted the machines, so I disabled it, but now I see it isnt heartbeat that causes these reboots. I use centos 5.1 with no self...

I've been taking a look at how RedHat (and CentOS) handles logrotate. According to the man page, logrotate is supposed to be fired by cron. But when I look at root's crontab $ sudo crontab lu root no crontab for root What exactly fires logrotate (and other scheduled events like "logwatch", which ends up in root's inbox)? === Al

zep wrote: > On 10/13/2015 09:54 AM, C. L. Martinez wrote: >> I haven't entries in conrtab's users file at this moment, but I have >> done a test: * * * * * ls -la, and it is not triggered. But like I say >> before, installed system cronjobs like logwatch task are not triggered > > I'd say that crontab doesn't actually prove that the job isn't being