2026-05-01, 03:33 PM
Not sure what is going on, have 4 tuners on this system. Ignore the network drive P is unavailable messages (it's not attached currently)
I will reboot the server...
Art
I will reboot the server...
Art
|
2026-05-01, 03:33 PM
Not sure what is going on, have 4 tuners on this system. Ignore the network drive P is unavailable messages (it's not attached currently)
I will reboot the server... Art
2026-05-01, 03:46 PM
(This post was last modified: 2026-05-01, 03:59 PM by mvallevand.)
That typically means the tuner got stuck in this case that tuner didn't see any request since the 24th
2026-04-24 18:01:00.085 [DEBUG][4] Graph stopping... I offer that there are issues with the tuner. Looking at the last request 2026-04-24 17:30:06.835 [INFO][4] Got POST request: /stream/start?slipseconds=5400&target=D%3A%5Cnextpvr%5CNBC%20Nightly%20News%20With%20Tom%20Llamas%5CSeason%2002%5CNBC.Nightly.News.With.Tom.Llamas.S02E106.ts took almost 6 seconds to tune 2026-04-24 17:30:06.837 [DEBUG][4] BuildGraph 2026-04-24 17:30:09.548 [DEBUG][4] locked=0, present=0, strength=41000, quality=0 (took 2500ms to check) 2026-04-24 17:30:12.365 [DEBUG][4] locked=1, present=1, strength=-10000, quality=100 (took 1296ms to check) which is a long time for ATSC. The same channel on another tuner 2026-05-01 00:41:44.198 [INFO][22] Got POST request: /stream/start?slipseconds=5400&target=D%3A%5Cnextpvr%5CNBC%20Nightly%20News%20With%20Tom%20Llamas%5CSeason%2002%5CNBC.Nightly.News.With.Tom.Llamas.S02E111.ts 2026-05-01 00:41:44.804 [DEBUG][22] locked=1, present=1, strength=-9000, quality=98 (took 594ms to check) Under one second. Martin
2026-05-01, 04:11 PM
I'll try changing the tuner priorities.
2026-05-01, 08:51 PM
(This post was last modified: 2026-05-01, 08:55 PM by mvallevand.)
Not sure it is question of priority all your tuners started going bad.
2026-05-01 01:13:00.172 [DEBUG][10] http://localhost:56450/stream/stop?handle=47 2026-05-01 06:44:00.278 [DEBUG][10] http://localhost:52016/stream/start?slip...S74E187.ts 2026-05-01 06:45:40.305 [DEBUG][10] http://localhost:56450/stream/start?slip...S74E187.ts 2026-05-01 06:45:48.042 [DEBUG][10] http://localhost:49943/stream/start?slip...2026E87.ts 2026-05-01 06:47:28.078 [DEBUG][10] http://localhost:52016/stream/start?slip...2026E87.ts 2026-05-01 06:49:08.098 [DEBUG][10] http://localhost:49802/stream/start?slip...2026E87.ts 2026-05-01 07:00:00.081 [DEBUG][10] http://localhost:49802/stream/start?slip...2026E87.ts 2026-05-01 07:01:40.105 [DEBUG][10] http://localhost:49943/stream/start?slip...2026E87.ts 2026-05-01 07:03:20.129 [DEBUG][10] http://localhost:52016/stream/start?slip...2026E87.ts 2026-05-01 07:05:00.148 [DEBUG][10] http://localhost:49802/stream/start?slip...2026E87.ts 2026-05-01 07:45:00.202 [DEBUG][10] http://localhost:49943/stream/start?slip...2026E87.ts 2026-05-01 07:46:40.263 [DEBUG][10] http://localhost:52016/stream/start?slip...2026E87.ts 2026-05-01 07:48:20.292 [DEBUG][10] http://localhost:49802/stream/start?slip...2026E87.ts 2026-05-01 08:00:00.272 [DEBUG][10] http://localhost:49802/stream/start?slip...2026E87.ts 2026-05-01 08:01:40.299 [DEBUG][10] http://localhost:49943/stream/start?slip...2026E87.ts 2026-05-01 08:03:20.317 [DEBUG][10] http://localhost:52016/stream/start?slip...2026E87.ts 2026-05-01 08:05:00.352 [DEBUG][10] http://localhost:49802/stream/start?slip...2026E87.ts There is some funny stuffy going on with your shared drivers too at the same time. 2026-05-01 06:46:19.957 [DEBUG][129] > The network path was not found. Also in 7.0.5 you don't need to run streams anymore. Martin
2026-05-02, 04:38 PM
Recordings were ok today after a reboot.
It has a HAUPPAUGE WinTV-quadHD PCI Express TV Tuner Card 1609 from 2017, so it's getting old. I'll research what my options are for replacing it. The network path (NAS) drive is currently offline, I only use it for archived recordings. What do you mean by streams? Thanks, Art
2026-05-02, 04:46 PM
NextPVR should no longer be recording the ADS you talked about here https://forums.nextpvr.com/showthread.ph...#pid605487 so you don't need streams in your scripts.
Martin
2026-05-08, 12:37 AM
Similar issue, different machine, but same configuration & hardware (different location). Posting this in case it helps somehow.
Difficult for me to understand the log regarding the issue. I know the machine was rebooted yesterday. Art
2026-05-08, 01:07 AM
It seems slightly different, how often do you run 3 comskips at once like that what is your CPU like?
Martin
2026-05-08, 01:17 AM
It's a Shuttle XPC SH67 Intel Quad Core I5-3470 3.2 GHz. 8g ram. Windows 10. (both systems are)
It's been in use for several years. I can reduce the comskip usage. I'll have to check if I've made any changes to either system the past month or so. Art
2026-05-08, 02:02 AM
Just checked the original machine for this thread and it just had a bunch of failures again.
Before I start replacing hardware, let me know if anything else needs to be checked or would help. Art |
|
|
| Possibly Related Threads… | |||||
| Thread | Author | Replies | Views | Last Post | |
| Failed recordings "Operation timed out" | Stanno | 8 | 2,462 |
2025-04-27, 07:26 PM Last Post: Nick017 |
|
|
|
failed recordings: operation timed out or recording service not running | jobby99 | 1 | 899 |
2024-09-23, 01:48 AM Last Post: mvallevand |
| The request was aborted: The operation has timed out. | Petrovski | 5 | 2,658 |
2020-08-21, 06:02 PM Last Post: sub |
|