2018-02-27, 04:27 AM
Hi,
Quite new to NextPVR, but so far it looks amazing, so well done. However, I have an issue.
Firstly, this is my setup: HD Homerun (DVB-T2) tuner, a dedicated PC acting as a server / recorder and several Raspberry Pi's on TV's all over the place.
I'm using the latest (December 2017) version of NextPVR.
The issue I have, has been seen before, where the tuner remains in use, recording to a 'c:\devxxxxx\null.ts' or something like that (Sorry cleared the problem, by restarting the NextPVR background service). Anyway, it's happening quite a lot. I only noticed because my network light was flashing like crazy when no recording where taking place.. or EPG updates.. so it shouldn't have been talking to the tuner. I'm not 100% sure what causes it, but once cleared it doesn't seem to appear by itself, so is probably after a recording.
As per the readme, I'm including the complete log files. On this subject, I noticed the loggs have a 'lot' of this...
2018-02-25 17:12:53.402 [DEBUG][25] Renew lease ok (0x160001)
2018-02-25 17:12:58.597 [DEBUG][25] Renew lease ok (0x160001)
2018-02-25 17:13:03.884 [DEBUG][23] Renew lease ok (0x160001)
2018-02-25 17:13:09.084 [DEBUG][23] Renew lease ok (0x160001)
2018-02-25 17:13:14.122 [DEBUG][23] Renew lease ok (0x160001)
2018-02-25 17:13:19.261 [DEBUG][20] Renew lease ok (0x160001)
2018-02-25 17:13:24.485 [DEBUG][20] Renew lease ok (0x160001)
2018-02-25 17:13:29.781 [DEBUG][20] Renew lease ok (0x160001)
2018-02-25 17:13:34.967 [DEBUG][25] Renew lease ok (0x160001)
2018-02-25 17:13:40.101 [DEBUG][25] Renew lease ok (0x160001)
.... so some of the log files are 500K, most of it these messags. (Notice theres ten odd per min... seems odd, but probably another un-related issue?)
Hope this drivel helps!
Thanks for NextPVR, it's great. Would love to get it to a reliable state for me. Thanks.
Quite new to NextPVR, but so far it looks amazing, so well done. However, I have an issue.
Firstly, this is my setup: HD Homerun (DVB-T2) tuner, a dedicated PC acting as a server / recorder and several Raspberry Pi's on TV's all over the place.
I'm using the latest (December 2017) version of NextPVR.
The issue I have, has been seen before, where the tuner remains in use, recording to a 'c:\devxxxxx\null.ts' or something like that (Sorry cleared the problem, by restarting the NextPVR background service). Anyway, it's happening quite a lot. I only noticed because my network light was flashing like crazy when no recording where taking place.. or EPG updates.. so it shouldn't have been talking to the tuner. I'm not 100% sure what causes it, but once cleared it doesn't seem to appear by itself, so is probably after a recording.
As per the readme, I'm including the complete log files. On this subject, I noticed the loggs have a 'lot' of this...
2018-02-25 17:12:53.402 [DEBUG][25] Renew lease ok (0x160001)
2018-02-25 17:12:58.597 [DEBUG][25] Renew lease ok (0x160001)
2018-02-25 17:13:03.884 [DEBUG][23] Renew lease ok (0x160001)
2018-02-25 17:13:09.084 [DEBUG][23] Renew lease ok (0x160001)
2018-02-25 17:13:14.122 [DEBUG][23] Renew lease ok (0x160001)
2018-02-25 17:13:19.261 [DEBUG][20] Renew lease ok (0x160001)
2018-02-25 17:13:24.485 [DEBUG][20] Renew lease ok (0x160001)
2018-02-25 17:13:29.781 [DEBUG][20] Renew lease ok (0x160001)
2018-02-25 17:13:34.967 [DEBUG][25] Renew lease ok (0x160001)
2018-02-25 17:13:40.101 [DEBUG][25] Renew lease ok (0x160001)
.... so some of the log files are 500K, most of it these messags. (Notice theres ten odd per min... seems odd, but probably another un-related issue?)
Hope this drivel helps!
Thanks for NextPVR, it's great. Would love to get it to a reliable state for me. Thanks.
