On Fri, Sep 23, 2011 at 2:45 PM, Burgholzer, Robert (DEQ) <robert.burghol...@deq.virginia.gov> wrote: > Scott - thanks, in pouring over the logs, I have not found anything certain, > but have turned up a ton of mesages about my sysadmins se-linux security and > php/pg (don't know if they're my app or script kiddies...). I will keep > looking for things pertianing to these crashes. The message relative to php > and pgsql: > Sep 20 11:37:32 deq1 setroubleshoot: SELinux is preventing php > (httpd_sys_script_t) "setopt" to <Unknown> (httpd_sys_script_t). For > complete SELinux messages. run sealert -l > 199268c4-b84d-4a33-a073-29bd4461f875
Take a peek here: http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD If you can get a trace I'm sure Joe can figure out what's making it croak. Not that I speak for Joe, I just have faith in him. :) -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
