[Desktop-packages] [Bug 264336] Re: pgsql fails to start due to shared buffer setting greater than kernel allows

2016-04-01 Thread Moi
can anyone help me I am getting that message on ubuntu I installed Ubuntu on my 
nexus 6 phone 
# service postgresql start
[] Starting PostgreSQL 9.4 database server: main[] The PostgreSQL 
server failed to start. Please check the log output: 2016-04-01 15:06:57 UTC 
[31454-1] FATAL: could not create shared memory segment: Function not 
implemented 2016-04-01 15:06:57 UTC [31454-2] DETAI[FAILiled system call was 
shmget(key=5432001, size=40, 03600). ... failed!
 failed!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/264336

Title:
  pgsql fails to start due to shared buffer setting greater than kernel
  allows

Status in linux package in Ubuntu:
  Won't Fix
Status in postgresql-8.3 package in Ubuntu:
  Won't Fix
Status in postgresql-9.1 package in Ubuntu:
  Confirmed
Status in postgresql-common package in Ubuntu:
  Invalid
Status in linux source package in Jaunty:
  Won't Fix
Status in postgresql-8.3 source package in Jaunty:
  Won't Fix
Status in postgresql-9.1 source package in Jaunty:
  Invalid
Status in postgresql-common source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: postgresql-8.3

  Freshly installed pgsql 8.3 on hardy got me this error when restarting:
  2008-09-03 09:16:39 EDT DETAIL:  Failed system call was shmget(key=5432001, 
size=38207488, 03600).
  2008-09-03 09:16:39 EDT HINT:  This error usually means that PostgreSQL's 
request for a shared memory segment exceeded your kernel's SHMMAX parameter.  
You can either reduce the request size or reconfigure the kernel with larger 
SHMMAX.  To reduce the request size (currently 38207488 bytes), reduce 
PostgreSQL's shared_buffers parameter (currently 4096) and/or its 
max_connections parameter (currently 103).
  If the request size is already small, it's possible that it is less 
than your kernel's SHMMIN parameter, in which case raising the request size or 
reconfiguring SHMMIN is called for.
  The PostgreSQL documentation contains more information about shared 
memory configuration.

  Checking the kernel settings:
  sudo sysctl -a | grep -i shm
  kernel.shmmax = 33554432
  kernel.shmall = 2097152
  kernel.shmmni = 4096

  The shared_buffers setting defaults to 32MB. I changed this down to
  25MB to test and then the server would start right up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264336/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 264336] Re: pgsql fails to start due to shared buffer setting greater than kernel allows

2014-03-03 Thread Sorin Sbârnea
I have the same problem with latest LTS Ubuntu, and the proper solution
is to set BOTH SHMMAX and SHMALL to the same value, the best is ¼ of
total memory.

kernel.shmmax = xxx
kernel.shmall = xxx

Still, I would consider this an real bug, especially because the
postgres error is misleading and incomplete.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/264336

Title:
  pgsql fails to start due to shared buffer setting greater than kernel
  allows

Status in “linux” package in Ubuntu:
  Won't Fix
Status in “postgresql-8.3” package in Ubuntu:
  Won't Fix
Status in “postgresql-9.1” package in Ubuntu:
  Confirmed
Status in “postgresql-common” package in Ubuntu:
  Invalid
Status in “linux” source package in Jaunty:
  Won't Fix
Status in “postgresql-8.3” source package in Jaunty:
  Won't Fix
Status in “postgresql-9.1” source package in Jaunty:
  Invalid
Status in “postgresql-common” source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: postgresql-8.3

  Freshly installed pgsql 8.3 on hardy got me this error when restarting:
  2008-09-03 09:16:39 EDT DETAIL:  Failed system call was shmget(key=5432001, 
size=38207488, 03600).
  2008-09-03 09:16:39 EDT HINT:  This error usually means that PostgreSQL's 
request for a shared memory segment exceeded your kernel's SHMMAX parameter.  
You can either reduce the request size or reconfigure the kernel with larger 
SHMMAX.  To reduce the request size (currently 38207488 bytes), reduce 
PostgreSQL's shared_buffers parameter (currently 4096) and/or its 
max_connections parameter (currently 103).
  If the request size is already small, it's possible that it is less 
than your kernel's SHMMIN parameter, in which case raising the request size or 
reconfiguring SHMMIN is called for.
  The PostgreSQL documentation contains more information about shared 
memory configuration.

  Checking the kernel settings:
  sudo sysctl -a | grep -i shm
  kernel.shmmax = 33554432
  kernel.shmall = 2097152
  kernel.shmmni = 4096

  The shared_buffers setting defaults to 32MB. I changed this down to
  25MB to test and then the server would start right up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264336/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Desktop-packages] [Bug 264336] Re: pgsql fails to start due to shared buffer setting greater than kernel allows

