Noodlesoft Forums

I added a new rule yesterday to run on a folder that's on a removable drive (based on the advice here, that the rule will run whenever the drive is visible), and on the first run, everything went as planned. I ejected and removed the drive, and then today, I put the drive in, but never saw the rule run, even after waiting around half an hour. I looked at the log file, and it looks like HazelHelper claims that at the time I ejected/removed the drive yesterday, it was a request for HazelHelper to terminate:

Code: Select all

2013-12-25 21:00:52.593 hazelworker[49756] Done processing folder ACTIVITY
2013-12-25 21:07:32.449 HazelHelper[49728] Received unmount notification from unknown filesystem at /Volumes/94AEB836-EC5C-4246-8E3F-43751059327C.
2013-12-25 21:07:34.081 HazelHelper[49728] Error opening event stream. Path does not exist: /Volumes/GARMIN/Garmin/ACTIVITY
2013-12-25 21:07:34.150 HazelHelper[49728] Received request to terminate
2013-12-25 21:07:34.151 HazelHelper[49728] Deregistering...
2013-12-25 21:07:34.151 HazelHelper[49728] Done
2013-12-25 21:07:34.797 hazelworker[49821] Scan folder is not accessible. Exiting.

That was the last entry in my log file, even though I have other rules that don't depend on the removable drive. Today, I then launched the Hazel system pref pane, and it claimed that it was running ("Status: Hazel is running"), but it clearly wasn't -- but then the log showed that HazelHelper STARTED running again, and started processing my rules:

Code: Select all

2013-12-26 16:07:19.054 HazelHelper[53328] HazelHelper v3.2.3 launching.
2013-12-26 16:07:19.994 hazelworker[53331] Processing folder Trash (forced)
2013-12-26 16:07:21.250 hazelworker[53331] Done processing folder Trash
2013-12-26 16:07:34.809 hazelworker[53336] Processing folder History
2013-12-26 16:07:37.137 hazelworker[53336] Done processing folder History
2013-12-26 16:07:49.765 hazelworker[53340] Processing folder Activities
2013-12-26 16:07:52.134 hazelworker[53340] Done processing folder Activities
2013-12-26 16:08:04.777 hazelworker[53341] Processing folder ACTIVITY
2013-12-26 16:08:06.909 hazelworker[53341] 3CQE2016.FIT: Rule Garmin FIT files matched.
2013-12-26 16:08:07.073 hazelworker[53341] [File Event] File copied: 3CQE2016.FIT copied from folder /Volumes/GARMIN/Garmin/ACTIVITY to folder /Users/jlevine/Dropbox/Garmin Backup.
2013-12-26 16:08:07.114 hazelworker[53341] Done processing folder ACTIVITY

What gives? Should I have to launch the Hazel system pref pane to get the rule to run?

Thanks in advance...
Jason

The terminate request usually only comes from the preference pane. I think the timing might be a red herring in this case. If you can repeat it on demand with System Preferences not running at all, then report back. In short, the Helper should always be running, the exception being when updating where Hazel will terminate it. It gets started by the pref pane when it is loaded if necessary.

I'll try, but I can tell you *definitively* that I didn't terminate the HazelHelper process using the pref pane (the 2013-12-25 21:07:34.150 entry in the log) -- I don't even believe I had the pref pane open. So there really is a bug there that you'll likely need to hunt down. I mean, the HazelHelper terminate event happens 69 milliseconds after the entry where HazelHelper reports an error finding the /Volumes/GARMIN/Garmin/ACTIVITY directory... that kind of timing is really unlikely to be random chance.

Are you seeing this happen consistently? If it only happened once, then it's actually pretty likely it's a coincidence but if it happens on demand consistently then there may be a correlation.