Re: Bug 14592

Here is the information I originally provided:

Bug reference: 14592
Logged by: Matt Zinicola
Email address: mattzinicola(at)gmail(dot)com
PostgreSQL version: 9.6.2
Operating system: Linux 4.9.13-201.fc25.x86_64
Description:

Log output:

2017-03-17 12:32:20.311 UTCFATAL: XX000: semctl(16187416, 0, SETVAL, 0)
failed: Invalid argument
2017-03-17 12:32:20.311 UTCLOCATION: IpcSemaphoreInitialize,
pg_sema.c:150
2017-03-17 12:32:20.312 UTCLOG: 00000: server process (PID 9720) exited
with exit code 1
2017-03-17 12:32:20.312 UTCLOCATION: LogChildExit, postmaster.c:3481
2017-03-17 12:32:20.312 UTCLOG: 00000: terminating any other active server
processes
2017-03-17 12:32:20.312 UTCLOCATION: HandleChildCrash, postmaster.c:3223
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: 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.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: 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.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: 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.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: 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.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: 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.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.313 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.313 UTCDETAIL: 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.
2017-03-17 12:32:20.313 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.313 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.313 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.313 UTCDETAIL: 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.
2017-03-17 12:32:20.313 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.313 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.314 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.314 UTCDETAIL: 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.
2017-03-17 12:32:20.314 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.314 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.314 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.314 UTCDETAIL: 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.
2017-03-17 12:32:20.314 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.314 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.315 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.315 UTCDETAIL: 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.
2017-03-17 12:32:20.315 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.315 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.316 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.316 UTCDETAIL: 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.
2017-03-17 12:32:20.316 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.316 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.317 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.317 UTCDETAIL: 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.
2017-03-17 12:32:20.317 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.317 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.317 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.317 UTCDETAIL: 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.
2017-03-17 12:32:20.317 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.317 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.318 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.318 UTCDETAIL: 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.
2017-03-17 12:32:20.318 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.318 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.319 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.319 UTCDETAIL: 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.
2017-03-17 12:32:20.319 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.319 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.319 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.319 UTCDETAIL: 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.
2017-03-17 12:32:20.319 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.319 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.319 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.319 UTCDETAIL: 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.
2017-03-17 12:32:20.319 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.319 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.320 UTCLOG: 00000: all server processes terminated;
reinitializing
2017-03-17 12:32:20.320 UTCLOCATION: PostmasterStateMachine,
postmaster.c:3747
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15400960, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15433729, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15466498, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15499267, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15532036, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15564805, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15597574, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15630343, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15663112, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15695881, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15728650, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15761419, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15794188, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15826957, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15859726, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15892495, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15925264, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15958033, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15990802, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16023571, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16056340, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16089109, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16121878, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16154647, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16187416, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16220185, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.358 UTCLOG: 00000: database system was interrupted;
last known up at 2017-03-17 12:30:44 UTC
2017-03-17 12:32:20.358 UTCLOCATION: StartupXLOG, xlog.c:6019
2017-03-17 12:32:20.515 UTCLOG: 00000: database system was not properly
shut down; automatic recovery in progress
2017-03-17 12:32:20.515 UTCLOCATION: StartupXLOG, xlog.c:6499
2017-03-17 12:32:20.521 UTCLOG: 00000: redo starts at E/A2C34F58
2017-03-17 12:32:20.521 UTCLOCATION: StartupXLOG, xlog.c:6754
2017-03-17 12:32:20.575 UTCLOG: 00000: invalid record length at E/A30CA380:
wanted 24, got 0
2017-03-17 12:32:20.575 UTCLOCATION: ReadRecord, xlog.c:4018
2017-03-17 12:32:20.575 UTCLOG: 00000: redo done at E/A30CA358
2017-03-17 12:32:20.575 UTCLOCATION: StartupXLOG, xlog.c:7017
2017-03-17 12:32:20.575 UTCLOG: 00000: last completed transaction was at
log time 2017-03-17 12:32:16.508864+00
2017-03-17 12:32:20.575 UTCLOCATION: StartupXLOG, xlog.c:7022
2017-03-17 12:32:21.039 UTCLOG: 00000: MultiXact member wraparound
protections are now enabled
2017-03-17 12:32:21.039 UTCLOCATION: SetOffsetVacuumLimit,
multixact.c:2624
2017-03-17 12:32:21.040 UTCLOG: 00000: database system is ready to accept
connections
2017-03-17 12:32:21.040 UTCLOCATION: reaper, postmaster.c:2816
2017-03-17 12:32:21.041 UTCLOG: 00000: autovacuum launcher started
2017-03-17 12:32:21.041 UTCLOCATION: AutoVacLauncherMain, autovacuum.c:416

On Wed, May 3, 2017 at 2:20 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Wed, May 3, 2017 at 10:59 AM, Matthew Zinicola <mattzinicola(at)gmail(dot)com>
> wrote:
>
>> Any update on this issue? It is a server crash that I continue to
>> experience daily with 9.6.2.
>>
>> If a fix isn't forthcoming, can I safely downgrade to 9.5.6?
>>
>
> ​I see initial reports for bugs 14591 and 14593 - but nothing for
> 14592...which should have been issued roughly March 16th.
>
> https://www.postgresql.org/list/pgsql-bugs/2017-03/
>
> I'm adding -www since a form submission the results in a bug number should
> appear in our archives.
>
> You might want to re-post the report here in the meantime.
>
> David J.
>
> ​
>
>