| From: | "Sahagian, David" <david(dot)sahagian(at)emc(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | lock and socket file |
| Date: | 2013-01-14 17:54:43 |
| Message-ID: | F3CBFBA88397EA498B22A05FFA9EC49D0109CD83E2@MX22A.corp.emc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Using Postgres 9.1
(1)
Simulate a "power failure" by hitting "Restart" on my VMware Workstation.
(2)
Turn on the VM (without any script removing lock or socket file).
(3)
Try to start postgres.
$ pgsql/bin/pg_ctl start -D pgdata
server starting
2013-01-14 FATAL: lock file "/tmp/.s.PGSQL.5432.lock" already exists
2013-01-14 HINT: Is another postmaster (PID 2770) using socket file "/tmp/.s.PGSQL.5432"?
So to be able to start Postgres . . .
In our "vm startup script", should we remove only the [.s.PGSQL.5432.lock] file ?
Or should we also remove the [.s.PGSQL.5432] file ?
Thanks,
-dvs-
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian Sutherland | 2013-01-14 17:55:53 | Re: plpython intermittent ImportErrors |
| Previous Message | Adrian Klaver | 2013-01-14 17:05:09 | Re: plpython intermittent ImportErrors |