Thread: PostgreSQL XID exceeded crash.
Hi!, I am having an XID issue with PostgreSQL, while doing a pg_restore from a 200MB saved database I get a server crash, searching through the debug messages I have found that PostgreSQL crashes due to a exausted XID resource with a message that looks this way (sorry for the Spanish log) UBICACIÓN: StartupXLOG, xlog.c:4820 LOG: 00000: el límite para el reciclaje de ID de transacciones es 2147484146, limitado por base de datos «postgres» That is, 2GB identifiers available. No the problem is localized I can think o several ways to fix it: 1. Increment XID capacity. I dont think this will work because with time I will reach the maximum value. 2. Reset XID counter?, I don't even know if this makes sense. 3. Do not make transactions?. In some cases I make thousands of SELECTS and I know the data being used it not going to be modified. If I close transactions the XID would decrement?... I do not really understand why this counter keeps growing without decrementing. I have read in http://www.thescripts.com/forum/thread173882.html that with the command pg_resetxlog I can tweak the XID but I am not sure if this is a safe way to fix the issue. Thanks :) Mario.
Mario Lopez wrote: > Hi!, > > I am having an XID issue with PostgreSQL, while doing a pg_restore from > a 200MB saved database I get a server crash, searching through the debug > messages I have found that PostgreSQL crashes due to a exausted XID > resource with a message that looks this way (sorry for the Spanish log) > > UBICACIÓN: StartupXLOG, xlog.c:4820 > LOG: 00000: el límite para el reciclaje de ID de transacciones es > 2147484146, limitado por base de datos «postgres» This is not a problem. If you see a crash, the message is elsewhere -- the message should start with ERROR, FATAL or PANIC. LOG is normal operation. I suggest you look at the log more closely. Maybe the error is the line above; LOCATION lines (UBICACIÓN) are located just below the log entry they are annotating. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Hi Alvaro,
Ok, maybe is not a crash but this issue makes postgresql reap all of
it's child processes and restart operations, after this error I get in
pg_restore this message:
pg_restore: [archivador (bd)] Error durante PROCESAMIENTO DE TABLA DE
CONTENIDOS:
pg_restore: [archivador (bd)] Error en entrada de la tabla de contenidos
1893; 0 1615776 TABLE DATA xxxxx postgres
pg_restore: [archivador (bd)] could not execute query: server closed the
connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
Command was: INSERT INTO xxxxx VALUES (1755298, 2, 117, 28, 1155,
52457, 1, 1, '', '', '', '', NULL);
pg_restore: [archivador (bd)] could not execute query: sin resultado
desde el servidor
I have a attached a log from the XID exhausted resources till it reaps
all of it's child processes, which ends in a crash from pg_restore or
any application using this table.
Thanks.
Alvaro Herrera escribió:
> Mario Lopez wrote:
>
>> Hi!,
>>
>> I am having an XID issue with PostgreSQL, while doing a pg_restore from
>> a 200MB saved database I get a server crash, searching through the debug
>> messages I have found that PostgreSQL crashes due to a exausted XID
>> resource with a message that looks this way (sorry for the Spanish log)
>>
>> UBICACIÓN: StartupXLOG, xlog.c:4820
>> LOG: 00000: el límite para el reciclaje de ID de transacciones es
>> 2147484146, limitado por base de datos «postgres»
>>
>
> This is not a problem. If you see a crash, the message is elsewhere --
> the message should start with ERROR, FATAL or PANIC. LOG is normal
> operation. I suggest you look at the log more closely.
>
> Maybe the error is the line above; LOCATION lines (UBICACIÓN) are
> located just below the log entry they are annotating.
>
>
DEBUG: 00000: StartTransactionCommand
UBICACI�N: start_xact_command, postgres.c:1983
DEBUG: 00000: StartTransaction
UBICACI�N: ShowTransactionState, xact.c:3930
DEBUG: 00000: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 273609597/1/0, nestlvl: 1,
children:<>
UBICACI�N: ShowTransactionStateRec, xact.c:3955
DEBUG: 00000: reaping dead processes
UBICACI�N: reaper, postmaster.c:2021
DEBUG: 00000: proceso de servidor (PID 31622) termin� con c�digo de salida 255
UBICACI�N: LogChildExit, postmaster.c:2419
LOG: 00000: proceso de servidor (PID 31622) termin� con c�digo de salida 255
UBICACI�N: LogChildExit, postmaster.c:2419
LOG: 00000: terminando todos los otros procesos de servidor activos
UBICACI�N: HandleChildCrash, postmaster.c:2309
DEBUG: 00000: sending SIGQUIT to process 31308
UBICACI�N: HandleChildCrash, postmaster.c:2362
DEBUG: 00000: sending SIGQUIT to process 31309
UBICACI�N: HandleChildCrash, postmaster.c:2396
DEBUG: 00000: reaping dead processes
UBICACI�N: reaper, postmaster.c:2021
LOG: 00000: todos los procesos fueron terminados; reinicializando
UBICACI�N: reaper, postmaster.c:2209
DEBUG: 00000: shmem_exit(0)
UBICACI�N: shmem_exit, ipc.c:126
DEBUG: 00000: invoking IpcMemoryCreate(size=110387200)
UBICACI�N: CreateSharedMemoryAndSemaphores, ipci.c:99
LOG: 00000: el sistema de bases de datos fue interrumpido en 2006-09-04 13:40:56 CEST
UBICACI�N: StartupXLOG, xlog.c:4373
LOG: 00000: el registro de checkpoint est� en 1/8C1A12A8
UBICACI�N: StartupXLOG, xlog.c:4441
LOG: 00000: registro de redo en 1/8C1A12A8; registro de undo en 0/0; apagado FALSE
UBICACI�N: StartupXLOG, xlog.c:4468
LOG: 00000: siguiente ID de transacci�n: 273407288; siguiente OID: 11724975
UBICACI�N: StartupXLOG, xlog.c:4471
LOG: 00000: siguiente MultiXactId: 5; siguiente MultiXactOffset: 10
UBICACI�N: StartupXLOG, xlog.c:4474
LOG: 00000: el sistema de bases de datos no fue apagado apropiadamente; se est� efectuando la recuperaci�n autom�tica
UBICACI�N: StartupXLOG, xlog.c:4531
LOG: 00000: redo comienza en 1/8C1A12EC
UBICACI�N: StartupXLOG, xlog.c:4568
LOG: 00000: conexi�n recibida: host=[local]
UBICACI�N: BackendRun, postmaster.c:2699
DEBUG: 00000: forked new backend, pid=32029 socket=6
UBICACI�N: BackendStartup, postmaster.c:2520
FATAL: 57P03: el sistema de base de datos est� inici�ndose
UBICACI�N: ProcessStartupPacket, postmaster.c:1589
DEBUG: 00000: proc_exit(0)
UBICACI�N: proc_exit, ipc.c:95
DEBUG: 00000: shmem_exit(0)
UBICACI�N: shmem_exit, ipc.c:126
DEBUG: 00000: exit(0)
UBICACI�N: proc_exit, ipc.c:113
DEBUG: 00000: reaping dead processes
UBICACI�N: reaper, postmaster.c:2021
DEBUG: 00000: proceso de servidor (PID 32029) termin� con c�digo de salida 0
UBICACI�N: LogChildExit, postmaster.c:2419
LOG: 00000: registro de longitud cero en 1/8E845664
UBICACI�N: ReadRecord, xlog.c:2763
LOG: 00000: redo listo en 1/8E84563C
UBICACI�N: StartupXLOG, xlog.c:4626
LOG: 00000: conexi�n recibida: host=[local]
UBICACI�N: BackendRun, postmaster.c:2699
DEBUG: 00000: forked new backend, pid=32032 socket=6
UBICACI�N: BackendStartup, postmaster.c:2520
FATAL: 57P03: el sistema de base de datos est� inici�ndose
UBICACI�N: ProcessStartupPacket, postmaster.c:1589
DEBUG: 00000: proc_exit(0)
UBICACI�N: proc_exit, ipc.c:95
DEBUG: 00000: shmem_exit(0)
UBICACI�N: shmem_exit, ipc.c:126
DEBUG: 00000: exit(0)
UBICACI�N: proc_exit, ipc.c:113
DEBUG: 00000: reaping dead processes
UBICACI�N: reaper, postmaster.c:2021
DEBUG: 00000: proceso de servidor (PID 32032) termin� con c�digo de salida 0
UBICACI�N: LogChildExit, postmaster.c:2419
LOG: 00000: el sistema de bases de datos est� listo
UBICACI�N: StartupXLOG, xlog.c:4820
LOG: 00000: el l�mite para el reciclaje de ID de transacciones es 2147484146, limitado por base de datos �postgres�
UBICACI�N: SetTransactionIdLimit, varsup.c:234
DEBUG: 00000: proc_exit(0)
UBICACI�N: proc_exit, ipc.c:95
DEBUG: 00000: shmem_exit(0)
UBICACI�N: shmem_exit, ipc.c:126
DEBUG: 00000: exit(0)
UBICACI�N: proc_exit, ipc.c:113
DEBUG: 00000: reaping dead processes
UBICACI�N: reaper, postmaster.c:2021
LOG: 00000: conexi�n recibida: host=[local]
UBICACI�N: BackendRun, postmaster.c:2699
LOG: 00000: conexi�n autorizada: usuario=postgres database=postgres
UBICACI�N: BackendRun, postmaster.c:2769
DEBUG: 00000: postmaster child[32040]: starting with (
UBICACI�N: BackendRun, postmaster.c:2847
DEBUG: 00000: postgres
UBICACI�N: BackendRun, postmaster.c:2850
DEBUG: 00000: -v196608
UBICACI�N: BackendRun, postmaster.c:2850
DEBUG: 00000: -p
UBICACI�N: BackendRun, postmaster.c:2850
DEBUG: 00000: postgres
UBICACI�N: BackendRun, postmaster.c:2850
DEBUG: 00000: )
UBICACI�N: BackendRun, postmaster.c:2852
DEBUG: 00000: InitPostgres
UBICACI�N: PostgresMain, postgres.c:2946
DEBUG: 00000: StartTransaction
UBICACI�N: ShowTransactionState, xact.c:3930
UBICACI�N: ShowTransactionStateRec, xact.c:3955
DEBUG: 00000: CommitTransaction
Mario Lopez wrote: > Hi Alvaro, > > Ok, maybe is not a crash but this issue makes postgresql reap all of > it's child processes and restart operations, after this error I get in > pg_restore this message: > > pg_restore: [archivador (bd)] Error durante PROCESAMIENTO DE TABLA DE > CONTENIDOS: > pg_restore: [archivador (bd)] Error en entrada de la tabla de contenidos > 1893; 0 1615776 TABLE DATA xxxxx postgres > pg_restore: [archivador (bd)] could not execute query: server closed the > connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > Command was: INSERT INTO xxxxx VALUES (1755298, 2, 117, 28, 1155, > 52457, 1, 1, '', '', '', '', NULL); > pg_restore: [archivador (bd)] could not execute query: sin resultado > desde el servidor > > I have a attached a log from the XID exhausted resources till it reaps > all of it's child processes, which ends in a crash from pg_restore or > any application using this table. The actual problem is shown in these lines: DEBUG: 00000: reaping dead processes UBICACION: reaper, postmaster.c:2021 DEBUG: 00000: proceso de servidor (PID 31622) termino con codigo de salida 255 UBICACION: LogChildExit, postmaster.c:2419 LOG: 00000: proceso de servidor (PID 31622) termino con codigo de salida 255 What you need to find out is why is this process is terminating with code 255. What is it anyway? If you added %p to log_line_prefix we could have a better idea of what is it and what is it doing. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Hola Alvaro, The process that are being reaped are postgresql child processes, more precisely the process that is attending my queryes... Here I have another log that has the %p %i and %x in that order but I see no clear difference. Thanks. Alvaro Herrera escribió: > Mario Lopez wrote: > >> Hi Alvaro, >> >> Ok, maybe is not a crash but this issue makes postgresql reap all of >> it's child processes and restart operations, after this error I get in >> pg_restore this message: >> >> pg_restore: [archivador (bd)] Error durante PROCESAMIENTO DE TABLA DE >> CONTENIDOS: >> pg_restore: [archivador (bd)] Error en entrada de la tabla de contenidos >> 1893; 0 1615776 TABLE DATA xxxxx postgres >> pg_restore: [archivador (bd)] could not execute query: server closed the >> connection unexpectedly >> This probably means the server terminated abnormally >> before or while processing the request. >> Command was: INSERT INTO xxxxx VALUES (1755298, 2, 117, 28, 1155, >> 52457, 1, 1, '', '', '', '', NULL); >> pg_restore: [archivador (bd)] could not execute query: sin resultado >> desde el servidor >> >> I have a attached a log from the XID exhausted resources till it reaps >> all of it's child processes, which ends in a crash from pg_restore or >> any application using this table. >> > > The actual problem is shown in these lines: > > DEBUG: 00000: reaping dead processes > UBICACION: reaper, postmaster.c:2021 > DEBUG: 00000: proceso de servidor (PID 31622) termino con codigo de salida 255 > UBICACION: LogChildExit, postmaster.c:2419 > LOG: 00000: proceso de servidor (PID 31622) termino con codigo de salida 255 > > > What you need to find out is why is this process is terminating with > code 255. What is it anyway? If you added %p to log_line_prefix we > could have a better idea of what is it and what is it doing. > > PID:3559 CMD_TAG:INSERT XID:273990712 DEBUG: 00000: name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid:273990712/1/0, nestlvl: 1, children: <> PID:3559 CMD_TAG:INSERT XID:273990712 UBICACI�N: ShowTransactionStateRec, xact.c:3955 PID:3559 CMD_TAG:idle XID:0 DEBUG: 00000: StartTransactionCommand PID:3559 CMD_TAG:idle XID:0 UBICACI�N: start_xact_command, postgres.c:1983 PID:3559 CMD_TAG:idle XID:273990713 DEBUG: 00000: StartTransaction PID:3559 CMD_TAG:idle XID:273990713 UBICACI�N: ShowTransactionState, xact.c:3930 PID:3559 CMD_TAG:idle XID:273990713 DEBUG: 00000: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid:273990713/1/0, nestlvl: 1, children: <> PID:3559 CMD_TAG:idle XID:273990713 UBICACI�N: ShowTransactionStateRec, xact.c:3955 PID:3559 CMD_TAG:INSERT XID:273990713 DEBUG: 00000: ProcessQuery PID:3559 CMD_TAG:INSERT XID:273990713 UBICACI�N: ProcessQuery, pquery.c:128 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3524 CMD_TAG: XID: DEBUG: 00000: proceso de servidor (PID 3559) termin� con c�digo de salida 255 PID:3524 CMD_TAG: XID: UBICACI�N: LogChildExit, postmaster.c:2419 PID:3524 CMD_TAG: XID: LOG: 00000: proceso de servidor (PID 3559) termin� con c�digo de salida 255 PID:3524 CMD_TAG: XID: UBICACI�N: LogChildExit, postmaster.c:2419 PID:3524 CMD_TAG: XID: LOG: 00000: terminando todos los otros procesos de servidor activos PID:3524 CMD_TAG: XID: UBICACI�N: HandleChildCrash, postmaster.c:2309 PID:3524 CMD_TAG: XID: DEBUG: 00000: sending SIGQUIT to process 3526 PID:3524 CMD_TAG: XID: UBICACI�N: HandleChildCrash, postmaster.c:2362 PID:3524 CMD_TAG: XID: DEBUG: 00000: sending SIGQUIT to process 3527 PID:3524 CMD_TAG: XID: UBICACI�N: HandleChildCrash, postmaster.c:2396 PID:3524 CMD_TAG: XID: LOG: 00000: todos los procesos fueron terminados; reinicializando PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2209 PID:3524 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3524 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3524 CMD_TAG: XID: DEBUG: 00000: invoking IpcMemoryCreate(size=110387200) PID:3524 CMD_TAG: XID: UBICACI�N: CreateSharedMemoryAndSemaphores, ipci.c:99 PID:3612 CMD_TAG: XID: LOG: 00000: el sistema de bases de datos fue interrumpido en 2006-09-04 16:08:06 CEST PID:3612 CMD_TAG: XID: UBICACI�N: StartupXLOG, xlog.c:4373 PID:3612 CMD_TAG: XID: LOG: 00000: el registro de checkpoint est� en 1/9307E6A0 PID:3612 CMD_TAG: XID: UBICACI�N: StartupXLOG, xlog.c:4441 PID:3612 CMD_TAG: XID: LOG: 00000: registro de redo en 1/93000058; registro de undo en 0/0; apagado FALSE PID:3612 CMD_TAG: XID: UBICACI�N: StartupXLOG, xlog.c:4468 PID:3612 CMD_TAG: XID: LOG: 00000: siguiente ID de transacci�n: 273975270; siguiente OID: 12298416 PID:3612 CMD_TAG: XID: UBICACI�N: StartupXLOG, xlog.c:4471 PID:3612 CMD_TAG: XID: LOG: 00000: siguiente MultiXactId: 5; siguiente MultiXactOffset: 10 PID:3612 CMD_TAG: XID: UBICACI�N: StartupXLOG, xlog.c:4474 PID:3612 CMD_TAG: XID: LOG: 00000: el sistema de bases de datos no fue apagado apropiadamente; se est� efectuando la recuperaci�nautom�tica PID:3612 CMD_TAG: XID: UBICACI�N: StartupXLOG, xlog.c:4531 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3612 CMD_TAG: XID: LOG: 00000: redo comienza en 1/93000058 PID:3612 CMD_TAG: XID: UBICACI�N: StartupXLOG, xlog.c:4568 PID:3612 CMD_TAG: XID: LOG: 00000: registro de longitud cero en 1/9323006C PID:3612 CMD_TAG: XID: UBICACI�N: ReadRecord, xlog.c:2763 PID:3612 CMD_TAG: XID: LOG: 00000: redo listo en 1/93230044 PID:3612 CMD_TAG: XID: UBICACI�N: StartupXLOG, xlog.c:4626 PID:3612 CMD_TAG: XID: DEBUG: 00000: el archivo de registro de transacciones �000000010000000100000092� ha sido reciclado PID:3612 CMD_TAG: XID: UBICACI�N: MoveOfflineLogs, xlog.c:2407 PID:3612 CMD_TAG: XID: DEBUG: 00000: el archivo de registro de transacciones �000000010000000100000090� ha sido reciclado PID:3612 CMD_TAG: XID: UBICACI�N: MoveOfflineLogs, xlog.c:2407 PID:3612 CMD_TAG: XID: DEBUG: 00000: el archivo de registro de transacciones �000000010000000100000091� ha sido reciclado PID:3612 CMD_TAG: XID: UBICACI�N: MoveOfflineLogs, xlog.c:2407 PID:3612 CMD_TAG: XID: LOG: 00000: el sistema de bases de datos est� listo PID:3612 CMD_TAG: XID: UBICACI�N: StartupXLOG, xlog.c:4820 PID:3612 CMD_TAG: XID: LOG: 00000: el l�mite para el reciclaje de ID de transacciones es 2147484146, limitado por base dedatos �postgres� PID:3612 CMD_TAG: XID: UBICACI�N: SetTransactionIdLimit, varsup.c:234 PID:3612 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3612 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3612 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3612 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3612 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3612 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3650 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3650 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3650 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3650 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3650 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3650 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3675 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3675 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3675 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3675 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3675 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3675 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3700 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3700 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3700 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3700 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3700 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3700 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3725 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3725 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3725 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3725 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3725 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3725 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3750 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3750 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3750 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3750 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3750 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3750 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3775 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3775 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3775 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3775 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3775 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3775 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3800 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3800 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3800 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3800 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3800 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3800 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3826 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3826 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3826 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3826 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3826 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3826 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3853 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3853 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3853 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3853 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3853 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3853 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3878 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3878 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3878 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3878 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3878 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3878 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3903 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3903 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3903 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3903 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3903 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3903 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3928 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3928 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3928 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3928 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3928 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3928 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3953 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3953 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3953 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3953 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3953 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3953 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:3979 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:3979 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:3979 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:3979 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:3979 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:3979 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:4004 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:4004 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:4004 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:4004 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:4004 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:4004 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:4029 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:4029 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:4029 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:4029 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:4029 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:4029 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021 PID:4054 CMD_TAG: XID: DEBUG: 00000: proc_exit(0) PID:4054 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:95 PID:4054 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:4054 CMD_TAG: XID: UBICACI�N: shmem_exit, ipc.c:126 PID:4054 CMD_TAG: XID: DEBUG: 00000: exit(0) PID:4054 CMD_TAG: XID: UBICACI�N: proc_exit, ipc.c:113 PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:3524 CMD_TAG: XID: UBICACI�N: reaper, postmaster.c:2021
Hola, Mario Lopez wrote: > Hola Alvaro, > > The process that are being reaped are postgresql child processes, more > precisely the process that is attending my queryes... > > Here I have another log that has the %p %i and %x in that order but I > see no clear difference. I see the same as you: the process that dies is the one that was doing the INSERT. There's no stated reason for the failure however ... the process just exits with code 255. I don't remember seeing this before. Is there anything on the kernel messages? I doubt it's the kernel, because we'd be seeing something about getting a signal, and I don't think it would be this reproducible. Maybe someone else has an idea? The previous-to-last message below is "server process exited with exit code 255". What PostgreSQL version is this exactly? Maybe this is the case where proc_exit() is called when it was already running? i.e. proc_exit(proc_exit_inprogress)? Alas, no, I see that that would return with exit code 1, not 255. > PID:3559 CMD_TAG:idle XID:273990713 DEBUG: 00000: StartTransaction > PID:3559 CMD_TAG:idle XID:273990713 UBICACI?N: ShowTransactionState, xact.c:3930 > PID:3559 CMD_TAG:idle XID:273990713 DEBUG: 00000: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid:273990713/1/0, nestlvl: 1, children: <> > PID:3559 CMD_TAG:idle XID:273990713 UBICACI?N: ShowTransactionStateRec, xact.c:3955 > PID:3559 CMD_TAG:INSERT XID:273990713 DEBUG: 00000: ProcessQuery > PID:3559 CMD_TAG:INSERT XID:273990713 UBICACI?N: ProcessQuery, pquery.c:128 > PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes > PID:3524 CMD_TAG: XID: UBICACI?N: reaper, postmaster.c:2021 > PID:3524 CMD_TAG: XID: DEBUG: 00000: proceso de servidor (PID 3559) termin? con c?digo de salida 255 > PID:3524 CMD_TAG: XID: UBICACI?N: LogChildExit, postmaster.c:2419 -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
Hi again.. There are no kernel messages and I do not seem to find anything related to this error code. The version installed is the last version available in Debian testing branch: postgresql-8.1 8.1.4-6 I have searched and there are not any known bugs about XID or processes exiting unexpectedly Any more ideas, please?. Thanks for your time Alvaro :). --- Mario. Alvaro Herrera escribió: > Hola, > > Mario Lopez wrote: > >> Hola Alvaro, >> >> The process that are being reaped are postgresql child processes, more >> precisely the process that is attending my queryes... >> >> Here I have another log that has the %p %i and %x in that order but I >> see no clear difference. >> > > I see the same as you: the process that dies is the one that was doing > the INSERT. There's no stated reason for the failure however ... the > process just exits with code 255. I don't remember seeing this before. > Is there anything on the kernel messages? I doubt it's the kernel, > because we'd be seeing something about getting a signal, and I don't > think it would be this reproducible. > > Maybe someone else has an idea? The previous-to-last message below is > "server process exited with exit code 255". > > What PostgreSQL version is this exactly? > > Maybe this is the case where proc_exit() is called when it was already > running? i.e. proc_exit(proc_exit_inprogress)? Alas, no, I see that > that would return with exit code 1, not 255. > > > >> PID:3559 CMD_TAG:idle XID:273990713 DEBUG: 00000: StartTransaction >> PID:3559 CMD_TAG:idle XID:273990713 UBICACI?N: ShowTransactionState, xact.c:3930 >> PID:3559 CMD_TAG:idle XID:273990713 DEBUG: 00000: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid:273990713/1/0, nestlvl: 1, children: <> >> PID:3559 CMD_TAG:idle XID:273990713 UBICACI?N: ShowTransactionStateRec, xact.c:3955 >> PID:3559 CMD_TAG:INSERT XID:273990713 DEBUG: 00000: ProcessQuery >> PID:3559 CMD_TAG:INSERT XID:273990713 UBICACI?N: ProcessQuery, pquery.c:128 >> PID:3524 CMD_TAG: XID: DEBUG: 00000: reaping dead processes >> PID:3524 CMD_TAG: XID: UBICACI?N: reaper, postmaster.c:2021 >> PID:3524 CMD_TAG: XID: DEBUG: 00000: proceso de servidor (PID 3559) termin? con c?digo de salida 255 >> PID:3524 CMD_TAG: XID: UBICACI?N: LogChildExit, postmaster.c:2419 >> > > > >
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Maybe someone else has an idea? The previous-to-last message below is
> "server process exited with exit code 255".
That's very strange if the platform is Linux --- I was guessing it was
Windows.
Please try to get a core dump from the crash and provide a stack trace.
Another thing that would be useful is to turn on log_statement so we can
see the exact command causing the crash.
regards, tom lane
Hi, The platform as you have seen is Debian testing branch. I have activated log_statement but again nothing clear, the query that makes the system fail has nothing strange on it here is a dump. I do not know how toget a stack trace and the "crash" does not provide a core dump :(. Could you explain how to obtain it?. Thanks, ID:8069 CMD_TAG:idle XID:274157580 DEBUG: 00000: StartTransaction PID:8069 CMD_TAG:idle XID:274157580 UBICACIÓN: ShowTransactionState, xact.c:3930 PID:8069 CMD_TAG:idle XID:274157580 DEBUG: 00000: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 274157580/1/0, nestlvl: 1, children: <> PID:8069 CMD_TAG:idle XID:274157580 UBICACIÓN: ShowTransactionStateRec, xact.c:3955 PID:8069 CMD_TAG:idle XID:274157580 LOG: 00000: sentencia: INSERT INTO scannmap4 VALUES (1719913, 2, 117, 28, 1155, 17072, 1, 1, '', '', '', '', NULL); PID:8069 CMD_TAG:idle XID:274157580 UBICACIÓN: log_after_parse, postgres.c:605 PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG: 00000: ProcessQuery PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN: ProcessQuery, pquery.c:128 PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG: 00000: CommitTransactionCommand PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN: finish_xact_command, postgres.c:2006 PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG: 00000: CommitTransaction PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN: ShowTransactionState, xact.c:3930 PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG: 00000: name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 274157580/1/0, nestlvl: 1, children: <> PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN: ShowTransactionStateRec, xact.c:3955 PID:8069 CMD_TAG:INSERT XID:0 LOG: 00000: duración: 0.460 ms PID:8069 CMD_TAG:INSERT XID:0 UBICACIÓN: exec_simple_query, postgres.c:1090 PID:8069 CMD_TAG:idle XID:0 DEBUG: 00000: StartTransactionCommand PID:8069 CMD_TAG:idle XID:0 UBICACIÓN: start_xact_command, postgres.c:1983 PID:8069 CMD_TAG:idle XID:274157581 DEBUG: 00000: StartTransaction PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN: ShowTransactionState, xact.c:3930 PID:8069 CMD_TAG:idle XID:274157581 DEBUG: 00000: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 274157581/1/0, nestlvl: 1, children: <> PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN: ShowTransactionStateRec, xact.c:3955 PID:8069 CMD_TAG:idle XID:274157581 LOG: 00000: sentencia: INSERT INTO scannmap4 VALUES (1719914, 2, 117, 28, 1155, 17073, 1, 1, '', '', '', '', NULL); PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN: log_after_parse, postgres.c:605 PID:8025 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:8025 CMD_TAG: XID: UBICACIÓN: reaper, postmaster.c:2021 PID:8025 CMD_TAG: XID: DEBUG: 00000: proceso de servidor (PID 8069) terminó con código de salida 255 PID:8025 CMD_TAG: XID: UBICACIÓN: LogChildExit, postmaster.c:2419 PID:8025 CMD_TAG: XID: LOG: 00000: proceso de servidor (PID 8069) terminó con código de salida 255 PID:8025 CMD_TAG: XID: UBICACIÓN: LogChildExit, postmaster.c:2419 PID:8025 CMD_TAG: XID: LOG: 00000: terminando todos los otros procesos de servidor activos PID:8025 CMD_TAG: XID: UBICACIÓN: HandleChildCrash, postmaster.c:2309 PID:8025 CMD_TAG: XID: DEBUG: 00000: sending SIGQUIT to process 8028 PID:8025 CMD_TAG: XID: UBICACIÓN: HandleChildCrash, postmaster.c:2362 PID:8025 CMD_TAG: XID: DEBUG: 00000: sending SIGQUIT to process 8029 PID:8025 CMD_TAG: XID: UBICACIÓN: HandleChildCrash, postmaster.c:2396 PID:8025 CMD_TAG: XID: DEBUG: 00000: reaping dead processes PID:8025 CMD_TAG: XID: UBICACIÓN: reaper, postmaster.c:2021 PID:8025 CMD_TAG: XID: LOG: 00000: todos los procesos fueron terminados; reinicializando PID:8025 CMD_TAG: XID: UBICACIÓN: reaper, postmaster.c:2209 PID:8025 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) PID:8025 CMD_TAG: XID: UBICACIÓN: shmem_exit, ipc.c:126 PID:8025 CMD_TAG: XID: DEBUG: 00000: invoking IpcMemoryCreate(size=110387200) PID:8025 CMD_TAG: XID: UBICACIÓN: CreateSharedMemoryAndSemaphores, ipci.c:99 PID:8120 CMD_TAG: XID: LOG: 00000: el sistema de bases de datos fue interrumpido en 2006-09-04 18:56:21 CEST PID:8120 CMD_TAG: XID: UBICACIÓN: StartupXLOG, xlog.c:4373 PID:8120 CMD_TAG: XID: LOG: 00000: el registro de checkpoint está en 1/93231A60 PID:8120 CMD_TAG: XID: UBICACIÓN: StartupXLOG, xlog.c:4441 PID:8120 CMD_TAG: XID: LOG: 00000: registro de redo en 1/93231A60; registro de undo en 0/0; apagado TR Tom Lane escribió: > Alvaro Herrera <alvherre@commandprompt.com> writes: > >> Maybe someone else has an idea? The previous-to-last message below is >> "server process exited with exit code 255". >> > > That's very strange if the platform is Linux --- I was guessing it was > Windows. > > Please try to get a core dump from the crash and provide a stack trace. > > Another thing that would be useful is to turn on log_statement so we can > see the exact command causing the crash. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > > >
Mario Lopez <mario@lar3d.com> writes:
> PID:8069 CMD_TAG:idle XID:274157581 LOG: 00000: sentencia: INSERT INTO
> scannmap4 VALUES (1719914, 2, 117, 28, 1155, 17073, 1, 1, '', '', '',
> '', NULL);
> PID:8069 CMD_TAG:idle XID:274157581 UBICACI�N: log_after_parse,
> postgres.c:605
> PID:8025 CMD_TAG: XID: DEBUG: 00000: proceso de servidor (PID 8069)
> termin� con c�digo de salida 255
Hm, well that gives us a little bit to go on. Tell us about the
schema of table scannmap4 ... what are its column datatypes, indexes,
rules, foreign keys, triggers? Can you reproduce the crash just by
feeding this one statement into it?
regards, tom lane
Hi, I forgot to mention that we are using plphp version 1.1 but I guess that in the process of making a pg_restore this issue does not really matter. Thanks Mario. Mario Lopez escribió: > Hi, > > The platform as you have seen is Debian testing branch. I have > activated log_statement but again nothing clear, the query that makes > the system fail has nothing strange on it here is a dump. > > I do not know how toget a stack trace and the "crash" does not provide > a core dump :(. Could you explain how to obtain it?. > > Thanks, > > ID:8069 CMD_TAG:idle XID:274157580 DEBUG: 00000: StartTransaction > PID:8069 CMD_TAG:idle XID:274157580 UBICACIÓN: ShowTransactionState, > xact.c:3930 > PID:8069 CMD_TAG:idle XID:274157580 DEBUG: 00000: name: unnamed; > blockState: DEFAULT; state: INPROGR, xid/subid/cid: > 274157580/1/0, nestlvl: 1, children: <> > PID:8069 CMD_TAG:idle XID:274157580 UBICACIÓN: > ShowTransactionStateRec, xact.c:3955 > PID:8069 CMD_TAG:idle XID:274157580 LOG: 00000: sentencia: INSERT > INTO scannmap4 VALUES (1719913, 2, 117, 28, 1155, 17072, 1, 1, '', '', > '', '', NULL); > PID:8069 CMD_TAG:idle XID:274157580 UBICACIÓN: log_after_parse, > postgres.c:605 > PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG: 00000: ProcessQuery > PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN: ProcessQuery, > pquery.c:128 > PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG: 00000: > CommitTransactionCommand > PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN: finish_xact_command, > postgres.c:2006 > PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG: 00000: CommitTransaction > PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN: > ShowTransactionState, xact.c:3930 > PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG: 00000: name: unnamed; > blockState: STARTED; state: INPROGR, xid/subid/cid: > 274157580/1/0, nestlvl: 1, children: <> > PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN: > ShowTransactionStateRec, xact.c:3955 > PID:8069 CMD_TAG:INSERT XID:0 LOG: 00000: duración: 0.460 ms > PID:8069 CMD_TAG:INSERT XID:0 UBICACIÓN: exec_simple_query, > postgres.c:1090 > PID:8069 CMD_TAG:idle XID:0 DEBUG: 00000: StartTransactionCommand > PID:8069 CMD_TAG:idle XID:0 UBICACIÓN: start_xact_command, > postgres.c:1983 > PID:8069 CMD_TAG:idle XID:274157581 DEBUG: 00000: StartTransaction > PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN: ShowTransactionState, > xact.c:3930 > PID:8069 CMD_TAG:idle XID:274157581 DEBUG: 00000: name: unnamed; > blockState: DEFAULT; state: INPROGR, xid/subid/cid: > 274157581/1/0, nestlvl: 1, children: <> > PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN: > ShowTransactionStateRec, xact.c:3955 > PID:8069 CMD_TAG:idle XID:274157581 LOG: 00000: sentencia: INSERT > INTO scannmap4 VALUES (1719914, 2, 117, 28, 1155, 17073, 1, 1, '', '', > '', '', NULL); > PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN: log_after_parse, > postgres.c:605 > PID:8025 CMD_TAG: XID: DEBUG: 00000: reaping dead processes > PID:8025 CMD_TAG: XID: UBICACIÓN: reaper, postmaster.c:2021 > PID:8025 CMD_TAG: XID: DEBUG: 00000: proceso de servidor (PID 8069) > terminó con código de salida 255 > PID:8025 CMD_TAG: XID: UBICACIÓN: LogChildExit, postmaster.c:2419 > PID:8025 CMD_TAG: XID: LOG: 00000: proceso de servidor (PID 8069) > terminó con código de salida 255 > PID:8025 CMD_TAG: XID: UBICACIÓN: LogChildExit, postmaster.c:2419 > PID:8025 CMD_TAG: XID: LOG: 00000: terminando todos los otros > procesos de servidor activos > PID:8025 CMD_TAG: XID: UBICACIÓN: HandleChildCrash, postmaster.c:2309 > PID:8025 CMD_TAG: XID: DEBUG: 00000: sending SIGQUIT to process 8028 > PID:8025 CMD_TAG: XID: UBICACIÓN: HandleChildCrash, postmaster.c:2362 > PID:8025 CMD_TAG: XID: DEBUG: 00000: sending SIGQUIT to process 8029 > PID:8025 CMD_TAG: XID: UBICACIÓN: HandleChildCrash, postmaster.c:2396 > PID:8025 CMD_TAG: XID: DEBUG: 00000: reaping dead processes > PID:8025 CMD_TAG: XID: UBICACIÓN: reaper, postmaster.c:2021 > PID:8025 CMD_TAG: XID: LOG: 00000: todos los procesos fueron > terminados; reinicializando > PID:8025 CMD_TAG: XID: UBICACIÓN: reaper, postmaster.c:2209 > PID:8025 CMD_TAG: XID: DEBUG: 00000: shmem_exit(0) > PID:8025 CMD_TAG: XID: UBICACIÓN: shmem_exit, ipc.c:126 > PID:8025 CMD_TAG: XID: DEBUG: 00000: invoking > IpcMemoryCreate(size=110387200) > PID:8025 CMD_TAG: XID: UBICACIÓN: CreateSharedMemoryAndSemaphores, > ipci.c:99 > PID:8120 CMD_TAG: XID: LOG: 00000: el sistema de bases de datos fue > interrumpido en 2006-09-04 18:56:21 CEST > PID:8120 CMD_TAG: XID: UBICACIÓN: StartupXLOG, xlog.c:4373 > PID:8120 CMD_TAG: XID: LOG: 00000: el registro de checkpoint está en > 1/93231A60 > PID:8120 CMD_TAG: XID: UBICACIÓN: StartupXLOG, xlog.c:4441 > PID:8120 CMD_TAG: XID: LOG: 00000: registro de redo en 1/93231A60; > registro de undo en 0/0; apagado TR > > Tom Lane escribió: >> Alvaro Herrera <alvherre@commandprompt.com> writes: >> >>> Maybe someone else has an idea? The previous-to-last message below is >>> "server process exited with exit code 255". >>> >> >> That's very strange if the platform is Linux --- I was guessing it was >> Windows. >> >> Please try to get a core dump from the crash and provide a stack trace. >> >> Another thing that would be useful is to turn on log_statement so we can >> see the exact command causing the crash. >> >> regards, tom lane >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 1: if posting/reading through Usenet, please send an appropriate >> subscribe-nomail command to majordomo@postgresql.org so that your >> message can get through to the mailing list cleanly >> >> >> > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > >