From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Matthew Green" <Matthewgreen(at)intelfax(dot)co(dot)uk> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Failing to boot Postgres on Red Hat Linux |
Date: | 2000-08-31 21:52:54 |
Message-ID: | 11347.967758774@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
"Matthew Green" <Matthewgreen(at)intelfax(dot)co(dot)uk> writes:
> pg:2345:respawn:/bin/su - postgres -c "/usr/local/pgsql/bin/postmaster -i -D /usr/local/pgsql/data >> /usr/local/pgsql/logs/server.log 2>&1 </dev/null"
> This seems to execute since if we introduce a deliberate error we get a warning on reboot.
> But with the line exactly as above we get no warnings, no server.log file is generated and the postmaster task is not visible if we run "ps -A" as root.
Hmm. If the server.log file is not getting created, then the postmaster
has never had a chance to start, because that file would be opened
before the postmaster is exec'd from su.
Two thoughts: (a) does user postgres have write permission on the
directory /usr/local/pgsql/logs? (b) are you sure that your standard
runlevel is one of 2,3,4,5? (see the init line in inittab)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sokel, John | 2000-08-31 22:25:18 | RE: Access import |
Previous Message | Marco Colombo | 2000-08-31 21:18:22 | Re: Vacuum DB |