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: postgre
sn_master 10.1.1.3 authentication
postgres 13217 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13218 5142 0 Jan09 ? 00:00:00 postgres: postgre edgate
10.1.1.1 authentication
postgres 13219 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13220 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13221 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13222 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
postgres 13223 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13224 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
postgres 13225 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
postgres 13226 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13227 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13228 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
postgres 13229 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
Jeremy Ashcraft 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
never finished. We then kill -9 the postmaster, which caused it to
die, but these child procs remain, even after a clean restart. Our
next step is to reboot the box, but before we do, I'm just curious
anyone else has seen this, why this happened, and if anyone know ways
to prevent this from happening again.....
thanks
--
jeremy ashcraft
operations/development
EDucation GATEways
jashcraft@xxxxxxxxxx
