Обсуждение: Pg7.1beta3: FATAL: s_lock(0x401f7010) at spin.c:147, stuck spinlock.

Поиск
Список
Период
Сортировка

Pg7.1beta3: FATAL: s_lock(0x401f7010) at spin.c:147, stuck spinlock.

От
"Valter Mazzola"
Дата:
what happens?

valter.

[i've done vacuum analyze while query are running... vacuum stopped at some 
point, then i've decided to ctrl-c, then killed postmaster]

-------------------------------------
postgres@lora:~$ /usr/pg71/bin/pg_ctl -D /usr/pg71/data/ stop

Smart Shutdown request at Fri Jan 12 05:46:11 2001
postmaster successfully shut down.

postgres@lora:~$ /usr/pg71/bin/pg_ctl -D /usr/pg71/data/ start

pg_ctl: It seems another postmaster is running. Trying to start postmaster 
anyway.
Lock file "/usr/pg71/data//postmaster.pid" already exists.
Is another postmaster (pid 11320) running in "/usr/pg71/data/"?
pg_ctl: Cannot start postmaster. Is another postmaster is running?

postgres@lora:~$ /usr/pg71/bin/pg_ctl -D /usr/pg71/data/ restart

Waiting for postmaster to shut down.........................
FATAL: s_lock(0x401f7010) at spin.c:147, stuck spinlock. Aborting.

FATAL: s_lock(0x401f7010) at spin.c:147, stuck spinlock. Aborting.
Startup failed - abort
done.
postmaster successfully shut down.
postmaster successfully started up

postgres@lora:~$ /usr/pg71/bin/postmaster: invalid argument -- '-D'

Try '/usr/pg71/bin/postmaster --help' for more information.

postgres@lora:~$ /usr/pg71/bin/pg_ctl -D /usr/pg71/data/ start
postmaster successfully started up
postgres@lora:~$ DEBUG:  starting up

DEBUG:  database system was interrupted being in recovery at 2001-01-12 
05:45:33This propably means that some data blocks are corruptedand you will have to use last backup for recovery.
DEBUG:  CheckPoint record at (0, 107606368)
DEBUG:  Redo record at (0, 107467584); Undo record at (0, 107484188); 
Shutdown FALSE
DEBUG:  NextTransactionId: 46738; NextOid: 59680
DEBUG:  database system was not properly shut down; automatic recovery in 
progress...
DEBUG:  redo starts at (0, 107467584)
FATAL 2:  out of free buffers: time to abort !


postgres@lora:~$
postgres@lora:~$
FATAL: s_lock(0x401f7010) at spin.c:147, stuck spinlock. Aborting.

FATAL: s_lock(0x401f7010) at spin.c:147, stuck spinlock. Aborting.
Startup failed - abort



_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



Re: Pg7.1beta3: FATAL: s_lock(0x401f7010) at spin.c:147, stuck spinlock.

От
Tom Lane
Дата:
Some of the noise here is coming from the fact that you didn't wait for
the old postmaster to quit before you tried to start another.  ("pg_ctl
stop" doesn't wait unless you say -w ... there's been some talk of
reversing that default ...)

However, it still looks like you had other problems.  What sort of
platform is this on?  Do the regression tests pass for you?
        regards, tom lane


Re: Pg7.1beta3: FATAL: s_lock(0x401f7010) at spin.c:147, stuck spinlock.

От
"Valter Mazzola"
Дата:
Architecture and regression.diffs:
valter.

-------------
valter@lora:$ uname -a:

Linux lorax 2.2.17 #3 Mon Oct 2 23:11:04 UTC 2000 i686 unknown
-------------

valter@lora:$ less
./src/test/regress/regression.diffs




*** ./expected/random.out       Thu Jan  6 06:40:54 2000
--- ./results/random.out        Fri Jan 12 06:18:18 2001
***************
*** 25,31 ****   GROUP BY random HAVING count(random) > 1;  random | count --------+-------
! (0 rows)
 SELECT random FROM RANDOM_TBL   WHERE random NOT BETWEEN 80 AND 120;
--- 25,32 ----   GROUP BY random HAVING count(random) > 1;  random | count --------+-------
!     103 |     2
! (1 row)
 SELECT random FROM RANDOM_TBL   WHERE random NOT BETWEEN 80 AND 120;

======================================================================



>From: Tom Lane <tgl@sss.pgh.pa.us>
>To: "Valter Mazzola" <txian@hotmail.com>
>CC: pgsql-hackers@postgresql.org
>Subject: Re: [HACKERS] Pg7.1beta3: FATAL: s_lock(0x401f7010) at spin.c:147, 
>stuck spinlock.
>Date: Thu, 11 Jan 2001 23:08:14 -0500
>
>Some of the noise here is coming from the fact that you didn't wait for
>the old postmaster to quit before you tried to start another.  ("pg_ctl
>stop" doesn't wait unless you say -w ... there's been some talk of
>reversing that default ...)
>
>However, it still looks like you had other problems.  What sort of
>platform is this on?  Do the regression tests pass for you?
>
>            regards, tom lane

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.