[FIXED] 0.4.0b2 does not remove blackhole files

[Sypher]

As the title says:  the 0.4.0b2 beta does not remove the blackhole files after processing them.

[shypike]

As nobody else complains about this:
Could you give more information?
What's in the logging?
Do the files get processed at all?

[Sypher]

Oh sorry.
Uhm, its the Win32 build. The blackhole folder is in the Sabnzbd folder. I am using "legacy" mode (the ini file inside the directory instead of files scattered across my system)

The files are getting processed, or atleast 1 of the 3 I had in there was back in the queue every time I started Sabnzbd.

2008-04-13 21:27:07,663::INFO::[sabnzbd.misc] Trying to import F:\SABnzbd\NZB_blackhole\Some.File.nzb

is in the logfile.

[shypike]

Any file which is not an NZB or not a proper NZB will remain in the blackhole.
Look carefully in the logging for warnings and errors.
Each file is examined only once during the running time of SABnzbd (it checks again on soft-restart).

[Sypher]

Okay, well it's an nzb. The nzb's are produced by Binsearch.
Never had any problems with them before, only since this beta release.

There are warnings at the connections page:

2008-04-14 13:01:26,976 WARNING IPV6 has priority on this system, potential Firefox issue
2008-04-14 13:01:33,105 ERROR [sabnzbd.misc] Error removing F:\SABnzbd\NZB_blackhole\69046.nzb
2008-04-14 13:01:34,210 ERROR [sabnzbd.misc] Error removing F:\SABnzbd\NZB_blackhole\123456.nzb
2008-04-14 13:01:35,368 ERROR [sabnzbd.misc] Error removing F:\SABnzbd\NZB_blackhole\543210.nzb

[shypike]

Access rights problem.
SABnzbd can read the files but cannot remove them.

[nzb_leecher]

i know someone with the opisite. If the last nzb is deleted it also deletes the nzb directory 

he always begins dloading with creating a new nzb dir  but he is so used by it he doesnt care anymore. Dont know whcih version he uses,

[Sypher]

Access rights problem.
SABnzbd can read the files but cannot remove them.

I have full access (administrator account), and this problem wasn't there with the 0.3.x releases...

[shypike]

Even as admin you may lock yourself out. Or if the R bit is set.
Can you delete the files from the command line?

[Sypher]

I have no problems with deleting manually if that's what you're asking. Via explorer -> delete and they're gone.
My knowledge of Windows is high enough to prevent me from being locked out, and the R bit isn't added magically, is it?

[shypike]

I could not think of a way to reproduce your deletion problem.

The code simply says:

Code: Select all

try:
    os.remove(path)
except:
    logging.error("[%s] Error removing %s", __NAME__, path)

So, unless the path displayed in the error message is not the correct path, I cannot
imagine what is wrong.

Same goes for the disappearing directory of nzb_leecher's friend.

[Sypher]

The path is correct, I have the proper permissions to delete the file but somehow SABnzbd is unable to do so.
But now I'm wondering why it did work in prior versions.

[AllRoCol]

As nobody else complains about this:
Could you give more information?
What's in the logging?
Do the files get processed at all?

I am having the same problem. I am logged in as an Adminstrator. The first two nzb files I downloaded both deleted, then I installed Sabnzb open and all of a sudden they won't delete. I don't know if that program has something to do with it or not.

[shypike]

What is "sabnzbd open"?
Windows refuses to remove files that are (still) accessed by other applications.

[AllRoCol]

What is "sabnzbd open"?
Windows refuses to remove files that are (still) accessed by other applications.

Found it on your forums third party apps list. http://forums.sabnzbd.org/index.php?topic=38.0

It is called sabnzbdopen on there, but installs as sabnzb open.

I believe that when installed, it was making nzb files read only when I downloaded them. As soon as I uninstalled and manually downloaded nzbs, the problem was gone.

Just my thought for the other guy.