Anyone know of a fix for failed items not appearing in the history?
Thanks,
b0x
Failed Items Not in History
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: Failed Items Not in History
How do you know a job failed if it’s not in the history?
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
Re: Failed Items Not in History
I see its going to fail due to missing parts or whatever its showing during download and then disappears from active once it gives up. It never appears in the history.
Re: Failed Items Not in History
Which SABnzbd version are you running? Which OS?
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
Re: Failed Items Not in History
Windows SABnzbd version: 2.3.2
Re: Failed Items Not in History
And lastly, were these queue items sent from a grabber like CouchPotato?
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
Re: Failed Items Not in History
I have been using either rss or dropped into sab via web interface or watch folder. Just added sonarr to the mix so it'd be nice if the failed retry feature worked. I went ahead and deleted my history1.db and threw something into the queue I knew recently failed - waiting for it to give up now.
Re: Failed Items Not in History
Ok it failed out and nothing in the history
Re: Failed Items Not in History
Are you performing any post-processing?
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
Re: Failed Items Not in History
Could you enable +Debug logging, download a small job and then share the portion of the log after "Starting Post-Processing on".
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: Failed Items Not in History
No post processing that I know of other then file checking.
Here's the setting in that section - https://ibb.co/bKhbJm
One change I can think of doing in the last couple months is the history limit - I've gone ahead and removed it and restarted Sab.
And now failed jobs are showing again...
Guess back to the old issue of the history.db growing so large it takes the entire vm to it's knees.
safihre is that this in special? - debug_log_decoding
Here's the setting in that section - https://ibb.co/bKhbJm
One change I can think of doing in the last couple months is the history limit - I've gone ahead and removed it and restarted Sab.
And now failed jobs are showing again...
Guess back to the old issue of the history.db growing so large it takes the entire vm to it's knees.
safihre is that this in special? - debug_log_decoding
Re: Failed Items Not in History
No, in the Status and Interface settings window (the wrench icon) on Glitter is where you can set Debug.
But seems you already fixed it! Debug setting would only slow your system down.
But seems you already fixed it! Debug setting would only slow your system down.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: Failed Items Not in History
"fixed", but will cause bigger issues soon enough with the rate my history grows.
I'll probably have to script something to clear it once a week if this is the work-around to the failed showing or not.
I'll probably have to script something to clear it once a week if this is the work-around to the failed showing or not.
Re: Failed Items Not in History
There is a setting in Config > Switches called "History Retention" where you can set auto-deleting of history!
What number of downloads are we talking about? I never knew about a limit really.
What number of downloads are we talking about? I never knew about a limit really.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: Failed Items Not in History
Yeah, I had that set to 1000 as shown here - https://ibb.co/bKhbJm
Which apparently was the cause of the failed not working/appearing.
As for total # of downloads... I'm nearing 800 since i reset it yesterday.
Which apparently was the cause of the failed not working/appearing.
As for total # of downloads... I'm nearing 800 since i reset it yesterday.