VNC Wiki Update - Have you got VNC working?

[wyldeone]

Question.

As I go through this, when I enter "cd ~/.vnc" (Setup Desktop Environment Access section), it responds that the directory does not exist. What am I missing?

The problem is that the ~/.vnc folder does not get created until the service is started, i have modified the wiki to reflect the correct sequence and instructions to creating the folder with the necessary files.

[wyldeone]

Bigfoot

I have complete the wiki page, I have tested everything I have put into but would be nice if people can test it out just to make sure i've not missed anything.

[bigfoot65]

Great and thanks! Yes it will be a trial and error of the guidance by users as you have already seen. It will just have to be updated over time. I will try to post an announcement on FB soon to get more attention.

[mjclarke]

Please could you let know which one creates the folder.

[ Post made via iPad ]

Well, I feel dumb. I missed the "systemctl daemon-reload" command in the wiki. When I did that, all went fine from there. Now, I can connect via my VPN client, but it doesn't connect if I use my server IP (connection refused), only when using HDA:1.

Thanks, wiki was overall easy to follow and clear, nice job!

UPDATE: Now I'm really dumb. "IP address:1" works, missed that part too in the wiki. I need a vacation!

[bigfoot65]

wyldeone:

As promised, it has been announced on FaceBook and Twitter. Keep up the great work and thanks so much for all your effort! This one was badly needed.

[droth49]

I have been following he development of the Wiki Update and am have found this problem, or is it my setup? Not sure if this is the right way to present this, if no I will take the 30 lashs and learn. This is the script from my command line when I tried to start the server:

[root@localhost droth49]# systemctl start vncserver@:l.service
Job for vncserver@:l.service failed. See 'systemctl status vncserver@:l.service' and 'journalctl -xn' for details.
[root@localhost droth49]# systemctl status vncserver@:l.service
vncserver@:l.service - Remote desktop service (VNC)
Loaded: loaded (/usr/lib/systemd/system/vncserver@:l.service; disabled)
Active: failed (Result: exit-code) since Sat 2014-01-04 15:50:03 CST; 49s ago
Process: 1168 ExecStart=/usr/bin/vncserver %i (code=exited, status=2)
Process: 1167 ExecStartPre=/usr/bin/vncserver -kill %i (code=exited, status=2)

Jan 04 15:50:03 localhost.localdomain systemd[1]: Starting Remote desktop ser...
Jan 04 15:50:03 localhost.localdomain vncserver[1167]: vncserver: The HOME en...
Jan 04 15:50:03 localhost.localdomain vncserver[1168]: vncserver: The HOME en...
Jan 04 15:50:03 localhost.localdomain systemd[1]: vncserver@:l.service: contr...
Jan 04 15:50:03 localhost.localdomain systemd[1]: Failed to start Remote desk...
Jan 04 15:50:03 localhost.localdomain systemd[1]: Unit vncserver@:l.service e...


[root@localhost droth49]# journalctl -xn
-- Logs begin at Mon 2013-12-23 21:36:59 CST, end at Sat 2014-01-04 15:50:17 CST
Jan 04 15:45:39 localhost.localdomain su[1126]: pam_unix(su:session): session op
Jan 04 15:50:01 localhost.localdomain CROND[1162]: (root) CMD (/usr/lib64/sa/sa1
Jan 04 15:50:03 localhost.localdomain systemd[1]: Starting Remote desktop servic
-- Subject: Unit vncserver@:l.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit vncserver@:l.service has begun starting up.
Jan 04 15:50:03 localhost.localdomain vncserver[1167]: vncserver: The HOME envir
Jan 04 15:50:03 localhost.localdomain vncserver[1168]: vncserver: The HOME envir
Jan 04 15:50:03 localhost.localdomain systemd[1]: vncserver@:l.service: control
Jan 04 15:50:03 localhost.localdomain systemd[1]: Failed to start Remote desktop
-- Subject: Unit vncserver@:l.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar ... alog/be02c
--
-- Unit vncserver@:l.service has failed.
--
-- The result is failed.
Jan 04 15:50:03 localhost.localdomain systemd[1]: Unit vncserver@:l.service ente
Jan 04 15:50:17 localhost.localdomain systemd[1]: Starting Cleanup of Temporary
-- Subject: Unit systemd-tmpfiles-clean.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Jan 04 15:50:17 localhost.localdomain systemd[1]: Started Cleanup of Temporary D
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-tmpfiles-clean.service has finished starting up.
--
-- The start-up result is done.

Have I done something wrong? What should I do to correct this?

[bigfoot65]

The answer is probably in the systemctl status vncserver@:l.service output. It is not fully displayed here, so if you could add it, would be helpful.

The important lines are cut off as ...

[wyldeone]

droth49

Please can you post me a copy of you vncserver@:1.service file.

Also from your command below

[root@localhost droth49]# systemctl start vncserver@:l.service
Job for vncserver@:l.service failed. See 'systemctl status vncserver@:l.service' and 'journalctl -xn' for details.[root@localhost droth49]# systemctl start

looks like you have a typo, it is meant to be a number after @ not a letter. Should be the vncserver@:<number>.service

[droth49]

Was having trouble with that. Could not make out weather it was a 1 or l. Will go back and edit the areas this occurs in and try again. Thank, hopefully it will start!

[bigfoot65]

Yea always best to stay away from using "1" or "l" as they look too similar. Recommend the wiki be updated to either show "2" or somewhere indicate "1" is one.