unable connect to socket: Connection refused (111) VNC server does not start

[porczynski]

VNC Server doesn't start in Vitualbox Windows host but in Linux host it's fine 😬

After smooth installation by initiv, after reboot, the VNC server not starting and we see the message "unable connect to secket: Connection refused (111)". When I export machine to the Linux host, the VNC server starting ok. ...it shouldn't matter what the host is. 🤔

• I did try delay start vnc viewer in /home/busyman/.config/openbox/autostart
• The VNC Server starts OK manually by: service vncserver start or systemctl start vncserver
• why vncserver service not starting automatically on Windows host only?

[porczynski]

It looks like the VNC server didn't start for the first time only. After manual second reboot, VNC server starts normaly. Check why

[porczynski]

• one interesting dependency: when changed Network config in VB host, the vncserver service not starting even after second ar third reboot. The problem occurs on both: bridged config (wireless network adapter) and NAT config (VB >> settings >> Network) Appliance get DHCP address ok. VNC server does not start

LAB:

• Windows host 2: WYSE DX0Q,GX-415GA/1.5GHz/4GB/SSD60GB/NIC:TP-Link Wireless USB Adapter

[porczynski]

BUG: initiv script durring the intallationprocess changes /etc/systemd/system.conf where the parameter DefaultTimeoutStartSec is changed to 10s. Default Debian value is 90s. ` _* TIP: 10s seems too low value for slower machines._vncserver` service needs more time to start

[porczynski]

/usr/bin/initiv

974 DefaultTimeoutStartSec=90s 975 DefaultTimeoutStopSec=90s ... 995 DefaultTimeoutStartSec=90s 996 DefaultTimeoutStopSec=90s

[porczynski]

commit https://github.com/busy4me/busy/commit/e894076603431cd1f0fb487393cd10a5da7e0e9a