Re: Postgresql fails to start?

From: Dianne Yumul <dianne(at)wellsgaming(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgresql fails to start?
Date: 2005-06-07 17:21:16
Message-ID: e6910c99e69ad246526ea19746699cd7@wellsgaming.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Can you say anything about the difference between the times where it
> gives the message and the times where it doesn't?

I get the message when I remove pgstartup.log before starting
postgresql. But if I leave pgstartup.log, it just says it failed to
start. Please see output below:

# /etc/rc.d/init.d/postgresql stop
Stopping postgresql service: [ OK ]
# ps aux | grep postmaster
root 10427 0.0 0.0 3752 664 pts/0 R+ 09:24 0:00 grep
postmaster
# rm -f pgstartup.log
# /etc/rc.d/init.d/postgresql start
/usr/bin/chcon: can't apply partial context to unlabeled file
/home/postgres/pgstartup.log
Starting postgresql service: [FAILED]
# ps aux | grep postmaster
postgres 10470 34.1 0.6 112404 5248 pts/0 S 09:24 0:02
/usr/bin/postmaster -p 5432 -D /home/postgres/data
root 10480 0.0 0.0 3756 668 pts/0 R+ 09:24 0:00 grep
postmaster

The pgstartup.log is empty. Also, data/pg_log/postgresql-Tue.log does
not contain any errors just stuff about database shutting down and
starting up. Now, trying without removing pgstartup.log:

# /etc/rc.d/init.d/postgresql stop
Stopping postgresql service: [ OK ]
# ps aux | grep postmaster
root 10244 0.0 0.0 3756 700 pts/0 R+ 09:20 0:00 grep
postmaster
# /etc/rc.d/init.d/postgresql start
Starting postgresql service: [FAILED]
# ps aux | grep postmaster
postgres 10566 20.6 0.6 112408 5312 pts/0 S 09:26 0:02
/usr/bin/postmaster -p 5432 -D /home/postgres/data
root 10577 0.0 0.0 3752 668 pts/0 R+ 09:26 0:00 grep
postmaster

I remember getting the message that postgresql started OK once or twice
yesterday, but could not get it to do now : (

> ls -Z /home/postgres/pgstartup.log

Gives:

Sorry, this option can only be used on a SELinux kernel.

But after setting selinux to permissive mode, ls -Z
/home/postgres/pgstartup.log gives:

-rw------- postgres postgres system_u:object_r:postgresql_log_t
/home/postgres/pgstartup.log

And I also tried starting postgresql with selinux in permissive mode,
but no dice.

> Oh, and is the message really complaining
> about /home/postgres/pgstartup.log? AFAICS the initscript should be
> messing with /var/lib/pgsql/pgstartup.log.

Sorry, I forgot to mention that I changed some of the defaults via
/etc/sysconfig/pgsql/postgresql file, which looks like this:

PGDATA=/home/postgres/data
PGLOG=/home/postgres/pgstartup.log

But even leaving the defaults alone gives me the same results:

# /etc/rc.d/init.d/postgresql start
/usr/bin/chcon: can't apply partial context to unlabeled file
/var/lib/pgsql/pgstartup.log
Initializing database: [ OK ]
Starting postgresql service: [FAILED]
# ps aux | grep postmaster
postgres 11003 9.4 0.3 19464 2988 pts/0 S 09:36 0:02
/usr/bin/postmaster -p 5432 -D /var/lib/pgsql/data

Many thanks for the help.

Dianne

On Jun 7, 2005, at 9:02 AM, Tom Lane wrote:

> Dianne Yumul <dianne(at)wellsgaming(dot)com> writes:
>>> Um, exactly which Postgres RPMs do you have installed?
>> Thanks for the response. I have the following installed:
>
>> postgresql-server-8.0.3-1
>> postgresql-8.0.3-1
>> postgresql-jdbc-8.0.3-1
>> postgresql-libs-8.0.3-1
>> postgresql-devel-8.0.3-1
>
> Hm, those are the most current versions.
>
> Can you say anything about the difference between the times where it
> gives the message and the times where it doesn't? Does
> ls -Z /home/postgres/pgstartup.log
> show anything different? Oh, and is the message really complaining
> about /home/postgres/pgstartup.log? AFAICS the initscript should be
> messing with /var/lib/pgsql/pgstartup.log.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2005-06-07 17:21:53 Re: return two elements
Previous Message Jaime Casanova 2005-06-07 17:16:00 Re: Issue with adding ORDER BY to EXCEPT.