Upload
Posted: Wed Jun 19, 2013 11:12 amIs it possible to upload to a particular directory on a server? I'm not sure how to specify the path in Hazel.
Page 1 of 1
Posted: Wed Jun 19, 2013 11:12 amRe: Upload
Posted: Wed Jun 19, 2013 2:16 pmI assume you are running Hazel 3.1? Click on the pop-up and select "Other...". From there, you enter the server and login details which will then connect you to the server where you can navigate to the correct folder.
Re: Upload
Posted: Wed Jun 19, 2013 4:58 pmSorry it wasn't obvious to me. I had expected a field to enter the path to the target directory.
Anyway after setting up a simple rule to upload a small text file to a subdirectory on the server I began to get messages that Hazelworker was crashing along with notifications that the file could not be uploaded. Since I send files to this subdirectory via FTP frequently I don't think the problem is on the server side. Any ideas?
Process: hazelworker [37385]
Path: /Users/USER/Library/PreferencePanes/Hazel.prefPane/Contents/Resources/hazelworker
Identifier: hazelworker
Version: 3.0.18 (890)
Code Type: X86-64 (Native)
Parent Process: HazelHelper [286]
User ID: 501
Date/Time: 2013-05-21 06:30:22.351 -0700
OS Version: Mac OS X 10.8.3 (12D78)
Report Version: 10
Interval Since Last Report: 164370 sec
Crashes Since Last Report: 16
Per-App Crashes Since Last Report: 1
Anonymous UUID: 13AEEE03-A833-DE01-672F-3012ABD0DCCC
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000084
VM Regions Near 0x84:
-->
__TEXT 0000000100000000-0000000100061000 [ 388K] r-x/rwx SM=COW /Users/USER/Library/PreferencePanes/Hazel.prefPane/Contents/Resources/hazelworker
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff8a8a7758 objc_msgSend_vtable14 + 24
1 com.apple.AutomatorFramework 0x00007fff89d8c94f -[AMWorkspace setError:] + 65
2 com.apple.AutomatorFramework 0x00007fff89d8ca9e -[AMWorkspace runWorkflowAtPath:withInput:error:] + 76
3 hazelworker 0x00000001000136e3 0x100000000 + 79587
4 hazelworker 0x000000010002333a 0x100000000 + 144186
5 hazelworker 0x00000001000031eb 0x100000000 + 12779
6 hazelworker 0x0000000100003c6a 0x100000000 + 15466
7 hazelworker 0x0000000100006c5a 0x100000000 + 27738
8 hazelworker 0x0000000100001a44 start + 52
Anyway after setting up a simple rule to upload a small text file to a subdirectory on the server I began to get messages that Hazelworker was crashing along with notifications that the file could not be uploaded. Since I send files to this subdirectory via FTP frequently I don't think the problem is on the server side. Any ideas?
Process: hazelworker [37385]
Path: /Users/USER/Library/PreferencePanes/Hazel.prefPane/Contents/Resources/hazelworker
Identifier: hazelworker
Version: 3.0.18 (890)
Code Type: X86-64 (Native)
Parent Process: HazelHelper [286]
User ID: 501
Date/Time: 2013-05-21 06:30:22.351 -0700
OS Version: Mac OS X 10.8.3 (12D78)
Report Version: 10
Interval Since Last Report: 164370 sec
Crashes Since Last Report: 16
Per-App Crashes Since Last Report: 1
Anonymous UUID: 13AEEE03-A833-DE01-672F-3012ABD0DCCC
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000084
VM Regions Near 0x84:
-->
__TEXT 0000000100000000-0000000100061000 [ 388K] r-x/rwx SM=COW /Users/USER/Library/PreferencePanes/Hazel.prefPane/Contents/Resources/hazelworker
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff8a8a7758 objc_msgSend_vtable14 + 24
1 com.apple.AutomatorFramework 0x00007fff89d8c94f -[AMWorkspace setError:] + 65
2 com.apple.AutomatorFramework 0x00007fff89d8ca9e -[AMWorkspace runWorkflowAtPath:withInput:error:] + 76
3 hazelworker 0x00000001000136e3 0x100000000 + 79587
4 hazelworker 0x000000010002333a 0x100000000 + 144186
5 hazelworker 0x00000001000031eb 0x100000000 + 12779
6 hazelworker 0x0000000100003c6a 0x100000000 + 15466
7 hazelworker 0x0000000100006c5a 0x100000000 + 27738
8 hazelworker 0x0000000100001a44 start + 52
Re: Upload
Posted: Wed Jun 19, 2013 5:17 pmAre you running an Automator action? That seems to be where the error is happening.
Re: Upload
Posted: Wed Jun 19, 2013 6:10 pmNo Automator action just using the upload feature.
I actually have a separate old Hazel rule that invokes an automator action to FTP using Transmit. It works fine but I was hoping to eliminate the Automator and Transmit portions of that rule.
All the new Hazel-only rule does is test for the name of the file (a one line text file) then uses the new Upload command to send it to a subdirectory on my server. I can set it up just fine but it fails on execution. First with an Upload Failed message then a Crash report. It keeps crashing until I disable the new rule.
https://dl.dropboxusercontent.com/u/284 ... 9%20PM.JPG
I actually have a separate old Hazel rule that invokes an automator action to FTP using Transmit. It works fine but I was hoping to eliminate the Automator and Transmit portions of that rule.
All the new Hazel-only rule does is test for the name of the file (a one line text file) then uses the new Upload command to send it to a subdirectory on my server. I can set it up just fine but it fails on execution. First with an Upload Failed message then a Crash report. It keeps crashing until I disable the new rule.
https://dl.dropboxusercontent.com/u/284 ... 9%20PM.JPG
Re: Upload
Posted: Thu Jun 20, 2013 12:49 pmThat crash is from running an Automator action. The date on that log is from May so I'm guessing it's from when you were using the Automator rule. Check your Library/Logs/Diagnostic Reports folder for more recent crashes and post/email those.
Re: Upload
Posted: Sat Jun 22, 2013 10:22 amSorry for the confusion sending you the wrong crash log.
With the latest update (3.1.1) things seem to be working now. If I run into a problem again I will let you know.
With the latest update (3.1.1) things seem to be working now. If I run into a problem again I will let you know.