Re: diagnosing a db crash - server exit code 2

Thanks Scott - I'm on the MFer. That is, I WILL be on it next Monday when I have time to sit down, gin up a test case and break this sucker. :)

Stay tuned, and thanks bunches,

r.b.

-----Original Message-----
From: Scott Marlowe [mailto:scott(dot)marlowe(at)gmail(dot)com]
Sent: Fri 9/23/2011 4:51 PM
To: Burgholzer, Robert (DEQ)
Cc: Joe Conway; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] diagnosing a db crash - server exit code 2

On Fri, Sep 23, 2011 at 2:45 PM, Burgholzer, Robert (DEQ)
<Robert(dot)Burgholzer(at)deq(dot)virginia(dot)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. :)