From: Matthew Excell (matt_at_possibilityforge.com)
Date: Wed 04 Sep 2002 - 02:59:52 BST
On Tue, 2002-09-03 at 16:11, Jacques Gelinas wrote:
> On the first vserver where you are running slapd and proftpd, can you do
>
> netstat -atn | grep LISTEN
>
> Normally, you should see lines like
>
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address State
> tcp 0 0 192.168.3.250:389 0.0.0.0:* LISTEN
> tcp 0 0 192.168.3.250:22 0.0.0.0:* LISTEN
>
> Here you see one vserver with an sshd and slapd server running. Both unmodified and
> bound to 192.168.3.250, not 0.0.0.0.
>
> Is this what you see ?
>
> I am running openldap 2.0.21 here without trouble.
Here is the netstat output from the vserver with proftpd and slapd
running:
tcp 0 0 192.168.90.187:2401 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:37 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:9 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:13 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:80 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:113 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:53 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:22 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:5432 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:953 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.187:25 0.0.0.0:* LISTEN
inetd, apache, named, postgresql - no slapd or proftpd
So I pulled a netstat on the root server:
tcp 0 0 0.0.0.0:32768 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:515 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.184:37 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.184:9 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.184:2988 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.184:13 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.184:143 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.184:113 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.184:22 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.184:25 0.0.0.0:* LISTEN
tcp 0 0 192.168.90.184:220 0.0.0.0:* LISTEN
tcp 0 0 :::389 :::* LISTEN
tcp 0 0 :::21 :::* LISTEN
tcp 0 0 ::1:953 :::* LISTEN
xinetd, sshd; lpd,rpc.statd & portmap (bound to everything - I'll remove
them later;) and three odd entries for slapd, proftpd, and the rndc port
for named (named appears to be working fine)
When I stop slapd and proftpd (from the vserver, of course) the 389
disappears from the netstat output, but 21 does not and proftpd will no
longer start (as I would expect with the port still tied up.)
Any hints? (Thanks for your time - it is a fantastic package.)
-- Matthew Excell <matt_at_possibilityforge.com> The Possibility Forge, Inc.