Re: [otrs] Unlock-Cronjob

Hello!

...

...

[...] PS: Use $OTRS_HOME/bin/Cron.sh {start|stop|restart} (as OTRS user) to start/stop this cronjobs from var/cron/*. The SuSE and Red Hat rc-script is doing this automatically.

I did that, but the probelm wasn't solved. I fixed a Syntax Error in my additions and the problem wasn't solved.

server:/opt/OpenTRS$ bin/UnlockTickets.pl --timeout

returns

UnlockTickets.pl - unlock tickets Copyright (c) 2002 Martin Edenhofer Unlock old tickets: (in cleanup) Can't call method "disconnect" on an undefined value at /opt/OpenTRS/bin/..//Kernel/System/DB.pm line 93 during global destruction.

Update Kernel/System/DB.pm ( http://otrs.org/cgi-bin/cvsweb.cgi/~checkout~/otrs/Kernel/System/DB.pm?rev=1... ) and this message should go.

Jup! Thanks for the quick help! The problem was cleared after updating and the tickets were unlocked.

...

and no tickets are unlocked. Perhaps I've got a problem escaping the @ in the history-entry but i don't see this blocking the whole unlock process.

[...] HistoryComment => "Sent lock timeout notification to '$UserData{UserEmail}','info\@domainname.com'.", [...]

This looks fine.

And didn't cause the problem :-)

...

Is there any other way of debugging? Could i send the return of cronjobs call to a file? Perhaps by replacing

...

...

/dev/null

Is there a way to check if the crownjobs are run properly?

[How to debugg cronjobs]

Hey thanks for the help. But your Kernel/System/db.pm update already fixed it. Now i've got my Unlock-Notifications & A notification, if a new ticket is assigned to a subscribed Queue. Thanks again! Hannes Lau