Hazel's broom doesn't sweep for me

I loved the concept of Hazel the moment I read about it in MacUser. Dowlnoaded, installed, everything seemed all present and correct in Sys Prefs.

BUT...

absolutely nothing happens. Hazel just sits there and nothing at all happens in the folders supposed being swept.

Did all the usual; logout, loginn... restart...uninstall, reinstall...reselect folder to be operated on...write a new test rule...run rules now

No matter what I do, Hazel does nothing at all.

Mac Power PCG5 dual 1.8G OS X 10.4.8

Any known conflicts :?:

Why is Hazel on strike? My Mac isn't WalMart after all.

Added some hours later:
Hazel has now worked on one folder but not on my download folder. Here are some bits from the log which look relevant:

2006-10-19 14:49:43.908 hazelfolderwatch[1898] Check-in with launchd failed: 13. Continuing.
2006-10-19 14:49:46.015 hazelfolderwatch[1898] Processing directories: ("/Users/dsl/xdloads")
2006-10-19 14:52:54.103 hazelfolderwatch[1904] Check-in with launchd failed: 13. Continuing.
2006-10-19 14:52:56.151 hazelfolderwatch[1904] Processing directories: ("/Users/dsl/ Holder Folder/camera mag candidates")
2006-10-19 14:52:56.155 hazelfolderwatch[1904] 101-0126_IMG.jpg: Rule test matched.
2006-10-19 14:52:56.243 hazelfolderwatch[1904] 101-0139_IMG_1.jpg: Rule test matched.
2006-10-19 14:52:56.245 hazelfolderwatch[1904] amazing dawn (no faking).jpg: Rule test matched.
2006-10-19 14:52:56.249 hazelfolderwatch[1904] amazing dawn (no faking).tif: Rule test matched.
2006-10-19 14:52:56.255 hazelfolderwatch[1904] IMG_0512.JPG: Rule test matched.
2006-10-19 14:52:56.257 hazelfolderwatch[1904] IMG_0516a.jpg: Rule test matched.
2006-10-19 14:52:56.259 hazelfolderwatch[1904] IMG_0578.JPG: Rule test matched.
2006-10-19 14:54:45.751 hazelfolderwatch[1911] Check-in with launchd failed: 13. Continuing.
2006-10-19 14:54:45.777 hazelfolderwatch[1911] Another hazelfolderwatch process is processing this directory. Exiting.
[...]
2006-10-19 17:21:36.636 hazelfolderwatch[2240] Processing directories: ("/Users/dsl/xdloads")
2006-10-19 17:22:55.664 hazelfolderwatch[2243] Processing directories: ("/Users/dsl/ Holder Folder/camera mag candidates")
2006-10-19 17:26:36.609 hazelfolderwatch[2248] Processing directories: ("/Users/dsl/xdloads")
2006-10-19 17:27:55.612 hazelfolderwatch[2249] Processing directories: ("/Users/dsl/ Holder Folder/camera mag candidates")

Hi,

Could you describe what rules you have in place for the downloads folder?

Also, it seems that the hazelfolderwatch process might be getting stuck. Maybe if you could do the following:

- Launch "Activity Monitor"
- Look for the hazelfolderwatch process.
- If it sticks around for a bit too long (like let's say a minute), select it and then select the View->Sample Process menu item.
- Send me what it dumps out.

Thanks.

The test rule I am using is

If all of the following conditions are met

Date Added is not in the last 6 weeks

Set color label to

It was a bit difficult to grab a process sample because hazelfolderwatch did not stick around for long in the activitiy monitor (2-3 seconds at most) but after some efforts at speedy mouse-clicking with fingers ready on the keyboard shortcut, I got this:

vmutils: can't find image for dynamic loader used by kernel_task [-1]!
Analysis of sampling pid 3262 every 10.000000 milliseconds
Call graph:
160 Thread_0f0f
160 0x22b4
160 0x2410
160 0x5d70
160 0x90040570
160 0x90040978
160 0x90040978

Total number in stack (recursive counted multiple, when >=5):

Sort by top of stack, same collapsed (when >= 5):
0x90040978 160
Sample analysis of process 3262 written to file /dev/stdout
Sampling process 3262 each 10 msecs 300 times
sampleTask: task_threads (os/kern) invalid argument
dyldNameStartingAtAddress:vm_read header (ipc/send) invalid destination port

Any help?

Thanks for getting back to me with the extra data.

One thing to keep in mind is that "Date Added" is not something OS X records so Hazel must record it itself. For the most part, the earliest "date added" is when Hazel scans the folder for the first time. Anything added after Hazel starts monitoring will have a correct "Date Added". So, unless you have been using Hazel for 6 weeks, you will not see any files colored yet. If you want to test this out, make another rule to match files with a recent date added and color them a different color.

Don't worry about the process sample. There was something in the logs you posted that hinted at a hung process but if they are disappearing faster than you can get to them, then I'd say that that probably isn't the problem.

In any case, let me know if my analysis above is indeed what is happening or if you suspect that it's something else.