Stefan Kaltenbrunner writes:
> On 06/22/2012 11:47 PM, Tom Lane wrote:
>> Could you gdb each of these processes and get a stack trace?
[ unsurprising stack traces ]
OK, so they're waiting exactly where they should be.
So what we know is that the shutdown failure is caused by the child
processes
On 06/22/2012 11:47 PM, Tom Lane wrote:
> Stefan Kaltenbrunner writes:
PID PENDING CAUGHT IGNORED BLOCKED COMMAND
12480 20004004 34084005 c942b002 fffefeff postgres: writer process
9841 20004004 34084007 c942b000 fffefeff postgres: wal writer process
>
>> this seems to be SIGU
On 06/22/2012 11:53 PM, Tom Lane wrote:
> oh, and just for comparison's sake, what do the postmaster's signal
> masks look like?
# ps -o pid,sig,sigcatch,sigignore,sigmask,command -p 18020
PID PENDING CAUGHT IGNORED BLOCKED COMMAND
180200 74084007 8972b0000
/home/pgbuild/
On Fri, Jun 22, 2012 at 2:57 PM, Andres Freund wrote:
> On Friday, June 22, 2012 08:51:55 PM Robert Haas wrote:
>> On Fri, Jun 22, 2012 at 2:16 PM, Stefan Kaltenbrunner
>>
>> wrote:
>> > sending a manual kill -15 to either of them does not seem to make them
>> > exit either...
>> >
>> > I did som
oh, and just for comparison's sake, what do the postmaster's signal
masks look like?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Stefan Kaltenbrunner writes:
>>> PID PENDING CAUGHT IGNORED BLOCKED COMMAND
>>> 12480 20004004 34084005 c942b002 fffefeff postgres: writer process
>>> 9841 20004004 34084007 c942b000 fffefeff postgres: wal writer process
> this seems to be SIGUSR1,SIGTERM and SIGQUIT
OK, I looked up OpenBSD
On 06/22/2012 11:02 PM, Tom Lane wrote:
> Stefan Kaltenbrunner writes:
>> On 06/22/2012 09:39 PM, Tom Lane wrote:
>>> (Hey Stefan, is there a way on BSD to check a process's signals-blocked
>>> state from outside? If so, next time this happens you should try to
>>> determine the children's signal
Stefan Kaltenbrunner writes:
> On 06/22/2012 09:39 PM, Tom Lane wrote:
>> (Hey Stefan, is there a way on BSD to check a process's signals-blocked
>> state from outside? If so, next time this happens you should try to
>> determine the children's signal state.)
> with help from RhodiumToad on IRC:
On 06/22/2012 09:39 PM, Tom Lane wrote:
> Andres Freund writes:
>> On Friday, June 22, 2012 08:51:55 PM Robert Haas wrote:
>>> I remarked to Stefan that the symptoms seem consistent with the idea
>>> that the children have signals blocked. But I don't know how that
>>> could happen.
>
>> You can
Andres Freund writes:
> On Friday, June 22, 2012 08:51:55 PM Robert Haas wrote:
>> I remarked to Stefan that the symptoms seem consistent with the idea
>> that the children have signals blocked. But I don't know how that
>> could happen.
> You cannot block sigkill.
sigterm is at issue, not sigk
Stefan Kaltenbrunner writes:
> On 06/22/2012 08:34 PM, Tom Lane wrote:
>> Still, panther is NetBSD so there may be some general BSD flavor to
>> whatever's going on here.
> yeah the threading reference was mostly because all backtraces contain
> references to threading libs and because the thread
On 06/22/2012 08:34 PM, Tom Lane wrote:
> Stefan Kaltenbrunner writes:
>> It has now happened at least twice that builds on spponbill started to
>> fail after it failed during ECPGcheck:
>> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2012-06-19%2023%3A00%3A04
>> the first failur
On Friday, June 22, 2012 08:51:55 PM Robert Haas wrote:
> On Fri, Jun 22, 2012 at 2:16 PM, Stefan Kaltenbrunner
>
> wrote:
> > sending a manual kill -15 to either of them does not seem to make them
> > exit either...
> >
> > I did some further investiagations with robert on IM but I don't think
On Fri, Jun 22, 2012 at 2:16 PM, Stefan Kaltenbrunner
wrote:
> sending a manual kill -15 to either of them does not seem to make them
> exit either...
>
> I did some further investiagations with robert on IM but I don't think
> he has any further ideas other than that I have a weird OS :)
> It see
On 06/22/2012 02:34 PM, Tom Lane wrote:
Stefan Kaltenbrunner writes:
It has now happened at least twice that builds on spponbill started to
fail after it failed during ECPGcheck:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2012-06-19%2023%3A00%3A04
the first failure was:
ht
Stefan Kaltenbrunner writes:
> It has now happened at least twice that builds on spponbill started to
> fail after it failed during ECPGcheck:
> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2012-06-19%2023%3A00%3A04
> the first failure was:
> http://www.pgbuildfarm.org/cgi-bin/sh
It has now happened at least twice that builds on spponbill started to
fail after it failed during ECPGcheck:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2012-06-19%2023%3A00%3A04
the first failure was:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2012-05-24%
17 matches
Mail list logo
