Linux - Debian Variant - Can't start server.


I can't get REAL VNC Server started on my Linux box.

Where I type in the following:

sudo systemctl start vncserver-x11-serviced.service

I get the following:

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

Anyone have any ideas how I can get around the problem?




  • Okay, I've sussed this out.

    This command work:    sudo systemctl enable vncserver-x11-serviced.service  

    This command fails:     sudo systemctl start vncserver-x11-serviced.service

    Ignore it. 

    In theory the service will start up at boot time.  But just in case, do the following.

    Assuming, being a Linux user, that you have added a line to your /etc/rc.local script that points to a login / startup script somewhere in your home user folder, then add the following lines to the your said, login / startup script.

    That should ensure it starts up

    if pgrep -x vncserver-x11-s >/dev/null
        echo "VNC Service vncserver-x11-serviced is Running..."
        echo "VNC Service vncserver-x11-serviced is NOT Running..."
        echo "Starting VNC Service vncserver-x11-serviced..."






    Comment actions Permalink
  • Hi Michael,

    I shuttle between two homes over a thousand kms apart. In both locations I have a couple of headless Raspberry Pi's running VNC server and monitoring things like temperature or electricity consumption. I occasionally hit a message "VNC server not listening to cloud connection" which makes it impossible for me to remote access Location A when I am in Location B ... until I can physically travel there and reboot the RPis.

    The disconnection seems due to either a temporary outage of the VNC cloud, or disruptions in internet connection at home. Either way, my RPis (running Raspberry OS, a Debian variant) seem unable to re-establish the VNC server-cloud link. Any solution?

    Comment actions Permalink
  • Hi Philippe

    A different issue in my case. 

    My Laptop runs Knoppix and it is not quite compatible with the way VNC likes to work.

    So I had to put a hack in place to ensure that VNC starts up. 

    Generally VNC Starts up at boot time, but the hack ensures that it restarts if VNC failed on boot up.  I also installed a cron task to check and restart as necessary incase VNC falls over.

    Funny though.  I have a headless RPI Cluster with 10 nodes and 26 cores.  And I also use VNC to connect to it to check the Node temperatures on the cluster.

    Cheers Mate

    Michael Blucher



    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post