Bug #2568
Mux scanning doesn't stop
100%
Description
I enabled idle scan on 3 of my 6 adapters. "Skip initial scan" is selected.
After 3 hours, the scan queue (in Services tab) is still at 91 out of 93 muxes (28.2E) and 5 out of 5 (23.5E).
I can see all the expected messages
Dec 21 15:27:23 sat tvheadend5893: mpegts: 12343.5H in 28.2E - tuning on STV090x Multistandard : DVB-S #5
Dec 21 15:27:23 sat tvheadend5893: subscription: 0454: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #5", network: "28.2E", mux: "12343.5H", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 21 15:27:23 sat tvheadend5893: mpegts: 11067.5V in 28.2E - tuning on STV090x Multistandard : DVB-S #4
Dec 21 15:27:23 sat tvheadend5893: subscription: 0455: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #4", network: "28.2E", mux: "11067.5V", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 21 15:27:33 sat tvheadend5893: mpegts: 11067.5V in 28.2E - scan needs more time
Dec 21 15:27:33 sat tvheadend5893: mpegts: 12343.5H in 28.2E - scan needs more time
Dec 21 15:27:46 sat tvheadend5893: mpegts: 11067.5V in 28.2E scan complete
Dec 21 15:27:46 sat tvheadend5893: subscription: 0455: "scan" unsubscribing
Dec 21 15:27:52 sat tvheadend5893: mpegts: 12343.5H in 28.2E scan complete
Dec 21 15:27:52 sat tvheadend5893: subscription: 0454: "scan" unsubscribing
Files
History
Updated by Rob vh almost 10 years ago
Updated by in fact, after I disabled "Idle scan" for all adapters and while hts is recording from these 2 muxes, I still see this in the log:
Dec 21 20:45:02 sat tvheadend5893: subscription: 0A65: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #3", network: "28.2E", mux: "11126.5V", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 21 20:45:02 sat tvheadend5893: mpegts: 11126.5V in 28.2E scan complete
Dec 21 20:45:02 sat tvheadend5893: subscription: 0A65: "scan" unsubscribing
Dec 21 20:45:03 sat tvheadend5893: subscription: 0A66: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #2", network: "23.5E", mux: "12187H", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 21 20:45:03 sat tvheadend5893: mpegts: 12187H in 23.5E scan complete
Dec 21 20:45:03 sat tvheadend5893: subscription: 0A66: "scan" unsubscribing
Dec 21 20:45:12 sat tvheadend5893: subscription: 0A67: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #3", network: "28.2E", mux: "11126.5V", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 21 20:45:12 sat tvheadend5893: mpegts: 11126.5V in 28.2E scan complete
Dec 21 20:45:12 sat tvheadend5893: subscription: 0A67: "scan" unsubscribing
Dec 21 20:45:13 sat tvheadend5893: subscription: 0A68: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #2", network: "23.5E", mux: "12187H", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 21 20:45:13 sat tvheadend5893: mpegts: 12187H in 23.5E scan complete
Dec 21 20:45:13 sat tvheadend5893: subscription: 0A68: "scan" unsubscribing
Dec 21 20:45:22 sat tvheadend5893: subscription: 0A69: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #3", network: "28.2E", mux: "11126.5V", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 21 20:45:22 sat tvheadend5893: mpegts: 11126.5V in 28.2E scan complete
Dec 21 20:45:22 sat tvheadend5893: subscription: 0A69: "scan" unsubscribing
Dec 21 20:45:23 sat tvheadend5893: subscription: 0A6A: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #2", network: "23.5E", mux: "12187H", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 21 20:45:23 sat tvheadend5893: mpegts: 12187H in 23.5E scan complete
Dec 21 20:45:23 sat tvheadend5893: subscription: 0A6A: "scan" unsubscribing
Updated by Rob vh almost 10 years ago
After the daily SEGV crash, the scan now occurs every 10 seconds on which ever mux is recording or streaming:
Dec 25 10:35:14 sat tvheadend29992: subscription: 1D0F: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #3", network: "28.2E", mux: "10964.25H", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 25 10:35:14 sat tvheadend29992: mpegts: 10964.25H in 28.2E scan complete
Dec 25 10:35:14 sat tvheadend29992: subscription: 1D0F: "scan" unsubscribing
Dec 25 10:35:24 sat tvheadend29992: subscription: 1D10: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #3", network: "28.2E", mux: "10964.25H", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 25 10:35:24 sat tvheadend29992: mpegts: 10964.25H in 28.2E scan complete
Dec 25 10:35:24 sat tvheadend29992: subscription: 1D10: "scan" unsubscribing
Dec 25 10:35:34 sat tvheadend29992: subscription: 1D11: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #3", network: "28.2E", mux: "10964.25H", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 25 10:35:34 sat tvheadend29992: mpegts: 10964.25H in 28.2E scan complete
Dec 25 10:35:34 sat tvheadend29992: subscription: 1D11: "scan" unsubscribing
Dec 25 10:35:44 sat tvheadend29992: subscription: 1D12: "scan" subscribing to mux, weight: 1, adapter: "STV090x Multistandard : DVB-S #3", network: "28.2E", mux: "10964.25H", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Dec 25 10:35:44 sat tvheadend29992: mpegts: 10964.25H in 28.2E scan complete
Dec 25 10:35:44 sat tvheadend29992: subscription: 1D12: "scan" unsubscribing
Updated by
Updated by Rob vh almost 10 years ago
- File hts.log.txt hts.log.txt added
My adapters are all disabled for inactive scanning, so you see the "no adapter enabled" messages.
While I enabled trace, a recording on 28.2E was busy, and that's the adapter where you see subscriptions happening.
Updated by Jaroslav Kysela almost 10 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset commit:tvheadend|cde79eb75fca1c46896a7f355f7ebec6f0ee065c.
Updated by Jaroslav Kysela almost 10 years ago
OK, I see the "problem" now. I added the check if the mux is already active then it's skipped, but I think that you should disable the Idle Scan at all (in the network settings - it's the default). It's not useful for the standard operation. I marked this field in the network grid as hidden now. If you like to scan periodically for new services, use the OTA EPG scheduler (each mux tune means that the new services are checked - scanned).
Updated by Raymond Paulsen almost 10 years ago
Updated by I did watch this issue from the side line and i noticed you recommend to disable idle scan?
There are 2 places idle scan is used, tv-adapters and in network tab.
what is recommended to turn off? This will not affect the epg update?
I appreciate a clarification on this settings
regards
Updated by Rob vh almost 10 years ago
@Jaroslav
Ehrm.... I already had "idle scan" disabled (for all networks and for all adapters). However, I confirm that 3.9.2318 no longer issues the subscribe/unsubscribe messages every 10 seconds.