Tuner devices not available after upgrade to 5.0.0.190826

[vintdiesel]

Upgraded from V5.0.0.190803 -> 5.0.0190826. Recordings failed and all scheduled items in TV guide turned yellow.

Checking devices shows all tuners "not available". Tried re-scanning and unpinning tuners makes no difference.
restarted docker container and rebooting host makes no difference.

Restoring docker image back to 5.0.0.190803 and rebooting the host got my tuners available again, however no recordings in the schedule were pending.
By going to the recurring recordings and updating them put them back into the pending list and recording could resume again.

My system is the Unraid server with WinTV components in my signature.
I am happy to test or detail further if necessary.

Damian

[vintdiesel]

Oops, plus the logs before I get told off by Martin.

[mvallevand]

Oops, plus the logs before I get told off by Martin.

You wouldn't my new strategy is to say nothing when there are no logs. In any case those logs show no devices marked present. Is your tuner a legacy HDHR? Something is off on that you perhaps a Missing chmod in docker.

Martin

[vintdiesel]

Hi Martin,
I am running a Hauppage Win-TV 2210 Dual DVB-T PCIe tuner card.
According to the host the tuners are present as DVB Adapter 0: NXP TDA10048HN DVB-T and DVB Adapter 1: NXP TDA10048HN DVB-T.

If I restore the docker image I have saved with the 190803 version, its all good. If I then upgrade the docker to pull the 190826 version, the tuners become "not available".
Near the top of nrecord.log.2 shows a good startup of the tuners:

2019-08-26 18:30:46.062 [DEBUG][1] Doing database updates
2019-08-26 18:30:46.063 [INFO][1] Version 5.0.0.190803
2019-08-26 18:30:46.224 [DEBUG][1] CaptureSource.LoadAll()
2019-08-26 18:30:46.849 [DEBUG][1] []
2019-08-26 18:30:46.863 [DEBUG][1] HDHR Discover
2019-08-26 18:30:56.484 [DEBUG][1] Local Devices: <devices>
<device>
<name>adapter1 (NXP TDA10048HN DVB-T)</name>
<type>DVB-T</type>
<filter>adapter1</filter>
<instance>1</instance>
<resource>adapter1</resource>
</device>
<device>
<name>adapter1 (NXP TDA10048HN DVB-T)</name>
<type>DVB-C</type>
<filter>adapter1</filter>
<instance>1</instance>
<resource>adapter1</resource>
</device>
<device>
<name>adapter0 (NXP TDA10048HN DVB-T)</name>
<type>DVB-T</type>
<filter>adapter0</filter>
<instance>1</instance>
<resource>adapter0</resource>
</device>
<device>
<name>adapter0 (NXP TDA10048HN DVB-T)</name>
<type>DVB-C</type>
<filter>adapter0</filter>
<instance>1</instance>
<resource>adapter0</resource>
</device>
</devices>

2019-08-26 18:30:56.487 [DEBUG][1] adapter1
2019-08-26 18:30:56.487 [DEBUG][1] adapter1
2019-08-26 18:30:56.487 [DEBUG][1] adapter0
2019-08-26 18:30:56.487 [DEBUG][1] adapter0

Near the top of nrecord.log shows the bad startup:

[...startup]
2019-08-26 20:33:57.181 [DEBUG][1] Checking if upgrade required
2019-08-26 20:33:57.183 [DEBUG][1] master file is /app/data/Config-master-dont-edit.xml
2019-08-26 20:33:57.191 [DEBUG][1] Doing database updates
2019-08-26 20:33:57.192 [DEBUG][1] Database: /config/npvr.db3
2019-08-26 20:33:57.293 [INFO][1] Version 5.0.0.190826
2019-08-26 20:33:57.424 [DEBUG][1] CaptureSource.LoadAll()
2019-08-26 20:33:57.980 [DEBUG][1] []
2019-08-26 20:33:57.994 [DEBUG][1] HDHR Discover
2019-08-26 20:33:59.054 [ERROR][1] Unexpected error scanning for other devices: System.ComponentModel.Win32Exception (13): Permission denied
at Interop.Sys.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setUser, UInt32 userId, UInt32 groupId, Int32& lpChildPid, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean shouldThrow)
at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at NShared.Visible.CaptureSource.UpdateDevices(ICaptureSourceUpdateStatus callback)

Damian

[mvallevand]

If you want fix this if your container is called nextpvr

docker exec -u 0 -it nextpvr /bin/bash

Then in docker for your i7

chmod +x /app/DeviceHost/x64/DeviceHostLinux

Martin

[vintdiesel]

Thanks Martin, I shall check this out. FYI some of the Linux based command line stuff I am still a bit of a newbie on.

[sub]

I think Martin is probably right - looks like I don't have the DeviceHostLinux marked as executable. Try this steps he mentioned above. A little later today I'll fix it in the Docker image.

[sub]

Actually I've updated the Docker image to fix this.

[vintdiesel]

Thanks guys, I could have set the permission but I opted for re-pulling the files into a clean docker image in case I had messed something else up. It's working again

[sub]

Great