Setting Device Status

[CDinger]

I am using Version: 5.0.1.191224 and notice that in setting > device status results are always "No devices are currently active" even if a show is being recorded. The TV  Guide indicates recording as the show is red.  I am using Arch thus a non-Debian installation. Everything else seems to be working fine.

[sub]

What type of device were you using?

[CDinger]

Sub,

It is working now. Below is my device output. I believe the problem is that I had removed dotnet-runtime 2.1 when I installed dotnet-runtime 3.1. I was looking through the logs and found an error unable to locate dotnet-runtime 2.1 so I reinstalled dotnet-runtime 2.1 and all is good. This reminds me I forgot to post logs...sorry

LocalRecorder (adapter3)

- /mnt/storage/Recorded_TV/Today/Today_20191225_07000900-0-0-0-0.tsIt is working now, device is "

Craig

[mvallevand]

Could you post the logs, you shouldn't require 2.2 anymore. I know you don't use the deb installer because you aren't Debian based you may not have upgraded properly (you do need to remove the old program folder) You may have missed DeviceHostLinux.

Martin

[CDinger]

Here is a snippet from the nrecord.log Note: I was working with my PostProcessing.sh file and messed up the /dev/null resulting in comskip output in the nrecord.log. This has since been corrected. 

2019-12-25 08:06:08.315 [DEBUG][7] Starting: bash -c "'/home/craig/.NPVR-data/scripts/ParallelProcessing.sh' '/mnt/storage/Recorded_TV/Leave It to Beaver/Season 04/Leave.It.to.Beaver.S04E33.Community.Chest.ts' 3.2 1140 21 'Leave It to Beaver'"
2019-12-25 08:06:08.333 [ERROR][142] It was not possible to find any compatible framework version
2019-12-25 08:06:08.333 [ERROR][142] The framework 'Microsoft.NETCore.App', version '2.1.0' was not found.
2019-12-25 08:06:08.333 [ERROR][142]   - The following frameworks were found:
2019-12-25 08:06:08.333 [ERROR][142]       3.1.0 at [/home/craig/dotnet/shared/Microsoft.NETCore.App]
2019-12-25 08:06:08.333 [ERROR][142]
2019-12-25 08:06:08.333 [ERROR][142] You can resolve the problem by installing the specified framework and/or SDK.
2019-12-25 08:06:08.333 [ERROR][142]
2019-12-25 08:06:08.333 [ERROR][142] The specified framework can be found at:
2019-12-25 08:06:08.333 [ERROR][142]   - https://aka.ms/dotnet-core-applaunch?fra...d=arch-x64

Craig

[mvallevand]

Ok yes I am guessing by logs you are using NextEnd and you didn't upgrade to the 3.1 version. I also think you need to add some start up delay for network availability after boot.


Martin

[CDinger]

I upgraded to NextEndv5-3.1, removed old dotnet and kept dotnet 3.1. All appears to be working well but I haven't recorded any sports programs so I have not tested my upgrade of NextEnd yet.

Martin, what led you to comment that I needed to add a delay on startup? Just trying to learn/understand more as I go.

I added ExecStartPre=/bin/sleep 30 to my nextpvr-server.service.

Craig

[mvallevand]

Socket errors at the server start indicated no network. You can read the system journal to see where networking is up in comparison with the server.

I've posted a script for RPi users that do this based on uptime so it only happens at startup, doing a sleep in the service will impact restarts.

Martin

[CDinger]

Thanks Martin,

Your suggestion to read the system journal really helped. I found that I had another systemd service restarting multiple times while waiting for network connectivity. I found a solution that works for both. It is similar to your uptime loop. I ping my router until I receive a connection indicating the network is up then continue with starting the service. I found an example using ping -c1 google.com but thought a ping to my router would work just as well and wouldn't be affected by google.com being reachable.

ExecStartPre=/bin/sh -c 'until ping -c1 192.168.0.1; do sleep 1; done;'
ExecStart=sh NPVR.sh

Craig
Craig