Ed Greshko wrote: >> HOWEVER, when I connect with "vncviewer server::5901", I get a blank >> screen with a momentary F8 prompt. I do not see the normal greeting >> screen. Something is still missing. > Then I noticed one thing which seems off or odd do me. > > When you do "systemctl -l status xvnc.socket" you system is outputting > 2 lines. > > Jul 10 14:10:50 server systemd[1]: Listening on XVNC Server. > Jul 10 14:10:50 server systemd[1]: Starting XVNC Server. > > My system outputs only one. > > Jul 11 06:48:30 f25f.greshko.com systemd[1]: Listening on XVNC Server. That is evidently due to something wrong during boot. After a fresh boot, here's what I see. [root@server ~]# systemctl status xvnc.socket xvnc.socket - XVNC Server Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor preset: disabled) Active: failed (Result: resources) Listen: 10.76.185.91:5901 (Stream) Accepted: 0; Connected: 0 Jul 10 16:57:13 server systemd[1]: xvnc.socket: Failed to listen on sock...ss Jul 10 16:57:13 server systemd[1]: Failed to listen on XVNC Server. Jul 10 16:57:13 server systemd[1]: xvnc.socket: Unit entered failed state. Jul 10 16:57:13 server systemd[1]: Starting XVNC Server. Hint: Some lines were ellipsized, use -l to show in full. [root@server ~]# systemctl start xvnc.socket [root@server ~]# systemctl status xvnc.socket xvnc.socket - XVNC Server Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor preset: disabled) Active: active (listening) since Mon 2017-07-10 17:04:20 PDT; 1s ago Listen: 10.76.185.91:5901 (Stream) Accepted: 0; Connected: 0 Jul 10 17:04:20 server systemd[1]: Listening on XVNC Server. Jul 10 17:04:20 server systemd[1]: Starting XVNC Server. > Without any clients connected/connecting can you check to see if Xvnc is > running? I only have a running /usr/bin/Xvnc when a client is connected. Without a connection, "ps -ef | grep vnc" shows only the grep. During an attempted connection, Xvnc is running with all the right options. > Also, check /var/log/kdm.log to see if there are errors. /var/log/kdm.log just tells me that useful messages are in syslog. In there, greping for kdm, I see: Jul 10 16:56:07 server audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=kdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 10 16:56:07 server audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=kdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 10 16:57:27 server audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=kdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 10 16:57:27 server kdm[1676]: plymouth is running Jul 10 16:57:27 server kdm[1676]: plymouth is active on VT 1, reusing for :0 Jul 10 16:57:27 server kdm[1676]: plymouth should quit after server startup Jul 10 16:57:30 server kdm[1676]: Quitting Plymouth with transition Jul 10 16:57:30 server kdm[1676]: Is Plymouth still running? no And when I try to connect, Jul 10 17:05:49 server kdm: fe80::3617:ebff:feeb:6b02:1[7472]: Cannot connect to fe80::3617:ebff:feeb:6b02:1, giving up Jul 10 17:05:49 server kdm[1676]: Display fe80::3617:ebff:feeb:6b02:1 cannot be opened -- Dave Close "Age is a very high price to pay for maturity." -- Tom Stoppard _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
