| From: | Sean Shanny <shannyconsulting(at)earthlink(dot)net> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Found this in the server log on MAC OSX |
| Date: | 2004-02-24 00:57:28 |
| Message-ID: | 403AA178.50608@earthlink.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ed,
If I continue to see the behavior I will turn the logging stuff on as
you suggested. The machine uptime is show 3+ days so it did not reboot.
Thanks.
--sean
Ed L. wrote:
>On Monday February 23 2004 8:43, Sean Shanny wrote:
>
>
>>I restarted postgres this morning to make a configuration file change
>>take effect and when I looked at the serverlog to make sure things were
>>ok I found the prior shutdown message(*in bold*). This shut down was
>>not initiated by me or anyone else who has access to the machine. Any
>>ideas as to what might be causing this?
>>
>>LOG: unexpected EOF on client connection
>>*LOG: received smart shutdown request *
>>*FATAL: the database system is shutting down
>>FATAL: the database system is shutting down
>>LOG: server process (PID 4691) was terminated by signal 9
>>LOG: terminating any other active server processes
>>LOG: statistics collector process (PID 361) was terminated by signal 9
>>
>>
>
>Looks like it got a SIGTERM, which is what you might get if someone shutdown
>OSX (osx pls gurus correct me). Maybe your machine rebooted? Logging
>pids and timestamps might help tell the tale next time ...
>
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seamus Thomas Carroll | 2004-02-24 01:37:39 | Create Schema functionality question |
| Previous Message | Ed L. | 2004-02-24 00:36:37 | Re: Found this in the server log on MAC OSX |