Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: rogue process maxing cpu and unresponsive to signals
- From: Jon Jensen <jon(at)jenseng(dot)com>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: "Decibel!" <decibel(at)decibel(dot)org>, pgsql-novice(at)postgresql(dot)org
- Subject: Re: rogue process maxing cpu and unresponsive to signals
- Date: Thu, 16 Aug 2007 15:27:38 -0600
If my theory is right that it's stuck in a kernel call, then *maybe* "strace -p pid" would show the suspended call. Or maybe not. Probably worth trying if you haven't rebooted yet.
Tom and Jim, Yeah, no luck on the strace either... ended up having to kill -9 it, so we may never know the root cause. Thanks for the help/suggestions though. Jon
- References:
- rogue process maxing cpu and unresponsive to signals
- From: Jon Jensen
- Re: rogue process maxing cpu and unresponsive to signals
- From: Decibel!
- Re: rogue process maxing cpu and unresponsive to signals
- From: Jon Jensen
- Re: rogue process maxing cpu and unresponsive to signals
- From: Tom Lane
- rogue process maxing cpu and unresponsive to signals
- Prev by Date: Fwd: How to create a spatial index on point data.
- Next by Date: large duplicated files
- Previous by thread: Re: rogue process maxing cpu and unresponsive to signals
- Next by thread: Re: rogue process maxing cpu and unresponsive to signals
- Indexes: