Scheduler is not running

[tek]

Hello, every time i restart the OTRS server, I have the message (Scheduler is not running) that appears in the console. I run the script (/otrs.Scheduler.pl -a start) and the message disappears. Ok but I would like the service to start automatically. I look at :
https://otrs.github.io/doc/manual/admin ... eduler-cli
I see :
OTRS provides init.d scripts to start / stop the OTRS Scheduler process automatically by the operating system. These scripts are located under OTRS_HOME/scripts.

But I do not find this file. How i should do for this service to start automatically?

Thx

[crythias]

Code: Select all

crontab -l -u otrs | grep Scheduler

Code: Select all

su - otrs
echo $HOME

[tek]

thx for your reply

Code: Select all

crontab -l -u otrs | grep Scheduler
*/5 * * * *    $HOME/bin/otrs.Scheduler.pl -w 1 >> /dev/null

Code: Select all

su - otrs
[root@servmotrs ~]# echo $HOME
/root

[nd0]

Seems to be the wrong HOME dir...

Code: Select all

echo $HOME

should be: /opt/otrs

... so you might have a permission issue ?!

[RStraub]

Not sure about that, the substitute user didn't go through properly. You see it in the shell the user is still root.

[tek]

Exactly RStraub

[root]

Check what homedir and shell the OTRS user hast:

Code: Select all

getent passwd otrs

If there is no valid login shell (see /etc/shell) try

Code: Select all

su - otrs -s /bin/bash

or set a valid shell:

Code: Select all

chsh -s /bin/bash otrs

[RichH]

I just figured out how to fix this on my CentOS 6.5 system running OTRS 3.3.12, there were read/write error in my otrs system log as well:

My mistake was that I didn't switch user correctly 'su - otrs' didn't work. I should have used 'su -s /bin/bash - otrs'. To fix this:

Code: Select all

service otrs stop
/opt/otrs/bin/otrs.Scheduler.pl -a stop --force
service crond stop
service httpd stop
su -s /bin/bash - otrs 
/opt/otrs/bin/otrs.RebuildConfig.pl
/opt/otrs/bin/otrs.LoaderCache.pl -o delete
/opt/otrs/bin/otrs.DeleteCache.pl
/opt/otrs/bin/otrs.DeleteSessionIDs.pl --all
exit (back to root)
/opt/otrs/bin/otrs.SetPermissions.pl --otrs-user=otrs --web-user=apache --otrs-group=apache --web-group=apache /opt/otrs

Code: Select all

mysql -u root -p
use otrs;
delete from process_id;
exit

Code: Select all

su -s /bin/bash - otrs
/opt/otrs/bin/Cron.sh start

reboot

check scheduler:
perl /opt/otrs/bin/otrs.Scheduler.pl -a status

[tek]

with :

su - otrs -s /bin/bash
chsh -s /bin/bash otrs

i can su - otrs
thx for that

Now i pass all command from RichH, the scheduler is running after a reboot + 5 min
but :

Code: Select all

perl /opt/otrs/bin/otrs.Scheduler.pl -a status
 >> Can't write opt/otrs/var/log/otrs.log: Aucun fichier ou dossier de ce type <<
Running 2325

[tupson]

The Debian 8 OS itself doesnt appear to have a cronjob for the Scheduler:

Code: Select all

: crontab -l -u otrs | grep Scheduler
: no crontab for otrs
But within Webmin there is a cronjob configured for OTRS services.

Code: Select all

test -x $HOME/bin/otrs.Scheduler.pl && $HOME/bin/otrs.Scheduler.pl -w 1 >> /dev/null

This job was defaulted to run every 5 minutes, but this also appears to be overkill for its use in my Agency. I have since adjusted thist to every 15 minutes (may even up it to 30 minutes).

The way I seemed to bandaid this issue on my appliance is just to reduce the restart timer within OTRS GUI (SysConfig --> Scheduler --> Core) "Scheduler::RestartAfterSeconds" from the default of 86400 (24hrs) to 3600 (1hr); so that it auto restarts every 1hr if there are any failures/stops in between.

Thus, down time (if there is any from the warning to begin with) is cleared/reset every hour.