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
2012/1/11 David E. Wheeler :
>
> So either the changes in 2aec3bc473e583f8fa07e133bc8def60ff1c09fe or some
> other commit fixed the underlying problem, or something is wonky with the
> RPM. I can’t imagine what, though, because I build from Git exactly the same
> way as Devrim has things specifi
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 build running:
postgre
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
2012/1/10 David E. Wheeler :
>
> Finally got back to this. Naturally, the car works perfectly when it’s in the
> shop.
Of course - that's all part of the game :-)
> I installed the pgrpms version of pgAgent, which Devrim uploaded a few weeks
> ago.
>
> http://yum.pgrpms.org/9.1/redhat/rhel-5-i
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
>> and capture the output so w
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 Mon, Jan 2, 2012 at 7:04 PM, David E. Wheeler wrote:
> 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 yea
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
>> find a fix I was happy with.
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 Fri, Dec 23, 2011 at 5:24 PM, David E. Wheeler wrote:
> 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.
OK, well I won't try to get you debugging wxWidgets code in GDB as
that's just painful, so please build fr
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 Friday, December 23, 2011, David E. Wheeler
wrote:
> 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 th
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 Thu, Dec 22, 2011 at 5:44 PM, David E. Wheeler wrote:
> 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 misunderstandin
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 Wed, Dec 21, 2011 at 10:08 PM, David E. Wheeler wrote:
> On Dec 21, 2011, at 1:57 AM, Dave Page wrote:
>
> Thanks. The logic used to determine the success or failure of a step
> is pretty simple:
>
>if (rc == 0)
>stepstatus = wxT("s");
>el
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 Wed, Dec 21, 2011 at 2:02 AM, David E. Wheeler wrote:
> 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 exclu
On Wed, Dec 21, 2011 at 2:00 AM, David E. Wheeler wrote:
> 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 redir
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 Mon, Dec 19, 2011 at 5:54 PM, David E. Wheeler wrote:
> 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;
Can you show me that with
On Mon, Dec 19, 2011 at 5:50 PM, David E. Wheeler wrote:
> 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
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 Fri, Dec 16, 2011 at 6:27 PM, David E. Wheeler wrote:
> 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 "Fai
On Fri, Dec 16, 2011 at 5:47 PM, David E. Wheeler wrote:
> 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 ba
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 via pgadmin-support mailing list (pgadmin-su
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
32 matches
Mail list logo
