srch

I have TightVNC installed and working on my Ubuntu 18.4 virtual server ... vncserver@1.service: Control process exited, code=exited status=2 ...

service: control process exited, code=exited status=98 systemd[1]: Failed to start Remote desktop service (VNC). systemd[1]: Unit vncserver@:1.service entered ...

... Main process exited, code=exited, status=2/INVALIDARGUMENT Okt 06 11:06:57 Mondroid systemd[1]: vncserver@:1.service: Failed with result 'exit-code'.

Unit vncserver@:7.service entered failed state. or. Job for vncserver@:7.service failed. See 'systemctl status vncserver@:7.service' and 'journalctl -xn' for details. Delete this folder: rm -r /tmp/.X11-unix/ And reboot. Then check tigervnc is ok for run port configure .

Process: 31934 ExecStart=/etc/rc.d/init.d/vncserver start (code=exited, status=2/INVALIDARGUMENT) CGroup: name=systemd:/system/vncserver.

vncserver@.service: ``` [Unit] Description=Start TightVNC server at ... -kill :1 > /dev/null 2>&1 (code=exited, status=2) Apr 19 18:34:49 ...

service failed because the control process exited with error code. See "systemctl status vncserver@:1.service" and "journalctl -xe" for details.

See 'systemctl status vncserver@:4.service' and 'journalctl -xn' for. ... -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Jul ...

06.08.2014 · Process: 23836 ExecStart=/sbin/runuser -l someuser -c /usr/bin/vncserver %i -geometry 1280x720 (code=exited, status=1/FAILURE) Process: 23828 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Aug 05 17:15:29 localhost runuser[23836]: runuser: may not be used by non-root users Aug 05 17:15 ...

vncserver@:1.service: control process exited, code=exited status=2. 主要原因：因为异常关机导致临时文件生成错误. 解决办法：删除vncserver产生的临时用户文件X1(vncserver@:1.service对应的)

26.09.2021 · Sep 06 20:04:33 test-machine01.local vncserver_wrapper[1807]: Warning: jedsupportal1.saudiacatering.local:1 is taken because of /tmp/.X11-unix/X1 Sep 06 20:04:33 test-machine01.local vncserver_wrapper[1807]: Remove this file if there is no X server test-machine01.local:1 Sep 06 20:04:33 test-machine01.local vncserver_wrapper[1807]: A VNC …

05.07.2020 · Jul 05 17:58:53 ip-172-32-8-143.us-east-2.compute.internal systemd[1]: vncserver@:2.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jul 05 17:58:53 ip-172-32-8-143.us-east-2.compute.internal systemd[1]: vncserver@:2.service: Failed with result 'exit-code'.

Process: 2026 ExecStop=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/ null 2>&1 || : (code=exited, status=0/SUCCESS).

13.02.2021 · VNCSERVER 重启后突然报错：ExecStart=usrbinvncserver_wrapper oracle %i (code=exited, status=2) Kevin6369 2021-02-13 21:27:22 1300 收藏 分类专栏： Linux 文章标签： linux centos tightvnc vnc

If above method do not take effect, you can edit file /etc/systemd/ system /vncserver @: 1. service and change Service —> Type from forking to simple. # vim /etc/systemd/system/ [email protected] :1.service # Edit Service section, change Type=forking to Type=simple.

Active: failed (Result: exit-code) since Thu 2016-09-29 15:52:31 CDT; 3s ago. Process: 3673 ExecStop=/usr/bin/vncserver -kill %i (code=exited, status=2)

29.11.2020 · Nov 28 13:44:54 Backup vncserver_wrapper[15033]: runuser: user <USER> does not exist Nov 28 13:44:54 Backup vncserver_wrapper[15033]: FATAL: 'runuser -l <USER>' failed! Nov 28 13:44:54 Backup systemd[1]: vncserver@:2.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Nov 28 13:44:54 Backup systemd[1]: vncserver@:2.service ...

See "systemctl status vncserver@:1.service" and "journalctl -xe" for details. Also if we check the status of the service, we observe PID file /root/.vnc/openstack.example:1.pid not readable (yet?) after start message which again was confusing to me as the permission on the PID file looked correct and it cannot change suddenly when I know the vnc service was working just fine.

vim /etc/systemd/system/vncserver@:1.service ... deemon :1 (code=exited, status=2) Process: 27180 ExecStartPre=/bin/sh -c /usr/bin/vncserver ...

25.03.2018 · Mar 25 12:35:37 waspy systemd[26401]: vncserver@1.service: Failed at step USER spawning /usr/bin/vncserver: No such process Mar 25 12:35:37 waspy systemd[26404]: vncserver@1.service: Failed at step USER spawning /usr/bin/vncserver: No such process Mar 25 12:35:37 waspy systemd[1]: vncserver@1.service: Control process exited, code=exited …