Hi Alex, a quick question. When I use rescan headers, sometimes the task will somehow fail half-way through and start from the beginning. I've set the max retry to 30 and I've seen 15 attempts in the task manager screen for a single newsgroup on a server. What could have possibly caused that? The server itself has no problem because I've other threads downloading from it.
Also, what does the different colors in the headers section of the task manager signifies?
Regards,
JK
Rescanning headers keep retrying ...
it shows the error in the task manager, the error pane after the headers pane.
if it is read timeout you may try to increase it (in properties->general, in the future it may move to properties->tasks).
different colors indicate different stages, for rescan it is rescanning first and then downloading new headers (by default newspro downloads new headers after rescan - set in properties->general).
if it is read timeout you may try to increase it (in properties->general, in the future it may move to properties->tasks).
different colors indicate different stages, for rescan it is rescanning first and then downloading new headers (by default newspro downloads new headers after rescan - set in properties->general).
-
Guest
Hi Alex,
What I meant was I was doing a rescan. In the task manager box, I'll see initially a green bar which I presume means rescanning. Then it will turn into a blue bar which I presume is downloading new headers. While it's happily downloading the new headers, sometimes, it will start all over again with a green bar?? There wasn't any error messages. There's a few times where this keeps happening again and again and the NG takes literally forever to rescan! Hope I wasn't doing anything wrong here?
Thanks.
Regards,
JK
What I meant was I was doing a rescan. In the task manager box, I'll see initially a green bar which I presume means rescanning. Then it will turn into a blue bar which I presume is downloading new headers. While it's happily downloading the new headers, sometimes, it will start all over again with a green bar?? There wasn't any error messages. There's a few times where this keeps happening again and again and the NG takes literally forever to rescan! Hope I wasn't doing anything wrong here?
Thanks.
Regards,
JK
what you can do is to uncheck properties->general, get new headers after rescan (the second column on the top), just invoke get new headers separatedly if you have such a problem.
i asked about it in the previous post, but here is the same question in more detail: try to temporarily set the number of retries for the server to zero (properties->servers) and check what error you see in the task manager when it happens (so it won't retry but will show the error right away), maybe you just need to increase the read timeout (or maybe you set a small value there and this is why it happens).
it is quite unusual for a server to terminate connection in the middle of a command and such errors are not retriable by default, so most probably it is timeout; since there is an error (it must be a retriable error like timeout) newspro just retries the task. i'll change it so the rescan flag will be cleared after successful rescan although i'm not sure anyone else runs into this.
i asked about it in the previous post, but here is the same question in more detail: try to temporarily set the number of retries for the server to zero (properties->servers) and check what error you see in the task manager when it happens (so it won't retry but will show the error right away), maybe you just need to increase the read timeout (or maybe you set a small value there and this is why it happens).
it is quite unusual for a server to terminate connection in the middle of a command and such errors are not retriable by default, so most probably it is timeout; since there is an error (it must be a retriable error like timeout) newspro just retries the task. i'll change it so the rescan flag will be cleared after successful rescan although i'm not sure anyone else runs into this.
-
Guest
it may be well not newsfeeds. if you have firewall - try to temporarily uninstall it; if you have something between your computer and the modem, try to connect directly and check whether it happens then.
it means recv (receive from socket) returns 0, documentation tells that it means graceful closing of connection (not by newspro of course), but i suspect sometimes the problem can be traced to a local cause.
anyway in the meantime you can just do rescan and getting new headers separatedly through unchecking the option I mentioned before.
it means recv (receive from socket) returns 0, documentation tells that it means graceful closing of connection (not by newspro of course), but i suspect sometimes the problem can be traced to a local cause.
anyway in the meantime you can just do rescan and getting new headers separatedly through unchecking the option I mentioned before.