Quade wrote:It means something is probably killing the connection out from under Newsbin. If you use SSL, you might try turning it off and seeing if that changes anything. If it does, it would suggest that maybe your security software is stepping on the connection.
I'm wondering if it has to do with the number of headers. This is a biggish group, probably hit by the recent spammers (which started this whole cycle in the first place). I nuked the whole installation and started over. So it is trying to grab a fairly large number of headers all at once.
Quade wrote:What server are you using? You might want to try disabling "Xfeatures" in the server advanced options.
dexter wrote:I've seen a couple of reports of this. I wonder if NewsHosting implemented some new connection timeout or something. You should be able to just do a "Download Latest Headers" on the group and it will pick up again from where the server errored out.
dexter wrote:I'm curious which plan you have with them. I wonder if only their metered plan does this or if it is across their tiers of service.
[02/12 06:00:31] ERROR NEWS SERVER ERROR: Newshosting SendCommand - Failed: 500 max connect time exceeded
Quade wrote:[02/12 06:00:31] ERROR NEWS SERVER ERROR: Newshosting SendCommand - Failed: 500 max connect time exceeded
This error is from the server. It's considered a fatal error in usenet. It suggests they're thrown some max connection time onto each connection.
How long does the connection go before this kicks in?
If you're already caught up with your header downloads, I'm surprised you'd see this.
Might ask Newshosting what the whole point of this error is.
pjcamp wrote:Their first claim was that it was a problematic interaction between Newsbin and my security software.
[02/17 15:54:45] DEBUG XOVER Numbers: <newsgroup> Min: 272082411 Max: 273082411 Newshosting
[02/17 15:54:45] DEBUG Newshosting <newsgroup> XOVER: <newsgroup> 272082411:273082411
[02/17 15:55:00] DEBUG DbWorker: Db Gz to Db Failed: <newsgroup>
[02/18 04:51:35] ERROR Server:Newshosting NNTPServer: Failed to read text line:
Quade wrote:I count at least 3 issues which look semi-unrelated.
1 - GZ to DB error. Has nothing to do with downloading headers. It happens after a successful download when headers are imported.
2 - 500 error from the server for old connection
3 - Read timeouts while reading headers indicating the connection dropped out.
Might be worth disabling xfeatures in the server advanced options. Then restart Newsbin. I'm not seeing any obvious security software symptoms but since security software does tend to F up downloading, it wouldn't shock me that it's related to that.
OK now it timed out while paused. That doesn't seem like it would be server related.
Quade wrote:OK now it timed out while paused. That doesn't seem like it would be server related.
Pause doesn't pause header downloads. Headers are different then file downloads. There's no good way to stop the download on the fly. The news server protocol doesn't support it. If you want to stop a header download you're better off just deleting it, then updating the groups again when you're ready for more. Newsbin will continue downloading from where it left off as long as you don't "Download all Headers" next time you download headers.
But if you can resume a download by deleting and restarting, why doesn't that happen on a timeout as well?
. It has stopped downloading three times but each time was the same error message: Failed to read text line. That's progress of a sort.
dexter wrote:Depends on where you are applying the filter. Sounds like you are just using a display filter which means the header info is still in the database. If you turn filters on for the post list by clicking the icon that looks like a power button, it will actively hide any headers matching your filter. Otherwise, the filtered posts are still displayed and are just tagged as filtered as you are seeing now.
If you want to keep these posts from getting in to the database at all, you need to apply the filter as a header download filter.
Users browsing this forum: Bing [Bot] and 2 guests