• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Logrotate Cron error

Pagemakers

Silver Pleskian
/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
/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


This happens on a domain migrated from Plesk 8.6
 
There is no /etc/cron.daily/prelink file in default Plesk 9.5.1 installation. It is not Plesk related file.
Aldo make sure that you have following default logrotate service settings:

# cat /etc/logrotate.conf
# 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.

# ll /etc/logrotate.d/
total 40
-rw-r--r-- 1 root root 167 Nov 13 05:47 httpd
-rw-r--r-- 1 root mailman 407 May 25 2008 mailman
-rw-r----- 1 root named 163 Jan 20 22:31 named
-rw-r--r-- 1 root root 61 Sep 4 2009 rpm
-rw-r--r-- 1 root root 232 Dec 8 20:31 samba
-rw-r--r-- 1 root root 68 Jan 21 2009 sa-update
-rw-r--r-- 1 root root 154 Oct 21 05:45 snmpd
-rw-r--r-- 1 root root 115 Nov 11 2008 sw-sso
-rw-r--r-- 1 root root 306 May 25 2008 syslog
-rw-r--r-- 1 root root 103 Jul 28 2009 tomcat5
 
I have…

# cat /etc/logrotate.conf
# 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.
[root@s15396544 /]# ll /etc/logrotate.d/
total 32
-rw-r--r-- 1 root root 147 Jan 7 2007 exim
-rw-r--r-- 1 root root 167 Nov 12 23:47 httpd
-rw-r--r-- 1 root mailman 407 May 24 2008 mailman
-rw-r----- 1 root named 163 Jan 20 16:31 named
-rw-r--r-- 1 root root 61 Sep 4 2009 rpm
-rw-r--r-- 1 root root 68 Jan 21 2009 sa-update
-rw-r--r-- 1 root root 306 May 25 2008 syslog
-rw-r--r-- 1 root root 100 Aug 20 2009 yum
 
Not sure that exim is necessary there. This MTA is not used in Plesk.
 
We removed exim out of that directory and still go this cron error:

/etc/cron.daily/logrotate:

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
 
Hmmm... just edit this /etc/cron.daily/prelink file and remove extra logs there... Or remove /etc/cron.daily/prelink file... But it is not Plesk file.
 
Actually it's an error code that comes in connection with Webalizer. My question is the same as those above. I know Webalizer is an external program included by the host (in this case 1and1) residing inside Plesk. So heading to the makers of Webalizer and/or the hosting itself is a better idea to get this situation fixed?

This error virtually "crashes" my entire server a couple of times a week, and there's just me to run it. Meaning I do have to sleep... only to wake up to find the server needs rebooting every other day.

Maybe I'll just take the da.mn thing off (turn it off) completely.

Watchdog is another one that gives me fits and starts. Is Watchdog part of Plesk? Haven't investigated that yet....
 
Hi,

im having the same issue after Updating Plesk to 10.1.1

Is there a known solution to this problem? I'd prefer having Webalizer or AWstats keep running.

Cheers,

Gordon
 
Back
Top