Dear peoples,

We had an oddness today with one of of postgres servers (Dell 2 CPU box running 
linux) and postgres 7.4. The server was under heavy load (50+ for a 1 minutes 
spike; about 20 for the 15 minute average) with about 250 connections (we still 
don't understand the heavy load itself).

Looking in the logs I see:
2004-11-13 13:30:28 LOG:  unexpected EOF on client connection
2004-11-13 13:30:40 LOG:  unexpected EOF on client connection
2004-11-13 13:38:28 LOG:  could not send data to client: Broken pipe
2004-11-13 13:42:15 LOG:  server process (PID 30272) was terminated by signal 9
2004-11-13 13:42:16 LOG:  terminating any other active server processes
2004-11-13 13:42:16 WARNING:  terminating connection because of crash of another
 server process

The EOFs are almost certainly Proxool closing connections from the client to 
the database.

The sysad who was on call today swears he didn't send a kill signal (or any 
signal at all) -- suddenly the load dropped off and the server was down. It has 
restarted normally and shows no signs of being worse for the wear (this is 
really a read-only db so data corruption chances are minimal, I think).

Just to rule out any internal chances, is there any way this shutdown could 
have been triggered from within postgres itself ? Can anyone construct any 
scenarios in which Linux, postgres or proxool could have done this without 
human intervention ?

I have looked through manuals and some FAQs and newsgroup discussions and my 
gut feeling is that this can't be from postgres, but I thought I'd ask in the 
chance that I am, as is often the case, Unclear On The Concept.

Thanks for any illumination,

Greg Williamson
DBA
GlobeXplorer LLC 

ps if this is not the right list please let know what might be an appropriate 
one. gracias!

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faqs/FAQ.html

Reply via email to