vdr-transcode - swiss knife for transcoding

jsffm · May 31, 2022 at 4:24 PM

Quote from pille2011

already running

pille2011 · May 31, 2022 at 4:25 PM

Code

root@stube:/home/frank# vt --ak
not running

jsffm · May 31, 2022 at 4:26 PM

sudo -u vdr vt --ak

pille2011 · May 31, 2022 at 4:27 PM

Code

frank@stube:~$ sudo -u vdr vt --ak
[sudo] Passwort für frank:
not running
frank@stube:~$

pille2011 · May 31, 2022 at 4:30 PM

Code

frank@stube:~$ sudo killall vt
vt: Kein Prozess gefunden
frank@stube:~$

pille2011 · May 31, 2022 at 4:59 PM

Wenn ich es manuell starte funktioniert es

Code

frank@stube:~$ sudo -u vdr vt --as &
[3] 6152
frank@stube:~$

seahawk1986 · May 31, 2022 at 5:39 PM

Ich hab mal in den Code geschaut - nachdem vt -as nicht forkt, sondern einfach weiter läuft und vt -ak nichts anderes macht als ein SIGTERM an den Prozess zu senden, kann man vt einfach unter Kontrolle von Systemd stellen (es darf natürlich keine weitere Instanz laufen, wenn die Systemd-Unit gestartet wird):

Code

[Unit]
Description=VDR transcode
[Service]
Type=simple
User=vdr
ExecStart=/usr/local/bin/vt --as
StandardOutput=journal
[Install]
WantedBy=multi-user.target

pille2011 · May 31, 2022 at 5:59 PM

Habe es gerade getestet

Code

root@stube:/home/frank# journalctl -u vt.service -b -l
-- Logs begin at Fri 2022-01-14 01:55:02 CET, end at Tue 2022-05-31 17:57:02 CEST. --
Mai 31 17:56:29 stube systemd[1]: Started VDR transcode.
Mai 31 17:56:29 stube vt[815]: already running
Mai 31 17:56:29 stube systemd[1]: vt.service: Main process exited, code=exited, status=99/n/a
Mai 31 17:56:29 stube systemd[1]: vt.service: Failed with result 'exit-code'.
root@stube:/home/frank#

Code

