Hi guys,
In the last couple of days i've started to see some strange issues with Sabnzbd+
I am running version 0.4.9 on a QNAP TS209 Pro II NAS box (Linux based file system) ... and have been doing so without issue for 9 months or so.
The box has 2TB of storage and has approx 450GB of free space.
In the last few days i've seen downloads failing and strange warnings and errors in the logs.
For example, I'm seeing the message below repeatedly:
2009-06-11 06:10:36,385
ERROR
[sabnzbd] Failure in tempfile.mkstemp
2009-06-11 06:10:36,400
WARNING
[articlecache] Flushing failed -> no art_id
What does this mean? Why is this happening?
More worryingly, after a failed download the file system on the NAS seems to go into 'Read-Only' mode and I have to reboot the box.
I have performed a FULL system scan of both drives and there are no reported errors, I have also performed a full bad blocks scan of both 1TB drives and there were no reported bad blocks. SMART also reports no problems with the drives. I have also tried uninstalling and reinstalling sabnzbd and that didn't seem to make a difference.
Any help greatly appreciated!
Kind Regards,
Paul.
0.4.9 - HELP - Failure in tempfile.mkstemp
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.
0.4.9 - HELP - Failure in tempfile.mkstemp
Last edited by pander on June 11th, 2009, 3:57 am, edited 1 time in total.
Re: 0.4.9 - HELP - Failure in tempfile.mkstemp
Usually this signals a problem with the OS and/or storage.
Have you checked if there are many orphaned files in the cache folder?
SABnzbd has the nasty habit of not always cleaning up files when the user deletes jobs.
If your queue is empty, there should be no SABnzbd_* files in the cache folder.
If there are, remove them.
You could also start up SABnzbd once with the --clean option,
however this wipe the queue AND the history.
Have you checked if there are many orphaned files in the cache folder?
SABnzbd has the nasty habit of not always cleaning up files when the user deletes jobs.
If your queue is empty, there should be no SABnzbd_* files in the cache folder.
If there are, remove them.
You could also start up SABnzbd once with the --clean option,
however this wipe the queue AND the history.
Re: 0.4.9 - HELP - Failure in tempfile.mkstemp
Hi,
Hmm, yeah, there were some files sitting in the cache folder before I uninstalled and reinstalled. I did remove them all but it didn't seem to make a difference. There are files in there again even now after I tried another test nzb to download, though it hasn't finished DL'ing so I guess they need to be there.
Any idea with regard to the 'Flushing' warning? What does 'no art_id' mean?
Regards,
Paul.
Hmm, yeah, there were some files sitting in the cache folder before I uninstalled and reinstalled. I did remove them all but it didn't seem to make a difference. There are files in there again even now after I tried another test nzb to download, though it hasn't finished DL'ing so I guess they need to be there.
Any idea with regard to the 'Flushing' warning? What does 'no art_id' mean?
Regards,
Paul.
Re: 0.4.9 - HELP - Failure in tempfile.mkstemp
I did not read the warnings carefully enough.
Looks like some problem in the article cacher.
What happens if you disable the articlecache?
Does it happen for every NZB file or just specific ones?
In the latter case could you email us a failing one? bugs@sabnzbd.org
"no article id" would suggest a faulty NZB file, but I cannot tell for sure right now.
Looks like some problem in the article cacher.
What happens if you disable the articlecache?
Does it happen for every NZB file or just specific ones?
In the latter case could you email us a failing one? bugs@sabnzbd.org
"no article id" would suggest a faulty NZB file, but I cannot tell for sure right now.