I'm using the following to force a refresh of a custom source XML data
curl -XPUT http://127.0.0.1:8089/dvr/lineups/XMLTV-sourcename
I stagger the refreshes for multiple sources in a cron job.
Problem I am seeing is that all custom XML sources are refreshed, not just the one specified.
Is this a bug, or a problem/misunderstanding on my end.
Thanks.
I don't have any servers with multiple XMLTV sources.
For my servers that have a single XMLTV source, the web UI still issues that PUT command when selecting 
Manage > Redownload XMLTV
From past experience, all M3U-based sources were lumped together for server operations; I believe this extends to guide updates.
Is there a reason why one of the refresh options available in the web UI is insufficient?
It's part of my scripts....I do my own Pluto, Stirr and Plex processing. The M3U update seems to be source specific. Just the guide XML that always seem to do everything.
Check what the web UI does (dev tools network inspector) when you select
Manage > Redownload XMLTV on one of your sources
If it just does that PUT for that source and the dvr log shows it redownloading all XMLTV sources, you know it's not just you.
That way you can express your concern about how it acts using the supported web UI, instead of the unsupported, private API.
Good idea. Did the double check (I had originally got the command from the forum) and its the same as I am using
The interesting thing is that the web does the same thing...
This is probably related to the web UI guide displaying all M3U channels regardless of which custom channel was chosen.
The manner in which importing M3U playlists is being used by some users is exposing these edge cases that were probably never conceived, because adding 8 different FAST services along with myriad random IPTV feeds was not the original intent.
This might be able to be fixed, but it may not be done as quickly as some may assume because it might need deeper architectural changes to address the root.
Please try the latest pre-release and let us know if the behavior is better.
Thanks for the quick update...but sorry, still the same downloading multiple sources.
Also, received a panic loading the pre-release
2024/01/10 14:27:09.411627 [SYS] Downloading new version v2024.01.10.2106
2024/01/10 14:27:13.082282 [SYS] Update downloaded and verified successfully.
2024/01/10 14:27:19.020618 [SYS] Bonjour service stopped.
2024/01/10 14:27:19.026203 [DVR] Recording engine stopped.
2024/01/10 14:27:19 [Recovery] 2024/01/10 - 14:27:19 panic recovered:
send on closed channel
runtime/chan.go:206 (0x40aea7)
runtime/chan.go:145 (0x40a936)
github.com/fancybits/channels-server/dvr/events.go:82 (0x1bdaf7a)
github.com/fancybits/channels-server/http_dvr_misc.go:114 (0x1bdaf18)
github.com/gin-gonic/gin@v1.9.1/context.go:169 (0x1b864f2)
github.com/fancybits/channels-server/http.go:410 (0x1b861f9)
github.com/gin-gonic/gin@v1.9.1/context.go:169 (0x1b86166)
github.com/fancybits/channels-server/http.go:387 (0x1b86154)
github.com/gin-gonic/gin@v1.9.1/context.go:169 (0xb7d40a)
github.com/fancybits/channels-server/http.go:362 (0x1b85e2b)
github.com/gin-gonic/gin@v1.9.1/context.go:169 (0x1b859c4)
github.com/fancybits/channels-server/http.go:276 (0x1b853b1)
github.com/gin-gonic/gin@v1.9.1/context.go:169 (0xb89639)
github.com/gin-gonic/gin@v1.9.1/recovery.go:107 (0xb89627)
github.com/gin-gonic/gin@v1.9.1/context.go:169 (0xb8881d)
github.com/gin-gonic/gin@v1.9.1/logger.go:240 (0xb887e0)
github.com/gin-gonic/gin@v1.9.1/context.go:169 (0xb7d40a)
github.com/gin-contrib/sessions@v0.0.5/sessions.go:54 (0x1b88dbc)
github.com/gin-gonic/gin@v1.9.1/context.go:169 (0x1c13d42)
github.com/fancybits/channels-server/http.go:586 (0x1c13d30)
github.com/gin-gonic/gin@v1.9.1/context.go:169 (0xb8793a)
github.com/gin-gonic/gin@v1.9.1/gin.go:598 (0xb875cd)
github.com/gin-gonic/gin@v1.9.1/gin.go:554 (0xb87111)
net/http/server.go:2938 (0x726f0d)
net/http/server.go:2009 (0x722933)
runtime/asm_amd64.s:1650 (0x4741a0)
Another update.....restarted the server. Now it only fetches the specified source and only reindexes other sources. This works.
The next pre-release will have a fix for the panic you saw. Thanks for reporting it.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
