On Thu, Aug 31, 2000 at 01:33:35AM -0400, Tom Lane wrote:
"Travis Bauer" [EMAIL PROTECTED] writes:
I'm getting:
FATAL: StreamServerPort: bind() failed: Address already in use
Is another postmaster already running on that port?
If not, wait a few seconds and retry.
Well, there were two other copies of postgress running, and at least one
was tying up port 5432, but . . .
I couldn't see them with 'ps' or 'ps -a', netstat did not list them as
using a port, but it did list something as having "Active UNIX domain
sockets," listing the tmp files I had deleted
On Thu, Aug 31, 2000 at 07:30:36AM -0500, Travis Bauer wrote:
Well, there were two other copies of postgress running, and at least one
was tying up port 5432, but . . .
I couldn't see them with 'ps' or 'ps -a', netstat did not list them as
using a port, but it did list something as having
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now I'm back in business, but I don't understand why they didn't show
up in ps or ps -a.
from the 'ps' manpage:
aSelect all processes on a terminal, includ-
ing those of other users
xSelect processes without
Travis Bauer [EMAIL PROTECTED] writes:
Well, there were two other copies of postgress running, and at least one
was tying up port 5432, but . . .
I couldn't see them with 'ps' or 'ps -a',
ps -a only lists processes that it thinks are spawned from interactive
sessions. You need ps -ax to see
On Thu, 31 Aug 2000, Tom Lane wrote:
Actually I think netstat only shows open connections, not processes
listening for connections. Does anyone know a (reasonably portable)
way of seeing which port numbers are being accept()ed on?
regards, tom lane
how about lsof,
At 10:15 31/08/00 -0400, Tom Lane wrote:
Actually I think netstat only shows open connections, not processes
listening for connections. Does anyone know a (reasonably portable)
way of seeing which port numbers are being accept()ed on?
netstat -a | grep LISTEN
works on most UNIX flavours
