[Solved]Error: Connection Error 595: Connection refused

ygolonac

New Member
Jan 21, 2014
11
0
1
Hello, I installed a cluster with two nodes (Prox1 and Prox2) in unicast mode.

when I access the gui of Prox1 I can not see or install anything on node 2 and vice versa equal, if I access next2 I can not do anything in prox 1. Tells me:

Error: Connection Error 595: Connection refused

thank you very much

root@prox1:~# cat /etc/pve/cluster.conf
<?xml version="1.0"?>
<cluster name="TELCAT" config_version="5">


<cman keyfile="/var/lib/pve-cluster/corosync.authkey" transport="udpu">
</cman>


<clusternodes>
<clusternode name="prox2" votes="1" nodeid="1"/>
<clusternode name="prox1" votes="1" nodeid="2"/></clusternodes>


</cluster>


root@prox1:~# pvecm status
Version: 6.2.0
Config Version: 5
Cluster Name: TELCAT
Cluster Id: 4882
Cluster Member: Yes
Cluster Generation: 300
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: prox1
Node ID: 2
Multicast addresses: 255.255.255.255

root@prox1:~# pvecm nodes
Node Sts Inc Joined Name
1 M 300 2014-01-21 23:58:22 prox2
2 M 296 2014-01-21 23:57:57 prox1

error.png
 
Last edited:
Re: Error: Connection Error 595: Connection refused

Yes, both nodes ara "green" and i see storange and vm in left side, baut when i do "click" in the node or vm: Connection Error 595: Connection refused

the accés log:

213.96.32.175 - root@pam [22/Jan/2014:08:12:16 +0100] "GET /api2/json/nodes/prox2/openvz/100/status/current HTTP/1.1" 200 338
213.96.32.175 - root@pam [22/Jan/2014:08:12:17 +0100] "GET /api2/json/nodes/prox2/openvz/100/config HTTP/1.1" 200 341
213.96.32.175 - root@pam [22/Jan/2014:08:12:18 +0100] "GET /api2/json/nodes/prox2/openvz/100/status/current HTTP/1.1" 200 337
213.96.32.175 - root@pam [22/Jan/2014:08:12:18 +0100] "GET /api2/json/cluster/resources HTTP/1.1" 200 697
213.96.32.175 - root@pam [22/Jan/2014:08:12:18 +0100] "GET /api2/json/cluster/tasks HTTP/1.1" 200 1318
213.96.32.175 - root@pam [22/Jan/2014:08:12:21 +0100] "GET /api2/json/nodes/prox1/tasks?errors=0&start=0&limit=500 HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:21 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:21 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:22 +0100] "GET /api2/json/cluster/resources HTTP/1.1" 200 699
213.96.32.175 - root@pam [22/Jan/2014:08:12:22 +0100] "GET /api2/json/cluster/tasks HTTP/1.1" 200 1318
213.96.32.175 - root@pam [22/Jan/2014:08:12:22 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:24 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:26 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:26 +0100] "GET /api2/json/cluster/tasks HTTP/1.1" 200 1318
213.96.32.175 - root@pam [22/Jan/2014:08:12:27 +0100] "GET /api2/json/cluster/resources HTTP/1.1" 200 697
213.96.32.175 - root@pam [22/Jan/2014:08:12:27 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:29 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:30 +0100] "GET /api2/json/cluster/resources HTTP/1.1" 200 695
213.96.32.175 - root@pam [22/Jan/2014:08:12:30 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:31 +0100] "GET /api2/json/cluster/tasks HTTP/1.1" 200 1318
213.96.32.175 - root@pam [22/Jan/2014:08:12:32 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:33 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:34 +0100] "GET /api2/json/cluster/resources HTTP/1.1" 200 695
213.96.32.175 - root@pam [22/Jan/2014:08:12:34 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
213.96.32.175 - root@pam [22/Jan/2014:08:12:35 +0100] "GET /api2/json/cluster/tasks HTTP/1.1" 200 1318
213.96.32.175 - root@pam [22/Jan/2014:08:12:36 +0100] "GET /api2/json/nodes/prox1/status HTTP/1.1" 595 -
 
Re: Error: Connection Error 595: Connection refused

what is the output of:

# cat /etc/pve/.members
 
Re: Error: Connection Error 595: Connection refused

{
"nodename": "prox2",
"version": 5,
"cluster": { "name": "TELCAT", "version": 5, "nodes": 2, "quorate": 1 },
"nodelist": {
"prox2": { "id": 1, "online": 1, "ip": "x.x.x.x"},
"prox1": { "id": 2, "online": 1, "ip": "x.x.x.x"}
}
}

The ips ara correct
 
Re: Error: Connection Error 595: Connection refused

I have this issue as well. I can see some of the graphs for a Host when logged into the other host of the cluster, but I can't see the summary.
I think it has something to do with multicast since this is the only server not located on the exact same switch, however, I'm not sure.
prox_no_route.PNG
When I am logged into zwtProx1 - 2 - 3 I cannot access zwtTEST.
And when I am in zwtTEST, I cannot access zwtProx1 - 2 - 3. zwtTEST is the only host not on the same physical switch, however, zwtTEST is connect via an unmanaged switched.
 
Re: Error: Connection Error 595: Connection refused

Hi, my two nodes are in the same switch and not use multicast. Use unicast. My error is "Connection refused" and your error is "no route to host"

I don't find the problem.

any idea?
 
Re: Error: Connection Error 595: Connection refused

i can't. In the datacenter don't permit multicast i the switch :(
I make test with 2 server in my office and work fine in unicast.
 
Re: Error: Connection Error 595: Connection refused

Hi, i don't find the problem...

I check all! any idea?
do you believe that it can be a problem whit the swicth? The problem is exclusive in pveproxy. The cluster, the corosync works fine.
 
Re: Error: Connection Error 595: Connection refused

Hi I had the same problem, please check /etc/hosts at every node you have in cluster. IP address in hosts file must be same as real IP on machine. My problem was that I changed IPs after installation proxmox on nodes.
 
Re: Error: Connection Error 595: Connection refused

the problem was the switch. Arrrrrrrr!!!
 
Unfortunately I ran into this error too.
I like to run a two node cluster in a hosted environment.
Good news: the cluster is running both nodes are "green" in the webgui, pvecm status looks good etc etc

both nodes have two interfaces, one facing the public internet, and one connected via a crosslink cabel to the other host (10G)
I created the cluster with:

pvecm create <clustername> --bindnet0_addr <ip> --ring0_addr <ip>

directing the cluster internal traffic to the cross linked interface

the firewall allows all traffic between these both (cross linked) interfaces AND all traffic between the two external addresses
IGMP is accepted between the the cross linked interfaces.

Now when I log into the webgui of host A there are both hosts marked "green" on the left menu,
when I click on host A everything works as expected (attributes are displayed in the main window)
when I click on host B I get the "Connection Error 595: Connection refused"
(AND vice versa, I can log into webgui of host B but from there can't access host A)

I have multicast ONLY between then cross linked interfaces,
my provider doesn't allow multicast over the external addresses.

Might the be the reason (and if so that would be ... sad and bad ;-) ?
Or do I miss any special config operation to make it work?

Any hint is appreciated!

TIA
 
Is there no way to get this working?
As mentioned I have the two systems connected via a crosslink cabel and only the ip address of those interfaces configured as
--bindnet0_addr <ip> --ring0_addr <ip>
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!