NoVNC fails on one node

[GodZone]

I have a 3 node cluster, from two of the nodes I can bring up a console on any VM but from the 3rd, I get the error "Failed to connect to server". On the node I see the following in /var/log/syslog

May 1 10:41:16 agree-92 pvedaemon[21925]: <geustace@pam> starting task UPID:agree-92:00004100:5E209DB3:5AE79B8C:vncproxy:126:geustace@pam:
May 1 10:41:16 agree-92 pvedaemon[16640]: starting vnc proxy UPID:agree-92:00004100:5E209DB3:5AE79B8C:vncproxy:126:geustace@pam:
May 1 10:41:16 agree-92 pvedaemon[16640]: Failed to run vncproxy.
May 1 10:41:16 agree-92 pvedaemon[21925]: <geustace@pam> end task UPID:agree-92:00004100:5E209DB3:5AE79B8C:vncproxy:126:geustace@pam: Failed to run vncproxy.
May 1 10:41:31 agree-92 pvedaemon[12426]: <root@pam> successful auth for user 'geustace@pam'

But I can't seem to find any additional information that gives any clue as to why running vncproxy fails. If someone can give me some help as to how to diagnose this issue it would be much appreciated.

pve-manager/5.0-30/5ab26bc (running kernel: 4.10.17-2-pve)

 

[dcsapak]

pve-manager/5.0-30/5ab26bc (running kernel: 4.10.17-2-pve)

first, please update, that version is very old, then try again if it still does not work, you can double click on the console task in the webgui and see if there are any more error messages

 

[GodZone]

I agree that 5.0 is not the most recent version but I'd hardly say it is 'very old'. The node that I cant get a console on was the last one added to the cluster, so I am wondering if I missed something when I did the build. This is a production cluster and I am not in a position to upgrade at this time.