Noodlesoft Forums

I am seeing tons of errors in the Hazel log that are all very similar errors, but for different folders. The one thing in common is that all of them are paused folders.

Some of the folders do not exist anymore (I've yet to review and clean them out), but other folders definitely exist (like the Desktop).

Appears as if any paused folder is filling up the log with these similar errors:

"Could not generate new bookmark data"

"Failed to create bookmark during decoding for"

Code: Select all

2016-12-21 00:01:11.422 hazelworker[91633] Could not generate new bookmark data for path /Volumes/Cheops/g art/Coghill Cartooning: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."
2016-12-21 00:01:11.422 hazelworker[91633] Failed to create bookmark during decoding for /Volumes/Cheops/g art/Coghill Cartooning.
2016-12-21 00:01:11.422 hazelworker[91633] Could not generate new bookmark data for path /Users/George/Dropbox/Work/Projects: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."
2016-12-21 00:01:11.422 hazelworker[91633] Failed to create bookmark during decoding for /Users/George/Dropbox/Work/Projects.
2016-12-21 00:01:11.422 hazelworker[91633] Could not generate new bookmark data for path /Volumes/Cheops/g art/Coghill Cartooning/Coghill Cartooning misc/blog post art: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."
2016-12-21 00:01:11.422 hazelworker[91633] Failed to create bookmark during decoding for /Volumes/Cheops/g art/Coghill Cartooning/Coghill Cartooning misc/blog post art.
2016-12-21 00:01:11.422 hazelworker[91633] Could not generate new bookmark data for path /Users/George/Desktop/_Hazel sweep: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."
2016-12-21 00:01:11.422 hazelworker[91633] Failed to create bookmark during decoding for /Users/George/Desktop/_Hazel sweep.


Unless you are seeing something going wrong behavior-wise, I'd ignore those errors. By themselves they may not be significant but only come into play if related to something else going wrong.

It was more a matter of the excessive cluttering of the log than anything else. Thanks for confirming it isn't anything to be concerned about. Guess it's time to clean out those old folders!