root@stube:/home/frank# systemctl status vt.service
● vt.service - VDR transcode
     Loaded: loaded (/lib/systemd/system/vt.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2022-05-31 17:56:29 CEST; 1min 13s ago
    Process: 815 ExecStart=/usr/local/bin/vt --as (code=exited, status=99)
   Main PID: 815 (code=exited, status=99)

Mai 31 17:56:29 stube systemd[1]: Started VDR transcode.
Mai 31 17:56:29 stube vt[815]: already running
Mai 31 17:56:29 stube systemd[1]: vt.service: Main process exited, code=exited, status=99/n/a
Mai 31 17:56:29 stube systemd[1]: vt.service: Failed with result 'exit-code'.
root@stube:/home/frank#

Display More

Startet leider nicht

Habe auch testweise das System ausgeschaltet und wieder neu gestartet,leider ohne Erfolg

pille2011 · May 31, 2022 at 6:33 PM

Code

root@stube:/home/frank# sudo systemctl enable vt.service
Created symlink /etc/systemd/system/multi-user.target.wants/vt.service → /lib/systemd/system/vt.service.
root@stube:/home/frank#

In /etc/systemd/system/multi-user.target.wants

ist die neue vt.service

Danach reboot

pille2011 · May 31, 2022 at 6:37 PM

Code

root@stube:/home/frank# journalctl -u vt.service -b -l
-- Logs begin at Sun 2022-01-16 09:21:38 CET, end at Tue 2022-05-31 18:36:38 CEST. --
Mai 31 18:36:05 stube systemd[1]: Started VDR transcode.
root@stube:/home/frank#

Code

root@stube:/home/frank# systemctl status vt.service
● vt.service - VDR transcode
     Loaded: loaded (/lib/systemd/system/vt.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2022-05-31 18:36:05 CEST; 1min 15s ago
   Main PID: 809 (vt)
      Tasks: 2 (limit: 9255)
     Memory: 5.9M
     CGroup: /system.slice/vt.service
             ├─ 809 /bin/bash /usr/local/bin/vt --as
             └─1500 sleep 60

Mai 31 18:36:05 stube systemd[1]: Started VDR transcode.
root@stube:/home/frank#

Display More

pille2011 · May 31, 2022 at 6:40 PM

Nach einem erneutem reboot kommt dann wieder Fehler

Code

root@stube:/home/frank# journalctl -u vt.service -b -l
-- Logs begin at Sun 2022-01-16 09:21:38 CET, end at Tue 2022-05-31 18:39:10 CEST. --
Mai 31 18:38:32 stube systemd[1]: Started VDR transcode.
Mai 31 18:38:32 stube vt[814]: already running
Mai 31 18:38:32 stube systemd[1]: vt.service: Main process exited, code=exited, status=99/n/a
Mai 31 18:38:32 stube systemd[1]: vt.service: Failed with result 'exit-code'.
root@stube:/home/frank# systemctl status vt.service
● vt.service - VDR transcode
     Loaded: loaded (/lib/systemd/system/vt.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2022-05-31 18:38:32 CEST; 47s ago
    Process: 814 ExecStart=/usr/local/bin/vt --as (code=exited, status=99)
   Main PID: 814 (code=exited, status=99)

Mai 31 18:38:32 stube systemd[1]: Started VDR transcode.
Mai 31 18:38:32 stube vt[814]: already running
Mai 31 18:38:32 stube systemd[1]: vt.service: Main process exited, code=exited, status=99/n/a
Mai 31 18:38:32 stube systemd[1]: vt.service: Failed with result 'exit-code'.
root@stube:/home/frank#

Display More

Seltsam

pille2011 · May 31, 2022 at 7:40 PM

Code

root@stube:/home/frank# systemctl show vt.service -p Conflicts
Conflicts=shutdown.target
root@stube:/home/frank#

Da stimmt irgendwas nicht ,aber was???

wmautner · May 31, 2022 at 9:24 PM

Looks like vt "believes" it's still running, probably due to a persistent and not deleted statefile.

Just tested, here it puts a /run/vt_server.pid. @ first run (directly started) and doesn't delete that file when "vt --ak".

But then, this file isn't hindering a restart and just stayed there - it was not updated on a 2nd "vt --as".

Puzzled ...

jsffm · May 31, 2022 at 9:38 PM

It is correct that the pid-file will not deleted at at --ak , but that makes no problem, everything works fine.

wmautner · June 1, 2022 at 8:08 AM

But then, if vt doesn't remember the state although it may be killed by systemd (since no "ExecStop" was provided), the fault must be in systemd.

I would add the "ExecStop = vt --ak" line to the service section and try if that helps.

seahawk1986 · June 1, 2022 at 8:40 AM

vt compares the content of the vt file with the existing pids in the system to determine if it is already running: https://github.com/jsffm/vdr-tran…transcode#L3632 - this can give false positives because a pid isn't unique across reboots. A quick way to fix this yould be to delete the pid file before starting the process (a better way would be to put the pid file into /run/$USER/, so it is lost when the system reboots):

Code

[Unit]
Description=VDR transcode
[Service]
Type=simple
User=vdr
ExecStartPre=rm -f %h/vdr-transcode/vt_server.pid
ExecStart=/usr/local/bin/vt --as
StandardOutput=journal
[Install]
WantedBy=multi-user.target

Systemd sending a SIGTERM to the process should not be a problem, that's the only important thing the server_kill function does: https://github.com/jsffm/vdr-tran…transcode#L3677

jsffm · June 1, 2022 at 10:50 AM

I guess /run/$USERmust be created as root after every start

Why do we speak english?

wmautner · June 1, 2022 at 11:19 AM

Quote from jsffm

Why do we speak english?

Hehe, ich glaub ich hab vor dem Artikel, auf den ich zuerst geantwortet hab, *irgendwas* englisches gelesen hier

Vielleicht eine systemd-manpage ...

pille2011 · June 1, 2022 at 11:56 AM

Ich kann nur Ost-Deutsch

pille2011 · June 1, 2022 at 2:43 PM

Quote from seahawk1986

[Unit]
Description=VDR transcode
[Service]
Type=simple
User=vdr
ExecStartPre=rm -f %h/vdr-transcode/vt_server.pid
ExecStart=/usr/local/bin/vt --as
StandardOutput=journal
[Install]
WantedBy=multi-user.target

Display More

Hab es gerade probiert,leider ohne Erfolg,da fehlen wohl root Rechte

Code

root@stube:/home/frank# journalctl -u vt.service -b -l
-- Logs begin at Fri 2022-01-21 14:16:02 CET, end at Wed 2022-06-01 14:40:04 CEST. --
Jun 01 14:38:36 stube systemd[1]: Starting VDR transcode...
Jun 01 14:38:36 stube rm[814]: /usr/bin/rm: das Entfernen von '/root/vdr-transcode/vt_server.pid' ist nicht möglich: Keine Berechtigung
Jun 01 14:38:36 stube systemd[1]: vt.service: Control process exited, code=exited, status=1/FAILURE
Jun 01 14:38:36 stube systemd[1]: vt.service: Failed with result 'exit-code'.
Jun 01 14:38:36 stube systemd[1]: Failed to start VDR transcode.

Code

root@stube:/home/frank# systemctl status vt.service
● vt.service - VDR transcode
     Loaded: loaded (/lib/systemd/system/vt.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2022-06-01 14:38:36 CEST; 1min 57s ago
    Process: 814 ExecStartPre=/usr/bin/rm -f /root/vdr-transcode/vt_server.pid (code=exited, status=1/FAILURE)

Jun 01 14:38:36 stube systemd[1]: Starting VDR transcode...
Jun 01 14:38:36 stube rm[814]: /usr/bin/rm: das Entfernen von '/root/vdr-transcode/vt_server.pid' ist nicht möglich: Keine Berechtigung
Jun 01 14:38:36 stube systemd[1]: vt.service: Control process exited, code=exited, status=1/FAILURE
Jun 01 14:38:36 stube systemd[1]: vt.service: Failed with result 'exit-code'.
Jun 01 14:38:36 stube systemd[1]: Failed to start VDR transcode.
root@stube:/home/frank#

Display More

vdr-transcode - swiss knife for transcoding

Participate now!

Tags

Users Viewing This Thread