Re: Database server restarting

On Mon, 5 May 2003, shoaib wrote:

> Thanks a lot for your prompt reply.
> We are rebooting the server for cleaning up the buffers of the
> system.Before rebooting I will shutdown database server.Can you provide
> any futher clue why suddenly at 4.17 aM it restarted.Our preventive
> maintenance run at 1 AM.
> And another process of Reading data from some flat files and updating it
> to database ended at 4.13 AM on the same day.

Hmmm...I assumed the 4:17 was from the scheduled reboot. It's a more difficult
issue if that was from the postmaster exiting by itself. Did the data loading
process end normally? It's a good few minutes but in the scheme of things 4
minutes for the postmaster to be restarted automatically may be isn't such a
long time.

I'm still drawn to this daily reboot process though. You do it to clean up the
system buffers. Why? Is there perhaps some instability in the system if the
system uses lots of memory? What is the hardware/os? Have you run hardware
diagnostics? If it's Intel/PC like there is a program called memtest86 which is
good at checking the memory. Be warned though, if you need that 24 hour up time
to run memtest86 properly you're going to lose a good few hours.

> -----Original Message-----
> From: Nigel J. Andrews [mailto:nandrews(at)investsystems(dot)co(dot)uk]
> Sent: Monday, May 05, 2003 7:08 PM
> To: shoaib
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Database server restarting
>
> On Mon, 5 May 2003, shoaib wrote:
>
> > Hello Everybody,
> >
> > We are using postgressql 7.2.2 . our system running is 24 hours day it
> a
> > preventive reboot once a day.
>
> Odd concept. What is this reboot preventing?
>
>
> > some time I am getting this error and after
> > it the sytem hang .Can any body help in this.
> >
> > DEBUG: pq_recvbuf: unexpected EOF on client connection
> > DEBUG: pq_recvbuf: unexpected EOF on client connection
> > DEBUG: pq_recvbuf: unexpected EOF on client connection
> > DEBUG: pq_recvbuf: unexpected EOF on client connection
> > DEBUG: database system was interrupted at 2003-05-03 04:17:19 SGT
> > DEBUG: checkpoint record is at 3/85EA18B0
> > DEBUG: redo record is at 3/85EA18B0; undo record is at 0/0; shutdown
> > FALSE
> > DEBUG: next transaction id: 4111285; next oid: 7557242
> > DEBUG: database system was not properly shut down; automatic recovery
> > in progress
>
> It looks like your preventative daily reboot is not preventing the
> problems it
> is causing. It is possible that the postmaster is not being shutdown
> properly
> because, for example, there is a client still connected and the shutdown
> script
> isn't forcing a fast shutdown. See pg_ctl manpage for infomation on the
> switches.
>
> As for worrying about the messages, there's no real error message in
> there,
> aside from the 'EOF on client connection', just the normal messages on
> start up
> from a bad shutdown. If you're worried, I would look at solving whatever
> the
> answer to the daily reboot question shows is the problem.
>
>
> > DEBUG: ReadRecord: record with zero length at 3/85EA18F0
> > DEBUG: redo is not required
> > DEBUG: recycled transaction log file 0000000300000083
> > DEBUG: recycled transaction log file 0000000300000084
> > DEBUG: database system is ready
> > DEBUG: pq_recvbuf: unexpected EOF on client connection
> >
> >
> > Regards
> >
> > Shoaib
> >
> >
>
>

--
Nigel J. Andrews