I thought I had sent this out apparently not,
Below is the log, in order to excecute /etc/init.d/cron status and /etc/init.d/cron start or restart I had to use sudo.
Oct 5 08:54:18 support init: cron main process (13148) killed by TERM signal
Oct 5 08:54:18 support cron[32634]: (CRON) INFO (pidfile fd = 3)
Oct 5 08:54:18 support cron[32635]: (CRON) STARTUP (fork ok)
Oct 5 08:54:19 support cron[32635]: (CRON) INFO (Skipping @reboot jobs -- not system startup)
Oct 5 08:55:01 support CRON[32664]: (fireline) CMD (date)
Oct 5 08:55:01 support sendmail[32666]: p95Ft16O032666: from=fireline, size=281, class=0, nrcpts=1, msgid=<201110051555.p95Ft16O032666@support.firelinebroadband.com>, relay=fireline@localhost
Oct 5 08:55:01 support sm-mta[32667]: p95Ft1qo032667: from=
Hi Garabed,
We can see now that your Cron jobs are running correctly from this line;
Oct 5 08:55:01 support CRON[32664]: (fireline) CMD (date)
So the next thing to do is get the OTRS cron jobs included in the crontab.
Firstly log in as your otrs user, fireline.
List the current items of the crontab and save them to a file (in case
you need to keep anything that is currently in the OTRS user's
crontab) e.g.
crontab -l > /opt/otrs/20111006_cronbackup
When you run the otrs Cron.sh script it will overwrite whatever is
currently in your crontab for the otrs user.
Switch to the OTRS bin directory;
cd /opt/otrs/bin
The syntax for running the Cron.sh script as root is as follows
sudo ./Cron.sh
From this point on the crontab should be working correctly. If the Cron.sh script still didn't run for some reason let us know. The next thing to check is that your generic agent has run. Check the otrs log file when you expect your Generic Agent to have run to confirm that it worked.
Let us know how you get on. Kind regards, Rory Clerkin
participants (2)
-
Garabed Yegavian -
Rory