otrs scheduler fails to start.

[jwhip]

So when I look at my services Scheduler does not start. I have tried to force it. But to no avail. Below are the messages that I'm seeing. It seems that I've been having this same issue will all 3.2 release. Any help would be great.

CentOS 6.4
OTRS 3.2.9

Code: Select all

httpd (pid  6565) is running...
Checking database connection... Trying to connect to database
DSN: DBI:mysql:database=otrs;host=localhost;
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.

Code: Select all

 ]# /opt/otrs/bin/otrs.Scheduler.pl -a stop --force
ERROR: OTRS-otrs.Scheduler-10 Perl: 5.10.1 OS: linux Time: Wed Jul 17 19:14:00 2013

 Message: Scheduler could not delete PID file! No such file or directory

 Traceback (7413):
   Module: /opt/otrs/bin/otrs.Scheduler.pl (unknown version) Line: 104

[root@OTRS2 ~]# /opt/otrs/bin/otrs.Scheduler.pl -a stop --force
ERROR: OTRS-otrs.Scheduler-10 Perl: 5.10.1 OS: linux Time: Wed Jul 17 19:14:12 2013

 Message: Scheduler could not delete PID file! No such file or directory

 Traceback (7415):
   Module: /opt/otrs/bin/otrs.Scheduler.pl (unknown version) Line: 104

[markinct]

I am having the same issue, OTRS 3.2.4, Ubuntu 12.04.

It seems that when the system attempts to start the scheduler it fails, but records the PID as if it started. Subsequent attempts to restart fail, until as the error message states, the script is executed to stop with the -force option. The scheduler has never failed to start when I've started it manually.