Jeremy Ashcraft <[EMAIL PROTECTED]> writes:
> in /proc
> codd 13262 # cat status {proc "filesystem"}
> Name: postmaster
> State: D (disk sleep)
> Because of the "D" state, it can't be killed as it is not interuptible
> (waiting on IO ?).
If the process is stuck in D state then it's not Po
If it's not sensitive information, what does this show?
>> lsof | grep 'pid of hung process'
>>
>From my systems guy:
in /proc
codd 13262 # cat status {proc "filesystem"}
Name: postmaster
State: D (disk sleep)
Because of the "D" state, it can't be killed as it is not interuptible
(w
Ben Kim wrote:
>> We're running 7.4.9 and have run into something strange.
>> A group of processes seem to have hung and cannot be killed. netstat
>> showed that there were no active TCP connections at the time.
>> Sending SIGTERM to the parent process caused PG to begin its
>> shutdown, but it n
>We're running 7.4.9 and have run into something strange.
>A group of processes seem to have hung and cannot be killed. netstat
>showed that there were no active TCP connections at the time. Sending
>SIGTERM to the parent process caused PG to begin its shutdown, but it
>never finished. We th
I forgot to include the process list:
postgres 13214 5142 0 Jan09 ?00:00:00 postgres: postgre edgate
10.1.1.3 authentication
postgres 13215 5142 0 Jan09 ?00:00:00 postgres: postgre edgate
10.1.1.1 authentication
postgres 13216 5142 0 Jan09 ?00:00:00 postgres: postg
We're running 7.4.9 and have run into something strange.
A group of processes seem to have hung and cannot be killed. netstat
showed that there were no active TCP connections at the time. Sending
SIGTERM to the parent process caused PG to begin its shutdown, but it
never finished. We then k
