![]() Process: 4774 ExecStart=/usr/sbin/runuser -l root -c /usr/bin/vncserver %i -geometry 1280x768 (code=exited, status=0/SUCCESS) Loaded: loaded enabled vendor preset: disabled)Īctive: failed (Result: resources) since Mon 09:39:21 MST 36s ago See "systemctl status and "journalctl -xe" for ~]# sudo systemctl status - Remote desktop service (VNC) # sudo systemctl start for failed because a configured resource limit was exceeded. ![]() See 'systemctl status and 'journalctl -xe' for details. ![]() I am getting below error when I submit "start system for failed because a configured resource limit was execeed. Process: 24425 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)įeb 11 10:09:35 localhost.localdomain systemd: Starting Remote desktop service (VNC).įeb 11 10:09:35 localhost.localdomain systemd: control process exited, code=exited status=98įeb 11 10:09:35 localhost.localdomain systemd: Failed to start Remote desktop service (VNC).įeb 11 10:09:35 localhost.localdomain systemd: Unit entered failed state. Process: 24429 ExecStart=/sbin/runuser -l dharmash -c /usr/bin/vncserver %i (code=exited, status=98) See 'systemctl status and 'journalctl -xn' for details.Īnd upon inspecting the status, I ~]# systemctl status - Remote desktop service (VNC)Īctive: failed (Result: exit-code) since Wed 10:09:35 EST 9min ago Systemctl start the error systemctl start for failed. I have the same error, and I tried all the above steps, but the error persists. # Content of home/USERNAME/.vnc/xstartup, owned by USERNAME # Clean any existing files in /tmp/.X11-unix environmentĮxecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'ĮxecStart=/sbin/runuser -l stanasa -c "/usr/bin/vncserver %i -geometry 1200x900"ĮxecStop=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :' Hint: Some lines were ellipsized, use -l to show in full. Jul 30 15:26:03 localhost.localdomain systemd: Unit e. Jul 30 15:26:03 localhost.localdomain systemd: Failed to start Remote desk. Jul 30 15:26:03 localhost.localdomain systemd: contr. Process: 13238 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Process: 13245 ExecStart=/sbin/runuser -l stanasa -c /usr/bin/vncserver %i (code=exited, status=98) See 'systemctl status and 'journalctl -xn' for ~]$ sudo systemctl status - Remote desktop service (VNC)Īctive: failed (Result: exit-code) since Wed 15:26:03 EDT 10s ago Issue: What can I do to make the config files load VNC service (with active GUI) for each user automatically at boot-up, to their assigned TCP ports?Ĭommand line log: sudo systemctl start for failed. Sometimes users connecting this way report only a black screen w/ a cross-pointer. This means that for every server restart, each VNC user has to SSH in and initialize a vncserver manually, figure out which port it opened on, and connect to that. Workaround: start vncserver manually by USER with "vncserver" command with no arguments. See 'systemctl status and 'journalctl -xn' for details. Systemctl start should report a successful start.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |