Error 502 to many tries in 4 seconds

jds · Post by **jds** » Tue Mar 18, 2003 6:41 pm

I sometimes get a message like this in clusters. What is causing it? Is it something I can adjust in NewsPro? The error is approximate. It goes by quickly.

alex · Post by **alex** » Tue Mar 18, 2003 7:03 pm

if it is not newsfeeds and caused by something unrelated connected to their restrictions, you may try to increase the number of retries or to introduce the connect delay (then better to have keep-alive on so not to suffer the delay on every task).

Tha*Lunat!k · Post by **Tha*Lunat!k** » Tue Mar 18, 2003 8:43 pm

It is a Newsfeeds message. Usually it happens when there is a server error but your newsreader continues to try to access the server and keeps generating the error.

Like recently the Goliath-East server has connections reduced to 2 per user instead of 3. NewsPro tried to open a third and I got the error that 2 was the max, then NewsPro tried to open a third connection again and I got the "502 Too many tries in 4 seconds" error over and over until I reduced the max tasks on Goliath-East to just 2 in the properties.

edfreeman · Post by **edfreeman** » Thu Mar 20, 2003 1:16 am

I wish Newsfeeds would just tell us when they do that . . .

Tha*Lunat!k · Post by **Tha*Lunat!k** » Thu Mar 20, 2003 8:06 pm

Someone in a forum somewhere mentioned that they were seeing an error related to 3 connections, and another person replied that Newsfeeds had said the server was having problems and reduced to 2 temporarily. I could find no post about that, but I dropped my limit to 2 anyhow.

Guest · Post by **Guest** » Sat Mar 22, 2003 8:17 pm

Or it could be one has reached one's download limit for the day

Tha*Lunat!k · Post by **Tha*Lunat!k** » Sun Mar 23, 2003 10:52 am

It could be that as well. I've found this error occurs when NewsPro tries to access a server that has reported an error to you just moment before.

For example NewsPro launches three tasks to a server, the first task gives an error "Too much downloaded", then the other two streams that were already launched report "Too many attempts in 4 seconds". The same goes for other errors such as "Invalid authentication info" or "Too many connections", etc.

Basically it happens as a result of attempts to connect upon already receiving a different error. I haven't had this error occur just out of nowhere though.