Downloaded files not prrocessed (Lion) - "Skipping for now"

Get help. Get answers. Let others lend you a hand.

Moderator: Mr_Noodle

Hi!

Hazel is tasked with some actions for files that are downloaded utilizing a download manager. During download these files are locked. Since I have upgraded to Lion I have entries in the log file that show that a file is detected by Hazel multiple times, but no action is executed

hazelfolderwatch[49986] File [...] is busy. Skipping for now.

For one file it looks like Hazel tries to process for eight times with an interval of 8 secondes between each try.

Any hints?

Regards,

LagaV
LagaV
 
Posts: 9
Joined: Fri Aug 05, 2011 11:38 am

You can ignore that message. It just means that Hazel is detecting that the file is in use. I can't say about frequency since it varies on the specific situation as to what else if happening at the time but I wouldn't worry about it unless Hazel still finds the file busy when it clearly isn't.
Mr_Noodle
Site Admin
 
Posts: 11865
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

The problem is, that after the mentioned 8 "file is busy" messages Hazel doesn't come back to the file when it is no longer busy. So rules aren't applied.

My current workaround is, that I request to run the run the rules manully (via PrefPane).

LagaV
LagaV
 
Posts: 9
Joined: Fri Aug 05, 2011 11:38 am

Does not come back ever or it takes some time? Thing is, there is no notification for when a file is no longer busy (it's hard enough to get apps to cooperate to indicate that the file is busy in the first place). Hazel can only know if a file is busy or not by checking it, but it can't check it constantly or it would drain resources. So, it has to take breaks and come back some time later.
Mr_Noodle
Site Admin
 
Posts: 11865
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

It doesn't come back automatically. I have to force a rerun of the rules. Ironically this didn't happen with Snow Leopard. This behavior started with Lion.

LagaV
LagaV
 
Posts: 9
Joined: Fri Aug 05, 2011 11:38 am

How long are you waiting? I may take up to a few minutes depending.
Mr_Noodle
Site Admin
 
Posts: 11865
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

Time does not help. Even after hours the rules aren't executed.
LagaV
 
Posts: 9
Joined: Fri Aug 05, 2011 11:38 am

Maybe Hazel lost track of the folders? Try re-adding the folders as follows:

- Export the rules for any of the affected folders.
- Remove the folder from Hazel.
- Add the folder back.
- Import the rules.

Give that a shot and report back.
Mr_Noodle
Site Admin
 
Posts: 11865
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

This same thing is happening to me and it's a fresh install.

It doesn't ever rerun the match.
milkypostman
 
Posts: 1
Joined: Wed Aug 31, 2011 1:00 pm

Mr_Noodle wrote:Maybe Hazel lost track of the folders? Try re-adding the folders as follows:

- Export the rules for any of the affected folders.
- Remove the folder from Hazel.
- Add the folder back.
- Import the rules.

Give that a shot and report back.


I tried that. After adding the folder and reimport rules are excuted.

Reboot and standby / wakeup kept the rules system alive.
LagaV
 
Posts: 9
Joined: Fri Aug 05, 2011 11:38 am

So, does that mean it's working now?
Mr_Noodle
Site Admin
 
Posts: 11865
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

Mr_Noodle wrote:So, does that mean it's working now?


Not reliably. I'm struggling to identify a pattern.

Currently it looks like files placed in a folder by AppA are not detected, when AppB places a file in the same folder this file is immediately picked up and all other files that were previously added by App A will then also be processed.
LagaV
 
Posts: 9
Joined: Fri Aug 05, 2011 11:38 am

Could you tell me what the two apps in question are?
Mr_Noodle
Site Admin
 
Posts: 11865
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

Mr_Noodle wrote:Could you tell me what the two apps in question are?


Apps are jDownloader and Finder . I now switched to 3.0b1, but there was no way to consistently reproduce the problem with the previous version. I'll reply if the problem arises again with 3.0b1
LagaV
 
Posts: 9
Joined: Fri Aug 05, 2011 11:38 am


Return to Support