-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Nov 17, 2007 at 08:19:37AM +0800, Hussain Jawad-FXRM43 wrote:
> Hello Sir,
>  
> I have installed postgresql DB on my Linux server.
>  
> When I am trying to stop and start the DB, below error is reported in
> postgresql start up log file.
>  
> FATAL:  lock file "postmaster.pid" already exists
> HINT:  Is another postmaster (PID 25372) running in data directory
> "/var/lib/pgsql/data"?
> FATAL:  lock file "postmaster.pid" already exists
> HINT:  Is another postmaster (PID 25372) running in data directory
> "/var/lib/pgsql/data"?

This doesn't look like a PostgreSQL bug. I'd suggest to post such
questions in other mailing lists. Have a look at

  <http://www.postgresql.org/community/lists/>

especially pgsql-general or pgsql-novice

> I have deleted the file postmaster.pid in the directory
> /var/lib/pgsql/data for number of times and restarted the postgresql
> service, but I am still not able to restart the server and the same
> error is repeating again.

- From your mail I gather that this postmaster.pid "appears" every time
you start the service. Things to check:

  (1) are you really sure the service is not running?
    (try e.g. ps wwaux | grep postmaster).

  (2a) if the answer to (1) is "service is not running", that would
      mean that the postmaster process starts, creates the PID file
      and dies unexpectedly. In this case: have you had a look at
      the relevant log files (typically in /var/log/postgresql --
      but it depends on distribution).

  (2a) if the answer to (1) is "is running", but your clients are not
      able to connect, perhaps the server is listening just on an unix
      domain socket while the clients are trying to contact it via an
      Internet socket.

HTH.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFHPtO6Bcgs9XrR2kYRAiEAAJ4gt/IKJSHvB4kJmADWChXmXdwtSgCfW52W
CiMqL1XXWgcN2X0Wi+7wumI=
=g8Jw
-----END PGP SIGNATURE-----


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

Reply via email to