There relevant logs should be before these messages, specifically about vncerver starting (or not starting in your case). vncserver starts, it setsup the environment and we capture the
$DISPLAY then run the sub shell (
mate.sh in this case) setting DISPLAY in the command. That’s one of the main things that needs to happen in
Here’s the relevant snippet from my logfile. vncserver started with DISPLAY
# this is the very first line in output.log Restoring modules from user's default, for system: "owens" Setting VNC password... Starting VNC server... Killing Xvnc process ID 91037 Xvnc process ID 91037 already killed Xvnc did not appear to shut down cleanly. Removing /tmp/.X11-unix/X12 Xvnc did not appear to shut down cleanly. Removing /tmp/.X12-lock Warning: o0808.ten.osc.edu:1 is taken because of /tmp/.X1-lock Remove this file if there is no X server o0808.ten.osc.edu:1 # ... removed for brevity Desktop 'TurboVNC: o0808.ten.osc.edu:14 (johrstrom)' started on display o0808.ten.osc.edu:14 and it was the first bit out output in the logfile. Log file is vnc.log Successfully started VNC server on o0808.ten.osc.edu:5914... Script starting...