Websockify timeout?

Get Help
1

OoD version - 3.1.1

The session will attempt to start the desktop, it will eventually timeout and change to completed.
Clicking the arrows again on that same job to relaunch results in a successful desktop launch.

I’m seeing the following in the log.
Launching desktop ‘mate’…
No such schema “org.mate.screensaver”
[websockify]: pid: 9270 (proxying 40636 ==> localhost:5901)
[websockify]: log file: ./websockify.log
[websockify]: waiting …
[websockify]: timed-out :(!
Cleaning up…
Killing Xvnc process ID 9218
Xvnc seems to be deadlocked. Kill the process manually and then re-run
/opt/TurboVNC/bin/vncserver -kill :1
to clean up the socket files.

Is this indicating that websockify isn’t starting in time ?
Since websockify never starts the websockify.log is empty.

Thank you.

2

I’m sure there is a better way to fix this, but this seemed to work.
Changed to 10seconds -/opt/ood/ondemand/root/usr/share/gems/3.1/ondemand/3.1.1-1/gems/ood_core-0.24.2/lib/ood_core/batch_connect/templates/vnc.rb

              elif [ $counter -ge **10** ]; then
                # timeout after ~5 seconds
                echo "[websockify]: timed-out :(!" >&2
3

Thanks for taking the time to fix it on your side. I’ll take a look at the library and see what we can do.

1 Like
4

If 10 works for you, then I’ll just increase the timeout to 10 on our side too.

5

It’s rare but I have found it would fail on 10 on slower servers.
Maybe 15 or 20 is the way to go. Can’t hurt either way.

Thanks for the quick response and a fantastic tool!

1 Like
6

I wonder if there’s more to this if it takes more than 10 seconds to boot up…

7

The use case is a bit different here vs. physical servers.
This is in AWS using EC2s so boot up time will be extended if the EC2 isn’t already up. EC2s are terminated after each job so generally speaking a new server is booting up each time.

8

I had the same issue with OOD 3.1.4.
I solved the issue by setting the timeout to 10 seconds.
This may be caused by using a slow ARM CPU.