Re: Database server restarting - Mailing list pgsql-general

Hello,

Thanks for you kind help.

But is there any particular reason for database to do such kind of
behavior.
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
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

Is there any particular reason for this thing.

Regards
Shoaib

-----Original Message-----
From: Nigel J. Andrews [mailto:nandrews@investsystems.co.uk]
Sent: Tuesday, May 06, 2003 4:55 PM
To: shoaib
Cc: 'Martijn van Oosterhout'; gearond@cvc.net;
pgsql-general@postgresql.org
Subject: RE: [GENERAL] Database server restarting

On Tue, 6 May 2003, shoaib wrote:

> When I login a console, I can see the prompt but after typing in login
> name system just don't respond it does not come to password prompt.

You may have to wait a long time which isn't very good because a) by the
time
the system has enough resources to proceed with your log in it's not in
the
same state it was in at the problem time (obviously) and b) the login
process
may well timeout the login attempt before it even gets to the stage of
asking
for the password.

You really do need to be logged in before the problem occurs. Indeed,
have more
than one session running, run system monitoring utilities like top and
procinfo
and also one you can type into without stopping those utilities.

If you can get the system to again you may also find it useful to run
your
cronjobs by hand to verify them individually and to then try and
replicate the
early morning conditions at whatever time you can test things. If you're
having
to wait overnight everytime just to take a look at a new piece of the
puzzle
you're locked into that timetable for generating and testing a solution.


--
Nigel Andrews