Jul 31 14:38:01. systemd: Failed with result ‘protocol’. Jul 31 14:38:01. systemd: Can’t open PID file /home/copuser/.vnc/.:2.pid (yet?) after start: No such file or directory Jul 31 14:37:58. systemd: Starting Remote desktop service (VNC)… Process: 5810 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill :2 > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Process: 5814 ExecStart=/sbin/runuser -l copuser -c /usr/bin/vncserver :2 -geometry 1280×1024 (code=exited, status=0/SUCCESS) Loaded: loaded enabled vendor preset: disabled)Īctive: failed (Result: protocol) since Fri 14:38:01 EDT 3min 1s ago May 17 09:45:47 OptiPlex-380 systemd: failed.Īny hints? I’ve checked the forums I could find, with no clue. May 17 09:45:47 OptiPlex-380 systemd: Unit entered failed state. May 17 09:45:47 OptiPlex-380 systemd: Failed to start Remote desktop service (VNC). ![]() May 17 09:45:47 OptiPlex-380 systemd: control process exited, code=exited status=2 ![]() May 17 09:45:47 OptiPlex-380 systemd: Starting Remote desktop service (VNC)… ![]() Process: 1232 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Process: 1238 ExecStart=/usr/sbin/runuser -l david -c /usr/bin/vncserver %i (code=exited, status=2) Loaded: loaded disabled vendor preset: disabled)Īctive: failed (Result: exit-code) since Tue 09:45:47 AEST 44s ago ~]# systemctl status – Remote desktop service (VNC) See “systemctl status and “journalctl -xe” for details. ~]# systemctl start for failed because the control process exited with error code. I did everything Exactly by the book, and ended here: :~$ vncviewer 192.168.1.15:3Įnter the VNC password that we have set in above step, after validating the authentication Remote Desktop session will start.Įnter the VNC Server IP Address and Port Number and then Click on OKĮnter the VNC Password & then click on OK.ĭesktop Session Will start after authentication. ~]# systemctl start ~]# systemctl enable -s ~]# Step:6 Access Remote Desktop Session. Start and Enable the VNC Service at boot.Įxecute below commands as root only. Switch to the user (linuxtechi) and run vncserver command to set the password as shown below : ~]# Step:5 Set the VNC password for the User. ~]# firewall-cmd -permanent -zone=public -add-port=5903/tcp Set the Firewall Rule if firewall is enabled on your linux box. In my case linuxtechi user will able to control and manage its desktop session using remote VNC clients. ~]# vi the “linuxtechi” user as per your requirement. So while Connecting to the VNC server We can specify port number as or ~]# cp /lib/systemd/system/ Step:4 Update the User’s Information in the Config File In my case i am using port 3, it means VNC will listen on “5903”. ~]# yum install tigervnc-server xorg-x11-fonts-Type1 Step:3 Setup VNC Server Configuration File.Ĭopy the VNC config file “/lib/systemd/system/ ” to the Copying the VNC config file we can mention the port number on which we want VNC service to be listen. opening up port 5901 on the server).~]# yum groupinstall "GNOME Desktop" Step:2 Install Tigervnc and other dependency Package. As long as the SSH port has been opened, you shouldn’t have to configure anything else (e.g. Remmina is convenient because it handles the SSH tunnel. Enter the SSH settings under the SSH Tunnel tab. COMPUTERNAME.local:1, :1 corresponds to the display number above). Enter the VNC connection settings under the basic tab (e.g. If using Ubuntu 20.04 as the client machine, Remmina (a VNC client) is installed by default. Sudo systemctl enable systemctl start systemctl status Connect Using Remmina VNC Client sudo mkdir /etc/vncĮxecStart=/usr/bin/vncserver -fg -depth 24 -geometry 1920x1200 -localhost no :%i This will create the typical Ubuntu desktop. & xrdb $HOME/.Xresources chmod 755 xstartupĬreate /etc/vnc/xstartup, edit the file, make executable. The fix comes from this post.Ĭreate ~/.vnc/xstartup, edit the file, make executable cd ~/.vnc Instructions found in other tutorials might work if you manually start the VNC server, but you will get a black screen if starting it as a service with GNOME (although it works with XFCE4). We want to run the VNC server as a system service (starts at boot), using GNOME (i.e. Vncserver -kill :1 Configure the VNC Server Test the installation by starting and then killing the server. TigerVNC supports virtual displays, is an active successor to TIghtVNC, and is easy to install from the Ubuntu repositories sudo apt install tigervnc-standalone-server Others can support virtual (remote) displays that are truly headless. controlling the visible logged-in desktop). Some VNC servers only support local VNC sessions (i.e. It was easy to set up a local VNC session, but going headless without a dummy adapter AND with the GNOME desktop was a challenge. no monitor plugged in) for Ubuntu 20.04 using GNOME was harder than anticipated. Creating a headless virtual VNC session (i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |