Why scheduler won't Auto start ?

[nouphet]

Testing OTRS for use, but after rebooted OS, OTRS Scheduler won't auto start.

My OTRS Environment

OTRS 3.3.5
CentOS 6.5
Apache 2.2.15
MySQL Server 5.1x

After reboot, I got this messages.

# /etc/init.d/otrs status
httpd (pid 1184) を実行中...
Checking database connection... Trying to connect to database
DSN: DBI:mysql:database=otrs;host=127.0.0.1
DatabaseUser: otrs

Connected.
done.
Checking OTRS Scheduler service.... Not Running, but PID is still registered! Use '-a stop --force' to unregister the PID from the database.
Error!
Maybe your database isn't configured yet?
Checking /opt/otrs/bin/otrs.PostMaster.pl ... (active) done.
Checking otrs spool dir... done.

Then I restarted OTRS Scheduler, but this time got this new message.

# /etc/init.d/otrs restart
Shutting down OTRS
Disable /opt/otrs/bin/otrs.PostMaster.pl ... done.
Shutting down cronjobs ...
done.
Shutting down OTRS scheduler ...
done.
Final shutdown of OTRS.. done
Starting OTRS..
Checking httpd ... done.
Checking database connection... Trying to connect to database
DSN: DBI:mysql:database=otrs;host=127.0.0.1
DatabaseUser: otrs

Connected.
done.
Starting OTRS Scheduler Service... ERROR: OTRS-otrs.Scheduler-58 Perl: 5.10.1 OS: linux Time: Fri Mar 21 20:23:03 2014

Message: NOTICE: otrs.Scheduler.pl is registered on the DB, but the registry has not been updated in 70 seconds!. The register will be deleted so Scheduler can start again without forcing

Traceback (1324):
Module: main::_AutoStop (unknown version) Line: 592
Module: /opt/otrs/bin/otrs.Scheduler.pl (unknown version) Line: 239

done.
Enable /opt/otrs/bin/otrs.PostMaster.pl ... done.
Checking otrs spool dir... done.
Creating cronjobs (source /opt/otrs/var/cron/*) ...
done.

-->> http://localhost/otrs/index.pl <<--
Final start of OTRS.. done

Why I got this messages

Starting OTRS Scheduler Service... ERROR: OTRS-otrs.Scheduler-58 Perl: 5.10.1 OS: linux Time: Fri Mar 21 20:23:03 2014

Message: NOTICE: otrs.Scheduler.pl is registered on the DB, but the registry has not been updated in 70 seconds!. The register will be deleted so Scheduler can start again without forcing

[Giulio Soleni]

Hi,
maybe it's not your specific case but I found a solution for a problem actually similar to yours here: viewtopic.php?f=62&t=17742

Indeed, it hasn't been necessary for me to specify any starting script in /etc/init.d/ however I needed to cleanup process_id table and that was enough to restore the correct run of the Scheduler service.

HTH,
Giulio

[nouphet]

Hi

thank you for the URL.
viewtopic.php?f=62&t=17742

I'll check it ! ^^