Closed worldofgeese closed 3 years ago
Thanks for opening your first issue here! Be sure to follow the issue template!
I'm afraid Run latest tag and observe over the next few hours as your server shits the bed.
do not qualify as proper steps to reproduce
I'm afraid
Run latest tag and observe over the next few hours as your server shits the bed.
do not qualify as proper steps to reproduce
Open to suggestions as to what qualifies. I know it's nzbget that is the source of my problems and I have attached a copy of my logs.
Is nzbget doing anything?
Is nzbget doing anything?
According to the logs it had grabbed "The Bachelorette" (yes yes I know it's embarrassing) but looks like it found it unhealthy and bailed.
EDIT: there's also repeated rejected connection attempts to one of my news servers.
I continued to throw myself against the rocks on this one, finally finding an enabled-by-default setting for Energy Efficient Ethernet which turned out to be the culprit.
Expected Behavior
Server minimally affected by nzbget container.
Current Behavior
As of the beginning of last week, the nzbget container causes huge performance loss in network connectivity to my server. SSH and other containers which depend on network bandwidth slow to a crawl. To test for the offending container, I tore my docker-compose.yml down to a minimum of containers and added a container back each day and observed the results. After 4 days and 4 containers, I put up NZBGet and can see a clear correlation between it and ssh access times over one minute, other containers like Synapse timing out, etc.
Steps to Reproduce
Environment
OS: Synology DSM 6.2 CPU architecture: x86_64/arm32/arm64 x86_64 How docker service was installed: DSM provided.
Command used to create docker container (run/create/compose/screenshot)
Docker logs
Logs attached. nzbget.log