| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Burgholzer, Robert (DEQ)" <Robert(dot)Burgholzer(at)deq(dot)virginia(dot)gov> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: diagnosing a db crash - server exit code 2 |
| Date: | 2011-09-23 20:51:35 |
| Message-ID: | CAOR=d=0FMarkOx8EbefrQ-Qc0P8mTWSOK=1S6irynm49Eyc_yw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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. :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Burgholzer, Robert (DEQ) | 2011-09-23 20:54:37 | Re: diagnosing a db crash - server exit code 2 |
| Previous Message | Burgholzer, Robert (DEQ) | 2011-09-23 20:45:56 | Re: diagnosing a db crash - server exit code 2 |