![]() ![]() If you are an organization using Chocolatey, we want your experience to be fully reliable.ĭue to the nature of this publicly offered repository, reliability cannot be guaranteed. Human moderators who give final review and sign off.Security, consistency, and quality checking.ModerationĮvery version of each package undergoes a rigorous moderation process before it goes live that typically includes: Jul 31 14:38:01. systemd: Failed to start Remote desktop service (VNC).Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community. ![]() ![]() Jul 31 14:38:01. systemd: :2.service: Failed with result ‘protocol’. Jul 31 14:38:01. systemd: :2.service: 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 (/etc/systemd/system/ :2.service enabled vendor preset: disabled)Īctive: failed (Result: protocol) since Fri 14:38:01 EDT 3min 1s ago :2.service – Remote desktop service (VNC) May 17 09:45:47 OptiPlex-380 systemd: :3.service failed.Īny hints? I’ve checked the forums I could find, with no clue. May 17 09:45:47 OptiPlex-380 systemd: Unit :3.service 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: :3.service: 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 (/etc/systemd/system/ :3.service disabled vendor preset: disabled)Īctive: failed (Result: exit-code) since Tue 09:45:47 AEST 44s ago :3.service – Remote desktop service (VNC).See “systemctl status :3.service” and “journalctl -xe” for details. Job for :3.service 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. ~]# Step:6 Access Remote Desktop Session. Ln -s '/etc/systemd/system/ :3.service' '/etc/systemd/system// :3.service' 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. Replace 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/ /etc/systemd/system/ :3.service 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”. While Copying the VNC config file we can mention the port number on which we want VNC service to be listen. ~]# 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 “/etc/systemd/system/. ~]# yum groupinstall "GNOME Desktop" Step:2 Install Tigervnc and other dependency Package.
0 Comments
Leave a Reply. |