On Thu, Mar 26, 2009 at 2:23 AM, Bill Moran <wmoran@xxxxxxxxxxxxxxxxx> wrote:
That was most likely me (doing a /etc/init.d/postgresql restart. I thought I would restart it after changing the user name. Notice that the time on that is 02:41 GMT. The actual shutdown occured on 07:05 GMT some four hours later.
Does that make sense?
In response to Tim Uckun <timuckun@xxxxxxxxx>:
Not likely to cause the DB to restart ... at least not in any OS
> Today the database shut down unexpectedly. I have included the log file
> that shows the shutdown. Can anybody tell me why this happened and how I can
> make sure it doesn't happen again.
>
> The only thing I can think of that I did was to specify a password for the
> postgres user in the operating system.
configuration that I'm aware of. However, you don't mention what
OS you're running ... that might be important.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Here is the log file. Very strange.
>
> 2009-03-25 00:02:01 GMT LOG: incomplete startup packet
> 2009-03-25 00:30:05 GMT LOG: could not receive data from client: Connection
> timed out
> 2009-03-25 00:30:05 GMT LOG: unexpected EOF on client connection
> 2009-03-25 00:30:05 GMT LOG: could not receive data from client: Connection
> timed out
> 2009-03-25 00:30:05 GMT LOG: unexpected EOF on client connection
> 2009-03-25 00:32:15 GMT LOG: could not receive data from client: Connection
> timed out
> 2009-03-25 00:32:15 GMT LOG: unexpected EOF on client connection
> 2009-03-25 02:41:57 GMT LOG: incomplete startup packet
> 2009-03-25 02:41:57 GMT LOG: received smart shutdown request
Sure looks like someone intentionally shut the database down.
That was most likely me (doing a /etc/init.d/postgresql restart. I thought I would restart it after changing the user name. Notice that the time on that is 02:41 GMT. The actual shutdown occured on 07:05 GMT some four hours later.
Does that make sense?
