We installed the upgrade to 3.1.11, coming from 3.1.10, in our test environment. Things were going smoothly until restarting the OTRS service. During the startup, it hit a snag at the OTRS Scheduler Service.
Code: Select all
[root@user init.d]# service otrs start
Starting OTRS..
Checking httpd ... done.
Checking database connection... Trying to connect to database
DSN: DBI:mysql:database=otrs;host=localhost;
DatabaseUser: otrs
It looks Ok! done.
Checking OTRS Scheduler Service... /etc/init.d/otrs: line 101: -a: command not found
1
Error!
This can happen if your database is not configured yet.
We confirmed our database is configured and we have not had this issue with prior installations. After looking around a bit, we found that the OTRS Scheduler Service command was not being defined in /etc/sysconfig/otrs. To clear up this issue, we added the following to it:
Code: Select all
/etc/sysconfig/otrs
# location of otrs.Scheduler.pl
#
OTRS_SCHEDULER=$OTRS_ROOT/bin/otrs.Scheduler.pl
OTRS_SCHEDULER_TEST="$OTRS_SCHEDULER -a status | grep 'Running'"
This immediately solved the issue. We can easily replicate the error by commenting out the new code and attempting to start the otrs service. At this point the otrs service is functioning on v3.1.11 without any problems, but we don't know what may have caused the initial problem or if this will continue with future installations.
