VNC Remote Access

afclark82 · 02-05-2020, 09:29 PM

I have the following setup:
- Server: Centos 7.7, with Gnome, & SSH
- Laptop: Windows 10

I am trying to set up tunneling using SSH user to a VNC Viewer. The server has very base set up and I need to be able to set up an FTP and GUI using Gnome. I have been following the link below using Digital Ocean and keep running into error messages.

https://www.digitalocean.com/communi...op-on-centos-7

At the end of Step 6, when the configuration is complete I run sudo systemctl restart vncserver@:4.service on the centos user. The output gives the following error:

Code:

Job for vncserver@:4.service failed because a configured resource limit was exceeded. See "systemctl status vncserver@:4.service" and "journalctl -xe" for details.

Then the status shows:

Code:

vncserver@:4.service - Remote desktop service (VNC)
   Loaded: loaded (/etc/systemd/system/vncserver@:4.service; enabled; vendor preset: disabled)
   Active: failed (Result: resources) since Thu 2020-02-06 03:26:49 UTC; 1min 58s ago
  Process: 6028 ExecStart=/usr/sbin/runuser -l aclark2 -c /usr/bin/vncserver %i (code=exited, status=0/SUCCESS)
  Process: 6022 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)

Feb 06 03:26:45 healportal.novalocal systemd[1]: Starting Remote desktop service (VNC)...
Feb 06 03:26:49 healportal.novalocal systemd[1]: New main PID 6061 does not belong to service, and PID file is not owned by root. Refusing.
Feb 06 03:26:49 healportal.novalocal systemd[1]: New main PID 6061 does not belong to service, and PID file is not owned by root. Refusing.
Feb 06 03:26:49 healportal.novalocal systemd[1]: Failed to start Remote desktop service (VNC).
Feb 06 03:26:49 healportal.novalocal systemd[1]: Unit vncserver@:4.service entered failed state.
Feb 06 03:26:49 healportal.novalocal systemd[1]: vncserver@:4.service failed.

Any help you can provide would be greatly appreciated.

berndbausch · 02-06-2020, 12:15 AM

There is a log file in the user's .vnc directory.

afclark82 · 02-06-2020, 08:02 AM

Here is the log.

Code:

Thu Feb  6 03:26:13 2020
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5901
 vncext:      created VNC server for screen 0
touch: cannot touch ‘/home/aclark2/.cache/imsettings/log’: No such file or directory

(process:3207): dconf-CRITICAL **: 03:26:16.386: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:3207): dconf-CRITICAL **: 03:26:16.387: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

Thu Feb  6 03:26:16 2020
 ComparingUpdateTracker: 0 pixels in / 0 pixels out
 ComparingUpdateTracker: (1:-nan ratio)

berndbausch · 02-06-2020, 04:02 PM

I don't know what these messages mean. Now it's time to use your most powerful tool, the internet browser combined with a search engine, and to figure out if the messages are related to the problem and what causes them.

Another potential information source is the systemd journal for the vncserver service.

afclark82 · 02-06-2020, 04:09 PM

Quote:

Originally Posted by berndbausch

I don't know what these messages mean. Now it's time to use your most powerful tool, the internet browser combined with a search engine, and to figure out if the messages are related to the problem and what causes them.

Another potential information source is the systemd journal for the vncserver service.

Unfortunately I have been trying that for weeks and can't figure it out... This was my last resort.

berndbausch · 02-06-2020, 04:52 PM

imsettings is software that provides input methods to applications, mostly for languages that don't have a 1-1 correspondence between key and character, such as Japanese or Chinese.

dconf is a low-level configuration system and settings management tool for Gnome.

Something is wrong in the way you set up your X environment in VNC. There should be a script in the .vnc directory that customizes your environment. I would look there.

Also, the access permissions problem with dconf seems to be common. Here is a workaround: remove the file or fix its permissions.

EDIT: I know very little about X11 and Gnome. My only marketable skill is searching.