From: Joshua N Pritikin <jpritikin@pobox.com>
Subject: how to avoid a restart loop?
Date: Sat, 3 Dec 2005 13:09:03 +0530 [thread overview]
Message-ID: <20051203073902.GK11535@always.joy.eth.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Today I noticed that the log was filling up with:
[2005-12-03 06:29:47 UTC] LOG: could not load root certificate file
+"/var/lib/postgresql/8.0/main/root.crt": No SSL error reported
[2005-12-03 06:29:47 UTC] DETAIL: Will not verify client certificates.
[2005-12-03 06:29:47 UTC] FATAL: lock file
+"/var/lib/postgresql/8.0/main/postmaster.pid" already exists
[2005-12-03 06:29:47 UTC] HINT: Is another postmaster (PID 288) running
in data
+directory "/var/lib/postgresql/8.0/main"?
I got 1 per second! A few megabytes later, I killed everything and
restart. Looks OK now, but how to avoid this in the future?
Do I need a ./finish script which does:
kill `cat /var/lib/postgresql/8.0/main/postmaster.pid`
??
Suggestions please. ;-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-12-03 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 7:39 Joshua N Pritikin [this message]
2005-12-04 16:43 ` Joshua N Pritikin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051203073902.GK11535@always.joy.eth.net \
--to=jpritikin@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).