2014-03-03 Thread Thom Brown
On 3 March 2014 13:27, Sorin Sbârnea sorin.sbar...@gmail.com wrote:

 I have the same problem with latest LTS Ubuntu, and the proper solution
 is to set BOTH SHMMAX and SHMALL to the same value, the best is ¼ of
 total memory.

 kernel.shmmax = xxx
 kernel.shmall = xxx

 Still, I would consider this an real bug, especially because the
 postgres error is misleading and incomplete.


SHMALL is measured in pages, whereas SHMMAX is measured in bytes.  They
shouldn't be set to the same values as one another.

Regards

Thom

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/264336

Title:
  pgsql fails to start due to shared buffer setting greater than kernel
  allows

Status in “linux” package in Ubuntu:
  Won't Fix
Status in “postgresql-8.3” package in Ubuntu:
  Won't Fix
Status in “postgresql-9.1” package in Ubuntu:
  Confirmed
Status in “postgresql-common” package in Ubuntu:
  Invalid
Status in “linux” source package in Jaunty:
  Won't Fix
Status in “postgresql-8.3” source package in Jaunty:
  Won't Fix
Status in “postgresql-9.1” source package in Jaunty:
  Invalid
Status in “postgresql-common” source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: postgresql-8.3

  Freshly installed pgsql 8.3 on hardy got me this error when restarting:
  2008-09-03 09:16:39 EDT DETAIL:  Failed system call was shmget(key=5432001, 
size=38207488, 03600).
  2008-09-03 09:16:39 EDT HINT:  This error usually means that PostgreSQL's 
request for a shared memory segment exceeded your kernel's SHMMAX parameter.  
You can either reduce the request size or reconfigure the kernel with larger 
SHMMAX.  To reduce the request size (currently 38207488 bytes), reduce 
PostgreSQL's shared_buffers parameter (currently 4096) and/or its 
max_connections parameter (currently 103).
  If the request size is already small, it's possible that it is less 
than your kernel's SHMMIN parameter, in which case raising the request size or 
reconfiguring SHMMIN is called for.
  The PostgreSQL documentation contains more information about shared 
memory configuration.

  Checking the kernel settings:
  sudo sysctl -a | grep -i shm
  kernel.shmmax = 33554432
  kernel.shmall = 2097152
  kernel.shmmni = 4096

  The shared_buffers setting defaults to 32MB. I changed this down to
  25MB to test and then the server would start right up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264336/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 264336] Re: pgsql fails to start due to shared buffer setting greater than kernel allows

2013-10-31 Thread hjs
This just started happening to me in 12.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/264336

Title:
  pgsql fails to start due to shared buffer setting greater than kernel
  allows

Status in “linux” package in Ubuntu:
  Won't Fix
Status in “postgresql-8.3” package in Ubuntu:
  Won't Fix
Status in “postgresql-9.1” package in Ubuntu:
  Confirmed
Status in “postgresql-common” package in Ubuntu:
  Invalid
Status in “linux” source package in Jaunty:
  Won't Fix
Status in “postgresql-8.3” source package in Jaunty:
  Won't Fix
Status in “postgresql-9.1” source package in Jaunty:
  Invalid
Status in “postgresql-common” source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: postgresql-8.3

  Freshly installed pgsql 8.3 on hardy got me this error when restarting:
  2008-09-03 09:16:39 EDT DETAIL:  Failed system call was shmget(key=5432001, 
size=38207488, 03600).
  2008-09-03 09:16:39 EDT HINT:  This error usually means that PostgreSQL's 
request for a shared memory segment exceeded your kernel's SHMMAX parameter.  
You can either reduce the request size or reconfigure the kernel with larger 
SHMMAX.  To reduce the request size (currently 38207488 bytes), reduce 
PostgreSQL's shared_buffers parameter (currently 4096) and/or its 
max_connections parameter (currently 103).
  If the request size is already small, it's possible that it is less 
than your kernel's SHMMIN parameter, in which case raising the request size or 
reconfiguring SHMMIN is called for.
  The PostgreSQL documentation contains more information about shared 
memory configuration.

  Checking the kernel settings:
  sudo sysctl -a | grep -i shm
  kernel.shmmax = 33554432
  kernel.shmall = 2097152
  kernel.shmmni = 4096

  The shared_buffers setting defaults to 32MB. I changed this down to
  25MB to test and then the server would start right up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264336/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 264336] Re: pgsql fails to start due to shared buffer setting greater than kernel allows

2013-08-26 Thread Nathan Osman
This is still not fixed. I just installed postgresql-9.1 on a brand new
installation of Ubuntu 13.04 (64-bit) and received the following error
when attempting to start the server:

 * Starting PostgreSQL 9.1 database server
 * The PostgreSQL server failed to start. Please check the log output:
