Joe, Thanks - I will try to check into this - however, we have done some tuning on the memory over the last 2 years and gotten it such that it is seldom if every having to dip into its swap too substantially -- according to "top", we remain under 1% swap usage during most times. Generally speaking, I run 3-5 of these large PHP processes simultaneously with no issue, however, when I issue even a "median" function call, after several calls (no consistent pattern that I can discern), the backend crashes.
If this were the OOM killer - any way I would diagnose it? regards, r.b. -----Original Message----- From: Joe Conway [mailto:[email protected]] Sent: Fri 9/23/2011 3:23 PM To: Burgholzer, Robert (DEQ) Cc: [email protected] Subject: Re: [ADMIN] diagnosing a db crash - server exit code 2 On 09/23/2011 12:02 PM, Burgholzer, Robert (DEQ) wrote: > I am trying to get my head around why I keep getting crashes to my PG > 8.3.7 database on CentOS - Linux version 2.6.18-164.el5. There are 3 > slightly different (I think) circumstances leading to a crash of the > database, all related in some way to long running PHP scripts with > intensive activity on PG connections. > #1 - execution of an R call via pLR (sometimes this may crash it all by > itself) > #2 - execution of a postGIS query (possible) > #3 - random occurences, all related to the same long running PHP scripts > > I have read that perhaps hardware and/or system settings may cause > this. I believe the system is running i9 processors, that may be set > into some sort of virtual multi-threading mode. Thanks for any insight > you all can give in tracking this down. Are you maybe getting bitten by the OOM killer? http://www.postgresql.org/docs/8.3/interactive/kernel-resources.html#AEN22246 Joe -- Joe Conway credativ LLC: http://www.credativ.us Linux, PostgreSQL, and general Open Source Training, Service, Consulting, & 24x7 Support
