Ok, I've guessed out the problem, which indeed was a misunderstanding in the way OTRS manages the "pending" state. I thought that the ticket's state would have been changed as soon as the timeout was reached, but it is instead changed by the PendingJobs.pl cron job, which by default runs every 2 hours.
My fault :P 2010/4/7 Marco Vannini <marco.vann...@gmail.com> > > >> >>> Based on the otrs file in /etc/init.d and in /etc/sysconfig for redhats >>> like system it is used to check if required services are running and to >>> populate cron table >>> >> I see. But in my case, the service won't start up because my DB is on >> another server and the script checks for the pid on the local machine :/ >> > > So you could set > OTRS_DB_RUNNING=0 > in /etc/sysconfig/otrs > > For the rest it is quite strange if it was not a successful start of the > service or if mails were not fetched by a fetchmail process or similar > (manual cron compilation for the postamaster.pl ? ) , but this is not a > problem... if something goes well why investigate :D > > > --------------------------------------------------------------------- > 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 > > NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! > http://www.otrs.com/en/support/enterprise-subscription/ > -- Claudio Tassini
--------------------------------------------------------------------- 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 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/
