Errors after power failure

On Wed, 14 Jan 2004 danfisher@bwkip.com wrote:

I have deleted the pid and restarted the postgresql and it is starting
fine. It just appears to not be accepting connections. I had to rebuild
the server the last time this happened. Starting to be a pain.

Firewalling maybe? Check which ports are open with nmap.

Heres what is get with nmap localhost

pgsql-general@postgresql.org

[root@database root]# nmap localhost

Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
Interesting ports on database (127.0.0.1):
(The 1590 ports scanned but not shown below are in state: closed)
Port State Service
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
80/tcp open http
111/tcp open sunrpc
443/tcp open https
783/tcp open hp-alarm-mgr
1024/tcp open kdm
1025/tcp open NFS-or-IIS
6000/tcp open X11
10000/tcp open snet-sensor-mgmt

Nmap run completed -- 1 IP address (1 host up) scanned in 2 seconds
[root@database root]#

And I doublechecked to make sure postmaster was running

Here is what is in the log file

LOG: database system was shut down at 2004-01-15 11:22:01 EST
LOG: checkpoint record is at 0/AF6940
LOG: redo record is at 0/AF6940; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 2676; next oid: 25169
LOG: database system is ready

-Dan

I would suspect the manner in which it was started. Does your postresql.conf
file have tcpip_socket=true?. If it is set to false and the script that
starts Postgres does not use the '-o -i' switch then the database will not
accept tcpip connections. Have you tried psql on the database host to see if
it can accept local connections via a unix socket?

On Thursday 15 January 2004 08:16 am, danfisher@bwkip.com wrote:

Heres what is get with nmap localhost

pgsql-general@postgresql.org

[root@database root]# nmap localhost

Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
Interesting ports on database (127.0.0.1):
(The 1590 ports scanned but not shown below are in state: closed)
Port State Service
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
80/tcp open http
111/tcp open sunrpc
443/tcp open https
783/tcp open hp-alarm-mgr
1024/tcp open kdm
1025/tcp open NFS-or-IIS
6000/tcp open X11
10000/tcp open snet-sensor-mgmt

Nmap run completed -- 1 IP address (1 host up) scanned in 2 seconds
[root@database root]#

And I doublechecked to make sure postmaster was running

Here is what is in the log file

LOG: database system was shut down at 2004-01-15 11:22:01 EST
LOG: checkpoint record is at 0/AF6940
LOG: redo record is at 0/AF6940; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 2676; next oid: 25169
LOG: database system is ready

-Dan

On Wed, 14 Jan 2004 danfisher@bwkip.com wrote:

I have deleted the pid and restarted the postgresql and it is starting
fine. It just appears to not be accepting connections. I had to
rebuild the server the last time this happened. Starting to be a
pain.

Firewalling maybe? Check which ports are open with nmap.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

--
Adrian Klaver
aklaver@comcast.net

If I could kiss you I would.

Everything is working now.

Apparently an old script I had was switched and you were right...the old
script was
not starting tcp connections....so...I enabled it in the postgresql.conf and
it is ok

Thank You

-Dan

Thanks for everyones help!!

-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org]On Behalf Of Adrian Klaver
Sent: Thursday, January 15, 2004 11:19 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Errors after power failure

I would suspect the manner in which it was started. Does your
postresql.conf
file have tcpip_socket=true?. If it is set to false and the script that
starts Postgres does not use the '-o -i' switch then the database will not
accept tcpip connections. Have you tried psql on the database host to see if
it can accept local connections via a unix socket?

On Thursday 15 January 2004 08:16 am, danfisher@bwkip.com wrote:

Heres what is get with nmap localhost

pgsql-general@postgresql.org

[root@database root]# nmap localhost

Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
Interesting ports on database (127.0.0.1):
(The 1590 ports scanned but not shown below are in state: closed)
Port State Service
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
80/tcp open http
111/tcp open sunrpc
443/tcp open https
783/tcp open hp-alarm-mgr
1024/tcp open kdm
1025/tcp open NFS-or-IIS
6000/tcp open X11
10000/tcp open snet-sensor-mgmt

Nmap run completed -- 1 IP address (1 host up) scanned in 2 seconds
[root@database root]#

And I doublechecked to make sure postmaster was running

Here is what is in the log file

LOG: database system was shut down at 2004-01-15 11:22:01 EST
LOG: checkpoint record is at 0/AF6940
LOG: redo record is at 0/AF6940; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 2676; next oid: 25169
LOG: database system is ready

-Dan

On Wed, 14 Jan 2004 danfisher@bwkip.com wrote:

I have deleted the pid and restarted the postgresql and it is starting
fine. It just appears to not be accepting connections. I had to
rebuild the server the last time this happened. Starting to be a
pain.

Firewalling maybe? Check which ports are open with nmap.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

--
Adrian Klaver
aklaver@comcast.net

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