"Lost connection to SABnzbd" ... make it less in-your-face and not GUI blocking.

[sanderjo]

I find SABnzbd too trigger-happy with the message "Lost connection to SABnzbd". It's too alarming and too blocking as it can easily happen on low-spec hardware. Annoying for users with such hardware

My proposal: do mention it, but in the SAB interface itself (not the current "overlay"), with something like "Last screen update 13 seconds ago", with that 13 seconds counting up, until the webbrowser gets a connection to SAB again.

Background: "Lost connection to SABnzbd" can happen if

1. SAB is too busy, or the hardware it's on is too busy
2. SAB is down, or crashed/restarting
3. network problems between webbrowser and SABnzbd

The new message should be better for 1, and maybe for 2.

Current message, blocking all info, until SAB is responding again

This is a screenshot from my SAB running on a low-spec ARM64 device (pystone a very low 11.000). SABs keeps humming & downloading, but sometimes it's too busy doing that and cannot serve the webbrowser from Cherrypy

[sanderjo]

Fun fact: on that low-spec CPU, SAB's Wrench says:

SAB doing nothing:

System load  0.59 | 0.13 | 0.13 | V=1579M R=64M
System performance (Pystone)  5274  Linux-5.15.25-sunxi64-aarch64-with-Ub

SAB downloading 10GB:

System load  4.95 | 5.05 | 3.07 | V=2059M R=240M
Download speed limited by  CPU (1434x)
System performance (Pystone)  2091  Linux-5.15.25-sunxi64-aarch64-with-Ub

Clear indication of an overloaded CPU, and thus technically understandable SAB cannot handle the webinterface on time.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[sanderjo]

@Safihre keep this one open, or close it?

[Safihre]

Let's keep it open!

[sgtcoder]

Mine does this all the time hundreds of times during downloads. 32vCPU with 32GB RAM. I preferred NZBGet, but it's a bit outdated.

[thezoggy]

Mine does this all the time hundreds of times during downloads. 32vCPU with 32GB RAM. I preferred NZBGet, but it's a bit outdated.

you should see why api calls to your sab instance are slow to respond back. like your on a remote vpn and just have slow responses in general to the server... so then having cpu hammered/disk io hammered is causing longer than normal responses back.

you can minimize some of this by not having sab set to show queue+history or large amounts of items at once.
that way you segment your api calls and make them smaller (so quickier to make it back to your client).
additionally to reduce strain on your server dont refresh queue every 1s.

you can change this all via wrench>web interface

then also there on the bottom, check off " Tabbed layout"