> That means that something else is using port 21064 - the TCP port that > the DLM uses. If the DLM can't bind to its port then it cannot start. What's weird is that I didn't change anything, just the storage, then needing to get the cluster quorum so that I could set up gfs. > Use netstat -tap or lsof to find out what is using that port. If you > can't stop that particular application that is using it, then you'll #lsof -i | grep 21064 Reveals nothing. # netstat -anp | grep 21064 Seems to show port 21064 being available. tcp 0 0 192.168.1.58:21064 0.0.0.0:* LISTEN - tcp 0 0 192.168.1.58:6809 192.168.1.62:21064 ESTABLISHED - tcp 0 0 192.168.1.58:21064 192.168.1.63:32780 ESTABLISHED - tcp 0 0 192.168.1.58:21064 192.168.1.92:6809 ESTABLISHED - tcp 0 0 192.168.1.58:21064 192.168.1.62:6809 ESTABLISHED - tcp 0 0 192.168.1.58:21064 192.168.1.40:6809 ESTABLISHED - # nmap -sT -O localhost PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 80/tcp open http 111/tcp open rpcbind 139/tcp open netbios-ssn 443/tcp open https 445/tcp open microsoft-ds 795/tcp open unknown 10000/tcp open snet-sensor-mgmt Is this a bug or something? I'm just not finding all that much on the net. I'm looking for dlm_lock port 21064 issues, etc. Mike -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