2013-08-26 11:40:41 PDT FATAL:  could not create shared memory segment: 
Invalid
argument
2013-08-26 11:40:41 PDT DETAIL:  Failed system call was shmget(key=5432001, 
size
=41263104, 03600).
2013-08-26 11:40:41 PDT HINT:  This error usually means that PostgreSQL's 
reques
t for a shared memory segment exceeded your kernel's SHMMAX parameter.  You 
can
either reduce the request size or reconfigure the kernel with larger 
SHMMAX.  To
 reduce the request size (currently 41263104 bytes), reduce PostgreSQL's 
shared
memory usage, perhaps by reducing shared_buffers or max_connections.
If the request size is already small, it's possible that it is less than
 your kernel's SHMMIN parameter, in which case raising the request size or 
recon
figuring SHMMIN is called for.
The PostgreSQL documentation contains more information about shared memo
ry configuration.
 
[fail]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/264336

Title:
  pgsql fails to start due to shared buffer setting greater than kernel
  allows

Status in “linux” package in Ubuntu:
  Won't Fix
Status in “postgresql-8.3” package in Ubuntu:
  Won't Fix
Status in “postgresql-9.1” package in Ubuntu:
  Confirmed
Status in “postgresql-common” package in Ubuntu:
  Invalid
Status in “linux” source package in Jaunty:
  Won't Fix
Status in “postgresql-8.3” source package in Jaunty:
  Won't Fix
Status in “postgresql-9.1” source package in Jaunty:
  Invalid
Status in “postgresql-common” source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: postgresql-8.3

  Freshly installed pgsql 8.3 on hardy got me this error when restarting:
  2008-09-03 09:16:39 EDT DETAIL:  Failed system call was shmget(key=5432001, 
size=38207488, 03600).
  2008-09-03 09:16:39 EDT HINT:  This error usually means that PostgreSQL's 
request for a shared memory segment exceeded your kernel's SHMMAX parameter.  
You can either reduce the request size or reconfigure the kernel with larger 
SHMMAX.  To reduce the request size (currently 38207488 bytes), reduce 
PostgreSQL's shared_buffers parameter (currently 4096) and/or its 
max_connections parameter (currently 103).
  If the request size is already small, it's possible that it is less 
than your kernel's SHMMIN parameter, in which case raising the request size or 
reconfiguring SHMMIN is called for.
  The PostgreSQL documentation contains more information about shared 
memory configuration.

  Checking the kernel settings:
  sudo sysctl -a | grep -i shm
  kernel.shmmax = 33554432
  kernel.shmall = 2097152
  kernel.shmmni = 4096

  The shared_buffers setting defaults to 32MB. I changed this down to
  25MB to test and then the server would start right up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264336/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 264336] Re: pgsql fails to start due to shared buffer setting greater than kernel allows

2013-05-21 Thread Martin Pitt
** Package changed: postgresql-8.4 (Ubuntu) = postgresql-9.1 (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/264336

Title:
  pgsql fails to start due to shared buffer setting greater than kernel
  allows

Status in “linux” package in Ubuntu:
  Won't Fix
Status in “postgresql-8.3” package in Ubuntu:
  Won't Fix
Status in “postgresql-9.1” package in Ubuntu:
  Confirmed
Status in “postgresql-common” package in Ubuntu:
  Invalid
Status in “linux” source package in Jaunty:
  Won't Fix
Status in “postgresql-8.3” source package in Jaunty:
  Won't Fix
Status in “postgresql-9.1” source package in Jaunty:
  Invalid
Status in “postgresql-common” source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: postgresql-8.3

  Freshly installed pgsql 8.3 on hardy got me this error when restarting:
  2008-09-03 09:16:39 EDT DETAIL:  Failed system call was shmget(key=5432001, 
size=38207488, 03600).
  2008-09-03 09:16:39 EDT HINT:  This error usually means that PostgreSQL's 
request for a shared memory segment exceeded your kernel's SHMMAX parameter.  
You can either reduce the request size or reconfigure the kernel with larger 
SHMMAX.  To reduce the request size (currently 38207488 bytes), reduce 
PostgreSQL's shared_buffers parameter (currently 4096) and/or its 
max_connections parameter (currently 103).
  If the request size is already small, it's possible that it is less 
than your kernel's SHMMIN parameter, in which case raising the request size or 
reconfiguring SHMMIN is called for.
  The PostgreSQL documentation contains more information about shared 
memory configuration.

  Checking the kernel settings:
  sudo sysctl -a | grep -i shm
  kernel.shmmax = 33554432
  kernel.shmall = 2097152
  kernel.shmmni = 4096

  The shared_buffers setting defaults to 32MB. I changed this down to
  25MB to test and then the server would start right up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264336/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp