Redhat cluster: port 1229 is not listening in KVM host for fence_virtd daemon but service is running
Hi! port 1229 is not listening in KVM host for fence_virtd daemon but service is running while setting up redhat clustering in 6.4
node1.public.cluster2.example.com.ssh > desktop.public.cluster2.example.com.43170: Flags [P.], seq 1055079231:1055079423, ack 3914263096, win 350, options [nop,nop,TS val 8684704 ecr 8312002], length 192
18:38:47.589497 IP desktop.public.cluster2.example.com.43170 > node1.public.cluster2.example.com.ssh: Flags [.], ack 192, win 176, options [nop,nop,TS val 8312011 ecr 8684704], length 0
18:38:49.275940 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:38:50.498208 IP node1.public.cluster2.example.com.33816 > 225.0.0.12.zented: UDP, length 176
18:38:50.498411 IP node1.public.cluster2.example.com.46222 > desktop.public.cluster2.example.com.domain: 10319+ PTR? 12.0.0.225.in-addr.arpa. (41)
18:38:50.498505 IP desktop.public.cluster2.example.com.domain > node1.public.cluster2.example.com.46222: 10319 Refused 0/0/0 (41)
18:38:50.498543 IP node1.public.cluster2.example.com.59668 > desktop.public.cluster2.example.com.domain: 10319+ PTR? 12.0.0.225.in-addr.arpa. (41)
18:38:50.498582 IP desktop.public.cluster2.example.com.domain > node1.public.cluster2.example.com.59668: 10319 Refused 0/0/0 (41)
18:38:51.275900 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:38:52.501950 IP node1.public.cluster2.example.com.43138 > 225.0.0.12.zented: UDP, length 176
18:38:53.276007 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:38:54.505936 IP node1.public.cluster2.example.com.56392 > 225.0.0.12.zented: UDP, length 176
18:38:55.276014 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:38:56.509830 IP node1.public.cluster2.example.com.43291 > 225.0.0.12.zented: UDP, length 176
18:38:57.275961 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:38:58.513806 IP node1.public.cluster2.example.com.53366 > 225.0.0.12.zented: UDP, length 176
18:38:59.276023 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:00.517821 IP node1.public.cluster2.example.com.33651 > 225.0.0.12.zented: UDP, length 176
18:39:01.276025 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:02.520989 IP node1.public.cluster2.example.com.42282 > 225.0.0.12.zented: UDP, length 176
18:39:03.276017 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:04.524858 IP node1.public.cluster2.example.com.53838 > 225.0.0.12.zented: UDP, length 176
18:39:05.275985 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:06.528787 IP node1.public.cluster2.example.com.33783 > 225.0.0.12.zented: UDP, length 176
18:39:07.276047 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:08.532794 IP node1.public.cluster2.example.com.41862 > 225.0.0.12.zented: UDP, length 176
18:39:09.276237 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:10.536723 IP node1.public.cluster2.example.com.34356 > 225.0.0.12.zented: UDP, length 176
18:39:11.276008 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:12.540770 IP node1.public.cluster2.example.com.55302 > 225.0.0.12.zented: UDP, length 176
18:39:13.275947 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:14.544707 IP node1.public.cluster2.example.com.50200 > 225.0.0.12.zented: UDP, length 176
18:39:15.275955 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:16.548640 IP node1.public.cluster2.example.com.42327 > 225.0.0.12.zented: UDP, length 176
18:39:17.275989 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:18.552292 IP node1.public.cluster2.example.com.38542 > 225.0.0.12.zented: UDP, length 176
18:39:19.276007 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:21.275999 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:23.275987 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:25.275900 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:27.275905 STP 802.1d, Config, Flags [none], bridge-id 8000.52:54:00:3a:90:cf.8005, length 35
18:39:28.560988 IP desktop.public.cluster2.example.com.43170 > node1.public.cluster2.example.com.ssh: Flags [P.], seq 1:49, ack 192, win 176, options [nop,nop,TS val 8352983 ecr 8684704], length 48
Responses
ServiceNxt,
I would start by running the following as root on the server
netstat -lnp --inet
This will list all listening ports and their associated services. Look in this list under the PID/Program Name for your fence_virtd process (or associated processes) and see if it is listening (may be listening only on localhost for example)
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
