On Jan 18, 2012, at 6:34 AM, Dave Page wrote:
>> Realized this when *neither* step ran last night. That certainly feels like
>> a bug to me: if I have the “End” field blank (NULL), it should remain blank
>> unless I set it.
>
> Agreed - I've committed a fix for this.
>
>>> In any event, I woul
On Jan 17, 2012, at 9:17 AM, Dave Page wrote:
>> It’s the standard schema, I think. Attached.
>
> I really wanted the data in it :-)
Oh, you didn’t say that. Will send privately in a mo.
David
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your s
On Jan 17, 2012, at 2:47 AM, Dave Page wrote:
> Can you get me a dump of the pgagent schema please?
It’s the standard schema, I think. Attached.
Best,
David
pgagent.sql
Description: Binary data
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to y
On Jan 16, 2012, at 9:05 AM, David E. Wheeler wrote:
> postgres=# select * from pgagent.pga_jobsteplog where jslid = 284;
> -[ RECORD 1 ]--
> jslid | 284
> jsljlgid| 211
> jsljstid| 1
> jslstatus | s
> jslresult | 0
> jslsta
On Jan 16, 2012, at 7:45 AM, Dave Page wrote:
> Depends on what the first step is doing. You have On Error set to Fail, which
> will cause subsequent steps to be skipped if an error is detected. What do
> you see in the job step log for the first step?
Success:
postgres=# select * from pgage
On Jan 3, 2012, at 9:50 AM, Guillaume Lelarge wrote:
>> Yeah, I’m a committer on check_postgres.pl, so the other check_postgres.pl
>> folks think it’s not a good place for it for some reason I can’t imagine
>> right now, you can expect that.
>>
>
> Oh, you too? funny :)
>
> Anyway, I don't re
On Jan 12, 2012, at 2:59 AM, Dave Page wrote:
> OK, so to make things a little easier, I wrapped up and uploaded a
> 3.2.0 tarball. The only changes from what you've seen in GIT are
> copyright notice updates.
Great, thank you. Now just have to set up a cron job to email Devrim once a day
to ask
On Jan 11, 2012, at 8:54 AM, David E. Wheeler wrote:
> Maybe I can install the Git build on the production box that’s having the
> problems and squeeze in a few tests between hourly runs of production
> code…I’ll try to do that today.
Done. Here's what I got with the RPM
On Jan 11, 2012, at 12:17 AM, Dave Page wrote:
> We haven't released a new version since then. I'm somewhat mystified
> about the lack of log data though - that's just plain odd. I assume
> it's not dumping it to stdout (which should only happen if a logfile
> isn't specified - which you seem to h
On Dec 28, 2011, at 2:08 PM, David E. Wheeler wrote:
>> OK, well I won't try to get you debugging wxWidgets code in GDB as
>> that's just painful, so please build from source having applied the
>> attached patch and then test your jobs with the log level set to DEBUG
On Jan 3, 2012, at 9:37 AM, Guillaume Lelarge wrote:
> I don't know of any, but if you do write one, please, submit it to
> check_postgres.pl.
Yeah, I’m a committer on check_postgres.pl, so the other check_postgres.pl
folks think it’s not a good place for it for some reason I can’t imagine right
pgAdmins,
Anyone written a Nagios plugin to report pgAgent failures? If not, I expect
I’ll be writing one, or perhaps submitting one to check_postgres.pl.
Thanks,
David
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.
On Jan 3, 2012, at 1:07 AM, Dave Page wrote:
>> Which is great. However, the /var/log/pgagent_91.log file is still empty.
>> Should I take that to mean that job output is not logged there, but only
>> errors from pgagent itself?
>
> Yes, it's really just a debug log.
Gotcha, thank you.
David
On Dec 20, 2011, at 6:00 PM, David E. Wheeler wrote:
>> Oh, OK. We use popen() to execute the task on *nix, and that only
>> reads STDOUT, so you should handle redirection in your script. I did
>> spend some time look at this a few years back as I recall, and didn't
>>
On Dec 23, 2011, at 9:33 AM, Dave Page wrote:
> OK, well I won't try to get you debugging wxWidgets code in GDB as
> that's just painful, so please build from source having applied the
> attached patch and then test your jobs with the log level set to DEBUG
> and capture the output so we can compa
On Dec 23, 2011, at 9:19 AM, Dave Page wrote:
> Everything looks fine. Care to try some debugging?
Sure. Tell me what to do.
David
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
On Dec 23, 2011, at 2:25 AM, Dave Page wrote:
> Hmm, that looks like it should work. I've just run some tests here,
> and can't find anything wrong. Successes are reported as such, and
> non-zero return values are reported as whatever the "on error" setting
> says they should be. Subsequent steps
On Dec 22, 2011, at 1:44 AM, Dave Page wrote:
> Which makes me think that either `rc`is not what gets put into jsresult, or
> that `steps->GetString(wxT("jstonerror"))` is returning "s", too. Or that I’m
> completely misunderstanding something, of course. :-)
>
> What's in pgagent.pga_jobstep w
On Dec 21, 2011, at 1:57 AM, Dave Page wrote:Thanks. The logic used to determine the success or failure of a stepis pretty simple: if (rc == 0) stepstatus = wxT("s"); else stepstatus = steps->GetString(wxT("jstonerror"));Which
On Dec 21, 2011, at 1:50 AM, Dave Page wrote:
>> Oh, good news, other platforms can’t be too far behind, right?
>
> I think you misread. As far as I know, it's *only* Mac OS X which
> isn't supported by wxWidgets in 64 bit builds. Windows, Linux, Solaris
> and HP-UX at least are all supported.
O
On Dec 20, 2011, at 12:12 AM, Dave Page wrote:
>> Would be handy for such output to appear somewhere in the job history…
>
> Oh, OK. We use popen() to execute the task on *nix, and that only
> reads STDOUT, so you should handle redirection in your script. I did
> spend some time look at this a fe
On Dec 20, 2011, at 12:14 AM, Dave Page wrote:
>> postgres=# select * from pgagent.pga_jobsteplog where jslresult <> 0;
>
> Can you show me that without the where clause please? If there's too
> much data, please filter by date to exclude lines that aren't on your
> original screenshot.
postgres
On Dec 19, 2011, at 1:52 AM, Dave Page wrote:
>> FYI, I have "On error" set to "Fail".
>
> What's actually in pgagent.pga_jobsteplog?
postgres=# select * from pgagent.pga_jobsteplog where jslresult <> 0;
jslid | jsljlgid | jsljstid | jslstatus | jslresult | jslstart
| js
On Dec 19, 2011, at 1:51 AM, Dave Page wrote:
> All of the internal logging goes to the file if specified, or stdout,
> with the exception of a couple of serious errors, like "failed to open
> the logfile". wxWidgets might be writing some of it's own logging
> output to stderr though I guess.
No,
On Dec 16, 2011, at 10:22 AM, David E. Wheeler wrote:
>
> Oh, one other question: If the exit code of an executed batch script is not
> 0, why is its status "Successful" in pgAdmin? Screen shot:
FYI, I have "On error" set to "Fail".
David
--
Sent vi
On Dec 16, 2011, at 9:47 AM, David E. Wheeler wrote:I have a few questions about pgAgent, which I’ve just set up and am using at work.Oh, one other question: If the exit code of an executed batch script is not 0, why is its status "Successful" in pgAdmin? Screen shot:Thanks,David
Howdy,
I have a few questions about pgAgent, which I’ve just set up and am using at
work.
• I’m using -s to send errors to a log file. However, it only seems to log
STDOUT, not STDERR. Is that right? Do I need to modify my batch scripts to 2>&1
to get STDERR output?
• When scheduling executio
27 matches
Mail list logo
