-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Are you running this in a FreeBSD jail under 6.1? It sounds like the problem that I had where a second postmaster starts up and stomp's on the previous postgresql's shared memory ... To "fix", you have to make sure that both instances run as different UIDs, so that one can't stomp on the other ... - --On Friday, October 20, 2006 17:05:53 -0400 Wes Sheldahl <[EMAIL PROTECTED]> wrote: > Hi, > > I seem to have an unstable/unreliable installation of postgresql, and I'm not > sure how to troubleshoot it. > > Symptoms: > $ psql postgres > psql: FATAL: semctl(851974, 3, SETVAL, 0) failed: Invalid argument > > (restart postgresql) > $ psql postgres > Welcome to psql 8.1.4, the PostgreSQL interactive terminal. > (rest of welcome message and psql prompt) > > It will work fine for a while, but later it will stop accepting connections > with the above error, until I restart postgresql again. It also happens when > I call a ruby script that connects to postgres: fails with same error message > sometimes, but works after restarting postgresql. > > Versions/Environment: > Postgresql 8.1.4 (installed from ports on FreeBSD 6.1) > > I've already tried reinstalling the postgresql81-server and > postgresql81-client ports and their dependencies via portupgrade, but the > symptoms persist. What else should I try? > > -- > Wes Sheldahl > [EMAIL PROTECTED] - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFOtuu4QvfyHIvDvMRAkUhAKChtw+L12z8UJhYfl8HfbzRm0kdoQCbBzjo aK5Pas9/HWfhjFNKMwnagXw= =35KQ -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
