rules not working for unarchive

Get help. Get answers. Let others lend you a hand.

Moderator: Mr_Noodle

rules not working for unarchive Thu Jul 27, 2023 1:06 am • by hawkpilot
I had my rules set up perfectly on my old Mac mini. It would monitor a folder on the desktop, run rules folder contents, find any RAR extensions, unarchive them, and then move the mkv file to a different folder. This worked well on my old Mac mini. Yesterday I replaced the Mac mini after cloning the same folders, etc. Hazel is set up with the same rules which I verified by looking at the hazel app on each Mac mini. Now, the rules run, but no archive is being unarchived. From the logs, it finds the rar extension files, and matches the rule to them, but nothing unarchives them.
hawkpilot
 
Posts: 7
Joined: Thu Feb 11, 2021 1:04 am

Re: rules not working for unarchive Thu Jul 27, 2023 8:46 am • by Mr_Noodle
Can you turn on debug mode (https://www.noodlesoft.com/kb/hazel-debug-mode/) and post the relevant logs?
Mr_Noodle
Site Admin
 
Posts: 11255
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

Re: rules not working for unarchive Mon Jul 31, 2023 2:13 am • by hawkpilot
2023-07-30 23:09:46.481 86Z3GCJ4MF.com.noodlesoft.HazelHelper[482] DEBUG: Thread 0x60000272c4c0: Run worker for folder: /Users/marble/Desktop/Downloaded
2023-07-30 23:09:46.481 86Z3GCJ4MF.com.noodlesoft.HazelHelper[482] DEBUG: Task already running for folder: /Users/marble/Desktop/Downloaded
2023-07-30 23:10:11.394 86Z3GCJ4MF.com.noodlesoft.HazelHelper[482] DEBUG: Thread 0x60000272c4c0: Timer fired for folder: /Users/marble/Desktop/Downloaded
2023-07-30 23:10:11.394 86Z3GCJ4MF.com.noodlesoft.HazelHelper[482] DEBUG: Thread 0x60000272c4c0: Run worker for folder: /Users/marble/Desktop/Downloaded
2023-07-30 23:10:11.395 86Z3GCJ4MF.com.noodlesoft.HazelHelper[482] DEBUG: Task already running for folder: /Users/marble/Desktop/Downloaded


I have a rule first if ANy of the following conditions are met (on the watched folder) if kind is "folder" then run rules on folder contents and then continue matching rules.

The second rule is if ANY of the following conditions are met Extention is .rar
then do the following.
Unarchive
then continue matching rules.


Third rule is if extension is .mkv or extention is .mp4 the do the following, MOVE to folder (designated folder)
hawkpilot
 
Posts: 7
Joined: Thu Feb 11, 2021 1:04 am

Re: rules not working for unarchive Mon Jul 31, 2023 8:45 am • by Mr_Noodle
It looks like you already have a long-running (possibly hung?) process on that folder. Launch Activity Monitor, search for hazelworker. Most will come and go but I'm guessing there will be one that sticks around. Note it's PID. From there, in Hazel's log, search for that PID and post the resulting excerpt.
Mr_Noodle
Site Admin
 
Posts: 11255
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

Re: rules not working for unarchive Mon Jul 31, 2023 3:22 pm • by hawkpilot
Mr_Noodle wrote:It looks like you already have a long-running (possibly hung?) process on that folder. Launch Activity Monitor, search for hazelworker. Most will come and go but I'm guessing there will be one that sticks around. Note it's PID. From there, in Hazel's log, search for that PID and post the resulting excerpt.


The PID for the hazelwork sticking around is 20618


023-07-31 12:19:58.081 86Z3GCJ4MF.com.noodlesoft.HazelHelper[482] DEBUG: Thread 0x60000272c4c0: Run worker for folder: /Users/marble/Desktop/Downloaded
2023-07-31 12:19:58.121 hazelworker[20618] Running worker (v5.1) for folder with identifier: 16777234-1416218.
2023-07-31 12:19:58.122 hazelworker[20618] ###main load address: 0x1029d4000
2023-07-31 12:19:58.122 hazelworker[20618] ###Hazel Core load address: 0x102bf8000
2023-07-31 12:19:58.122 hazelworker[20618] ###Noodle load address: 0x102f18000
2023-07-31 12:19:58.122 hazelworker[20618] ###CK load address: 0x102ad4000
2023-07-31 12:19:58.128 hazelworker[20618] DEBUG: Program is licensed.
2023-07-31 12:19:58.134 hazelworker[20618] DEBUG: Error reading file /Users/marble/Library/Application Support/Firefox/prefs.js: Error Domain=NSCocoaErrorDomain Code=260 "The file “prefs.js” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Users/marble/Library/Application Support/Firefox/prefs.js, NSUnderlyingError=0x6000015b5a10 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
2023-07-31 12:19:58.135 hazelworker[20618] DEBUG: Could not read Mail preferences.
2023-07-31 12:19:58.135 hazelworker[20618] Processing folder Downloaded (forced)
2023-07-31 12:19:58.135 hazelworker[20618] DEBUG: Pausing to wait for things to settle down.
2023-07-31 12:20:00.139 hazelworker[20618] DEBUG: Processing directories: (
"/Users/marble/Desktop/Downloaded"
)
2023-07-31 12:20:00.174 86Z3GCJ4MF.com.noodlesoft.HazelHelper[482] DEBUG: Checking events for path /Users/marble/Desktop/Downloaded, folder Downloaded
2023-07-31 12:20:00.175 hazelworker[20618] DEBUG: Received file event: {
date = "2023-07-31 19:19:58 +0000";
path = "<NoodlePathSet: 0x600001ba93e0>\n /Users/marble/Desktop/Downloaded : 18446744073709551615\n";
}
2023-07-31 12:20:00.175 hazelworker[20618] DEBUG: About to process directory /Users/marble/Desktop/Downloaded
2023-07-31 12:20:00.176 hazelworker[20618] DEBUG: .DS_Store: File is hidden/invisible. Skipping.
2023-07-31 12:20:00.233 hazelworker[20618][PREDICTION] DEBUG: Calculating fire time - predicate: typeObject isType: "public.folder" result: 1
2023-07-31 12:20:00.233 hazelworker[20618][PREDICTION] DEBUG: Next fire time: 4000-12-31 16:00:00.000
2023-07-31 12:20:00.233 hazelworker[20618][PREDICTION] DEBUG: Bail out: OR predicate
hawkpilot
 
Posts: 7
Joined: Thu Feb 11, 2021 1:04 am

Re: rules not working for unarchive Tue Aug 01, 2023 8:56 am • by Mr_Noodle
I see you are running 5.1, which is a bit old. Can you try updating to the latest (5.2.2)? Note that the in-app updater on 5.1 is broken so I suggest downloading and installing the update manually.
Mr_Noodle
Site Admin
 
Posts: 11255
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

Re: rules not working for unarchive Wed Aug 02, 2023 1:15 am • by hawkpilot
Mr_Noodle wrote:I see you are running 5.1, which is a bit old. Can you try updating to the latest (5.2.2)? Note that the in-app updater on 5.1 is broken so I suggest downloading and installing the update manually.



Thank you! That appears to have fixed the problem!
hawkpilot
 
Posts: 7
Joined: Thu Feb 11, 2021 1:04 am


Return to Support

cron