/var/log/messages doesn't really show anything (see below). Just my repeated manual restarts because of the daemon crashing. Yes, all three crash each time, I can't figure out why rsyslog and postfix die because of a database issue. I'm not familiar with the oom killer. I'll google around. Do you have any advice on how to test that as a cause?
May 20 09:59:28 kernel: rklogd 2.0.6, log source = /proc/kmsg started.
May 20 10:22:51 rsyslogd: [origin software="rsyslogd" swVersion="2.0.6" x-pid="18289" x-info="
http://www.rsyslog.com"][x-configInfo udpReception="No" udpPort="514" tcpReception="No" tcpPort="0"] restart
May 20 10:22:51 kernel: rklogd 2.0.6, log source = /proc/kmsg started.
May 20 11:26:26 rsyslogd: [origin software="rsyslogd" swVersion="2.0.6" x-pid="17507" x-info="
http://www.rsyslog.com"][x-configInfo udpReception="No" udpPort="514" tcpReception="No" tcpPort="0"] restart
On Thu, May 20, 2010 at 3:21 PM, Joshua D. Drake
<jd@commandprompt.com> wrote:
On Thu, 2010-05-20 at 15:10 -0500, Spencer Anderson wrote:
> I have a Ruby on Rails web site that is running on a CentOS 5 server
> using Apache 2 with Passenger and PostgreSQL 8.4. Over the past two
> weeks I am seeing my PostgreSQL daemon, postfix, and rsyslog daemons
> all die at the same time, this happens at least 5 times per day at
> random times. Apache however, does not die.
All three? What does /var/log/messages or /var/log/syslog say?
I wonder if the oom killer is acting up.
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
--
Spencer Anderson
spencer@minneapp.com(424) 901-1363
