So I have a little problem:
My Internet provider has tweaked my DSL connection to the point where I get semi-frequent PPP disconnects. That is the link margin drops and the PPPoA connection terminates. Often, I know this has happened because the SABNZBD rate drops to 0. I think log onto my router and reconnect (which might do it automatically, but this is quicker). Once connected, I can freely web surf etc. However, it becomes reasonably painful to get SABNZBD downloading again. Usually I wait a few minutes, but nothing happens. Then I try pausing the queue, forcing a disconnect, and then resuming. However, that results in error messages that "Your per-user connection limit reached." Finally, if I pause for about 10 minutes and then resume then everything comes back to normal.
Any thoughts on how to recover quicker? Since SABNZBD is running on a remote machine, it is a bit of a pain to restart (have to VNC in, stop the HTPC software, etc). I posted a while back about being able to restart the server remotely. Not sure if that would help or not. Maybe I'm just stuck until the usenet server reallizes I'm gone for good?
thanks!
Connection problems when DSL goes down, then up
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Connection problems when DSL goes down, then up
We have done a lot to improve recovering from disconnect behaviour,
but it will never be perfect.
If you set very large timeouts for the server, recovery will take longer.
Usenet servers are also notoriously bad at detecting dropped connections
and happily increment the connection counter.
Normally the best thing to do is to leave it alone and let SABnzbd and
the server sort things out. This may take a while.
Unless it's stuck for a long time (say 15 min after restored connection), I'd
leave it alone.
but it will never be perfect.
If you set very large timeouts for the server, recovery will take longer.
Usenet servers are also notoriously bad at detecting dropped connections
and happily increment the connection counter.
Normally the best thing to do is to leave it alone and let SABnzbd and
the server sort things out. This may take a while.
Unless it's stuck for a long time (say 15 min after restored connection), I'd
leave it alone.