Triggers automatically went to error state in quartz

[yogesh nikhar]

I am using a quartz version: '2.1.4' with the Postgres database. 

When I working with local database jobs trigger working fine,

 but when I went for remote database server triggers are automatically moved to Error state and I did not get any log for that. 

So this cause I am not able to troubleshoot. When these triggers are moved to error state it was not firing again. 

Anyone having an idea why its happen...

[Marko Lahma]

This is quite impossible to troubleshoot with this information. You should enable logging and see what happens under the hood. And please upgrade to newer version, there is no version 2.1.4 in existence. The latest usually has the least known problems.

-Marko

--
You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quartznet+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quartznet/6e9af40d-9cd9-4e91-aa1b-41936a76a926n%40googlegroups.com.