Fw: Fw: Postgresql 7 does not always start on RH 6.2 - Mailing list pgsql-general
From | Warren Flemmer |
---|---|
Subject | Fw: Fw: Postgresql 7 does not always start on RH 6.2 |
Date | |
Msg-id | 01c0373b$02fc4820$a23b1fc4@ras.netlab.co.za Whole thread Raw |
List | pgsql-general |
Logs now working. For interest all that needed to be done was change >/dev/null to >/var/log/postgresql. All the permissions must have already been set for this file, it work straight away. (RH6.2, postgresql 7, and installation from rpm) Now for the log message: pg_ctl: It seems another postmaster is running. Try to start postmaster anyway. pg_ctl: Cannot start postmaster. Is another postmaster running? Can't create pid file: /var/lib/pgsql/data/postmaster.pid Is another postmaster (pid 494( running? This occured on the third reboot. The first two started fine. The system was shutdown the same way each time (from Gnome). I had a look for /tmp/.s.PGSQL.5432, nothing was there. Perhaps the attempt to start postgresql cleared it because any second attempt to start postgresql works. I tried to start and stop the postgresql from the console a few times (probably about 20 times) to see what would happen. On one occasion postgresql did not start and the log had the following (all other attempts were fine): pg_ctl: It seems another postmaster is running. Try to start postmaster anyway. pg_ctl: Cannot start postmaster. Is another postmaster running? 001016.08:24:29.899 [1949] IpcmemoryCreate: shmget failed (identifier removed) key=5432007, size=66060, permission=600 This type of error is usually caused by an improper shared memory or System V IPC semaphore configuration. .... SISegmentInit: segment create failed. Identifier removed 001016.08:24:29.901 [1949] FATAL 1: CreateSharedIntervalidation state: Failed segment init The system is a standard PC with an Intel 166 cpu and 32 megs memory. I have used to system for varies tasks over the last few years with no failures. I have no reason to suspect the hardware. Warren -----Original Message----- From: KuroiNeko <evpopkov@carrier.kiev.ua> To: pgsql-general@postgresql.org <pgsql-general@postgresql.org> Date: Sunday, October 15, 2000 12:25 PM Subject: Re: Fw: [GENERAL] Postgresql 7 does not always start on RH 6.2 > > Warren, > >> su -l postgres -c "/usr/bin/pg_ctl -D $PGDATA -p /usr/bin/postmaster >> start >> >/dev/null 2>&1" > > > Something like this: > >su -l postgres -c "/usr/bin/og_ctl -D $PGDATA -p /usr/bin/postmaster start >>> /var/log/pgsql 2>&1" > > Then check that /var/log/pgsql exists and is writeable by postgres user. >Eg, include pgsql in a group called log, then > ># chown root.log /var/log ># chmod 0750 /var/log ># cd /var/log ># echo -n > ./pgsql ># chown postgres.root ./pgsql ># chmod 0600 ./pgsql > > Also, make sure that /var and / are 5 for user postgres. > Another reason for postmaster to fail is a stale UNIX domain socket, >usually /tmp/.s.PGSQL.5432 It remains in /tmp if for some reason postmaster >hasn't been stopped correctly. > > HTH > > Ed > > >--- > Well I tried to be meek > And I have tried to be mild > But I spat like a woman > And I sulked like a child > I have lived behind the walls > That have made me alone > Striven for peace > Which I never have known > > Dire Straits, Brothers In Arms, The Man's Too Strong (Knopfler) >
pgsql-general by date: