[Bug 1649877] Re: PostgreSQL dies with fatal semctl eror

2018-07-27 Thread Tim Bishop
An update, years later. Still broken on 16.04, but working on 18.04.

Linux pgtest1604 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
postgresql-9.5 9.5.13-0ubuntu0.16.04

Linux pgtest1804 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
postgresql-10 10.4-0ubuntu0.18.04

Disappointing to see this issue received no attention on 16.04, but I
suppose there is at least a way forward now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649877

Title:
  PostgreSQL dies with fatal semctl eror

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.5/+bug/1649877/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1649877] Re: PostgreSQL dies with fatal semctl eror

2017-03-20 Thread Naresh G
I have the same issue 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

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.

memory.


Can you tell me what is the exact root cause of this issue?
Is it something related to user UID?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649877

Title:
  PostgreSQL dies with fatal semctl eror

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.5/+bug/1649877/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1649877] Re: PostgreSQL dies with fatal semctl eror

2017-01-04 Thread Andrea
I have the same issue on different servers. All postgres UIDs and GIDs
are set as 3003. After the change of UID and GID to 199 as Tim Bishop
suggest the errors gone away !

I made some tests changing the UIDs and GIDs.

UID   GID  Status  
999   999  Postgres works 
999  1000  Postgres works 
1000  999  Postgres crash
1000 1000  Postgres crash 

The problem seems related to UID > 999

The postgresql source code compiled on the same server (xenial) works
perfectly with UID and GID 3003

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649877

Title:
  PostgreSQL dies with fatal semctl eror

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.5/+bug/1649877/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1649877] Re: PostgreSQL dies with fatal semctl eror

2017-01-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: postgresql-9.5 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649877

Title:
  PostgreSQL dies with fatal semctl eror

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.5/+bug/1649877/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs