Re: Errors after power failure

Heres what is get with nmap localhost

pgsql-general(at)postgresql(dot)org

[root(at)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(at)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(at)bwkip(dot)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