By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,301 Members | 1,233 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,301 IT Pros & Developers. It's quick & easy.

uptime problem

P: n/a

I have trouble: when client-program broke connection to Postgre I see
in logs:

FATAL: This connection has been terminated by the administrator.
LOG: shutting down

and I must start Postgre again. Postgre starting as:

pg_ctl -D /usr/local/pgdata -o \"-S\" start

I have PostgreSQL 7.3.4 (build from FreeBSD ports).

Whats wrong?

Thanks in advance!

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Nov 11 '05 #1
Share this Question
Share on Google+
2 Replies

P: n/a
On Wednesday 20 August 2003 18:51, Vasili G. Yanov wrote:
I have trouble: when client-program broke connection to Postgre I see
in logs:

FATAL: This connection has been terminated by the administrator.
LOG: shutting down

and I must start Postgre again. Postgre starting as:

pg_ctl -D /usr/local/pgdata -o \"-S\" start


If you get rid of that -S and specify a logfile, I am sure you will find
something in logs that would help you.

Discardign logs is not a good idea in general. Not especially if you have
problems..

Shridhar
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)

Nov 11 '05 #2

P: n/a
On Wednesday 20 August 2003 19:01, Vasili G. Yanov wrote:
I have trouble: when client-program broke connection to Postgre I see
in logs:

FATAL: This connection has been terminated by the administrator.
LOG: shutting down

and I must start Postgre again. Postgre starting as:

pg_ctl -D /usr/local/pgdata -o \"-S\" start


SD> If you get rid of that -S and specify a logfile, I am sure you will
find SD> something in logs that would help you.

SD> Discardign logs is not a good idea in general. Not especially if you
have SD> problems..

I store all logs in syslog.


Hmm.. Looking at the error message again, looks like somebody is killing
postmaster.

Is there any other script which is trying to kick in?

HTH

Shridhar
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

Nov 11 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.