Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#26336 - Postgresql fails to start while system start up
Attached to Project:
Arch Linux
Opened by Alexander (heaven) - Saturday, 08 October 2011, 07:15 GMT
Last edited by Dan McGee (toofishes) - Sunday, 09 October 2011, 21:21 GMT
Opened by Alexander (heaven) - Saturday, 08 October 2011, 07:15 GMT
Last edited by Dan McGee (toofishes) - Sunday, 09 October 2011, 21:21 GMT
|
DetailsDescription:
Postgresql fails to start as daemon while system start up. But starts normally when launching it manually through /etc/rc.d/postgresql start command. Additional info: Inside of a /var/log/postgresql.log: FATAL: could not create shared memory segment: ???????????? ???????? DETAIL: Failed system call was shmget(key=5432001, size=41279488, 03600). 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 41279488 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 reconfiguring SHMMIN is called for. The PostgreSQL documentation contains more information about shared memory configuration. All becomes okay after decreasing shared_buffers down to 24MB in /var/lib/postgres/data/postgresql.conf |
This task depends upon
Comment by Dan McGee (toofishes) -
Sunday, 09 October 2011, 21:21 GMT
Fix your system. I'm not sure how you are adjusting SHMMAX so that it works later, but it isn't happening early enough and thus the daemon startup fails. You should be using /etc/sysctl.conf to adjust the shmmax value- rc.local is not ran until after daemon startup.