I am not sure what happened, but I suspect an improper server shutdown and when I opened SAB, the queue was gone (empty). I then went to the status and Queue Repair tab and clicked "Add" to the job that was pending. Since then, SAB seems to both download and repair/verify the same content! The verifying phase does not end, it runs in an endless loop... I tried killing par2, restarting SAB, killing SAB, nothing to do.
Sab does not even shutdown or restart using the interface. I need to use the CLI and kill the python process.
What woul dbe the best way to recover this situation?
SAB screwed up good...
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: SAB screwed up good...
Quick fix: stop SABnzbd, remove the offending item from the "temporary download folder"
and start SABnzbd again.
An item can temporarily be in both queues when post-processing decides that it
needs extra par2 files.
Does it hang up each time in the par2/unrar process?
It may be advisable to disable multi-code par2 in Config->Switches.
and start SABnzbd again.
An item can temporarily be in both queues when post-processing decides that it
needs extra par2 files.
Does it hang up each time in the par2/unrar process?
It may be advisable to disable multi-code par2 in Config->Switches.
-
nzbtuxnews
- Jr. Member
- Posts: 85
- Joined: March 5th, 2011, 2:03 pm
Re: SAB screwed up good...
Well before you replied I fixed it. It was weird and really messed up.
The verification process ended up saying that I had missing blocks (what a surprise!!) and ended up. I clicked the remove nzb button, remove the downloading job by also clicking the remove nzb button, killed par2, killed SAB and restarted it. I then had a totally empty queue and went to the orphaned jobs page and re-added the job. All is fine now.
I am not sure what happened but I believe the server was interrupted as I remember when I started up I saw lots of ReiserFS repair and journaling operations.
I will keep an eye on this...
Thanks for your assistance Shypike!
The verification process ended up saying that I had missing blocks (what a surprise!!) and ended up. I clicked the remove nzb button, remove the downloading job by also clicking the remove nzb button, killed par2, killed SAB and restarted it. I then had a totally empty queue and went to the orphaned jobs page and re-added the job. All is fine now.
I am not sure what happened but I believe the server was interrupted as I remember when I started up I saw lots of ReiserFS repair and journaling operations.
I will keep an eye on this...
Thanks for your assistance Shypike!