No response from server: Page 2 - Usenapp

No response from server

Bernd

Constantly until I restarted and selected "get latest headers..."
At the moment everything is well.
I´ll do more testing tomorrow.
Thank you for Usenapp and the quick replies.

Andre

Try to limit the "Max. connection" settings to 1 and see how it goes.

Bernd

First I tried to increase the Socket timeout to 30 sec.
That did not work. While downloading today I had the same problem as yesterday.
Connecting... Timing out ... Connecting etc...
It seems that once it disconnected no amount of reconnecting is going to fix it so you have to restart the app.
Setting Max connections to 1 indeed seems to fix the problem.

Andre

Thanks for the info.

I've created a trial account at news.individual.de and tested, but I don't have any re-connection issues.

Anyway, I'm working on it.

Andre

In the news.individual.de FAQ I read that they allow up to 4 simultaneous connections. You have configured 5 connections.
Can you change it to 3 or 4 and see how it goes?

Andre

I believe I've found the issue.

As far as I can tell it has nothing to do with the connections, but it seems that when a single article is remaining to be downloaded then the download cycles is not released and ends up in a loop.

Working on it.. 🙂

Bernd

Andre As far as I can tell it has nothing to do with the connections, but it seems that when a single article is remaining to be downloaded then the download cycles is not released and ends up in a loop.

That sounds like it could be the cause.

Andre

Bernd

Version v0.56.1 is released.
Messages like "Waiting for server response" are still there, because news servers not always respond directly, but the main issue was the endless loop and I hope that this has been fixed.

Can you confirm that?

Bernd

Andre Version v0.56.1 is released.
Messages like "Waiting for server response" are still there, because news servers not always respond directly, but the main issue was the endless loop and I hope that this has been fixed.

Can you confirm that?

Confirmed.
I´ll let you know if it happens again but at the moment all is fine.

Andre

Good to hear. I'll keep the discussion open for a while.

Bernd

Sorry, but the issue is still not entirely fixed.
Today I posted a reply into a group and reloaded all headers.
In that group the connecting... timeout, connecting... timeout loop again.
After reloading all headers again it worked.

Andre

Bernd

Can you email me the log file next time it occurs? Hopefully it shows more information regarding this issue.
The log file can be opened in "File->Open Logfile"

Thank you.

Bernd

OK. I´ll do that.

Andre

I think v0.59 has completely fixed it.
If not, please let me know otherwise I'll mark the thread as solved.

Thank you.

Andre

Sorry to hear that.
The problem is that I cannot reproduce this issue, so it is kind of hard to get this fixed.
I hope the log file gives more additional info, but please keep me sending them until it is fixed.

I'll remove your post with the link to the log file for privacy reasons.
You can also email me directly if you like.

Thanks.

Andre

I think I have found the problem.

The GROUP command and XOVER command are occasionally sent to the server in a single batch.
The server should respond to each command in the same order, but I suspect that isn't always the case and might depends on the server software.

That should explain why you have this problems and others don't (different providers = different server software)

In update v0.60, I've changed the way Usenapp communicates with the server and hopefully this has solved the problem.

v0.60 will be released this weekend.

Andre

v0.60 is released 🙂

Bernd

I think that was the problem.
Download is now very fast without any repetitions.
I´ll tell you in a couple of days if the problem reappers but right now it looks good.

Andre

Awesome.. Let's hope for the best 🙂

Bernd

I think you can close this one at last.
Thanks a lot for fixing it.
I know how hard it can be to fix something that you can´t reproduce.

« Previous Page