Hello, everyone. So, here's the problem: In a nutshell, Postgres doesn't seem to be listening on port 5432 (which is where everything seems to be looking for it). Nmap confirms this, plus none of the stuff that lsof lists as being owned by postgres seems to deal with a socket (here's the dump in case it helps):
------------------ sh 14806 postgres cwd DIR 3,3 4096 272268 /usr/lib/postgresql/bin sh 14806 postgres rtd DIR 3,3 4096 2 / sh 14806 postgres txt REG 3,3 461400 239637 /bin/bash sh 14806 postgres mem REG 3,3 98325 191635 /lib/ld-2.1.97.so sh 14806 postgres mem REG 3,3 232780 191758 /lib/libncurses.so.5.0 sh 14806 postgres mem REG 3,3 8792 191663 /lib/libdl-2.1.97.so sh 14806 postgres mem REG 3,3 1074056 191643 /lib/libc-2.1.97.so sh 14806 postgres mem REG 3,3 41896 192368 /lib/libnss_compat-2.1.97.so sh 14806 postgres mem REG 3,3 71072 192367 /lib/libnsl-2.1.97.so sh 14806 postgres 0u CHR 136,1 3 /dev/pts/1 sh 14806 postgres 1u CHR 136,1 3 /dev/pts/1 sh 14806 postgres 2u CHR 136,1 3 /dev/pts/1 sh 14806 postgres 255u CHR 136,1 3 /dev/pts/1 postmaste 15043 postgres cwd DIR 3,6 4096 239051 /var/lib/postgres postmaste 15043 postgres rtd DIR 3,3 4096 2 / postmaste 15043 postgres txt REG 3,3 1318556 273718 /usr/lib/postgresql/bin/postgres postmaste 15043 postgres mem REG 3,3 98325 191635 /lib/ld-2.1.97.so postmaste 15043 postgres mem REG 3,3 20788 191649 /lib/libcrypt-2.1.97.so postmaste 15043 postgres mem REG 3,3 71072 192367 /lib/libnsl-2.1.97.so postmaste 15043 postgres mem REG 3,3 8792 191663 /lib/libdl-2.1.97.so postmaste 15043 postgres mem REG 3,3 117224 192362 /lib/libm-2.1.97.so postmaste 15043 postgres mem REG 3,3 7664 192378 /lib/libutil-2.1.97.so postmaste 15043 postgres mem REG 3,3 143336 191769 /lib/libreadline.so.4.1 postmaste 15043 postgres mem REG 3,3 232780 191758 /lib/libncurses.so.5.0 postmaste 15043 postgres mem REG 3,3 1074056 191643 /lib/libc-2.1.97.so postmaste 15043 postgres mem REG 3,3 41896 192368 /lib/libnss_compat-2.1.97.so postmaste 15043 postgres 0r CHR 1,3 207752 /dev/null postmaste 15043 postgres 1w REG 3,6 1204635 223237 /var/log/postgres.log postmaste 15043 postgres 2w REG 3,6 1204635 223237 /var/log/postgres.log postmaste 15043 postgres 3u unix 0xc2e91310 61857279 /var/run/postgresql/.s.PGSQL.5432 ------------ I have recently purged and reinstalled the latest unstable version of postgres (dpkg reports 7.0.3-2). The regression tests don't work because they can't connect to the database (obviously). This is the process that 'ps ax' shows: ------------ /usr/lib/postgresql/bin/postmaster -b /usr/lib/postgresql/bin/postgres -B 128 -D /var/lib/postgres/data -d 0 ------------ I am running a Debian Potato/Woody Frankenstein, which may be part of the problem. I am using kernel-image '2.2.17pre6-1' (unmodified from the distro... it's amazing how well the 2.2.x images run without recompiles). I'd be happy to supply any other info that might be helpful. On a possibly-related note, Kaffe doesn't seem to be properly listening on port 8007. lsof has this entry: ------------ Kaffe 286 www-data 5u IPv4 417 TCP cmayes:8007 (LISTEN) ------------ However, web-based services like Enhydra can't connect to it. Plus, an nmap of localhost (and cmayes) turns up zilch on 8007. Kaffe's version # is 1.0.6-1. TIA, -Chris __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
