Deadlock avoided on Tahoe

Hello,

I am updated to Tahoe yesterday and Hazel 6.0.4 has stopped working on an iCloud to NAS rule. A rule that has been error free for months so I assume it is a Tahoe problem, but in case you need bug reports I figured I would post.

Rule runs on an iCloud folder and renames moves any files there to a NAS folder (Synology). The error is "The operation couldn't be completed. Resource Deadlock Avoided."

Log file below.

Thanks,
Lee

Log 2025-09-18 14:47:40.242 hazelworker[26327] 2025-09-18 New Scan-2.pdf: Rule Move to NAS matched.
2025-09-18 14:47:40.246 hazelworker[26327] [File Event] File renamed: /Users/lee/Library/Mobile Documents/com~apple~CloudDocs/Weekly receipts/2025-09-18 New Scan-2.pdf renamed to /Users/lee/Library/Mobile Documents/com~apple~CloudDocs/Weekly receipts/2025-09-18 New Scan-1.pdf.
2025-09-18 14:47:40.257 hazelworker[26327] Error moving file from /Users/lee/Library/Mobile Documents/com~apple~CloudDocs/Weekly receipts/2025-09-18 New Scan-1.pdf to /Users/lee/Library/CloudStorage/SynologyDrive-MyDrive/Receipts/2025-09-18 New Scan-1.pdf: Error Domain=NSPOSIXErrorDomain Code=11 "Resource deadlock avoided"
2025-09-18 14:47:40.257 hazelworker[26327] [Error] Move failed: Could not move file 2025-09-18 New Scan-1.pdf from folder /Users/lee/Library/Mobile Documents/com~apple~CloudDocs/Weekly receipts to folder /Users/lee/Library/CloudStorage/SynologyDrive-MyDrive/Receipts/2025-09-18 New Scan-1.pdf.
2025-09-18 14:47:48.345 hazelworker[26327] 2025-09-18 New Scan-1.pdf: Rule Move to NAS matched.
2025-09-18 14:47:48.353 hazelworker[26327] [File Event] File renamed: /Users/lee/Library/Mobile Documents/com~apple~CloudDocs/Weekly receipts/2025-09-18 New Scan-1.pdf renamed to /Users/lee/Library/Mobile Documents/com~apple~CloudDocs/Weekly receipts/2025-09-18 New Scan-2.pdf.
2025-09-18 14:47:48.365 hazelworker[26327] Error moving file from /Users/lee/Library/Mobile Documents/com~apple~CloudDocs/Weekly receipts/2025-09-18 New Scan-2.pdf to /Users/lee/Library/CloudStorage/SynologyDrive-MyDrive/Receipts/2025-09-18 New Scan-2.pdf: Error Domain=NSPOSIXErrorDomain Code=11 "Resource deadlock avoided"
2025-09-18 14:47:48.365 hazelworker[26327] [Error] Move failed: Could not move file 2025-09-18 New Scan-2.pdf from folder /Users/lee/Library/Mobile Documents/com~apple~CloudDocs/Weekly receipts to folder /Users/lee/Library/CloudStorage/SynologyDrive-MyDrive/Receipts/2025-09-18 New Scan-2.pdf.

Unfortunately, that is a generic error provided by cloud storage plugins. Are you able to do the same operation manually in Finder?

Yes, I can do it manually. NAS and iCloud are both working fine as far as I can tell, I have been able to move files, etc as normal.

Try experimenting with using a local drive at either the source or destination to help isolate where the problem lies. If you have access to other cloud services (e.g. Dropbox) see if you get similar results there.

Sorry for the delay. It is working with all other rules, except files located on iCloud Drive.

It will move files to iCloud Drive though, just not off of iCloud Drive. I will see what else it will not do.

I have got the very same Probleme here. I cannot move or copy files from iCloud anymore. Worked fine before with Sequoia.

2025-09-28 17:54:54.314 hazelworker[19161] Error copying file from /Users/username/Library/Mobile Documents/iCloud~net~doo~scanbot/Documents/z2025-06-11 17-46-34-pdf.pdf to /Users/username/SwiftScan - lokal/z2025-06-11 17-46-34-pdf.pdf: Error Domain=NSPOSIXErrorDomain Code=11 "Resource deadlock avoided"

I have tried to spilt the Hazel rules into two rules. The first is doing a rename, which still works fine.

What makes me wonder is that it wants to use the documents folder, but my documents folder is not in iCloud, and the folder it shall move it is not within the local documents folder.

Did you give Hazel full disk access?

Mr_Noodle wrote:Did you give Hazel full disk access?

Yes, Hazel got full access.

I need to provide more details.

I have a scanner app running on my iPhone which uploads any scans into iCloud.
Hazel detects this reliably and renames those files. Then it is supposed to move those files into a local folder.
This worked fine until it came to Tahoe.

Here it becomes interesting as I just noticed the following:
Hazel unsuccessfully tries to put a new incoming file into the local folder.

So I have to view the file within iCloud with the preview function.
But once I touched the file (space bar) Hazel suddenly takes another try and now the file will be moved correctly into the local folder.

I have Documents and Desktop in iCloud and optimize Mac Storage also switched on - but my local folder (where Hazel should copy the file to) has been relocated outside the documents folder.
I now have tried to place the local target folder within documents but this also does no work, results are still the same.

It's not very urgent as I still can access these files within iCloud but it damages the trust in Hazel a little bit.

Thanks for your help.

That seems to indicate the files are not being downloaded locally. Do you see a cloud icon next to the files before you preview them?

Note that the current beta version has an option to force files to be downloaded before Hazel processes them. You can check out the beta forums if you are interested in testing.

Mr_Noodle wrote:That seems to indicate the files are not being downloaded locally. Do you see a cloud icon next to the files before you preview them?

Note that the current beta version has an option to force files to be downloaded before Hazel processes them. You can check out the beta forums if you are interested in testing.

I recognized another symptom now. Hazel tried to access a local folder which I already have moved and renamed. I of course had updated the respective rule to point to the new folder which was accepted by Hazel as the entry was not greyed out. But Hazel still insisted on trying to copy the file into the old deleted folder.

I then went into the programs folder and dragged the Hazel App into the trash. Then I installed version 5.3.6 again and everything worked fine now. iCloud files are also now being handled correctly. Problem solved.

It seems to me that Hazel somehow was stuck and not being able to adopt changes anymore which have been made to the existing rules.

Anyhow. Thanks for your help. Much appreciated.

I soon intend to upgrade to Hazel 6. It got nice new features which probably will be useful to me. I then see then if a problem like this will occur again.