Skip site navigation (1) Skip section navigation (2)

Re: PG 9.1 Windows 7 64-bit pgAdmin says all pgAgent jobs fail

From: Guy Rouillier <guyr(at)burntmail(dot)com>
To: pgadmin-support(at)postgresql(dot)org
Subject: Re: PG 9.1 Windows 7 64-bit pgAdmin says all pgAgent jobs fail
Date: 2012-03-06 09:51:57
Message-ID: 4F55DE3D.80307@burntmail.com (view raw or flat)
Thread:
Lists: pgadmin-support
On 3/5/2012 7:26 AM, Dave Page wrote:

>>>>> The step or the job shows as failed? What's the output from the step?
>>>>
>>>>
>>>>
>>>> Both the step and the job are shown as failed.  Thanks.
>>>
>>>
>>> And the step output?
>>
>>
>> I think you are referring to the "Output" column in the Statistics tab.
>>   That column is completely blank for all tests.
>
> Can you confirm from the server log (on the server on which the step
> runs), that the step does actually run or not?
>
> Assuming it does, try running pgAgent with the log level increased to
> WARNING to see if anything shows up there.

Ok, I finally figured this out.  The step does run; using the sample job 
I provided, the table is updated with the current date.  In my original 
post, I provided the output of a DEBUG run; that should have had at 
least as much detail as WARNING, yes?

At any rate, the problem was (drum roll...) I neglected to put a commit 
after my update statement in the job step SQL.  After doing so, the job 
and step are both successful.

So now the only thing odd is that the update actually *was* committed, 
even the job indicated it had failed.  I say this because the updated 
value persisted between reboots.

Thanks for persisting, Dave.

-- 
Guy Rouillier



In response to

pgadmin-support by date

Next:From: Colin BeckinghamDate: 2012-03-06 14:19:36
Subject: View create usage
Previous:From: Guillaume LelargeDate: 2012-03-05 21:32:59
Subject: Re: pgadmin 1.14.2, ERROR:column tgconstraint does not exist

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group