Update (10/20/17.1A)
I hadn't check the log files before I wrote the previous update below (becuz it was a successful download
There are 50+ "HTTP Error 500: Internal Server Error" msgs that occurred during the download, a number of them were for the same EP(?) nos. So I guess it's a good sign that the s/w is working because, despite the errors (which I assume are caused by the zap2it website), the downloads have completed successfully. Something I haven't experienced in a while.
Cheers.....
Update (10/20/17.1)
Think I may have solved things for me, as in everything. Have had 2 nights of successful guide downloads with xtra details download/append enabled. I won't be convinced until I get at least 1 good week of error-free downloads, tho.
I'm thinking this all traces back to the system crash I mentioned previously. First I thought either an IP addr conflict or maybe a router issue (this latter one from last Sun. early AM when we had a power loss and maybe a few brownouts leading up to it causing a glitch in the router) and have rebooted the router at least once since then. I had also changed the network cable (but that's an unlikely culprit becuz I could ping to the RPI 3 without data loss...it was getting out from the system that seemed to be the problem). So, yesterday I went into the OSMC/RPI 3 management addon and changed the IP addr (Had done this before without success and I also tried using DHCP....no help either). At one point I noticed there was a "Reset" button on the screen where I changed the IP addr. Pressing that seems to have been the key. This is the first time in a long time that I've had 2 consecutive successful downloads (w/xtra details enabled). Like I said, when I get to 7 or more, I'll believe it. However, I'm more optimistic this morning.
My guess is the "system crash" may have impacted the network setup on the HDD (the recent power outage just made things unacceptably worse). Hitting "Reset" seems to have cleaned out whatever it might have been and put it back to some sort of default config, which then allowed me to successfully redo the IP addr setup.
I'll keep you posted on the progress
And I think I''m in a good place to check out the new code when it's ready.....Cheers....
Update (10/18/17.2)
Ignore the previous update (10/18/17.1) below. Discovered I have an internet connection problem with the RPI 3. Can't tell if it's h/w (like cable or switch box...most likely) or something in the system. Seems to ping OK to the address but the url problem in the log listed below is due to the RPI 3 not getting out to the network (says it's busy, etc.). Won't be able to troubleshoot for a day or 2. I do have another new/unused RPI 3 I could replace it with, but it doesn't have an MPEG license installed yet. Shouldn't be a problem just to see if the RPI 3 is OK. Still thinking it's related to the system crash I had a month or 2 back (as in, maybe a partial cause).
Let you know what I find....Cheers.....
Update (10/18/17.1)
OK. Something very odd is now happening. I disabled both download and append xtra details (have been experimenting with the combination of the 2) and got the error msg below (note....log files show recent date so zap2xml is attempting to run). Haven't had a guide update in ~4 days.
Anything obvious to you? I'm wondering if somehow some of the network stuff on the RPI 3 got messed up
Or, is it possible the website isn't available ~3AM in the morning (when my downloads are supposed to happen)?
Thx and cheers....
Logging in as
[email protected]
http://tvschedule.zap2it.com/tvlistings/...tvschedule
Exception
error<class 'urllib2.URLError'>
Traceback (most recent call last):
File "/home/osmc/.kodi/addons/script.module.zap2xml/zap2xml.py", line 2147, in <module>
main()
File "/home/osmc/.kodi/addons/script.module.zap2xml/zap2xml.py", line 2054, in main
data = getURL(url)
File "/home/osmc/.kodi/addons/script.module.zap2xml/zap2xml.py", line 213, in getURL
login()
File "/home/osmc/.kodi/addons/script.module.zap2xml/zap2xml.py", line 633, in login
loginZAP(br)
File "/home/osmc/.kodi/addons/script.module.zap2xml/zap2xml.py", line 567, in loginZAP
br.open(urlRoot + 'ZCLogin.do?method=getStandAlonePage&aid=tvschedule')
File "/home/osmc/.kodi/addons/script.module.mechanize/lib/mechanize/_mechanize.py", line 203, in open
return self._mech_open(url, data, timeout=timeout)
File "/home/osmc/.kodi/addons/script.module.mechanize/lib/mechanize/_mechanize.py", line 230, in _mech_open
response = UserAgentBase.open(self, request, data)
File "/home/osmc/.kodi/addons/script.module.mechanize/lib/mechanize/_opener.py", line 193, in open
response = urlopen(self, req, data)
File "/home/osmc/.kodi/addons/script.module.mechanize/lib/mechanize/_urllib2_fork.py", line 344, in _open
'_open', req)
File "/home/osmc/.kodi/addons/script.module.mechanize/lib/mechanize/_urllib2_fork.py", line 332, in _call_chain
result = func(*args)
File "/home/osmc/.kodi/addons/script.module.mechanize/lib/mechanize/_urllib2_fork.py", line 1142, in http_open
return self.do_open(httplib.HTTPConnection, req)
File "/home/osmc/.kodi/addons/script.module.mechanize/lib/mechanize/_urllib2_fork.py", line 1118, in do_open
raise URLError(err)
urllib2.URLError: <urlopen error [Errno 110] Connection timed out>
---------------------------------------------------------------------------------------------------------------------------------
Update (10/13/17):
Discovered I had a power cable issue so I needed to restart my "experiment". More later...
Checked the TVHeadEnd addon again. Indeed it does not update the Internal EPG cron setting (checked and I was editing the correct one). I used the addon, requested to change it and used the on-screen keyboard to make the change. When I clicked on "Done" and it returned to the "Select an EPG grabber configuration to edit" window, the internal cron setting had not changed. I also confirmed it with the web interface.
Then I made an edit with the web interface, did a save and went back to the addon. It showed the change I made.
So, either my system is behaving badly (which is always a possibility
or something's amiss with the addon.
Have not checked any of the other items on the list, but will do so when I get the chance and report back.
Cheers....
(2017-10-11, 21:49)stephr1 Wrote: [ -> ]As I said, I look forward to the new version. Hopefully that makes my current "stuff" like it never happened
wrt to cron setting...fairly certain it was the internal grabber, but I'll try it again and make sure. Just as a side note, I did not see the OTA cron setting change either. I'll confirm that, as well.
Cheers and thx....
(2017-10-11, 18:25)edit4ever Wrote: [ -> ]Thanks for the update - my new version won't use mechanize - so that should help you.
As for the cron setting - there are two different cron lines - one for OTA and one for internal grabbers - so make sure you were changing the internal grabber cron. :-)