Hazel crashing

[dbingham]

I am noticing some strange things going on with Hazel in the console. When I view the system.log I see the following output:

Code: Select all

Nov  3 12:25:04 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:25:04 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:25:04 dbingham launchd[27881]: com.noodlesoft.HazelHelper: 9 more failures without living at least 60 seconds will cause job removal
Nov  3 12:25:04 dbingham launchd[27881]: com.noodlesoft.HazelHelper: will restart in 10 seconds
Nov  3 12:25:15 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:25:15 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:25:15 dbingham launchd[27881]: com.noodlesoft.HazelHelper: 8 more failures without living at least 60 seconds will cause job removal
Nov  3 12:25:15 dbingham launchd[27881]: com.noodlesoft.HazelHelper: will restart in 10 seconds
Nov  3 12:25:27 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:25:27 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:25:27 dbingham launchd[27881]: com.noodlesoft.HazelHelper: 7 more failures without living at least 60 seconds will cause job removal
Nov  3 12:25:27 dbingham launchd[27881]: com.noodlesoft.HazelHelper: will restart in 10 seconds
Nov  3 12:25:37 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:25:37 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:25:37 dbingham launchd[27881]: com.noodlesoft.HazelHelper: 6 more failures without living at least 60 seconds will cause job removal
Nov  3 12:25:37 dbingham launchd[27881]: com.noodlesoft.HazelHelper: will restart in 10 seconds
Nov  3 12:25:47 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:25:47 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:25:47 dbingham launchd[27881]: com.noodlesoft.HazelHelper: 5 more failures without living at least 60 seconds will cause job removal
Nov  3 12:25:47 dbingham launchd[27881]: com.noodlesoft.HazelHelper: will restart in 10 seconds
Nov  3 12:25:57 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:25:57 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:25:57 dbingham launchd[27881]: com.noodlesoft.HazelHelper: 4 more failures without living at least 60 seconds will cause job removal
Nov  3 12:25:57 dbingham launchd[27881]: com.noodlesoft.HazelHelper: will restart in 10 seconds
Nov  3 12:26:08 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:26:08 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:26:08 dbingham launchd[27881]: com.noodlesoft.HazelHelper: 3 more failures without living at least 60 seconds will cause job removal
Nov  3 12:26:08 dbingham launchd[27881]: com.noodlesoft.HazelHelper: will restart in 10 seconds
Nov  3 12:26:18 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:26:18 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:26:18 dbingham launchd[27881]: com.noodlesoft.HazelHelper: 2 more failures without living at least 60 seconds will cause job removal
Nov  3 12:26:18 dbingham launchd[27881]: com.noodlesoft.HazelHelper: will restart in 10 seconds
Nov  3 12:26:30 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:26:30 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:26:30 dbingham launchd[27881]: com.noodlesoft.HazelHelper: 1 more failure without living at least 60 seconds will cause job removal
Nov  3 12:26:30 dbingham launchd[27881]: com.noodlesoft.HazelHelper: will restart in 10 seconds
Nov  3 12:26:42 dbingham launchd[27881]: com.noodlesoft.HazelHelper: exited abnormally: Abort trap
Nov  3 12:26:42 dbingham launchd[27881]: com.noodlesoft.HazelHelper: respawning too quickly! throttling
Nov  3 12:26:42 dbingham launchd[27881]: com.noodlesoft.HazelHelper: too many failures in succession

