./scripts/upcp not running anymore

[vwiley1]

Hi,

My auto updates and backups are not running anymore. They are supposed to run everynight and send me an email. At first I just thought I wasn't receiving the emails, but I did SSH over to my second harddrive and noticed that no backups have been made since 3/30/04 and they are supposed to be done everyday.

Does anyone have any idea on how I can get this to run everynight again?

Vince Wiley

 

[vwiley1]

Actually here is an edit....

I have looked at logwatch for the past 20 days prior to 3/30/04 and compared them to logwatch's after 3/30/04

It seems all of the below has not been ran since 3/30/04

/scripts/cleanmsglog > /dev/null 2>&1: 1 Time(s)
/scripts/upcp: 1 Time(s)
/usr/local/bandmin/bandmin: 48 Time(s)
/usr/local/bandmin/ipaddrmap: 1 Time(s)
/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1: 288 Time(s)
/usr/mailscanner/bin/check_mailscanner > /dev/null 2<&1: 144 Time(s)
/usr/sbin/exim_tidydb /var/spool/exim callout > /dev/null 2>&1: 1 Time(s)
/usr/sbin/exim_tidydb /var/spool/exim reject > /dev/null 2>&1: 1 Time(s)
/usr/sbin/exim_tidydb /var/spool/exim retry > /dev/null 2>&1: 1 Time(s)
/usr/sbin/exim_tidydb /var/spool/exim wait-remote_smtp > /dev/null 2>&1: 1 Time(s)
/usr/sbin/exim_tidydb /var/spool/exim_incoming callout > /dev/null 2>&1: 1 Time(s)
/usr/sbin/exim_tidydb /var/spool/exim_incoming reject > /dev/null 2>&1: 1 Time(s)
/usr/sbin/exim_tidydb /var/spool/exim_incoming retry > /dev/null 2>&1: 1 Time(s)
/usr/sbin/exim_tidydb /var/spool/exim_incoming wait-remote_smtp > /dev/null 2>&1: 1 Time(s)
personal crontab listed: 2 Time(s)
personal crontab reloaded: 1 Time(s)
personal crontab replaced: 1 Time(s)

Any way to get all these to run again?

 

[nickn]

I've seen this same problem a few times now in the last few days.

 

[vwiley1]

My problem was resolved late last night.

I had 2 issues:

1. I recently installed mailscanner, I had to edit the exim.conf and add the line queue_only_override = false

2. My crontab file got messed up somehow.
I had to crontab -e while logged in as root and fix the whole file.

Vince