Noodlesoft Forums

I have files being moved to the trash & copied to other folders in order to work around permission issues.

Well I've noticed that sometimes when I check the folder that the copied files were sent to every once in a while one of the files names will show up in the list but the name will be ghosted (lighter) & not really there unable to open. Then when I send the same files through again the files will be normal?

Do you know what is causing this?

It is scaring the crap out of me because we are using Hazel to move files for my company & a lot is riding on my shoulders for files to really be there.

Maybe it's in the process of being copied? Try doing it in Finder manually and see if you get the same thing.

I've been manually coping files for years & have not had this problem. I have also been doing it (Tests) in the same folders as that are being watched & it has not happen.

Maybe it has to do with when it is being moved into the watched folder & sometimes it takes time to copy into the watched folder but Hazel is trying to copy it forward before it is finished coping into the watched folder?

I'm not sure but really need a fix.

When you see the file ghosted, check the logs to see if it's in the middle of a copy. Also, do these tend to be large files?

I set up the ability to post images to forums now & while I'm at it let me plug a friend's automator script that will give you the ability to (On a Mac) right click any image then select the service & it will put the image in http://imgur.com/ & then copy the URL to your clipboard inside the Bulletin Board Code tags. So then all you have to do is paste it.

Just see http://www.johneday.com/272/imgur-service-for-fast-image-sharing if your interested. It is very easy!

OK here you go. I wanted a way to confirm if all the files were copied across the network & if not I can know which ones were not. So this is what I came up with.

What I'm trying to have happen is this. When files are moved into a folder the files will be moved to the trash & then copied to a temp hold folder (on the same computer) & the label color changed to nothing; then copied to another folder (on another computer over our network) then copied again to the same temp hold folder (on the same computer (with if file exists: replace)) but this time when copied to temp hold folder it will change the label color to green.

The reason for this. Lets say the computer for some reason was not connected to the other computer on the network then it would not be able to copy the files over the network & then it will not recopy the files back to the temp hold folder & change there label color to green (because of the order of the rules) so I will know that any files in the temp hold folder if there labels are not green then it was not copied over the network. Plus I have Hazel watching the temp hold folder for any files that labels are not green if so it will send me a Growl. Then I can easily find the non copied files & copy them over. Please see the images. Hope this is clear.

One problem is that I get a Growl message always because I don't know how to have Hazel wait to check if the files labels are green??

This may not be a good way to set it up so please tell me otherwise.

Plus here is the part of the log when the file became ghosted. (See Image)

2012-08-23 14:06:49.523 hazelworker[68923] ILDR3V-010805-16098-01.ai: Rule All Files Move to Server matched.
2012-08-23 14:06:49.949 hazelworker[68923] [File Event] File moved: ILDR3V-010805-16098-01.ai moved from folder /Users/b3po/Public/Move via Hazel to folder /Users/b3po/.Trash.
2012-08-23 14:06:50.203 hazelworker[68923] [File Event] File copied: ILDR3V-010805-16098-01.ai copied from folder /Users/b3po/.Trash to folder /Users/b3po/Public/Temp Finished IL's.
2012-08-23 14:06:50.387 hazelworker[68930] File .DS_Store is busy. Skipping for now.
2012-08-23 14:06:50.494 hazelworker[68930] ILDR3V-010805-16098-01.ai: Rule Not Green Because Not Connected to Server matched.
2012-08-23 14:06:50.494 hazelworker[68933] Sending metrics to scheduler. Next scheduled run: 5828963-12-19 19:00:00.000
2012-08-23 14:06:50.522 hazelworker[68930] Hazel Alert: /Users/b3po/Public/Temp Finished IL'sB3PO NOT CONNECTED TO SERVER
2012-08-23 14:06:50.522 hazelworker[68930] [Custom Message] Hazel Alert: /Users/b3po/Public/Temp Finished IL'sB3PO NOT CONNECTED TO SERVER
2012-08-23 14:06:50.993 hazelworker[68923] [File Event] File copied: ILDR3V-010805-16098-01.ai copied from folder /Users/b3po/Public/Temp Finished IL's to folder /Volumes/Illustration Pages for Shar/Moved from B3PO via Hazel.
2012-08-23 14:06:51.130 hazelworker[68923] [File Event] File copied: ILDR3V-010805-16098-01.ai copied from folder /Volumes/Illustration Pages for Shar/Moved from B3PO via Hazel to folder /Users/b3po/Public/Temp Finished IL's.
2012-08-23 14:06:51.156 hazelworker[68923] Warning: busy fire time is in the past: 2012-08-23 14:06:44 -0400

And here is part of the log when a file worked correctly. (which is 99.9% of the time)