This happened right after I logged out and back in. I checked with launchctl and sure enough, HazelHelper is no longer loaded. When I try reloading HazelHelper with launchctl load ~/Library/LaunchAgents/*HazelHelper.plist it starts up and begins this failure cycle again.

Any help would be greatly appreciated!

-dbingham
Hazel v1.1.1

[dbingham]

Well, I seem to have fixed my own problem. I still don't know why it was crashing, but after doing a complete uninstall (using the uninstall button in the pref panel) and then installing it again, the problem seems to have gone away. Perhaps it was an upgrade bug from pre 1.1?

Anyway, seems to be fixed.

Thanks.

-dbingham

[Mr_Noodle]

I'm glad you were able to rectify it but I'm sorry you re-installed to do it. If it happens again, let me know as I haven't seen this before and would like to fix it. Also, if you get any log messages indicating why HazelHelper terminated, that would be great.

Thanks.

[troubledwine]

I'm having the same problem. It *might* have started after a log out / log in situation. I'm not sure. I noticed the rules stopped working about 2 days ago.

Here's a bit of the console log:

Code: Select all

2007-02-07 22:37:59.030 hazelfolderwatch[11332] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2c03, name = 'Processes-0.76414977'
2007-02-07 22:37:59.034 hazelfolderwatch[11332] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (Processes-0.76414977)
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: exited abnormally: Abort trap
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: 8 more failures without living at least 60 seconds will cause job removal
2007-02-07 22:39:45.685 hazelfolderwatch[11336] Another hazelfolderwatch process is processing this directory. Exiting.
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: 8 more failures without living at least 60 seconds will cause job removal
2007-02-07 22:44:00.174 hazelfolderwatch[11352] Another hazelfolderwatch process is processing this directory. Exiting.
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: 8 more failures without living at least 60 seconds will cause job removal
2007-02-07 22:44:45.490 hazelfolderwatch[11353] Another hazelfolderwatch process is processing this directory. Exiting.
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: 8 more failures without living at least 60 seconds will cause job removal
2007-02-07 22:49:45.545 hazelfolderwatch[11358] Another hazelfolderwatch process is processing this directory. Exiting.
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: 8 more failures without living at least 60 seconds will cause job removal
2007-02-07 22:50:02.542 hazelfolderwatch[11359] Another hazelfolderwatch process is processing this directory. Exiting.
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: 8 more failures without living at least 60 seconds will cause job removal
2007-02-07 22:54:45.488 hazelfolderwatch[11368] Lockfile is stale. Updating time and proceeding.
2007-02-07 22:54:45.796 hazelfolderwatch[11368] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2003, name = 'NSApplication-MainThread-2c68-15065350768885#'
2007-02-07 22:54:45.799 hazelfolderwatch[11368] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (NSApplication-MainThread-2c68-15065350768885#)
2007-02-07 22:54:45.803 hazelfolderwatch[11368] *** Assertion failure in -[NSApplication _createWakeupPort], AppKit.subproj/NSApplication.m:3578
2007-02-07 22:54:45.804 hazelfolderwatch[11368] CFMessagePortCreateLocal returned NULL port
2007-02-07 22:54:47.817 hazelfolderwatch[11368] Processing directories: ("/Users/xxxxxxxxxxxx/Downloads")
2007-02-07 22:54:48.205 hazelfolderwatch[11368] xxxxxxxxx.avi: Rule No Longer New Files matched.
2007-02-07 22:54:48.247 hazelfolderwatch[11368] xxxxxxxxxxxxxxxxxxxxxx: Rule No Longer New Files matched.
************* personal file directory information as it tried to process some new files ***********
2007-02-07 22:54:48.954 hazelfolderwatch[11368] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2c03, name = 'Processes-0.76939265'
2007-02-07 22:54:48.961 hazelfolderwatch[11368] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (Processes-0.76939265)
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: exited abnormally: Abort trap
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: 7 more failures without living at least 60 seconds will cause job removal
2007-02-07 22:56:07.321 hazelfolderwatch[11370] Another hazelfolderwatch process is processing this directory. Exiting.
launchd[406]: com.noodlesoft.Hazel.hazelfolderwatch-234881049-458996: 7 more failures without living at least 60 seconds will cause job removal
2007-02-07 23:01:14.541 hazelfolderwatch[11442] Another hazelfolderwatch process is processing this directory. Exiting.
2007-02-07 23:05:16.692 hazelfolderwatch[11450] Another hazelfolderwatch process is processing this directory. Exiting.
2007-02-07 23:07:16.062 hazelfolderwatch[11455] Another hazelfolderwatch process is processing this directory. Exiting.
2007-02-07 23:10:16.681 hazelfolderwatch[11459] Lockfile is stale. Updating time and proceeding.

[troubledwine]

Same thing is now happening on my second computer at the office:

Code: Select all

launchd[312]: com.noodlesoft.Hazel.hazelfolderwatch-234881029-545228: 1 more failure without living at least 60 seconds will cause job removal
2007-02-08 16:38:39.403 hazelfolderwatch[9092] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2003, name = 'NSApplication-MainThread-2384-284231772554012#'
2007-02-08 16:38:39.403 hazelfolderwatch[9092] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (NSApplication-MainThread-2384-284231772554012#)
2007-02-08 16:38:39.404 hazelfolderwatch[9092] *** Assertion failure in -[NSApplication _createWakeupPort], AppKit.subproj/NSApplication.m:3578
2007-02-08 16:38:39.404 hazelfolderwatch[9092] CFMessagePortCreateLocal returned NULL port
2007-02-08 16:38:41.407 hazelfolderwatch[9092] Processing directories: ("/Users/xxxxxxxxxxx/Downloads")
launchd[312]: com.noodlesoft.Hazel.hazelfolderwatch-234881029-545228: 1 more failure without living at least 60 seconds will cause job removal
2007-02-08 16:43:39.403 hazelfolderwatch[9097] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2003, name = 'NSApplication-MainThread-2389-284531773077775#'
2007-02-08 16:43:39.404 hazelfolderwatch[9097] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (NSApplication-MainThread-2389-284531773077775#)
2007-02-08 16:43:39.404 hazelfolderwatch[9097] *** Assertion failure in -[NSApplication _createWakeupPort], AppKit.subproj/NSApplication.m:3578
2007-02-08 16:43:39.405 hazelfolderwatch[9097] CFMessagePortCreateLocal returned NULL port
2007-02-08 16:43:41.408 hazelfolderwatch[9097] Processing directories: ("/Users/xxxxxxxxxxx/Downloads")
launchd[312]: com.noodlesoft.Hazel.hazelfolderwatch-234881029-545228: 1 more failure without living at least 60 seconds will cause job removal
2007-02-08 16:48:39.405 hazelfolderwatch[9106] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2003, name = 'NSApplication-MainThread-2392-284831774270964#'
2007-02-08 16:48:39.407 hazelfolderwatch[9106] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (NSApplication-MainThread-2392-284831774270964#)
2007-02-08 16:48:39.407 hazelfolderwatch[9106] *** Assertion failure in -[NSApplication _createWakeupPort], AppKit.subproj/NSApplication.m:3578
2007-02-08 16:48:39.407 hazelfolderwatch[9106] CFMessagePortCreateLocal returned NULL port
2007-02-08 16:48:41.410 hazelfolderwatch[9106] Processing directories: ("/Users/xxxxxxxxxxx/Downloads")
launchd[312]: com.noodlesoft.Hazel.hazelfolderwatch-234881029-545228: 1 more failure without living at least 60 seconds will cause job removal
2007-02-08 16:53:39.404 hazelfolderwatch[9108] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2003, name = 'NSApplication-MainThread-2394-285131773477755#'
2007-02-08 16:53:39.405 hazelfolderwatch[9108] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (NSApplication-MainThread-2394-285131773477755#)
2007-02-08 16:53:39.406 hazelfolderwatch[9108] *** Assertion failure in -[NSApplication _createWakeupPort], AppKit.subproj/NSApplication.m:3578
2007-02-08 16:53:39.406 hazelfolderwatch[9108] CFMessagePortCreateLocal returned NULL port
2007-02-08 16:53:41.409 hazelfolderwatch[9108] Processing directories: ("/Users/xxxxxxxxxxx/Downloads")
launchd[312]: com.noodlesoft.Hazel.hazelfolderwatch-234881029-545228: 1 more failure without living at least 60 seconds will cause job removal
2007-02-08 16:58:39.404 hazelfolderwatch[9110] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2003, name = 'NSApplication-MainThread-2396-285431773703382#'
2007-02-08 16:58:39.405 hazelfolderwatch[9110] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (NSApplication-MainThread-2396-285431773703382#)
2007-02-08 16:58:39.405 hazelfolderwatch[9110] *** Assertion failure in -[NSApplication _createWakeupPort], AppKit.subproj/NSApplication.m:3578
2007-02-08 16:58:39.405 hazelfolderwatch[9110] CFMessagePortCreateLocal returned NULL port
2007-02-08 16:58:41.408 hazelfolderwatch[9110] Processing directories: ("/Users/xxxxxxxxxxx/Downloads")
launchd[312]: com.noodlesoft.Hazel.hazelfolderwatch-234881029-545228: 1 more failure without living at least 60 seconds will cause job removal
2007-02-08 17:03:39.403 hazelfolderwatch[9115] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2003, name = 'NSApplication-MainThread-239b-285731772603668#'
2007-02-08 17:03:39.404 hazelfolderwatch[9115] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (NSApplication-MainThread-239b-285731772603668#)
2007-02-08 17:03:39.405 hazelfolderwatch[9115] *** Assertion failure in -[NSApplication _createWakeupPort], AppKit.subproj/NSApplication.m:3578
2007-02-08 17:03:39.405 hazelfolderwatch[9115] CFMessagePortCreateLocal returned NULL port
2007-02-08 17:03:41.408 hazelfolderwatch[9115] Processing directories: ("/Users/xxxxxxxxxxx/Downloads")
launchd[312]: com.noodlesoft.Hazel.hazelfolderwatch-234881029-545228: 1 more failure without living at least 60 seconds will cause job removal


[Mr_Noodle]

Yes, there's a problem right now with Hazel after logging out and logging in. After consulting with an Apple engineer, it appears to be a shortcoming in using launchd to do what I am using it for. If you want the semi-technical explanation: when you log out, the context launchd is in is deactivated so when you log back in, it's in a somewhat crippled state. As a result some operations will break.

I have written my own replacement for launchd (at least the parts that I used launchd for) for the next version and am shooting for a beta by the end of the month.

Until then, it appears a reboot is the only way to reset things. Also, if it's feasible in your situation, you can avoid the problem by not logging out and using fast user switching instead.

In any case, I hope you can hang on for a bit.

[troubledwine]

No problem. At least you know what it is.

At home it won't be that big of a deal, but at work, I log in and out every day.

Is there a way I could "unload" the helper with something like Lingon which would help the situation on the work computer?

[Mr_Noodle]

Unfortunately, the user-level launchd is in this state permanently until the next reboot.

Another thing to try is just locking your screen at the end of the day (if you are the only one using the machine) or doing a restart instead of logging out. Not really ideal and I apologize for the inconvenience but this should be rectified soon.