Search Postgresql Archives

PostgreSQL terminated with "signal 66"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi everyone,

Have you seen PostgreSQL terminated abnormally with "signal 66" ?

I'm using PostgreSQL 8.1.4 on Windows XP SP2.
autovacuum process aborted with "signal 66", and "startup process" 
aborted also.

-----
2008-01-18 10:04:56 892 LOCATION:  AutoVacMain, autovacuum.c:412
2008-01-18 10:05:56 3808 LOG:  00000: autovacuum process (PID 1160) was terminated by signal 66
2008-01-18 10:05:56 3808 LOCATION:  LogChildExit, postmaster.c:2436
2008-01-18 10:05:56 3808 LOG:  00000: terminating any other active server processes
2008-01-18 10:05:56 3808 LOCATION:  HandleChildCrash, postmaster.c:2317
2008-01-18 10:05:56 2152 WARNING:  57P02: terminating connection because of crash of another server process
2008-01-18 10:05:56 2152 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2008-01-18 10:05:56 2152 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2008-01-18 10:05:56 2152 LOCATION:  quickdie, postgres.c:2105
2008-01-18 10:05:56 2436 WARNING:  57P02: terminating connection because of crash of another server process
2008-01-18 10:05:56 2436 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2008-01-18 10:05:56 2436 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2008-01-18 10:05:56 2436 LOCATION:  quickdie, postgres.c:2105
2008-01-18 10:05:56 2536 WARNING:  57P02: terminating connection because of crash of another server process
2008-01-18 10:05:56 2536 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2008-01-18 10:05:56 2536 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2008-01-18 10:05:56 2536 LOCATION:  quickdie, postgres.c:2105
2008-01-18 10:05:57 3808 LOG:  00000: all server processes terminated; reinitializing
2008-01-18 10:05:57 3808 LOCATION:  reaper, postmaster.c:2217
2008-01-18 10:05:57 3808 LOG:  00000: startup process (PID 3668) was terminated by signal 66
2008-01-18 10:05:57 3808 LOCATION:  LogChildExit, postmaster.c:2436
2008-01-18 10:05:57 3808 LOG:  00000: aborting startup due to startup process failure
2008-01-18 10:05:57 3808 LOCATION:  reaper, postmaster.c:2062
2008-01-18 10:05:57 1336 LOG:  00000: logger shutting down
2008-01-18 10:05:57 1336 LOCATION:  SysLoggerMain, syslogger.c:361
-----

This trouble does not occur after this.
Do you know meaning of "signal 66" ?

Thanks

-----
Akio Iwaasa (NEC Soft, Ltd.)
mail : iwaasa@xxxxxxxxxxxxxxxxx
URL  : http://www.necsoft.com/eng/index.html

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux