On 07/08/17 09:40, CLOSE Dave wrote: > Almost. But the service isn't starting. > > # systemctl status -l xvnc@:.service > xvnc@:.service - XVNC per Connection Daemon > Loaded: loaded (/etc/systemd/system/xvnc@.service; enabled; vendor > preset: disabled) > Active: failed (Result: resources) > > Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Got more than one socket. > Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Failed to run 'start' > task: Invalid argument > Jul 07 18:27:08 server systemd[1]: Failed to start XVNC per Connection > Daemon. > Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Unit entered failed > state. > Jul 07 18:27:08 server systemd[1]: xvnc@:.service: Failed with result > 'resources'. > Jul 07 18:27:08 server systemd[1]: Starting XVNC per Connection Daemon...
You actually don't want xvnc@.service to be enabled or started. The connection to the socket triggers starting of Xvnc On my system with no VNC clients connected. [root@f25f system]# ps -eaf | grep vnc root 3523 1251 0 10:04 pts/0 00:00:00 grep --color=auto vnc [root@f25f system]# systemctl status xvnc@.service Failed to get properties: Unit name xvnc@.service is missing the instance name. [root@f25f system]# systemctl status xvnc.socket ● xvnc.socket - XVNC Server Loaded: loaded (/etc/systemd/system/xvnc.socket; enabled; vendor preset: disabl Active: active (listening) since Sat 2017-07-08 10:04:27 CST; 48s ago Listen: [::]:5900 (Stream) Accepted: 3; Connected: 0 Jul 08 10:04:27 f25f.greshko.com systemd[1]: Listening on XVNC Server. Once a client connects.... [root@f25f system]# ps -eaf | grep vnc root 3529 1 1 10:06 ? 00:00:00 /usr/bin/Xvnc -inetd -query localhost -geometry 1024x768 -depth 24 -once -SecurityTypes=None > > # systemctl status -l 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 07 18:27:06 server systemd[1]: xvnc.socket: Failed to listen on > sockets: Cannot assign requested address > Jul 07 18:27:06 server systemd[1]: Failed to listen on XVNC Server. > Jul 07 18:27:06 server systemd[1]: xvnc.socket: Unit entered failed state. > Jul 07 18:27:06 server systemd[1]: Starting XVNC Server. I find it odd that you get this "Listen: 10.76.185.91:5901" when your file below for xvnc.socket has "ListenStream=10.76.185.91:5900". That is 5901 v.s. 5901. I think you may have done something like what the vncserver@.service file tells you to do? That is enable xvnc@:1.service? Here are my files... [root@f25f system]# pwd /etc/systemd/system [root@f25f system]# cat xvnc@.service | grep -v ^# [Unit] Description=XVNC Per-Connection Daemon [Service] ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768 -depth 24 -once -SecurityTypes=None StandardInput=socket StandardError=syslog [root@f25f system]# cat xvnc.socket | grep -v ^# [Unit] Description=XVNC Server [Socket] ListenStream=5900 Accept=yes [Install] WantedBy=sockets.target And, with no client connected.... root@f25f system]# netstat -nap | grep 5900 tcp6 0 0 :::5900 :::* LISTEN 1/systemd And connected.... [root@f25f system]# netstat -nap | grep 5900 tcp6 0 0 :::5900 :::* LISTEN 1/systemd tcp6 0 0 192.168.1.198:5900 192.168.1.18:56272 ESTABLISHED 1/systemd -- Fedora Users List - The place to go to speculate endlessly
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
