"Unit service entered failed state" When Trying to Start a Properly Configured VNC Service
(Doc ID 2432667.1)
Last updated on AUGUST 16, 2018
Applies to:Oracle Compute Cloud Service - Version N/A and later
Oracle Linux Cloud Service - Version Oracle Linux 7.0 and later
Information in this document applies to any platform.
- Even when the vnc configuration unit file( vncserver_opc@:1.service ) is ok, failed to start VNC service
Aug 07 21:59:14 testx systemd: PID file /home/opc/.vnc/localhost.localdomain:1.pid not readable (yet?) after start.
Aug 07 21:59:14 testx systemd: Failed to start Remote desktop service (VNC).
Aug 07 21:59:14 testx systemd: Unit vncserver_opc@:1.service entered failed state.
Aug 07 21:59:14 testx systemd: vncserver_opc@:1.service failed.
- Occasionally there could be the below error:
Remove This File If There Is No X Server
- The display of the started VNC process (ps -ef|grep vnc) is not the one associated with the one in the configuration
In this example of server testx, the opc user should be able to start VNC with the display number 1, but it wrongly started with 14.
$ ps -fea | grep vnc
opc 2723 1 0 20:20 ? 00:00:00 /usr/bin/Xvnc :14 -auth /home/opc/.Xauthority -desktop testx:14 (opc) -fp catalogue:/etc/X11/fontpath.d -geometry 1024x768 -pn -rfbauth /home/opc/.vnc/passwd -rfbport 5914 -rfbwait 30000 ps -fea | grep vnc
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document