Re: Postmaster already running !!! - Mailing list pgsql-bugs

From Ing. Jhon Carrillo - Caracas, Venezuela
Subject Re: Postmaster already running !!!
Date
Msg-id 00f901c58ec7$5e253520$1400a8c0@tgusta2
Whole thread Raw
In response to Postmaster already running !!!  ("Sivaraman K.G" <Ganapathy.Sivaraman@alcatel.com>)
List pgsql-bugs
Hi,

only remove postmaster.pid (NO clean up)

good look.


Jhon Carrillo
jdigital (a) cantv.net=20
Caracas - Venezuela

  ----- Original Message -----=20
  From: Sivaraman K.G=20
  To: pgsql-bugs@postgresql.org=20
  Sent: Friday, July 22, 2005 2:30 AM
  Subject: [BUGS] Postmaster already running !!!


  Hi,=20
  I am running PostgreSQL version 8.0 in Solaris 8.=20
  I am starting the postmaster when the system is coming up.=20
  I am facing the following problem :=20

  FATAL:  lock file "/data/ALAsm/PGSQL/data/postmaster.pid" already exists=
=20
  HINT:  Is another postmaster (PID 448) running in data directory "/data/A=
LAsm/PGSQL/data"?=20

  is coming, eventhough postmaster wasn't running and postmaster fail to st=
art, which makes my system to go down (due to my script).=20

  I have to manually clean up the postmaster.pid from the directory /data/A=
LAsm/PGSQL/data (from where I have initialized the database using=20
  initdb and running the postmaster).=20

  Can anyone help what is the problem here ?.=20

  Also, I got another problem.=20

  LOG:  could not bind IPv6 socket: Cannot assign requested address=20
  HINT:  Is another postmaster already running on port 5432? If not, wait a=
 few seconds and=20
  retry.=20
  LOG:  could not bind socket for statistics collector: Cannot assign reque=
sted address=20
  LOG:  database system was interrupted at 2005-07-21 15:05:15 CDT=20
  LOG:  checkpoint record is at 0/E06260=20
  LOG:  redo record is at 0/E06260; undo record is at 0/0; shutdown TRUE=20
  LOG:  next transaction ID: 174106; next OID: 25721=20
  LOG:  database system was not properly shut down; automatic recovery in p=
rogress=20
  LOG:  record with zero length at 0/E062A0=20
  LOG:  redo is not required=20
  PANIC:  could not access status of transaction 174106=20
  DETAIL:  could not read from file "/data/ALAsm/PGSQL/data/pg_clog/0000" a=
t offset 40960: Error 0=20
  LOG:  startup process (PID 501) was terminated by signal 6=20
  LOG:  aborting startup due to startup process failure=20

  After this, postmaster is not running and the system got rebooted continu=
ously.=20
  In this case, I have to manually cleanup all the database and run initdb =
again to setup the database.=20

  Can any one help, what is the problem?.=20
=20=20=20=20

  Thanks=20
  Siva=20
=20=20=20=20
=20=20=20=20

--=20
K.G.Sivaraman, Axes Technologies (I) Pvt Ltd

"The only SERVICE to be done for our lower classes is to give them=20
EDUCATION, to develop their lost individuality" - Swami Vivekananda
=20=20=20=20

pgsql-bugs by date:

Previous
From: "Andrus Adamchik"
Date:
Subject: BUG #1780: JDBC driver "setNull" throws for BLOB and CLOB columns
Next
From: Bruce Momjian
Date:
Subject: Re: abstime bug