From: | "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com> |
---|---|
To: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | too many Fatal Error 1: shutdown messages |
Date: | 2003-01-08 16:24:57 |
Message-ID: | 73309C2FDD95D11192E60008C7B1D5BB04C74489@snt452.corp.bcbsm.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Running PostgreSQL 7.2.1 on RedHat Linux 7.2
Over the past few days, the database has been acting
strange and have been trying to shutdown. While my
postmaster is running debug level 2, when I check my
logs to see why, I get :
[snip from log]
Jan 8 09:54:16 test_srv postgres[19069]: [12354] FATAL 1:
The database system is shutting down
[/snip from log]
There doesn't seem to be any rhyme or reason for it;
yesterday, I thought it was one of the drives having
problems and the kernel gave an error.
Last night, I thought it was because of too many
users logging in (it had reached it's max and gave that
message).
Both seem to be red herrings.
I'm going to expand on the debug level to see the whys and
hows of some of these things, but, I'm running out of ideas.
Any suggestions?
-X
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Mascari | 2003-01-08 16:36:07 | Re: tracking down breakins? |
Previous Message | Johnson, Shaunn | 2003-01-08 16:10:18 | tracking down breakins? |