On Fri, Oct 05, 2012 at 06:19:07PM -0500, Paul Dyer wrote:
I have vdsm.conf set for ssl=true. When I run vdsClient from localhost, I get connection refused.
# vdsClient -s localhost list table Connection to localhost:54321 refused # vdsClient -s 0 list table Connection to 172.249.6.135:54321 refused
My host IPADDR is set to a 10. address internally, but I have added an external secondary address to the nic.
# ip addr show 6: xxxx: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN link/ether 14:fe:b5:ca:5a:78 brd ff:ff:ff:ff:ff:ff inet 10.249.6.135/24 brd 10.249.6.255 scope global rhevm inet 172.249.6.135/24 scope global rhevm
From a remote host, the vdsClient works okay.
# vdsClient -s 172.249.6.135 list table 86e03987-8d54-4d1b-af39-85200b959e2f 7268 rh5-royal Up
My question, what could cause ECONNREFUSED from a localhost?
I got this from strace: 16:36:49 connect(3, {sa_family=AF_INET, sin_port=htons(54321), sin_addr=inet_addr("172.249.6.135")}, 16) = -1 ECONNREFUSED (Connection refused) <0.000439>
I would guess that local routing table have 172.249.6.135-bound packet go outside.
what's your `route -n` ?
could you `traceroute 172.249.6.135` ?
which is the ip address bound to vdsm's port 54321? netstat -lntp
Dan.