Fw: Postfix with Cyrus Help
Anybody got any tips as to where I should proceed in this?
Thanks in advance,
Curtis
>
>
> > Curtis Vaughan said:
> >
> > > Well, I never saw any TIME_WAIT, so I went ahead and restarted inetd.
> >
> > if you didn't see any TIME_WAIT or LISTEN entries in netstat after
> > you killed inetd for services that inetd loads then you should be
> > ok.
> >
> > telnet localhost 143 and see if it connects. it should ..
>
> No, no, no. If you read further down my last message you'll see that
LISTEN
> is there and that it never goes away.
> I can connect to port 143 no problem, but I can't authenticate, just like
> with cyradm.
>
> Here's the rest of my last message:
>
> Pacifica:/etc# netstat -an | grep 13
> tcp 0 0 0.0.0.0:13 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:113 0.0.0.0:* LISTEN
> tcp 0 0 10.0.1.13:22 10.0.1.254:41323
> ESTABLISHED
>
> So, I have, as you say, both LISTEN and TCP for port 13, so:
>
> >fuser -n tcp 13
> >
> >(replace tcp with udp if far left says it is udp) to find the
> >process id of the program that is using that port. then find
> >it in the process list (ps auxw | grep <PID>) where <PID> is
> >the number that fuser returns.
> >
> >I would expect it to be another instance of inetd..
> >
> >
> Well, tcp provides a pid (13409) but udp produces no response.
> So:
>
> Pacifica:/etc# fuser -n tcp 13
> 13/tcp: 13409
> Pacifica:/etc# ps auxw | grep 13409
> root 13409 0.0 0.5 1988 700 ? S 22:50 0:00 inetd
>
> >repeat with all the other services that came up with "address already
> >in use" until running netstat for each one returns nothing, no
> >LISTEN, and no TIME_WAIT or anything related to those ports.
> >
> >
> I'm a little lost here. The thing is, LISTEN never goes away for one.
> I've waited hours but still get:
>
> Pacifica:/etc# netstat -an | grep 13
> tcp 0 0 0.0.0.0:13 0.0.0.0:*
LISTEN
>
> and I've never seen "address already in use". Finally, I'm not really
> sure what other services I should run netstat for.
>
> >then start inetd again, it should be back to normal. Note that
> >waiting for TIME_WAIT can take some time, I have seen it take up
> >to 20 minutes for the system to release the socket/port.
> >
Reply to: