came across this problem myself.
turned out after much playing around that it was a change to the pg_hba.conf
was a syntax error in the all all posgres trust sameuser line.
deleted it and postgres fired up from /etc/init.d or as a service.
just my very late twopenneth
--
View this mess
On 05/31/2012 12:45 AM, Bart Lateur wrote:
Alan Hodgson writes:
On Wednesday, May 30, 2012 08:22:58 PM Bart Lateur wrote:
Luckily this is a development machine, but as we don't know what
causes the problem we fear we might one day face the exact same
problem where it does matter: on a producti
> Alan Hodgson writes:
> > On Wednesday, May 30, 2012 08:22:58 PM Bart Lateur wrote:
> >> Luckily this is a development machine, but as we don't know what
> >> causes the problem we fear we might one day face the exact same
> >> problem where it does matter: on a production machine. So we'd like
Alan Hodgson writes:
> On Wednesday, May 30, 2012 08:22:58 PM Bart Lateur wrote:
>> Luckily this is a development machine, but as we don't know what causes
>> the problem we fear we might one day face the exact same problem where
>> it does matter: on a production machine. So we'd like to know exa
On Wednesday, May 30, 2012 08:22:58 PM Bart Lateur wrote:
> Luckily this is a development machine, but as we don't know what causes
> the problem we fear we might one day face the exact same problem where
> it does matter: on a production machine. So we'd like to know exactly
> what went wrong..
C
Bart:
Failing a more definitive diagnostic approach, I suggest that you post
your entire pgstartup.log rather than just the error message. My guess
is that the position in that log where the error occurs will give folks
who are more familiar with the startup sequence a reasonable idea of
whe
(Sorry if message threading is a bit off; I'm replying from a different
mail account as the previous post, so the "ref" header won't match.)
Well I tried
/usr/bin/pg_ctl -D /var/lib/pgsql/data start -l /tmp/pglogfile
and it just says
server starting
and then... nothing. It seem
On 05/30/12 8:25 AM, Bart Lateur wrote:
After an update on the system, and adding mod_ssl in Apache (is this
related? No idea.), Postgres no longer starts up. It just fails
silently. “pgstartup.log” contains only one single line:
runuser: cannot set groups: Operation not permitted
did yo
On Wed, May 30, 2012 at 8:55 PM, Bart Lateur wrote:
> CentOS 5.x (now 5.8), Postgres 8.4.something. Postgres had been up and
> running for over a year now.
>
> ** **
>
> After an update on the system, and adding mod_ssl in Apache (is this
> related? No idea.), Postgres no longer starts up. It