Page 1 of 4 123 ... LastLast
Results 1 to 10 of 31

Thread: epg auto update failed

  1. #1
    Join Date
    Sep 2015
    Location
    United States
    Posts
    19

    epg auto update failed

    EPG auto update for my IPTV service xml failed 3 nights in a row. It never fails if I hit update EPG in settings. The funny thing is it seems random because I have the exact same IPTV account with same username/settings on another pc running at another house(different update time). This morning that one succeeded while mine failed, yesterday morning they both failed. My service only offers 24 hours ahead of epg so if I don't catch it I lose my recordings for the day. I should probably switch to SD and map my channels because 24 hours sucks anyway but since lots of people use IPTV xml I figure why not throw this out there? Thanks.

    EDIT: snip

  2. #2
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,660
    I removed the logs url because an exception message had an xmltv url with username/password. (usually IPTV providers don't have username/password protection on this, so I wasn't obfuscating this info in the logs)

    I can see it tried to update the EPG overnight, but wasn't able to download the from the URL. It looks like it's something networky, possible to do with using a proxy or vpn?
    2019-03-20 02:07:11.971 [ERROR][10] Unexpected error processing xmltv file (http://iptv-area-51.tv:2095/xmltv.php?...snip...): System.Net.WebException: An exception occurred during a WebClient request. ---> System.Configuration.ConfigurationErrorsException: Error creating the Web Proxy specified in the 'system.net/defaultProxy' configuration section. ---> System.DllNotFoundException: Unable to load DLL 'rasapi32.dll':

  3. #3
    Join Date
    Sep 2015
    Location
    United States
    Posts
    19
    Ahh thanks I missed that it didn't obscure my info thanks for removing that. No proxy, no vpn just a super random problem that seems exclusive to the auto-update system. Probably also exclusive to that iptv service's way of handling requests. Even when I make a powershell script to download the epg file it seems to work every time. *Shrugs*

  4. #4
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,660
    When you hit the 'update epg' button does that work? That function, and the overnight update, both run the same bit of code. The only difference is that one is that the overnight update is running as a different user account ("localsystem").

  5. #5
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,660
    Googling the message, I can see plenty of posts with this same error. It does sound like something about proxy settings or similar. You sure your machine or router doesn't use VPN or proxy?

  6. #6
    Join Date
    Sep 2015
    Location
    United States
    Posts
    19
    Yes I saw that when I googled this error. I am a little out of my depth so I simply went to amibehindproxy on google and it said no for both v4 and v6 and while I run VPN on another computer I have in the house it's not on the one running nextpvr. As I said this error comes up in another house too. so while I've never been able to reproduce the error through manual epg updates it may just be something exclusive to that iptv service's system unfortunately. Any help would be appreciated but it's starting to look like I need to give SD their 25 bucks. Another question would be if this can't be resolved through the normal update system since I have a powershell script that downloads the epg to a local file is it possible to get nvpr's iptv system to use that instead of a download?

  7. #7
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,660
    You can always run "nextpvr.exe -UpdateEPGOnly" to force it to run the EPG as your account. You can run this manually, or use the Windows scheduler to have it happen at a certain time.

  8. #8
    Join Date
    Sep 2015
    Location
    United States
    Posts
    19
    makes sense I guess my answer is to schedule that to run as a fail safe after the normal auto update every night so I guess problem solved. My next question has to do with having to restart the recording service and kill ffmpeg every time I open kodi. Is that normal and if not should I make a new thread here or start one over on the kodi forum?

  9. #9
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,660
    What is running ffmpeg? Does that run each time you view/record an IPTV channel? It shouldn't.

  10. #10
    Join Date
    Sep 2015
    Location
    United States
    Posts
    19
    I assumed it had something to do with transcoding that sometimes triggers that ffmpeg that's in the "other" folder of npvr which I'm guessing it shouldn't need to do. I guess I could just delete it since it doesn't get used other than me having to kill it. When I start kodi or even emby on the initial startup I always have to restart the recording process. In Kodi it would say tuner not available until I did and after that it was fine. However a lot of times I also have to kill ffmpeg which would be running my cpu to 100% or else right clicking npvr in the notification tray does nothing. Once I do this all channels play fine, changing channels is fine. This is also consistent across those two totally different computers in different houses I mentioned earlier so I'm assuming this another issue specific to my iptv provider.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •