PgAgent Jobs randomly failing to start

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

PgAgent Jobs randomly failing to start

Piers Lillystone
Hello,

We were hoping someone could help us with a PgAgent job issue we've been having. We're using PgAgent to schedule batch scripts (that run a compiled matlab exe file) on a Windows 2019 server and are having issues making the jobs reliably start. Basically the jobs either start perfectly fine or fail within a few microseconds (see attached images of the job statistics and step statistics). When a job fails to run I have not been able to find any error log or console output.

We're currently working around this by scheduling several consecutive times the job should run at (e.g. 6:00am, 6:05am, etc) but even this schedule fails on occasion and is obviously not a great solution! I've also tried to force the batch script to output a log file, but sadly nothing is output when the job fails.

Thanks for any help you can provide
Piers Lillystone

Step_schedule_results.PNG (196K) Download Attachment
Job_schedule_results.PNG (141K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: PgAgent Jobs randomly failing to start

Neel Patel
Hi,

Can you give us below information.
  • Have you seen any error in the respective pgagent log table or log file ?
  • Can you share the sample test with us ?
Thanks,
Neel Patel

On Mon, Dec 7, 2020 at 7:03 PM Piers Lillystone <[hidden email]> wrote:
Hello,

We were hoping someone could help us with a PgAgent job issue we've been having. We're using PgAgent to schedule batch scripts (that run a compiled matlab exe file) on a Windows 2019 server and are having issues making the jobs reliably start. Basically the jobs either start perfectly fine or fail within a few microseconds (see attached images of the job statistics and step statistics). When a job fails to run I have not been able to find any error log or console output.

We're currently working around this by scheduling several consecutive times the job should run at (e.g. 6:00am, 6:05am, etc) but even this schedule fails on occasion and is obviously not a great solution! I've also tried to force the batch script to output a log file, but sadly nothing is output when the job fails.

Thanks for any help you can provide
Piers Lillystone