The error log shows the following:
- Code: Select all
2015-11-29 20:46:24.582 hazelworker[20764] [Error] Internal Error.: Hazel has encountered an internal error and cannot process folder Documents. Please check the logs for more details.
Moderator: Mr_Noodle
2015-11-29 20:46:24.582 hazelworker[20764] [Error] Internal Error.: Hazel has encountered an internal error and cannot process folder Documents. Please check the logs for more details.
2015-11-30 20:05:07.000 hazelworker[24326] ###main load address: 0x10a0e0000
2015-11-30 20:05:07.002 hazelworker[24326] ###Noodle load address: 0x10a1f4000
2015-11-30 20:05:07.002 hazelworker[24326] ###CK load address: 0x10a1ba000
2015-11-30 20:05:07.054 hazelworker[24326] Processing folder Applications (forced)
2015-11-30 20:05:09.686 hazelworker[24326] Done processing folder Applications
2015-11-30 20:05:15.693 hazelworker[24331] ###main load address: 0x10999f000
2015-11-30 20:05:15.695 hazelworker[24331] ###Noodle load address: 0x109aac000
2015-11-30 20:05:15.695 hazelworker[24331] ###CK load address: 0x109a73000
2015-11-30 20:05:15.722 hazelworker[24331] Processing folder Documents
2015-11-30 20:05:17.901 hazelworker[24331] Could not load internal db /Users/steve/Library/Application Support/Hazel/16777217-506249.hazeldb: Error Domain=NSCocoaErrorDomain Code=3840 "Encountered unexpected character k on line 74556 while looking for close tag" UserInfo={NSDebugDescription=Encountered unexpected character k on line 74556 while looking for close tag, kCFPropertyListOldStyleParsingError=The data couldn’t be read because it isn’t in the correct format.}
2015-11-30 20:05:17.903 hazelworker[24331] [Error] Internal Error.: Hazel has encountered an internal error and cannot process folder Documents. Please check the logs for more details.
2015-11-30 20:05:17.907 HazelHelper[586] Worker process for folder /Users/steve/Documents did not check in.
Mr_Noodle wrote:It seems that something corrupted one of Hazel's internal database files. I suggest removing the following:
/Users/steve/Library/Application Support/Hazel/16777217-506249.hazeldb
Hazel will reconstruct it next time it runs and hopefully things should work after that.