Hi,
I am running v0.7.20.14 on my Synology and SAB keeps on stopping for some odd reason. There is nothing in the logs at all stating as to why.
Running DSM 5.2-5592 Update 4
Anyone have any ideas.
Thanks
Keeps On Stopping On Synology
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: Keeps On Stopping On Synology
Can you post some of the logs here? Specifically the parts where it shuts down and restarts?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: Keeps On Stopping On Synology
That is the thing i do not see any logs stating there is an issue or shutting down. the only logs i see is when i start it again. this seems to only be on this new verion as the old one never did this.
-
druftiacto
- Newbie
- Posts: 12
- Joined: April 27th, 2015, 6:57 am
Re: Keeps On Stopping On Synology
@Vodka2
Your reasoning skills are decidedly weak. Do you drink too much... erm... vodka, perhaps? The assumption you make is based on a logical fallacy, named 'post hoc ergo propter hoc'. You can find more information in the Stanford Encyclopedia of Philosophy on http://plato.stanford.edu/entries/fallacies/
On a more serious note, it's impossible to help you without relevant logging. The fact that you aren't able to deliver logs, probably means that there are other factors at work. Perhaps insufficient memory? This has happened to me before with both a WD My Book and my Synology Disk Station. The OS will then kill certain processes for you, but this will almost certainly be written to the SYSTEM logs, so please refer to those! This is just a suggestion.
PS:
look for these messages:
process (7777) killed by TERM signal, where 7777 could be any other process ID.
Your reasoning skills are decidedly weak. Do you drink too much... erm... vodka, perhaps? The assumption you make is based on a logical fallacy, named 'post hoc ergo propter hoc'. You can find more information in the Stanford Encyclopedia of Philosophy on http://plato.stanford.edu/entries/fallacies/
On a more serious note, it's impossible to help you without relevant logging. The fact that you aren't able to deliver logs, probably means that there are other factors at work. Perhaps insufficient memory? This has happened to me before with both a WD My Book and my Synology Disk Station. The OS will then kill certain processes for you, but this will almost certainly be written to the SYSTEM logs, so please refer to those! This is just a suggestion.
PS:
look for these messages:
process (7777) killed by TERM signal, where 7777 could be any other process ID.