Hey all we are using some AP7920's as a fence device. This has been working out pretty good until our latest cluster. It seems to only effect clusters with pve 3.2, I don't have any 3.1 installs anymore, but I have 7 pve 2.3's and none of those nodes have issues. On our new cluster we get this when trying to access the pdu with fence_apc root@fpracprox1:~# fence_apc -x -l device -p medent168 -a 10.80.5.48 -o status -n 1 -vvUnable to connect/login to fencing deviceThe Unable to connect/login to fencing device returns within 1 second of issuing the command, adding an additional timeout doesn't help at all. I have also tried disabling sshv1, disabling sshv2, and having them both enabled, all with the same results. Now I can get on another server here in house and run the same command. This server is running the exact same version of pve and packages as the one above.root@supprox2:~# fence_apc -x -l device -p medent168 -a 10.80.5.48 -o status -n 1 -vvdevice@10.80.5.48's password:As you can see I get the password prompt it provides the password and I get a status of OK, exactly what I want to see. I then move onto the second node of this very same cluster and get the Unable to connect issue. Just like before it returns almost instantly so I don't think its a timeout issue.root@supprox1:~# fence_apc -x -l device -p medent168 -a 10.80.5.48 -o status -n 1 -vvUnable to connect/login to fencing deviceOne thing I have pinned down is this is only an issue on pve 3.2 clusters. I have 7 pve 2.3 clusters and not a single node has an issue with fence_apc. I am stumped at this point, unsure what to try next, but I do feel its something realted to proxmox. We have unboxed/configured 3 brand new PDU's all with the same results. I think we have 10 or so in stock to try, but I don't think its a PDU issue.
Last edited: