Critical Errors - How Critical?
Posted: Sun Mar 03, 2013 11:16 amv 6.42.
Yes, I searched the forum.
I typically run 3 connections but have tried 5.
Cable connection with pay provider. Auto updates is on (changed from hourly to 3 hours while writing this to try to isolate cause).
I receive frequent "ERROR NNTPSocket - Server:xxxx.com NNTPServer: Timeout - Waiting for Server to send Data: Socket - Read or Write Timeout" errors. Maybe 25 in a 5 second period.
Checking the logging tab, there may be a pattern that the errors follow-
[(time)] DEBUG - Checking Autodownload: alt.binaries.group
[(time)] DEBUG - DbWorker: Db Updated:alt.binaries.group:server-(number).rv4
Downloads work from headers, nzbs, and nzbs created from headers.
I understand that I can turn the pop-up window off, yet it seems like a good idea to have it if it is truly critical.
Is it possible that this error could come from me:
- forgetting to do the import on a group when I updated to 6.42?
- forgetting to do whatever the fix was when the server updated its numbering system recently? It doesn't seem to always be the same groups, but some are fairly consistent.
If it's from an occasional lag problem, is there something configurable to add a few ms before the error is triggered?
Every hour or two (or three) there's also a:
"[(time)] ERROR - Error: SSL Negotiation Failed, Host: (server).com Error: SSL Connection Failed: 5 Error 10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has
failed to respond." thrown in there.
Any suggestions are appreciated.
Yes, I searched the forum.
I typically run 3 connections but have tried 5.
Cable connection with pay provider. Auto updates is on (changed from hourly to 3 hours while writing this to try to isolate cause).
I receive frequent "ERROR NNTPSocket - Server:xxxx.com NNTPServer: Timeout - Waiting for Server to send Data: Socket - Read or Write Timeout" errors. Maybe 25 in a 5 second period.
Checking the logging tab, there may be a pattern that the errors follow-
[(time)] DEBUG - Checking Autodownload: alt.binaries.group
[(time)] DEBUG - DbWorker: Db Updated:alt.binaries.group:server-(number).rv4
Downloads work from headers, nzbs, and nzbs created from headers.
I understand that I can turn the pop-up window off, yet it seems like a good idea to have it if it is truly critical.
Is it possible that this error could come from me:
- forgetting to do the import on a group when I updated to 6.42?
- forgetting to do whatever the fix was when the server updated its numbering system recently? It doesn't seem to always be the same groups, but some are fairly consistent.
If it's from an occasional lag problem, is there something configurable to add a few ms before the error is triggered?
Every hour or two (or three) there's also a:
"[(time)] ERROR - Error: SSL Negotiation Failed, Host: (server).com Error: SSL Connection Failed: 5 Error 10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has
failed to respond." thrown in there.
Any suggestions are appreciated.