pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeremy Ashcraft <jashcraft@edgate.com>
To: pgsql-admin@postgresql.org
Subject: Re: strange hung processes
Date: Thu, 02 Feb 2006 12:22:59 -0800
Message-ID: <43E26A23.1080208@edgate.com> (raw)
In-Reply-To: <D1D2D51E3BE3FC4E98598248901F75940328DAFF@ausmail2k4.aus.pervasive.com>
References: <D1D2D51E3BE3FC4E98598248901F75940328DAFF@ausmail2k4.aus.pervasive.com>

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
(waiting on IO ?).


codd opt # lsof -p 13263
COMMAND     PID     USER   FD   TYPE DEVICE    SIZE     NODE NAME
postmaste 13263 postgres  cwd    DIR   8,17     464     4030
/app1/user/postgres
postmaste 13263 postgres  rtd    DIR    8,3     488        2 /
postmaste 13263 postgres  txt    REG   8,17 2552859     5012
/app1/pg/7.4.9/bin/postgres
postmaste 13263 postgres  mem    REG    0,0                0 [heap]
(stat: No such file or directory)
postmaste 13263 postgres  DEL    REG    0,7                0 /SYSV0052e2c1
postmaste 13263 postgres  mem    REG    8,3   35428     5729
/lib/libnss_files-2.3.4.so
postmaste 13263 postgres  mem    REG    8,5   18852     6895
/usr/lib/libgpm.so.1.19.0
postmaste 13263 postgres  mem    REG    8,3  266284     5965
/lib/libncurses.so.5.4
postmaste 13263 postgres  mem    REG    8,3 1167808     5977
/lib/libc-2.3.4.so
postmaste 13263 postgres  mem    REG    8,3  151896     5755
/lib/libm-2.3.4.so
postmaste 13263 postgres  mem    REG    8,3   10620     5987
/lib/libdl-2.3.4.so
postmaste 13263 postgres  mem    REG    8,3   75848     6003
/lib/libnsl-2.3.4.so
postmaste 13263 postgres  mem    REG    8,3   60884     5998
/lib/libresolv-2.3.4.so
postmaste 13263 postgres  mem    REG    8,3   18424     6006
/lib/libcrypt-2.3.4.so
postmaste 13263 postgres  mem    REG    8,3  173996     6007
/lib/libreadline.so.4.3
postmaste 13263 postgres  mem    REG    8,3   63204     5976
/lib/libz.so.1.2.2
postmaste 13263 postgres  mem    REG    8,3   95392     5915
/lib/ld-2.3.4.so
postmaste 13263 postgres    0r   CHR    1,3             2767 /dev/null
postmaste 13263 postgres    1w   REG    8,7 7513385     3649
/var/log/pg/ruby.log.bak1
postmaste 13263 postgres    2w   REG    8,7 7513385     3649
/var/log/pg/ruby.log.bak1
postmaste 13263 postgres    5u  sock    0,4         11790654 can't
identify protocol




view thread (6+ messages)  latest in thread

Message-ID: <43E26A23.1080208@edgate.com>
Permalink:  ../43E26A23.1080208@edgate.com/
Also on:    postgresql.org/message-id/43E26A23.1080208@edgate.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jashcraft@edgate.com
  Subject: Re: strange hung processes
  In-Reply-To: <43E26A23.1080208@edgate.com>
  References: <D1D2D51E3BE3FC4E98598248901F75940328DAFF@ausmail2k4.aus.pervasive.com> <43E26A23.1080208@edgate.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox