recurring recordings not scheduled

[CDinger]

I noticed today that only 3 recordings were pending, 2 movies and one of the NFL playoff games. Normally the pending list is very long. I modified my NFL recurring so the games are now scheduled. However, none of my regular series are scheduled. I have not idea what happened.

I am using a fresh install of Arch Linux with current version of nextpvr.

logs attached

[mvallevand]

NextPVR makes the odd decision that if a tuner is not available at the start

2021-01-09 07:31:30.069 [ERROR][1] ERROR: Open frontend0 failed

It won't schedule the recording. It is quite annoying on my HDHR device which mioght be uplugged and on your machine by the time your recording is to happen they would probably work too.

You will need to force an EPG update now and will likely need to change your startup script to allow enough time for the devices to load in the future

Martin

[CDinger]

Thanks Martin,

I'm not sure why the problem started today, I have done several reboots in the past without incident. At any rate I added a longer sleep, it was 1 previously

Code:

[Unit]
Description=start nextpvr

[Service]
Type=simple
User=craig
WorkingDirectory=/home/craig/NPVR
ExecStartPre=/bin/sh -c 'until ping -c1 192.168.0.99; do sleep 20s; done;'
ExecStart=/usr/share/dotnet/dotnet /home/craig/NPVR/./NextPVRServer.dll
Restart=on-failure
RestartSec=10000ms

[Install]
WantedBy=multi-user.target

Craig

[mvallevand]

You'd need to check your system logs. Your aren't using a network tuner so there is no reason to assume that because your network is up that your tuners devices have also started.

Martin

[CDinger]

I'm not sure how to use the logs to know how to modifiy the systemd unit. However, I think this may work

ExecStartPre=systemctl is-system-running --wait

Code:

[Unit]
Description=start nextpvr

[Service]
Type=simple
User=craig
WorkingDirectory=/home/craig/NPVR
#ExecStartPre=/bin/sh -c 'until ping -c1 192.168.0.99; do sleep 20s; done;'
ExecStartPre=systemctl is-system-running --wait
ExecStart=/usr/share/dotnet/dotnet /home/craig/NPVR/./NextPVRServer.dll > /dev/null
Restart=on-failure
RestartSec=10000ms

[Install]
WantedBy=multi-user.target

Craig

[mvallevand]

What I do is check the system log for the time it takes for my tuner drivers to load. Then I created a PreStartup.sh as I showed here https://forums.nextpvr.com/showthread.ph...#pid530707

Martin

[CDinger]

Thanks Martin,

I added a PreStartup.sh, the tuners load within 2 seconds but I thought I would leave a little wiggle room.

Code:

#!/bin/bash

read -d. uptime < /proc/uptime
echo $uptime
while [ $uptime -lt  4 ]; do
        sleep 1
        read -d. uptime < /proc/uptime
done

Craig

[mvallevand]

That seems fast, you may be missing something, your uptime will be much longer with your network dealy.

Martin

[CDinger]

Martin,

Correct me if I am wrong, I'm basing time on journalctl -b. This reboot from start to last tuner driver = 3 sec. I am using a M2 HDD for booting which helps with speed. There is now a slight lag until the nextpvr web browser is up and operational after a reboot.

Code:

Jan 09 17:35:45 Arch kernel: Linux version 5.10.5-arch1-1 (linux@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #1 SMP PREEMPT Thu, 07 Jan 2021 09:50:43 +0000

Code:

Jan 09 17:35:47 Arch kernel: tveeprom: decoder processor is CX23888 (idx 34)

Code:

Jan 09 17:35:48 Arch kernel: cx23885: cx23885[1]/0: found at 0000:04:00.0, rev: 4, irq: 16, latency: 0, mmio: 0x51000000

Craig

[mvallevand]

I would look for the firmware downloaded and especially the registering adapter and driver loaded messages that should follow those

Martin