Scheduler process is registered but might not be running

[ccummings]

I keep getting this notification after migrating our OTRS installation to Linux. I click on it and chose Force start...but the message comes back within a few hours.

[crythias]

... where do you get this message?

[ccummings]

It shows up at the top of the dashboard. If I click on it, I can start the schedular manually, but it the message will come back within a day whether or not a check the box to force start.

[ccummings]

Any suggestions?

[cordeos]

Has anyone found a solution to this scheduler issue? We have 4 OTRS 3.1.10 machines (also moved to Linux from a previous Windows install) that are experiencing the same problem.

[cordeos]

If you continually receive the OTRS Scheduler warning in the GUI... "Scheduler process is registered but might no be running."
We have found this often occurs after we migrate OTRS server or change the OTRS server hostname and/or IP address.

The cause seems to be multiple scheduler process records stuck in the database. The entries here are not deleted by OTRS and the Scheduler status check does not correctly filter its check by correct hostname or PID. Check your OTRS database, table process_id to see if there are multiple entries for the scheduler daemon. Try deleting all records in the table, then restart the OTRS service...

MYSQL SCRIPT:
use otrs;
delete from process_id;

THEN from command line:
service otrs restart

Check back in your process_id table and you should now have a single, correct data row for the Scheduler.

[PeterLee]

Try this way:
1. copy /opt/ots/var/scripts/otrs-schedule-linux to /etc/init.d
2. edit otrs-schedule-linux:
change your otrs_home to /opt/otrs
change otrs user and group to apache

3. chkconfig --add otrs-shedule-linux
4. then add to service for start-up

See this for details, http://doc.otrs.org/3.2/en/html/scheduler.html