Hi,

I already tried that with same results. One other thing that I discovered is that when I run ps -u otrs I get:

PID TTY TIME CMD

27247 ? 00:00:00 otrs.Scheduler.

Which stays there till I don't kill it manually.

I created exactly same setup in virtual machine that is running MYSQL where scheduler is working just fine. Could MSSQL be causing scheduler not starting? Also any idea why are error log files created, but empty?

On 16 November 2015 at 16:07, bahram salim <salim.bahram@hotmail.fr> wrote:

Hello,

try otrs.Scheduler.pl -a start -f

Date: Mon, 16 Nov 2015 15:12:17 +0100
From: branislav.brna@gmail.com
To: otrs@otrs.org
Subject: [otrs] OTRS 4, unable to start scheduler

Hello,
I just freshly installed OTRS4 for client on Centos 6.5 with MSSQL. I managed to get database connection working, but for some reason that I cant figure out I am unable to get Scheduler running. I can start Cron fine, but when I try to run otrs.Scheduler.pl -a start and then otrs.Scheduler.pl -a status I am still getting Not running! I also found multiple error logs in /var/log/ folder with name SchedulerERR, but all log files are empty. Any idea what might be causing this behavior?

Branislav

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs