I have been trying to start a TigerVNC server on port 5901 in order to remote-control the Gnome GUI of our Centos 7 server. However when starting the service using:
Code: Select all
sudo systemctl start vncserver@:1
Code: Select all
[admin@jump001 ~]$ sudo systemctl status vncserver@:1
● vncserver@:1.service - Remote desktop service (VNC)
Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2022-07-07 13:20:38 CEST; 7s ago
Process: 3944 ExecStop=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
Process: 4011 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
Main PID: 4017 (vncserver_wrapp)
CGroup: /system.slice/system-vncserver.slice/vncserver@:1.service
├─4017 /bin/sh /usr/bin/vncserver_wrapper admin :1
└─4329 sleep 0.1
Jul 07 13:20:38 jump001.ipbb.mgt.local systemd[1]: Starting Remote desktop service (VNC)...
Jul 07 13:20:38 jump001.ipbb.mgt.local systemd[1]: Started Remote desktop service (VNC).
Jul 07 13:20:41 jump001.ipbb.mgt.local vncserver_wrapper[4017]: New 'jump001.ipbb.mgt.local:1 (admin)' desktop is jump001.ipbb.mgt.local:1
Jul 07 13:20:41 jump001.ipbb.mgt.local vncserver_wrapper[4017]: Starting applications specified in /home/admin/.vnc/xstartup
Jul 07 13:20:41 jump001.ipbb.mgt.local vncserver_wrapper[4017]: Log file is /home/admin/.vnc/jump001.ipbb.mgt.local:1.log
[admin@jump001 ~]$ sudo systemctl status vncserver@:1
● vncserver@:1.service - Remote desktop service (VNC)
Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2022-07-07 13:20:46 CEST; 4s ago
Process: 4345 ExecStop=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
Process: 4017 ExecStart=/usr/bin/vncserver_wrapper admin %i (code=exited, status=2)
Process: 4011 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
Main PID: 4017 (code=exited, status=2)
Jul 07 13:20:38 jump001.ipbb.mgt.local systemd[1]: Starting Remote desktop service (VNC)...
Jul 07 13:20:38 jump001.ipbb.mgt.local systemd[1]: Started Remote desktop service (VNC).
Jul 07 13:20:41 jump001.ipbb.mgt.local vncserver_wrapper[4017]: New 'jump001.ipbb.mgt.local:1 (admin)' desktop is jump001.ipbb.mgt.local:1
Jul 07 13:20:41 jump001.ipbb.mgt.local vncserver_wrapper[4017]: Starting applications specified in /home/admin/.vnc/xstartup
Jul 07 13:20:41 jump001.ipbb.mgt.local vncserver_wrapper[4017]: Log file is /home/admin/.vnc/jump001.ipbb.mgt.local:1.log
Jul 07 13:20:46 jump001.ipbb.mgt.local vncserver_wrapper[4017]: FATAL: 'vncserver :1' failed to start after 5 seconds!
Jul 07 13:20:46 jump001.ipbb.mgt.local systemd[1]: vncserver@:1.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 07 13:20:46 jump001.ipbb.mgt.local systemd[1]: Unit vncserver@:1.service entered failed state.
Jul 07 13:20:46 jump001.ipbb.mgt.local systemd[1]: vncserver@:1.service failed.
Code: Select all
[admin@jump001 ~]$ cat /home/admin/.vnc/jump001.ipbb.mgt.local:1.log
Xvnc TigerVNC 1.8.0 - built Oct 13 2020 16:13:03
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12004000, The X.Org Foundation
Thu Jul 7 13:20:38 2022
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5901
vncext: created VNC server for screen 0
/home/admin/.vnc/xstartup: line 5: 4055 Terminated /etc/X11/xinit/xinitrc
Killing Xvnc process ID 4049
[admin@jump001 ~]$
Code: Select all
[admin@jump001 ~]$ cat /home/admin/.vnc/xstartup
#!/bin/sh
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
/etc/X11/xinit/xinitrc
#dbus-launch /usr/bin/startx &
# Assume either Gnome or KDE will be started by default when installed
# We want to kill the session automatically in this case when user logs out. In case you modify
# /etc/X11/xinit/Xclients or ~/.Xclients yourself to achieve a different result, then you should
# be responsible to modify below code to avoid that your session will be automatically killed
if [ -e /usr/bin/gnome-session -o -e /usr/bin/startkde ]; then
vncserver -kill $DISPLAY
fi
Code: Select all
[admin@jump001 ~]$ sudo tail /var/log/messages
Jul 7 13:36:59 localhost systemd: Starting Remote desktop service (VNC)...
Jul 7 13:36:59 localhost systemd: Started Remote desktop service (VNC).
Jul 7 13:36:59 localhost systemd: Started Session c6 of user admin.
Jul 7 13:36:59 localhost systemd: Starting Session c6 of user admin.
Jul 7 13:37:02 localhost vncserver_wrapper: New 'jump001.ipbb.mgt.local:1 (admin)' desktop is jump001.ipbb.mgt.local:1
Jul 7 13:37:02 localhost vncserver_wrapper: Starting applications specified in /home/admin/.vnc/xstartup
Jul 7 13:37:02 localhost vncserver_wrapper: Log file is /home/admin/.vnc/jump001.ipbb.mgt.local:1.log
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.068945]: IMSettings-Daemon[4654]: INFO: Starting imsettings-daemon...
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.069156]: IMSettings-Daemon[4654]: INFO: [HOME=/home/admin/.config/imsettings]
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.069231]: IMSettings-Daemon[4654]: INFO: [XINPUTRCDIR=/etc/X11/xinit/]
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.069294]: IMSettings-Daemon[4654]: INFO: [XINPUTDIR=/etc/X11/xinit/xinput.d/]
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.069350]: IMSettings-Daemon[4654]: INFO: [MODULEDIR=/usr/lib64/imsettings]
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.069410]: IMSettings-Daemon[4654]: INFO: [MODULES=gsettings]
Jul 7 13:37:03 localhost org.a11y.Bus: Activating service name='org.a11y.atspi.Registry'
Jul 7 13:37:03 localhost org.a11y.Bus: Successfully activated service 'org.a11y.atspi.Registry'
Jul 7 13:37:03 localhost org.a11y.atspi.Registry: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jul 7 13:37:03 localhost gnome-session: gnome-session-binary[4561]: WARNING: software acceleration check failed: Child process exited with code 1
Jul 7 13:37:03 localhost gnome-session-binary[4561]: WARNING: software acceleration check failed: Child process exited with code 1
Jul 7 13:37:03 localhost journal: Cannot open display:
Jul 7 13:37:03 localhost org.a11y.atspi.Registry: X connection to :1 broken (explicit kill or server shutdown).
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.523999]: IMSettings-Daemon[4654]: INFO: Release the ownership of com.redhat.imsettings
Jul 7 13:37:03 localhost org.gtk.vfs.Daemon: A connection to the bus can't be made
Jul 7 13:37:03 localhost com.redhat.imsettings: Exiting...
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.524303]: GLib-GIO[4654]: CRITICAL **: Error while sending AddMatch() message: The connection is closed
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.524429]: GLib-GIO[4654]: CRITICAL **: Error while sending AddMatch() message: The connection is closed
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.524655]: IMSettings-Daemon[4654]: INFO: Unloading imesttings module: gsettings
Jul 7 13:37:03 localhost com.redhat.imsettings: [ 1657193823.524791]: IMSettings-Daemon[4654]: INFO: imsettings-daemon is shut down.
Jul 7 13:37:08 localhost vncserver_wrapper: FATAL: 'vncserver :1' failed to start after 5 seconds!
Jul 7 13:37:08 localhost systemd: vncserver@:1.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 7 13:37:08 localhost systemd: Unit vncserver@:1.service entered failed state.
Jul 7 13:37:08 localhost systemd: vncserver@:1.service failed.
Jul 7 13:37:14 localhost journal: No devices in use, exit
[admin@jump001 ~]$
Code: Select all
[admin@jump001 ~]$ yum list installed | grep vnc
gtk-vnc2.x86_64 0.7.0-2.el7 @anaconda
gvnc.x86_64 0.7.0-2.el7 @anaconda
tigervnc-icons.noarch 1.8.0-22.el7 @updates
tigervnc-license.noarch 1.8.0-1.el7 @anaconda
tigervnc-server.x86_64 1.8.0-21.el7 installed
tigervnc-server-minimal.x86_64 1.8.0-21.el7 installed
[admin@jump001 ~]$
If anyone has seen this before, or knows what might be wrong looking at the logs, please let me know .