what is this cron error?

[werbemaxe]

Hi there,

since I have a root server, I cannot ask anyone, but I am responsible myself for the server. However, I don't know what this cron error is coming up.. every day..

Who can give me a hint and tell me if it's important or not.


/etc/cron.daily/logrotate:

error: error accessing /var/log/exim: No such file or directory
error: exim:3 glob failed for /var/log/exim/*log
error: found error in /var/log/exim/*log , skipping
error: stat of /var/log/maillog failed: No such file or directory
/etc/cron.daily/prelink:

/etc/cron.daily/prelink: line 45: /var/log/prelink/prelink.log: No such file or directory
/etc/cron.daily/prelink: line 46: /var/log/prelink/prelink.log: No such file or directory
/etc/cron.daily/prelink: line 47: /var/log/prelink/prelink.log: No such file or directory


thanks, max

 

[105547111]

There is no /var/log/exim and it's bombing the logrotate.

Open up /etc/cron.daily/logrotate and see what it's doing.

What's your OS and version and can you check another server of the same OS to see if the file is in /var/log?

 

[werbemaxe]

the OS is CentOS 5: Linux 2.6.18-194.26.1.el5xen

this is the content of logrotate:

________________
#!/bin/sh

/usr/sbin/logrotate /etc/logrotate.conf
EXITVALUE=$?
if [ $EXITVALUE != 0 ]; then
/usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]"
fi
exit 0
__________________


and since it's pointing to the logrotate.conf, here is the content of the .conf file:

___________

# see "man logrotate" for details
# rotate log files weekly
weekly

# keep 4 weeks worth of backlogs
rotate 4

# create new (empty) log files after rotating old ones
create

# uncomment this if you want your log files compressed
#compress

# RPM packages drop log rotation information into this directory
include /etc/logrotate.d

# no packages own wtmp -- we'll rotate them here
/var/log/wtmp {
monthly
minsize 1M
create 0664 root utmp
rotate 1
}

# system-specific logs may be also be configured here.

_________


I don't have access to another server of the same OS.

Any idea though what this could be?

I need to know if this is important or harmful for my server or if I can neglect it.

thanks, max