| Summary: | dev-db/postgresql - init.d script should use better errormessage on startup when SHMMMAX is to low | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ann Ohnym <gentosaker> |
| Component: | [OLD] Server | Assignee: | PgSQL Bugs <pgsql-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | leho |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
amazing, i would never have thought of this. i had a larger shmmax set from an ancient Oracle XE install which i deleted when cleaning up for openrc. next startup postgresql-8.3 wouldn't start, as OP describes. http://www.akadia.com/services/ora_linux_install_10g.html sysctl -w kernel.shmmax=2147483648 did the trick. not entirely sure how this could be reported from the ebuild aside from a plain text notice "this could be your problem". my default shmmax was: kernel.shmmax = 33554432 Addressed in bug #311047 Committed. |
I get this error on starting postgresql /etc/init.d/postgresql-8.3 restart * Service postgresql-8.3 starting * Starting PostgreSQL ... waiting for server to start...............................................................could not start server [ !! ] * The pid-file doesn't exist but pg_ctl reported a running server. * Please check whether there is another server running on the same port or read the log-file. [ !! ] * ERROR: postgresql-8.3 failed to start The problem is that SHMMAX is set to low. Better error message is needed! Reproducible: Always Steps to Reproduce: 1.increase shared buffers in postgresql 2.restart postgresql 3. Warn that shmmax is set to low.