Re: Database server restarting - Mailing list pgsql-general
From | Dennis Gearon |
---|---|
Subject | Re: Database server restarting |
Date | |
Msg-id | 3EB7DA02.8070408@cvc.net Whole thread Raw |
In response to | Re: Database server restarting ("shoaib" <shoaibm@vmoksha.com>) |
List | pgsql-general |
Look in the archives about disk and memory testing. memtest86 and some other program. 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 and > Red Hat linux 7.3. > We are about to install 70 such servers. > > Please help. > > regards > Shoaib > > -----Original Message----- > From: Dennis Gearon [mailto:gearond@cvc.net] > Sent: Monday, May 05, 2003 11:13 PM > To: shoaib > Cc: 'Nigel J. Andrews'; pgsql-general@postgresql.org > Subject: Re: [GENERAL] Database server restarting > > Modern OS's shouldn' need rebooting, unless something else is wrong. > What's the quality of your hardware? Any applications compiled on bad > hardware? > > sigh, is it a windows environment? > > 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. >>Your help is really appreciated. >> >>Regards >>Shoaib >> >>-----Original Message----- >>From: Nigel J. Andrews [mailto:nandrews@investsystems.co.uk] >>Sent: Monday, May 05, 2003 7:08 PM >>To: shoaib >>Cc: pgsql-general@postgresql.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 >>> >>> >> >> > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > >
pgsql-general by date: