Обсуждение: [BUGS] BUG #14594: postgres dies with fatal error

The following bug has been logged on the website:

Bug reference:      14594
Logged by:          naresh g
Email address:      gnareshdba@gmail.com
PostgreSQL version: 9.4.5
Operating system:   RHEL 7.2
Description:


postgresql (9.4.5) instance restarts with below error during backup times
-

2017-03-19 19:00:21 EDT PANIC: semop(id=152698887) failed: Invalid
argument
2017-03-19 19:00:21 EDT PANIC: semop(id=152698887) failed: Invalid
argument
2017-03-19 19:00:26 EDT FATAL: semctl(152666118, 6, SETVAL, 0) failed:
Invalid argument
2017-03-19 19:00:26 EDT LOG: server process (PID 13090) exited with exit
code 1
2017-03-19 19:00:26 EDT LOG: terminating any other active server processes
2017-03-19 19:00:26 EDT WARNING: terminating connection because of crash of
another server process
2017-03-19 19:00:26 EDT 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.
2017-03-19 19:00:26 EDT HINT: In a moment you should be able to reconnect to
the database and repeat your command.
2017-03-19 19:00:26 EDT WARNING: terminating connection because of crash of
another server process
2017-03-19 19:00:26 EDT 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.
2017-03-19 19:00:26 EDT HINT: In a moment you should be able to reconnect to
the database and repeat your command.
2017-03-19 19:00:26 EDT WARNING: terminating connection because of crash of
another server process
2017-03-19 19:00:26 EDT 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.

Instance crashes and starts automatically.

on RHEL 7.2, and UID set to (id -u postgres)
2011

I have below backups configured -
pg_basebackup --xlog -R -P --gzip --format=t
pg_backup_rotated.sh


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On 3/20/2017 3:26 PM, gnareshdba@gmail.com wrote:
>
> postgresql (9.4.5) instance restarts with below error during backup times
> -

is this problem repeatable on more than one server?

9.4.5 is 6 bug updates behind 9.4.11...  does this problem occur with 
9.4.11?


-- 
john r pierce, recycling bits in santa cruz



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

gnareshdba@gmail.com writes:
> Operating system:   RHEL 7.2

> postgresql (9.4.5) instance restarts with below error during backup times

> 2017-03-19 19:00:21 EDT PANIC: semop(id=152698887) failed: Invalid argument

You need to prevent systemd from deleting Postgres' semaphores.
See the discussion of RemoveIPC here:

https://wiki.postgresql.org/wiki/Systemd

> on RHEL 7.2, and UID set to (id -u postgres) 2011

That's not the UID typically used on RHEL for Postgres, which is probably
why systemd doesn't know to exempt it from RemoveIPC.

            regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs