Search found 3 matches
- January 30th, 2025, 5:22 pm
- Forum: General Help
- Topic: "Lost Connection," Signal 15 & Restart
- Replies: 12
- Views: 36569
Re: "Lost Connection," Signal 15 & Restart
The health check you do is on a non existing endpoint. So it probably gives a 400 or 500 error. So that results in the system thinking Sab is unhealthy and forcing a restart. You should strip the ping part, just call /sabnzbd Then it probably works. Hah! Right you are. Thanks for pointing out my ro...
- January 29th, 2025, 10:21 pm
- Forum: General Help
- Topic: "Lost Connection," Signal 15 & Restart
- Replies: 12
- Views: 36569
Re: "Lost Connection," Signal 15 & Restart
You know it means some other process sent that signal 15 = SIGTERM to SABnzbd? I do. The great thing: with bpftrace -> killsnoop you can find the sending process Brilliant. Unfortunately, the Docker version (20.10.23) installed with Synology DSM 7.2.2 doesn't support cap-add PERFMON or BPF , which ...
- January 28th, 2025, 10:55 pm
- Forum: General Help
- Topic: "Lost Connection," Signal 15 & Restart
- Replies: 12
- Views: 36569
"Lost Connection," Signal 15 & Restart
I'm running Sabnzbd v4.4.1 under Docker v20.10.23 on a Synology DS920+ running DSM v7.2.2. The relevant Docker Compose service is: sabnzbd: image: sabnzbd:latest container_name: sabnzbd restart: unless-stopped network_mode: "service:vpn" depends_on: vpn: condition: service_healthy volumes:...