Display's on vm's intermittently working.

Ry-Guy

Cadet
Joined
Mar 6, 2023
Messages
7
Whenever I try to connect to the vm display I get a 503 error. I narrowed it down to an issue with haproxy, but when I try to restart the haproxy service I get these errors


Broadcast message from systemd-journald@Milky-Way (Thu 2023-11-16 13:41:14 EST):
haproxy[259967]: backend be_20 has no server available!
Broadcast message from systemd-journald@Milky-Way (Thu 2023-11-16 13:41:14 EST):
haproxy[259967]: backend be_26 has no server available!
Broadcast message from systemd-journald@Milky-Way (Thu 2023-11-16 13:41:14 EST):
haproxy[259967]: backend be_27 has no server available!
Broadcast message from systemd-journald@Milky-Way (Thu 2023-11-16 13:41:14 EST):
haproxy[259967]: backend be_30 has no server available!
Broadcast message from systemd-journald@Milky-Way (Thu 2023-11-16 13:41:14 EST):
haproxy[259967]: backend be_33 has no server available!
Broadcast message from systemd-journald@Milky-Way (Thu 2023-11-16 13:41:15 EST):
haproxy[259967]: backend be_39 has no server available!
Broadcast message from systemd-journald@Milky-Way (Thu 2023-11-16 13:41:15 EST):
haproxy[259967]: backend be_45 has no server available!
Broadcast message from systemd-journald@Milky-Way (Thu 2023-11-16 13:41:15 EST):
haproxy[259967]: backend be_48 has no server available!

The display will occasionally come back after a restart or just randomly throughout the day. Any help getting the mv displays to stay up would be greatly apreciated.
 
Top