Errors in getting one channel's data = problems

Lucas · Post by **Lucas** » Mon Aug 01, 2005 8:41 am

Alan,

the erc works well. Thanks. At least I don't have to watch it over.
On average it takes 4-6 tries and late at night to get a succesfull run (72 channels configured).

It is strange though. These errors only started appearing the last 2 moths or so.

I' ve been using your grabber since its inception and did not have the issue in the past.

Has something changed on the RT site?

Post by **alanbirtles** » Mon Aug 01, 2005 8:55 am

not that i know of, it could just be increased traffic, I know that I probably have in the region of 500-1000 users and there is the traffic from the main xmltv application too, i could add an option to configure what the connection and read timeouts are, but as far as i can remember they are set at 10s which is pretty high anyway

Post by **alanbirtles** » Mon Aug 01, 2005 5:50 pm

there is actually already an option to increase the timeouts, open the ini file and in the options section change the item called "Timeouts (ms)" to the number of milliseconds you want to set the timeouts to

Lucas · Post by **Lucas** » Tue Aug 02, 2005 8:40 am

I did and it makes a difference.

Previously I was changing them in the GUI but that did not have an effect.
It was reverting back to defaults every time.

I did a run last night and there were no errors first go.

In general I run the grab once a week.

Post by **alanbirtles** » Mon Aug 29, 2005 8:42 pm

just found that the retries parameters werent being displayed in the config screen properly (the changes were being saved though), also the connection timeouts are something different to the retries delay (i only put them in the ini file because most people wont need to change them and the grabber wont work if you set them too low)

Lucas · Post by **Lucas** » Tue Aug 30, 2005 12:10 pm

Figured it out already.

Note that in the ini file I've set the value to 3000.
Nevertheless I still get timeouts.........

Post by **alanbirtles** » Tue Aug 30, 2005 12:16 pm

i think the default is 10000, but on a slow dialup connection (especially all the way from greece) the timeouts could be even higher, there is no disadvantage to having higher timeouts it just means that is the connection does fail it will wait longer before realising

Lucas · Post by **Lucas** » Tue Aug 30, 2005 2:35 pm

From memory it was 1000 and I increased it to 3000.

Maybe I will wip it up to 30000 (30secs) to see if that helps

Lucas · Post by **Lucas** » Fri Sep 09, 2005 8:18 am

Alan, tried 2.20 this morning.

Works fine. I ran the console version.
Don't know if it is a one of thing but there were no timeout retries.