I'm receiving various intermittent errors when connecting to icetv from my T4.
The log various shows Can not retrieve channel map, can not download EPG, can not download timers. Read timed out.
It doesn't seem to be causing a problem as it is only intermittent.
There were a couple of other similar reports (http://beyonwiz.com.au/forum/viewtopic.php?f=55&t=11492) on the Beyonwiz forum last night. One user's (Maindee) may be due to the user having problems in their local network.
I noticed logged "Can not retrieve channel map" errors in my T4's IceTV logs between 21:00 and 22:00 last night, and another one (on a different T4) at 10:18 today.
The error reports on the Beyonwiz forum came from users in Melbourne, Perth and Canberra, so not region-specific.
The problem appears to have been resolved around 10:30Am today.
I am getting my updates regularly now.
Quote from: grampus on September 17, 2017, 12:06:54 PM
The problem appears to have been resolved around 10:30Am today.
I am getting my updates regularly now.
Hasn't gone away for me:
2017-09-17 18:14:10 AEST - "Can not retrieve channel map"
2017-09-17 18:17:58 AEST - "Can not download EPG"
2017-09-17 18:18:08 AEST - "Can not download timers"
2017-09-17 18:20:28 AEST - "EPG download OK"
2017-09-17 18:20:29 AEST - "Timers updated OK"
Quote from: prl on September 17, 2017, 06:21:39 PM
Quote from: grampus on September 17, 2017, 12:06:54 PM
The problem appears to have been resolved around 10:30Am today.
I am getting my updates regularly now.
Hasn't gone away for me:
2017-09-17 18:14:10 AEST - "Can not retrieve channel map"
2017-09-17 18:17:58 AEST - "Can not download EPG"
2017-09-17 18:18:08 AEST - "Can not download timers"
2017-09-17 18:20:28 AEST - "EPG download OK"
2017-09-17 18:20:29 AEST - "Timers updated OK"
Nor me. ole foot in mouth.
Intermittent failures now.
Still having problems with Icetv.
Not sure how this will help but traced api.tpg.com.au
Which seems to get to a router at tpg, then gets sent out to the US.
into the wilderness.
Of course I don't have a trace when the service was working for comparison.
And maybe only see what I want to see.
The first few routers would be my NBN router, then via my isp TPG
Any suggestions?
-- Scany to api.icetv.com.au ---
1) 192-168-1-1.tpgi.com.au (192.168.1.1) 4.204 ms, 12/12 ps, 0.0% loss
2) 10-20-25-29.tpgi.com.au (10.20.25.29) 18.604 ms, 12/12 ps, 0.0% loss
3) 203-219-155-130.tpgi.com.au (203.219.155.130) 33.206 ms, 12/12 ps, 0.0% loss [AS 7545] Australia
4) syd-gls-har-crt2-be-10.tpgi.com.au (202.7.173.17) 32.402 ms, 12/12 ps, 0.0% loss [AS 7545] Australia
5) 203.29.134-140.tpgi.com.au (203.29.134.140) 38.414 ms, 12/12 ps, 0.0% loss [AS 7545] Australia
6) 202.7.162.38 (202.7.162.38) 30.716 ms, 12/12 ps, 0.0% loss [AS 7545] Australia
7) * * *
8) * * *
9) 52.95.37.163 (52.95.37.163) 30.469 ms, 12/12 ps, 0.0% loss United States
10) 52.95.37.33 (52.95.37.33) 25.286 ms, 12/12 ps, 0.0% loss United States
11) 52.95.37.48 (52.95.37.48) 33.867 ms, 12/12 ps, 0.0% loss United States
12) 52.95.37.57 (52.95.37.57) 27.044 ms, 12/12 ps, 0.0% loss United States
13) 54.240.192.113 (54.240.192.113) 26.482 ms, 12/12 ps, 0.0% loss [AS 16509] United States
14) * * *
as a further test, I went through logon procedure on the Beyonwiz. The login worked as OK as shown in the log.
I can only assume from this that it doesn't go via the same entry point at Ice as opposed to the entry point for updates.
so my tiny brain is a little more confused.
It seems to be very intermittent for me. There's been a few errors in the log this morning but the epg is up to date and timers are coming through.
I am seeing the same thing on the T2 that I have here, not sure what the root cause is at the moment though, but we are checking it out.
Thanks, Daniel.
Is there anything that a user can supply to,assist in this problem?
I've seen it reported that some IceFolk think that I'm helping Daniel Hall with this problem. Beyond the posts describing the problem that I've made here and on the Beyonwiz forum, I'm not (and I don't think I can, other than testing whether it has been resolved).
I have been helping Daniel with another (http://forum.icetv.com.au/iceforum/icetv-epg-content/5/7flix-epg-blank-saturday-16th/5750/) IceTV EPG problem.
I'm having the same intermittent errors on a Beyonwiz T4. Here is a graphic of the iceTV log.
not sure if it willhelp anyone who may be looking at the problem.
but FWIW
I've had 1/2 hourly updates from around 12:30 pm, and covering the same period shown n the above post up now without error.
where as before as like most I imagine it was pretty abysmal
I am seeing something in the server logs at the moment and am zeroing in on a possible cause, hopefully will have some more information soon.
Good to hear. Thanks for the update, Daniel.
I'm not sure if this is related, but my Skippa has been driving me crazy for the last week, where it becomes unresponsive to the remote for about 5-10 seconds every 30-60 seconds.
I normally have only seen such behaviour when there has been internet connection or IceTV server issues.
I've been suspecting things like HDD fragmentation, dying power supply, hardware, etc. There have been a few times I've wondered if it was Ice server related.
Any other Skippa users experiencing this behaviour recently?
Does ad-skip processing rely on recurring server/internet access, as it seems to be worse during such times.
I've seen the same behaviour. I assumed it was because I had recently replaced the hard disk, but apparently not.
Try a factory reset without formatting the hard drive. It works from when mine gets wonky.
I'll try the factory reset this weekend, but if that doesn't help I'm considering swapping out the HDD to my backup Skippa (yes, lucky me :) ) to try and troubleshoot.
Before I go to all that trouble: DANIEL - did anything come from the possibly-suspect log activity which may indicate an intermittent server issue?
I am definitely seeing instances where the server can take up to a maximum of 30 seconds to respond to a request (which is the max, and the minimum is only 124ms), the average being 8.99 seconds, and with the Beyonwiz timeout set to 10 seconds once it gets above that we get an issue.
Quote from: Daniel Hall at IceTV on September 22, 2017, 10:36:06 AM
I am definitely seeing instances where the server can take up to a maximum of 30 seconds to respond to a request (which is the max, and the minimum is only 124ms), the average being 8.99 seconds, and with the Beyonwiz timeout set to 10 seconds once it gets above that we get an issue.
Thanks for that.
Do you know if the Skippa constantly polls the server, or just every 5 minutes for data updates?
As advised, I've been having this loss of response constantly for the last week or two, and its appears more so during ad-skip processing or recording.
Quote from: ChrisW on September 22, 2017, 10:53:33 AM
Quote from: Daniel Hall at IceTV on September 22, 2017, 10:36:06 AM
I am definitely seeing instances where the server can take up to a maximum of 30 seconds to respond to a request (which is the max, and the minimum is only 124ms), the average being 8.99 seconds, and with the Beyonwiz timeout set to 10 seconds once it gets above that we get an issue.
Thanks for that.
Do you know if the Skippa constantly polls the server, or just every 5 minutes for data updates?
As advised, I've been having this loss of response constantly for the last week or two, and its appears more so during ad-skip processing or recording.
The Skippa connects every 15 minutes for guide and timer updates, autoskip settings updates are less frequent (from memory its only once per hour) and there is no contact with the server while autoskip is processing.
The slow responses are only for the API at this stage, the autoskip updates are currently averaging only 9.29ms for requests. So any slowdown and unresponsiveness is probably from the delays in getting timer and epg information, timeouts and issues here can affect the interface and responsiveness of the box due to the way the requests are made.
Ok, this one has definitely been resolved now, request times are back to an average of around 2 seconds.
Great! Thanks, Daniel. I'll keep an eye on it for the next few days.
Good one. my log starts at 1622pm. 1/2 hour updates. no errors since then
Skippa behaviour has also returned to normal.
Thanks Daniel.
I haven't seen any timeout issues on our Beyonwiz T series boxes since Daniel posted that the problem had been fixed.
+1
and a 2 :)
Reluctant to resurrect an old thread but I have been experiencing random failures of my T2 to update at 15 minute intervals lately. Looking at the IceTV log this morning I observed two instances of "Can not retrieve channel map" on consecutive polls of the IceTV servers. Regular 15 minute updates resumed successfully thereafter.
I'm not going to discount networking issues at my end, but because the updating issues are apparently random and updates resume successfully, that does not look like the cause to me.
Quote from: Daniel Hall at IceTV on September 25, 2017, 03:21:09 PM
Ok, this one has definitely been resolved now, request times are back to an average of around 2 seconds.
There haven't been any other more recent posts on this forum, or as far as I can see the Beyonwiz forum, about this issue, so it would seem that there is nothing awry at the IceTV end.
Would anyone care to hazard a guess as to the cause of this intermittent issue? It is not so critical to the functioning of the T2 as updates appear to resume after about an hour.
Quote from: raymondjpg on June 06, 2019, 11:04:29 AM
There haven't been any other more recent posts on this forum, or as far as I can see the Beyonwiz forum, about this issue, so it would seem that there is nothing awry at the IceTV end.
I've had it 49 times this month, and 100 times last month - so I wouldn't rule out the IceTV end.
Quote from: grumpy_geoff on June 06, 2019, 01:13:51 PMI've had it 49 times this month, and 100 times last month - so I wouldn't rule out the IceTV end.
I based that assessment on the apparent lack of complaints about the issue over the past two years.
Just to reassure myself that my LAN or wireless AP are not at fault I would really like to view IceTV update logs from the T2 that go back further than those available through the plugin GUI. Can you point me to where I might find those logs? I did a search via Filezilla but couldn't see anything obvious.
TIA
I had a look around and there was a table that was full, have cleaned this out now and setup some checks on it, should be all good again just after 2pm.
Quote from: Daniel Hall at IceTV on June 06, 2019, 01:50:09 PMI had a look around and there was a table that was full, have cleaned this out now and setup some checks on it, should be all good again just after 2pm.
Thanks Daniel, but I'd still like to have a look at my update logs overnight from early morning 6 June. I suspect that such logs do not exist on the T2 (I had a look but can't be sure). Can IceTV provide me with those logs? If I need to lodge a support ticket I'll do so.
Regards
Quote from: raymondjpg on June 06, 2019, 01:35:02 PM
Quote from: grumpy_geoff on June 06, 2019, 01:13:51 PMI've had it 49 times this month, and 100 times last month - so I wouldn't rule out the IceTV end.
I based that assessment on the apparent lack of complaints about the issue over the past two years.
Just to reassure myself that my LAN or wireless AP are not at fault I would really like to view IceTV update logs from the T2 that go back further than those available through the plugin GUI. Can you point me to where I might find those logs? I did a search via Filezilla but couldn't see anything obvious.
TIA
I was checking the debug logs, but you need to have debug logging enabled of course.
Quote from: grumpy_geoff on June 06, 2019, 03:29:01 PMI was checking the debug logs, but you need to have debug logging enabled of course.
Thanks. I can always enable debug logging overnight and see what transpires.
Quote from: raymondjpg on June 06, 2019, 01:58:45 PM
Quote from: Daniel Hall at IceTV on June 06, 2019, 01:50:09 PMI had a look around and there was a table that was full, have cleaned this out now and setup some checks on it, should be all good again just after 2pm.
Thanks Daniel, but I'd still like to have a look at my update logs overnight from early morning 6 June. I suspect that such logs do not exist on the T2 (I had a look but can't be sure). Can IceTV provide me with those logs? If I need to lodge a support ticket I'll do so.
Regards
Hi raymondjpg,
I have had an email sent to you with a screenshot of the logs.
Quote from: Daniel Hall at IceTV on June 06, 2019, 04:57:01 PMI have had an email sent to you with a screenshot of the logs.
Thanks Daniel but that email has not come through (yet).