logwatch 4.3.2 not cleaning up /tmp

[hc_andy]

Hi All,

We're running logwatch 4.3.2 on our plesk server and all of a sudden logwatch doesn't seem to be cleaning up after itself. We had to go in and manually delete the logwatch file from /tmp. With /tmp only being 95M and the logwatch file filling this up, customer's scripts and database can't write to /tmp any more.

Any suggestions on why logwatch is not cleaning up after itself?

Currently running Plesk 8.2 on Red Hat Enterprise Linux ES release 3 (Taroon Update 6).

[root@plesk2 cron.daily]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/tmpMnt 95M 339K 90M 1% /tmp

[root@plesk2 tmp]# du -h
95M ./logwatch.yao16972
1.0K ./hsperfdata_tomcat4
95M .

[root@plesk2 tmp]# ls -lah ./logwatch.yao16972
total 95M
drwx------ 2 root root 1.0K Sep 17 04:05 .
drwxrwxrwt 7 root root 95K Sep 17 11:31 ..
-rw-r--r-- 1 root root 0 Sep 17 04:02 autorpm
-rw-r--r-- 1 root root 141K Sep 17 04:02 cron
-rw-r--r-- 1 root root 0 Sep 17 04:02 exim
-rw-r--r-- 1 root root 0 Sep 17 04:02 maillog
-rw-r--r-- 1 root root 46M Sep 17 04:02 messages
-rw-r--r-- 1 root root 0 Sep 17 04:05 rt314
-rw-r--r-- 1 root root 0 Sep 17 04:05 samba
-rw-r--r-- 1 root root 47M Sep 17 04:05 secure
-rw-r--r-- 1 root root 0 Sep 17 04:05 tac_acc
-rw-r--r-- 1 root root 25 Sep 17 04:05 up2date
-rw-r--r-- 1 root root 0 Sep 17 04:02 xferlog

Thanks.

Andy