[otrs] Generic Agent
Rory
rclerkin at gmail.com
Thu Oct 6 12:45:18 GMT 2011
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 <start|stop|restart> <otrs_username>
For your system you would run;
sudo ./Cron.sh restart fireline
Once the script has run check that the crontab for the otrs user has been filled
crontab -l
Once done, review your crontab backup file for any entries you might
want to restore to you otrs users crontab and add them as necessary.
Last thing is to make sure the generic agent crontab entry is enabled.
List the contents of your crontab and look for the section about the
Generic Agent.
Make sure the following line does not have a hash symbol (#) at the
start of the line which sould comment it out;
*/10 * * * * $HOME/bin/otrs.GenericAgent.pl -c db >> /dev/null
If the line is commented out with a # then open the crontab for
editing and remove it. Save the changes and you are done.
>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
More information about the otrs
mailing list