The operation has timed out

[artmetz]

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

[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

[artmetz]

I'll try changing the tuner priorities.

[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