Log errors for alias files in PDF Services folder

[gcoghill]

Seeing a ton of repeated errors in the log for the following:

2023-12-12 17:42:54.036 hazelworker[10887] Could not resolve path for bookmark data: Error Domain=NSCocoaErrorDomain Code=259 "The file couldn’t be opened because it isn’t in the correct format."

2023-12-12 17:42:54.167 hazelworker[10887] Could not load alias file at /Users/George/Library/PDF Services/_print 1-sided: Error Domain=NSCocoaErrorDomain Code=256 "The file couldn’t be opened."

2023-12-12 17:42:54.167 hazelworker[10887] Could not load alias file at /Users/George/Library/PDF Services/_print 2-sided: Error Domain=NSCocoaErrorDomain Code=256 "The file couldn’t be opened."

The latter two are for alias files in the PDF Services folder, and I have Hazel rules for the originals. I have folders on the desktop to save downloaded PDF files using the PDF Print Service in the Print dialog box. Hazel is not watching these aliases, but the originals which are on the desktop.

There is also an application alias in the PDF Services folder, which may be the other repeated error about "bookmark data"?

[Mr_Noodle]

Still unclear on your setup. What are you rules doing to the originals? Can you post more surrounding context from the logs?

[gcoghill]

The rules on the original folders simply rename the files and move to another folder (which is also monitored by Hazel, and runs a shell script to print using defined presets).

The rule itself works fine.

The folder aliases are created when adding these folders to the PDF Services menu in the Print dialog box. So basically, I hit "Print", the dialog box comes up, in the "PDF" menu at the bottom I choose one of the folders I added, and the PDF is saved to that folder.

The original folders are on the desktop.

As far as log context, there are just repeated entries for these errors. There are some other log entries of course, but do not seems related:

Code: Select all

2023-12-13 15:37:38.301 hazelworker[1265] Done processing folder Trash
2023-12-13 15:37:39.988 hazelworker[1341] Running worker (v5.3.1) for folder with identifier: trash.
2023-12-13 15:37:39.989 hazelworker[1341] ###Arch: arm64
2023-12-13 15:37:39.989 hazelworker[1341] ###main load address: 0x1027b0000
2023-12-13 15:37:39.989 hazelworker[1341] ###Hazel Core load address: 0x102dc4000
2023-12-13 15:37:39.989 hazelworker[1341] ###Noodle load address: 0x1030b4000
2023-12-13 15:37:39.989 hazelworker[1341] ###CK load address: 0x102cb8000
2023-12-13 15:37:39.995 hazelworker[1341] Processing folder Trash

However, I did discover that there was another Folder and rule set that was monitoring the Library folder, and this is probably why these alias files are being scanned.

Maybe I have this rule set setup improperly. trying to back up a few app preferences and application support folders (Hazel & TextExpander).

Rule scans the User folder, then sorts down via a "run rules on some subfolders" rule at bottom of rule set. It scans

Preferences
Application Support
Library

And then the rules above it filter for the specific files I want to back up.

I tried to limit this using "enclosing folder" criteria.

Is my setup way too "wide"? Seems like it is scanning folders I was trying to exclude. I did note that one rule was not using "enclosing folder" criteria, and maybe that was causing Hazel to scan the entire folder.

[gcoghill]

Looking at the Log file again, it appears these errors are taking place when Hazel is processing the Trash folder. They are all enclosed in-between the entries:

Code: Select all

2023-12-13 18:10:08.351 hazelworker[21188] Processing folder Trash
2023-12-13 18:10:10.276 hazelworker[21188] Done processing folder Trash

[Mr_Noodle]

Logs for different runs can be interspersed. Can you email in a larger excerpt from the logs?