thanks a lot... looks really good.
I just found out that it was a power failure and it didn't come up automatically. After the sysadmin rebooted the system Postgres apparently didn't start correctly or at least didn't start after AOLserver did. If I do a manual reboot everything works fine though.
This is what I got in the server log:
Error: Ns_PgOpenDb(postgres): Could not connect to localhost::MyServer: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
Obviously there was nothing in /tmp cause it got rebooted. When I started Postgres manually (/etc/rc.d/init.d/postgresql start) it said that it will force a start although another server might already be running and it worked.
Any hints on how Postgres will start properly after a power failure and in the future an automatic start of the server?
I installed nmap and did:
[root@www root]# nmap -sT -O localhost
Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
Interesting ports on localhost.localdomain (127.0.0.1):
(The 1598 ports scanned but not shown below are in state: closed)
Port State Service
22/tcp open ssh
25/tcp open smtp
80/tcp open http
Remote operating system guess: Linux Kernel 2.4.0 - 2.5.20
Uptime 0.169 days (since Wed Oct 22 09:14:53 2003)
Nmap run completed -- 1 IP address (1 host up) scanned in 5 seconds
But I actually have webmin running on https on port 8000.
1. Why didn't nmap show port 8000 to be open?
2. Should I rather tunnel webmin through the ssh port? And how do I do this (just heard about it ?