Thread: Database server restartig

Shoaib-

The "unexpected EOF on client connection" messages probably aren't cause for
great concern, as they could be caused by any event that results in a
connection getting lost, such as a telnet session getting lost.

The "database system was interrupted" message is likely the important one in
this case and indicates that the database has been started up but is not
finding the everything tidied up as it should be if a graceful shutdown has
been done. Does the time match your daily reboot? Perhaps you aren't calling
pg_ctl -stop before doing the reboot.

BTW, unless you've got something else running on the system that requires it
and if this is a Linux system, the reboot probably isn't necessary for
either the OS or postgreSQL.

-Nick


-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of shoaib
Sent: Sunday, May 04, 2003 9:57 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Database server restartig


Hello Everybody,

We are using postgressql 7.2.2 . our system running is 24 hours day it a
preventive reboot once a day.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
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

Our server reboots at 1 aM in the morning and the job I mentioned starts
at 4 aM in the morning and the job ended at 4.13 AM. This process is
database extensive around 10000 records are updated / inserted.Can it be
the cause of this problem.  After this thing happened my server just
hangs.

Last night I faced the same problem again on another server and it was
after yet another DB extensive process.
The  system has 1 GB RAM, 1 GHZ processor and RAID 1 installed on it.
We are about to install 70 such servers.

Please help.

regards
Shoaib

-----Original Message-----
From: Nick Fankhauser [mailto:nickf@ontko.com]
Sent: Monday, May 05, 2003 7:58 PM
To: shoaib; pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Database server restartig

Shoaib-

The "unexpected EOF on client connection" messages probably aren't cause
for
great concern, as they could be caused by any event that results in a
connection getting lost, such as a telnet session getting lost.

The "database system was interrupted" message is likely the important
one in
this case and indicates that the database has been started up but is not
finding the everything tidied up as it should be if a graceful shutdown
has
been done. Does the time match your daily reboot? Perhaps you aren't
calling
pg_ctl -stop before doing the reboot.

BTW, unless you've got something else running on the system that
requires it
and if this is a Linux system, the reboot probably isn't necessary for
either the OS or postgreSQL.

-Nick


-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of shoaib
Sent: Sunday, May 04, 2003 9:57 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Database server restartig


Hello Everybody,

We are using postgressql 7.2.2 . our system running is 24 hours day it a
preventive reboot once a day.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
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

modifying 10000 records is not a big deal, and it sounds like you have
adequate hardware so I'm not seeing a correlation here, unless you've
got bad hardware or something. what OS/distro are you running? are you
running ecc ram? look through your system messages, perhaps you got a
flaky kernel thats having i/o issues with your file system (post that
too)

Robert Treat

On Tue, 2003-05-06 at 01:40, shoaib wrote:
> Our server reboots at 1 aM in the morning and the job I mentioned starts
> at 4 aM in the morning and the job ended at 4.13 AM. This process is
> database extensive around 10000 records are updated / inserted.Can it be
> the cause of this problem.  After this thing happened my server just
> hangs.
>
> Last night I faced the same problem again on another server and it was
> after yet another DB extensive process.
> The  system has 1 GB RAM, 1 GHZ processor and RAID 1 installed on it.
> We are about to install 70 such servers.
>
> Please help.
>
> regards
> Shoaib
>
> -----Original Message-----
> From: Nick Fankhauser [mailto:nickf@ontko.com]
> Sent: Monday, May 05, 2003 7:58 PM
> To: shoaib; pgsql-admin@postgresql.org
> Subject: RE: [ADMIN] Database server restartig
>
> Shoaib-
>
> The "unexpected EOF on client connection" messages probably aren't cause
> for
> great concern, as they could be caused by any event that results in a
> connection getting lost, such as a telnet session getting lost.
>
> The "database system was interrupted" message is likely the important
> one in
> this case and indicates that the database has been started up but is not
> finding the everything tidied up as it should be if a graceful shutdown
> has
> been done. Does the time match your daily reboot? Perhaps you aren't
> calling
> pg_ctl -stop before doing the reboot.
>
> BTW, unless you've got something else running on the system that
> requires it
> and if this is a Linux system, the reboot probably isn't necessary for
> either the OS or postgreSQL.
>
> -Nick
>
>
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org
> [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of shoaib
> Sent: Sunday, May 04, 2003 9:57 PM
> To: pgsql-admin@postgresql.org
> Subject: [ADMIN] Database server restartig
>
>
> Hello Everybody,
>
> We are using postgressql 7.2.2 . our system running is 24 hours day it a
> preventive reboot once a day.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
> 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html