Another Hazel worker process is processing folder
Posted: Fri Dec 12, 2014 1:48 pmI have a love for Hazel, and it works great for everything I do.
I have one mac mini that is so problematic though, I want to throw it against the wall.
I have a number of folders on 3 different machines, exact same folder structure, and the rules are exports, imports.
The rules work on 2 of the machines, this one..not much at all. I find that after a few days, i have to reboot the machine to get hazel to do anything. Turn on and off Hazel won't do anything different, and the preview always shows one of the rules is in need of application. So its not like its stuck with nothing to do.
I found a thread here that says to rename the folder, no different. I can see in the debug log that the rules unload and load. So I removed the folder out of hazel, (after export) and added back, imported rules. I can see the folder sync and then a timer fire, and then a line saying that another hazelworker is processing this folder.
This is fresh after a reboot too. So it didn't even fire the first rule. The other thread I ran across was on dropbox, but this is just a folder on the local HD, nothing fancy.
Ive been playing with this machine for the last maybe 4 months, updates done etc, but finally had a minute to look further into this and post something. I essentially waited out a bug that I hoped existed ha!
I have one mac mini that is so problematic though, I want to throw it against the wall.
I have a number of folders on 3 different machines, exact same folder structure, and the rules are exports, imports.
The rules work on 2 of the machines, this one..not much at all. I find that after a few days, i have to reboot the machine to get hazel to do anything. Turn on and off Hazel won't do anything different, and the preview always shows one of the rules is in need of application. So its not like its stuck with nothing to do.
I found a thread here that says to rename the folder, no different. I can see in the debug log that the rules unload and load. So I removed the folder out of hazel, (after export) and added back, imported rules. I can see the folder sync and then a timer fire, and then a line saying that another hazelworker is processing this folder.
This is fresh after a reboot too. So it didn't even fire the first rule. The other thread I ran across was on dropbox, but this is just a folder on the local HD, nothing fancy.
Ive been playing with this machine for the last maybe 4 months, updates done etc, but finally had a minute to look further into this and post something. I essentially waited out a bug that I hoped existed ha!
- Code: Select all
2014-12-12 11:37:00.249 HazelHelper[276] DEBUG: Thread 0x60800007c940: Timer fired for folder: /Users/default/Movies/3 - Movies
2014-12-12 11:37:00.249 HazelHelper[276] DEBUG: Thread 0x60800007c940: Run worker for folder: /Users/default/Movies/3 - Movies
2014-12-12 11:37:00.317 hazelworker[5736] Another hazelworker process is processing folder with identifier 16777218-216534534. Exiting.
2014-12-12 11:37:00.325 HazelHelper[276] DEBUG: Thread 0x60800007c940: Task removed: [5736]