Hazel unable to move file

[Iluvatar]

Hi,

I have Hazel active on my Downloads folder.
However, I ran into a problem recently.
Hazel seems unable to move a particular file.
It moves it to the destination folder (you can see it appear there),
then the file is at once moved back to the download folder and Hazel tells me through Growl that the file could not be moved...

Help!

[Mr_Noodle]

Please check the logs. Go to the Info pane and click on "View Log". Post any errors you find there.

[Iluvatar]

Please check the logs. Go to the Info pane and click on "View Log". Post any errors you find there.

Hi,

I just tried it again and it worked immediately.
That's curious because a couple of hours ago I clicked "Run Rules Now" several times and it always produced an error.
Looking at the log files, I got this:

Code: Select all

2011-09-22 11:09:56.667 hazelfolderwatch[32808] XXX.pdf: Rule [private] matched.
2011-09-22 11:09:57.157 hazelfolderwatch[32808] Error moving file /Users/root/Downloads/XXX.pdf to [private]/XXX.pdf: -47 - File is busy (delete)
2011-09-22 11:09:57.162 hazelfolderwatch[32808] [Error] Move failed: Could not move file XXX.pdf from folder /Users/root/Downloads to folder [private].

I replaced the real path with [private]
the file name with XXX.pdf
and my username with root

Regards

[Mr_Noodle]

It's an odd issue which I attribute to an Apple bug. I'm guessing you are moving across disks? If so, what happens is that the file is copied then the original is deleted. The problem is that the original file is busy so the part where the original is deleted fails. This causes the whole operation to fail except that the Apple code that does this doesn't clean up after itself. So, as a workaround, I delete the copied file at the destination and let it try again later as the move action has to be self-consistent at the end. It's pretty bad but Apple at the moment refuses to fix it.

[Iluvatar]

I'm guessing you are moving across disks?

Yes.

It's pretty bad but Apple at the moment refuses to fix it.

That's too bad. Thanks anyway for your effort.

[draklorien]

I just upgraded from Hazel 2 to v3.0.4 (Build 790) (I didn't uninstall & reinstall) and find that my files aren't moving. I scan my docs from a Fujitsu ScanSnap into a folder called Scanned Docs located into the Documents folder. These files are being moved from the local hard drive to a statically attached usb ext drive that hasn't been remove and is still currently attached and browseable. I can manually move the files but Hazel don't move them at all.

This is always worked prior to the upgrade. Now nothing works. Here is a copy of my rules and the logs. No permissions or other changes have been made to the system or folder that I am aware of or USB drive. I am the only one that uses the system so I am not aware of any user permissions that have changed. Not sure of how to attached my exported rules but simply I can into 1 local folder & based on name and color label, Hazel moves the file to the correct folder on the ext usb.

Thx,

Draklorien

Log file
2012-04-22 00:59:39.904 HazelHelper[878] Could not lock uninstall log /Users/Shared/Hazel/Uninstall Log: No such file or directory
2012-04-22 00:59:39.959 HazelHelper[878:207] launch path not accessible
2012-04-22 05:06:01.727 HazelHelper[878:207] launch path not accessible
2012-04-22 05:06:08.752 HazelHelper[878:207] launch path not accessible
2012-04-22 05:06:08.770 HazelHelper[878:207] launch path not accessible
2012-04-22 05:06:17.924 HazelHelper[878:207] launch path not accessible
2012-04-22 05:06:53.774 HazelHelper[878:207] launch path not accessible
2012-04-22 05:06:53.775 HazelHelper[878:207] launch path not accessible
2012-04-22 05:08:29.622 HazelHelper[878:207] HIToolbox: ignoring exception 'launch path not accessible' that raised inside Carbon event dispatch
(
0 CoreFoundation 0x00007fff822e5784 __exceptionPreprocess + 180
1 libobjc.A.dylib 0x00007fff80048f03 objc_exception_throw + 45
2 CoreFoundation 0x00007fff822e55a7 +[NSException raise:format:arguments:] + 103
3 CoreFoundation 0x00007fff822e5534 +[NSException raise:format:] + 148
4 Foundation 0x00007fff860b3321 -[NSConcreteTask launchWithDictionary:] + 463
5 HazelHelper 0x000000010000ab67 start + 36723
6 HazelHelper 0x000000010000b5a7 start + 39347
7 AppKit 0x00007fff819d1eda -[NSApplication sendAction:to:from:] + 95
8 AppKit 0x00007fff819f646a -[NSMenuItem _corePerformAction] + 365
9 AppKit 0x00007fff819f61d4 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 121
10 AppKit 0x00007fff81c7bcf4 -[NSMenu _internalPerformActionForItemAtIndex:] + 35
11 AppKit 0x00007fff81b2d9e9 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 136
12 AppKit 0x00007fff819d899c NSSLMMenuEventHandler + 321
13 HIToolbox 0x00007fff859587f7 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1002
14 HIToolbox 0x00007fff85957d46 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 395
15 HIToolbox 0x00007fff85975a81 SendEventToEventTarget + 45
16 HIToolbox 0x00007fff859a4c35 _ZL18SendHICommandEventjPK9HICommandjjhPKvP20OpaqueEventTargetRefS5_PP14OpaqueEventRef + 387
17 HIToolbox 0x00007fff859d1a0a SendMenuCommandWithContextAndModifiers + 56
18 HIToolbox 0x00007fff859d19c2 SendMenuItemSelectedEvent + 101
19 HIToolbox 0x00007fff859d18d2 _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 150
20 HIToolbox 0x00007fff85adaa69 _ZL19PopUpMenuSelectCoreP8MenuData5PointdS1_tjPK4RecttjS4_S4_PK10__CFStringPP13OpaqueMenuRefPt + 1618
21 HIToolbox 0x00007fff85adadc2 _HandlePopUpMenuSelection7 + 665
22 AppKit 0x00007fff81b2a99b _NSSLMPopUpCarbonMenu3 + 3720
23 AppKit 0x00007fff81d5a6f9 -[NSStatusBarButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 162
24 AppKit 0x00007fff81a5c2f5 -[NSControl mouseDown:] + 624
25 AppKit 0x00007fff819763a7 -[NSWindow sendEvent:] + 5409
26 AppKit 0x00007fff81d5b498 -[NSStatusBarWindow sendEvent:] + 68
27 AppKit 0x00007fff818abafa -[NSApplication sendEvent:] + 4719
28 AppKit 0x00007fff818426de -[NSApplication run] + 474
29 AppKit 0x00007fff8183b3b0 NSApplicationMain + 364
30 HazelHelper 0x0000000100001c28 start + 52
)
2012-04-22 06:01:55.731 HazelHelper[878:207] launch path not accessible
2012-04-22 06:01:55.756 HazelHelper[878:207] launch path not accessible
2012-04-22 06:02:04.208 HazelHelper[878:207] launch path not accessible
2012-04-22 06:03:12.517 HazelHelper[878:207] launch path not accessible
2012-04-22 06:03:12.890 HazelHelper[878:207] launch path not accessible
2012-04-22 06:03:29.231 HazelHelper[878:207] launch path not accessible
2012-04-22 06:03:29.231 HazelHelper[878:207] launch path not accessible
2012-04-22 06:03:37.766 HazelHelper[878:207] launch path not accessible
2012-04-22 06:04:08.187 HazelHelper[878:207] launch path not accessible
2012-04-22 06:04:08.284 HazelHelper[878:207] launch path not accessible
2012-04-22 06:07:32.256 HazelHelper[878:207] launch path not accessible
2012-04-22 06:07:36.867 HazelHelper[878:207] launch path not accessible

[Mr_Noodle]

It's better if you email support for these types of issues. In this case, it seems you have a bad install. Try the following procedure:

- Quit System Preferences.
- Go to your Library/PreferencePanes folder and throw away Hazel.prefPane
- Download the latest version from the site.
- Move the new Hazel.prefPane to Library/PreferencePanes
- Launch System Preferences and load up Hazel.

If you are still having problems, please email.

[draklorien]

Before I saw your fix, I ended up rebooting my mac and now Hazel is consistently working. Never had to reboot before after a Hazel upgrade.

thx

Drak