2012-08-23 14:06:53.160 hazelworker[68923] ILCN15-040601-05.pdf: Rule All Files Move to Server matched.
2012-08-23 14:06:53.315 hazelworker[68923] [File Event] File moved: ILCN15-040601-05.pdf moved from folder /Users/b3po/Public/Move via Hazel to folder /Users/b3po/.Trash.
2012-08-23 14:06:53.640 hazelworker[68923] [File Event] File copied: ILCN15-040601-05.pdf copied from folder /Users/b3po/.Trash to folder /Users/b3po/Public/Temp Finished IL's.
2012-08-23 14:06:53.858 hazelworker[68923] [File Event] File copied: ILCN15-040601-05.pdf copied from folder /Users/b3po/Public/Temp Finished IL's to folder /Volumes/Illustration Pages for Shar/Moved from B3PO via Hazel.
2012-08-23 14:06:54.043 hazelworker[68923] [File Event] File copied: ILCN15-040601-05.pdf copied from folder /Volumes/Illustration Pages for Shar/Moved from B3PO via Hazel to folder /Users/b3po/Public/Temp Finished IL's.

I'm not sure if I understand why you are doing things this way. Some comments:
- Is there a reason why you just don't do a move initially? Why do the whole rigamarole with the trash?
- Instead of having this whole temp folder thing, just have Hazel retry copying to the other machine. It will eventually succeed when the network share is online.

In your log excerpt, one thing that sticks out is that it appears you have two different processes operating on the same file. If you have Hazel monitoring any of the folders that are destinations of this rule, then they may end up stepping on each other. For instance, this line:

2012-08-23 14:06:50.494 hazelworker[68930] ILDR3V-010805-16098-01.ai: Rule Not Green Because Not Connected to Server matched.

Shows another process that is matching the file against a different rule than the one you have above. This is happening while it is executing the rule above.

I suggest maybe stepping back and describing what you are trying to do here. It seems to me that things are being made overcomplicated just to confirm files have been copied.

The reason that the files are moved to the trash & then copied to the other folders is in order to work around permission issues as I said in the 1st post.

When files & folders are moved forward over a network of Mac OSX computers the Permissions become a problem like not being able to edit the files after that move; unless you go in as an administrator a manually change the permissions all to Read & Write. So to work around this we move to trash & copy to other folders. Copy does not make Permissions all Read Only & also allows the ownership to become that of the computer it is copied to plus not everyone is at the same level of Permissions on the network.

- Instead of having this whole temp folder thing, just have Hazel retry copying to the other machine. It will eventually succeed when the network share is online.

With that in mind this suggestion as far as I know will not work because if the computer is not connected to the network it will move the file to the trash & just not copy to the other computer.

I think it is because the order has to be; put rule Move to trash at top then put rule to Copy below because as I think as I understand it (Which I'm not sure I do or why) we have to have Move to trash above Copy to other computer because if it were the other way around it would Copy the file to the other computer & just leave the original file in the folder (Not moving it to the trash) This is what I think I was told in my other Post.

I think your problem is you are not paying attention to the order of the rules. If you think about it, any file that has been added more than 10 minutes ago was also added more than 5 minutes ago. In that case, the first rule is the one that will be executed. You need to change the order of the rules to establish priority. Use the rule preview to check your work.

http://www.noodlesoft.com/forums/viewtopic.php?f=4&t=1629

Maybe I'm confused HA HA. I'm am confused but am learning. This order of the rules thing, I have not wrapped my head around it yet? It seems backwards to how I would think it should be & not sure what detail that I'm missing but would love to get it.

So that being written, now do you see what I'm trying to do? If one of the computers involved on our network was disconnected for some reason then I don't want the files to just be moved to the trash so I have it 1st move to trash then Copy to a Temp folder on itself (with label no color) then Copy to folder on other computer (with label Green) over the network then Copy again to the Temp folder (this time label color Green & replacing on) so that if it did not copy over the network then the label will be left at no color & then a Growl will be sent to me (because I have the Temp folder watched for files whose label are no color & a Growl is sent) Plus I can easily go into the Temp folder when this happens & see right away which files are the ones that did not get copied over the network because of the no color label.

As far as this:

In your log excerpt, one thing that sticks out is that it appears you have two different processes operating on the same file. If you have Hazel monitoring any of the folders that are destinations of this rule, then they may end up stepping on each other. For instance, this line:

I think I took care of this problem with adding the if statement Date Added... So the 2 rules will not step on each other & this seems to be the case so far. See image:

Was this how the rule looked during the period of the logs you posted before? Because it doesn't look like it waited 5 minutes before processing it. Also, does the file stay ghosted permanently or does it eventually unghost? Lastly, is there anything running on the other computer which might do something with the file?

Maybe the 5 minutes rule fixed the problem? Let me get back to you if not. I do have one file in the folder that is ghosted but that may have happened before I added the 5 minute rule so I will keep an eye out for more ghost.

This is interesting, I did try to copy a good version of the ghosted file (NON_GHOSTED) into the folder where the ghosted file is (to replace it with the good file but a dialog box came up & said "Can't... because file... is busy") so I had to delete the ghosted file & them put the good file inside.