Can somebody please help me with a working systemd file for TigerVNC Scraping server in Debian Bookworm?

Mastiff · 11-12-2023, 01:13 PM

This command starts the server from a command line window:

Code:

x0vncserver -display :0 -localhost no -passwordfile /home/mastiff/.vnc/passwd

But I can't get it to work as a systemd service file. Can somebody please help me out there? I have trieda few different files from the web, but nothing has worked. This is what I have now:

Code:

[Unit]
Description=Remote desktop service (VNC) for :0 display
Requires=display-manager.service
After=network-online.target
After=display-manager.service

[Service]
ExecStartPre=/bin/sleep 10
Type=simple
ExecStart=x0vncserver -display :0 -localhost no -passwordfile /home/mastiff/.vnc/passwd
Restart=on-failure
RestartSec=10s

[Install]
WantedBy=multi-user.target

It looks on status like it's working, but I can't connect to it:

Code:

● tigervncserver.service - Remote desktop service (VNC) for :0 display
     Loaded: loaded (/lib/systemd/system/tigervncserver.service; enabled; prese>
     Active: activating (start-pre) since Sun 2023-11-12 20:11:48 CET; 4s ago
Cntrl PID: 4001 (sleep)
      Tasks: 1 (limit: 2454)
     Memory: 168.0K
        CPU: 1ms
     CGroup: /system.slice/tigervncserver.service
             └─4001 /bin/sleep 10

nov. 12 20:11:48 virtuell-HomeAssistant systemd[1]: Starting tigervncserver.ser>
lines 1-11/11 (END)...skipping...
● tigervncserver.service - Remote desktop service (VNC) for :0 display
     Loaded: loaded (/lib/systemd/system/tigervncserver.service; enabled; preset: enabled)
     Active: activating (start-pre) since Sun 2023-11-12 20:11:48 CET; 4s ago
Cntrl PID: 4001 (sleep)
      Tasks: 1 (limit: 2454)
     Memory: 168.0K
        CPU: 1ms
     CGroup: /system.slice/tigervncserver.service
             └─4001 /bin/sleep 10

nov. 12 20:11:48 virtuell-HomeAssistant systemd[1]: Starting tigervncserver.service - Remote desktop service (VNC) for :0 displa>
~

Can somebody who knows what they're actually doing please help me out here?

pan64 · 11-13-2023, 06:00 AM

you can check pages like this: https://superuser.com/questions/1717...ine-separately
Otherwise need to know what's happening to be able to fix it

allend · 11-13-2023, 07:19 AM

Perhaps section 4.2 from this ArchWiki page?

Mastiff · 11-14-2023, 12:19 PM

Thank you, but those pages are amongst those I have tried. I have never gotten any further than that the service is activated on startup and then deactivated. Journalctl doesn't show anything else either.

What can I say more about what happens? That's all the info I get from journalctl:

Code:

nov. 14 19:15:32 virtuell-machine sudo[3225]: pam_unix(sudo:session): session closed for user root
nov. 14 19:15:32 virtuell-machine systemd[1]: Started tigervncserver.service - Remote desktop service (VNC) for :0 display.
nov. 14 19:15:32 virtuell-machine x0vncserver[3235]: New X0tigervnc server 'virtuell-machine.MY-DOMAIN-NAME:0 (root)' on p>
nov. 14 19:15:32 virtuell-machine x0vncserver[3235]: Use xtigervncviewer -SecurityTypes VncAuth -passwd /tmp/tigervnc.p17U>
nov. 14 19:15:33 virtuell-machine systemd[1]: tigervncserver.service: Deactivated successfully.

And the log isn't really telling me much either:

Code:

Tue Nov 14 19:07:00 2023
 Geometry:    Desktop geometry is set to 1440x900+0+0
 XDesktop:    Using evdev codemap
 XDesktop:    
 XDesktop:    XTest extension present - version 2.2
 Main:        Listening for VNC connections on local interface(s), port 5900
3NI3X0 New X0tigervnc server 'virtuell-HomeAssistant.MY_DOMAIN:0 (root)' on port 5900 for display :0.
3NI3X0 Use xtigervncviewer -SecurityTypes VncAuth -passwd /tmp/tigervnc.BES9Fb/passwd :0 to connect to the VNC server.
 Main:        Terminated
Killing X0tigervnc process ID 1581... success!

So it seems like it's getting a kill signal as soon as it's started up.

pan64 · 11-14-2023, 12:59 PM

Quote:

Originally Posted by Mastiff

Thank you, but those pages are amongst those I have tried.

Would be better to explain what did you try and what's happened, otherwise we cannot give you any help. Probably next time will will suggest you something that you have already tried again...

Quote:

Originally Posted by Mastiff

I have never gotten any further than that the service is activated on startup and then deactivated. Journalctl doesn't show anything else either.

What can I say more about what happens? That's all the info I get from journalctl:

Code:

nov. 14 19:15:32 virtuell-machine sudo[3225]: pam_unix(sudo:session): session closed for user root
nov. 14 19:15:32 virtuell-machine systemd[1]: Started tigervncserver.service - Remote desktop service (VNC) for :0 display.
nov. 14 19:15:32 virtuell-machine x0vncserver[3235]: New X0tigervnc server 'virtuell-machine.MY-DOMAIN-NAME:0 (root)' on p>
nov. 14 19:15:32 virtuell-machine x0vncserver[3235]: Use xtigervncviewer -SecurityTypes VncAuth -passwd /tmp/tigervnc.p17U>
nov. 14 19:15:33 virtuell-machine systemd[1]: tigervncserver.service: Deactivated successfully.

And the log isn't really telling me much either:

Code:

Tue Nov 14 19:07:00 2023
 Geometry:    Desktop geometry is set to 1440x900+0+0
 XDesktop:    Using evdev codemap
 XDesktop:    
 XDesktop:    XTest extension present - version 2.2
 Main:        Listening for VNC connections on local interface(s), port 5900
3NI3X0 New X0tigervnc server 'virtuell-HomeAssistant.MY_DOMAIN:0 (root)' on port 5900 for display :0.
3NI3X0 Use xtigervncviewer -SecurityTypes VncAuth -passwd /tmp/tigervnc.BES9Fb/passwd :0 to connect to the VNC server.
 Main:        Terminated
Killing X0tigervnc process ID 1581... success!

So it seems like it's getting a kill signal as soon as it's started up.

this is not the log we need. Why it was killed, what terminated this service?

Mastiff · 11-14-2023, 01:04 PM

Thanks for the patience, and sorry that I wasn't precise enough in my first message! Where do I find the log you need? The first was journalctl and the second was Tigervnc's own log, which ends up in the directory .vnc. Where do I find out what killed it?

Edit: I don't think it was the kernel, there's lots of CPU available, and the memory should be enough:

MemTotal: 2158488 kB
MemFree: 514376 kB
MemAvailable: 1238000 kB