Re: Quite strange crash - Mailing list pgsql-hackers
From | Denis Perchine |
---|---|
Subject | Re: Quite strange crash |
Date | |
Msg-id | 01010812404602.00613@dyp.perchine.com Whole thread Raw |
In response to | Re: Quite strange crash (Tom Lane <tgl@sss.pgh.pa.us>) |
Responses |
Re: Quite strange crash
|
List | pgsql-hackers |
On Monday 08 January 2001 00:08, Tom Lane wrote: > Denis Perchine <dyp@perchine.com> writes: > > Does anyone seen this on PostgreSQL 7.0.3????? > > FATAL: s_lock(401f7435) at bufmgr.c:2350, stuck spinlock. Aborting. > > Were there any errors before that? No... Just clean log (I redirect log from stderr/out t file, and all other to syslog). Here it is just from the begin: ---- DEBUG: Data Base System is starting up at Sun Jan 7 04:22:00 2001 DEBUG: Data Base System was interrupted being in production at Thu Jan 4 23:30:22 2001 DEBUG: Data Base System is in production state at Sun Jan 7 04:22:00 2001 FATAL: s_lock(401f7435) at bufmgr.c:2350, stuck spinlock. Aborting. FATAL: s_lock(401f7435) at bufmgr.c:2350, stuck spinlock. Aborting. Server process (pid 1008) exited with status 6 at Sun Jan 7 04:29:07 2001 Terminating any active server processes... Server processes were terminated at Sun Jan 7 04:29:07 2001 Reinitializing shared memory and semaphores ----- As far as you can see it happends almost just after start. I can give you full list of queries which was made by process 1008. But basically there was only queries like this: select message_id from pop3 where server_id = 6214 insert into pop3 (server_id, mailfrom, mailto, subject, message_id, sent_date, sent_date_text, recieved_date, state) values (25641, 'virtualo.com', 'jrdias@mail.telepac.pt', 'Joao roque Dias I have tried them all....this one is for real........!', '20010107041334.CVEA17335.fep02-svc.mail.telepac.pt@anydomain.com', '2001-01-07 04:06:23 -00', 'Sat, 06 Jan 2001 23:06:23 -0500', 'now', 1) And the last query was: Jan 7 04:27:53 mx postgres[1008]: query: select message_id from pop3 where server_id = 22615 > I've been suspicious for awhile that the system might neglect to release > buffer cntx_lock spinlocks if an elog() occurs while one is held. This > looks like it might be such a case, but you're only showing us the end > symptom not what led up to it ... Just say me what can I do. Unfortunatly I can not reproduce the situation... -- Sincerely Yours, Denis Perchine ---------------------------------- E-Mail: dyp@perchine.com HomePage: http://www.perchine.com/dyp/ FidoNet: 2:5000/120.5 ----------------------------------
pgsql-hackers by date: