PHD syncing and OmniGraffle package files

Question

I am having an issue where package files synced to the home directory are appearing empty at a later date.
This issue seems to be directly related to OmniGraffle documents, affecting anything that is a .graffle (OmniGraffle Document) or .gstencil (OmniGraffle Stencil) that are stored as packages. We are using OmniGraffle 5.2.1. I have the ability to save the documents as a flat file type, I am unsure of the stencils.
Our enviornment - clients are running on MacBook Pro's with OS 10.5.8. Servers are Mac OS Server 10.5.8. Home directories are stored in an xSAN enviornment (2.2). Users belong to a group (portable homes) in OD that manages the Mobility Preferences and PHD syncing.
I performed a test where I logged the user in, added a .graffle doc to their desktop, logged them out, restarted and logged back in. Upon login, the "outer shell" of the package was still there, but had no contents.
Below I have a few excerpts from the FileSyncAgent-verbose.log from the users system. The file I was monitoring was named "NetworkDiagramMaster-2010_vB.graffle"
Logged user out:
1:: [573] PHD-L-fd-yCD8Svr1-smith Scanning flagged directory "Desktop/NetworkDiagramMaster-2010_vB.graffle/"
1:: [573] PHD-L-fd-yCD8Svr1-smith Scanning flagged directory "Desktop/NetworkDiagramMaster-2010_vB.graffle/QuickLook/"
1:: [573] network: PACKAGE ADD (DEEP) "Desktop/NetworkDiagramMaster-2010_vB.graffle" {(Priority=1, READY)}
1:: [573] <GO> network: PACKAGE ADD (DEEP) "Desktop/NetworkDiagramMaster-2010_vB.graffle" {(Priority=1, EXECUTING)}
1:: [573] ...<OK> : ADD ./data.plist
1:: [573] ...<OK> : ADD ./image130.png
1:: [573] ...<OK> : ADD ./image136.pdf
1:: [573] ...<OK> : ADD ./image137.pdf
1:: [573] ...<OK> : ADD ./image138.pdf
1:: [573] ...<OK> : ADD ./image139.pdf
1:: [573] ...<OK> : ADD ./image140.pdf
1:: [573] ...<OK> : ADD ./image141.emf
1:: [573] ...<OK> : ADD ./image142.emf
1:: [573] ...<OK> : ADD ./image143.emf
1:: [573] ...<OK> : ADD ./image144.emf
1:: [573] ...<OK> : ADD ./image145.emf
1:: [573] ...<OK> : ADD ./image146.png
1:: [573] ...<OK> : ADD ./image147.emf
1:: [573] ...<OK> : ADD ./image148.emf
1:: [573] ...<OK> : ADD ./image149.emf
1:: [573] ...<OK> : ADD ./image150.emf
1:: [573] ...<OK> : ADD ./image151.emf
1:: [573] ...<OK> : ADD ./image152.png
1:: [573] ...<OK> : ADD ./image153.png
1:: [573] ...<OK> : ADD ./image154.tiff
1:: [573] ...<OK> : ADD ./image155.bmp
1:: [573] ...<OK> : ADD ./image156.jpg
1:: [573] ...<OK> : ADD ./image157.pdf
1:: [573] ...<OK> : ADD ./image158.emf
1:: [573] ...<OK> : ADD ./image159.emf
1:: [573] ...<OK> : ADD ./image160.emf
1:: [573] ...<OK> : ADD ./image161.emf
1:: [573] ...<OK> : ADD ./image162.emf
1:: [573] ...<OK> : ADD ./image164.tiff
1:: [573] ...<OK> : ADD ./image165.png
1:: [573] ...<OK> : ADD ./image166.jpg
1:: [573] ...<OK> : ADD ./image167.ai
1:: [573] ...<OK> : ADD ./image168.bmp
1:: [573] ...<OK> : ADD ./image169.bmp
1:: [573] ...<OK> : ADD ./image170.bmp
1:: [573] ...<OK> : ADD ./image171.eps
1:: [573] ...<OK> : ADD ./image172.tiff
1:: [573] ...<OK> : ADD ./image173.jpg
1:: [573] ...<OK> : ADD ./image174.jpg
1:: [573] ...<OK> : ADD ./image175.jpg
1:: [573] ...<OK> : ADD ./image176.gif
1:: [573] ...<OK> : ADD ./image177.bmp
1:: [573] ...<OK> : ADD ./image178.png
1:: [573] ...<OK> : ADD ./image179.tiff
1:: [573] ...<OK> : ADD ./image18.wmf
1:: [573] ...<OK> : ADD ./image180.pdf
1:: [573] ...<OK> : ADD ./image20.pdf
1:: [573] ...<OK> : ADD ./image23.tiff
1:: [573] ...<OK> : ADD ./image24.tiff
1:: [573] ...<OK> : ADD ./image31.bmp
1:: [573] ...<OK> : ADD ./image32.wmf
1:: [573] ...<OK> : ADD ./image33.pdf
1:: [573] ...<OK> : ADD ./image34.pdf
1:: [573] ...<OK> : ADD ./image36.pdf
1:: [573] ...<OK> : ADD ./image37.pdf
1:: [573] ...<OK> : ADD ./image38.tiff
1:: [573] ...<OK> : ADD ./image39.pdf
1:: [573] ...<OK> : ADD ./image40.pdf
1:: [573] ...<OK> : ADD ./image41.pdf
1:: [573] ...<OK> : ADD ./image42.pdf
1:: [573] ...<OK> : ADD ./image44.pdf
1:: [573] ...<OK> : ADD ./image45.pdf
1:: [573] ...<OK> : ADD ./image46.pdf
1:: [573] ...<OK> : ADD ./image47.pdf
1:: [573] ...<OK> : ADD ./image48.pdf
1:: [573] ...<OK> : ADD ./image54.tiff
1:: [573] ...<OK> : ADD ./image55.pdf
1:: [573] ...<OK> : ADD ./image56.pdf
1:: [573] ...<OK> : ADD ./image57.pdf
1:: [573] ...<OK> : ADD ./image58.pdf
1:: [573] ...<OK> : ADD ./image59.pdf
1:: [573] ...<OK> : ADD ./image60.pdf
1:: [573] ...<OK> : ADD ./image61.pdf
1:: [573] ...<OK> : ADD ./image62.jpg
1:: [573] ...<OK> : ADD ./image63.jpg
1:: [573] ...<OK> : ADD ./image64.jpg
1:: [573] ...<OK> : ADD ./image65.jpg
1:: [573] ...<OK> : ADD ./image66.png
1:: [573] ...<OK> : ADD ./QuickLook/Preview.pdf
1:: [573] ...<OK> : ADD ./QuickLook/Thumbnail.tiff
1:: [573] ...<OK> : ADD ./QuickLook
1:: [573] <OK> network: PACKAGE ADD (DEEP) "Desktop/NetworkDiagramMaster-2010_vB.graffle" {(Priority=1, EXECUTING)}
1:: [573] -[SPeer(protected) processPackageJob:]: Found 'empty' package job. Ignoring.
I checked the users folder on the server and the file was in their desktop folder, completely intact.
Restarted, logged user back in:
0:: [117] [2010/03/24 11:08:07.598] PHD:Contents CONFLICT at "Desktop/NetworkDiagramMaster-2010_vB.graffle/"
0:: [117] [2010/03/24 11:08:07.598] PHD:--------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ---
0:: [117] [2010/03/24 11:08:07.598] PHD:AVV  | CVV  | Info:Finder | Info:Mod Date  | Info:Mode | Info:NodeID  | Info:Props | Info:User/Group  | LVV  | Object Name | ObjectID  | Status
0:: [117] [2010/03/24 11:08:07.598] PHD:PHD-L-fd-yCD8Svr1-smith1269439466[] | PHD-L-fd-yCD8Svr1-smith1269439466[] |  FF:0000  | 2010/03/24 10:58:19 | rwxr-xr-x | ID:0x0000000096957a |   | U: 1104 G: 20 | PHD-L-fd-yCD8Svr1-smith1269439466[] | /  | 0x1adb3d0 <x-coredata://68B7FC25-9F7D-4013-A591-E646B2A38B43/SNode/p15455> |  P
0:: [117] [2010/03/24 11:08:07.598] PHD:PHD-L-fd-yCD8Svr1-smith1269439466[] | PHD-L-fd-yCD8Svr1-smith1269439466[] |  FF:0000  | 2010/03/24 10:58:19 | rwxr-xr-x | ID:0x00000000168882 |   | U: 1104 G: 20 | PHD-L-fd-yCD8Svr1-smith1269439466[] | /  | 0x1a0a130 <x-coredata://5BC3195E-D57D-4CB2-BEEC-103892292F44/SNode/p15507> |  D
0:: [117] [2010/03/24 11:08:07.599] PHD:CONFLICT at "Desktop/NetworkDiagramMaster-2010_vB.graffle/" auto-resolved: winning peer "network", new version vector: PHD-L-fd-yCD8Svr1-smith1269439466[]
1:: [117] PHD:Sync job generation pass 2 of 2 for "HomeSync_Mirror" took 0.08 seconds
1:: [117] PHD:Sync jobs for peer local
1:: [117] PHD: local: DELETE "Desktop/NetworkDiagramMaster-2010_vB.graffle" {(Priority=1, READY)}
1:: [117] PHD: local: ADD "Desktop/NetworkDiagramMaster-2010_vB.graffle" {(Priority=1, BLOCKED)}
1:: [117] PHD:Items to copy: 20, bytes to copy: 879
1:: [117] PHD:<OK> local: DELETE "Desktop/NetworkDiagramMaster-2010_vB.graffle" {(Priority=1, EXECUTING)}
1:: [117] PHD:<OK> local: ADD "Desktop/NetworkDiagramMaster-2010_vB.graffle" {(Priority=1, EXECUTING)}
1:: [117] PHD:-[SPeer(protected) processPackageJob:]: Found 'empty' package job. Ignoring.
This time, when checking the file on the desktop of the users system, the file was there, but there were no contents in the package.
The user has since logged out and left for the day, but I checked the server and for now, the file seems to be OK. It appears that when the person syncs later, the "blank" file is pushed from their system back up to the server. Then both files are blank.
I am not sure, but the phrase "Found 'empty' package job. Ignoring." appears a few times in the log. I think this may have something to do with the issue, but I am not sure how to fix it. I have many users and it is beginning to worry me that there may be other files which are not getting copied properly.
Has anyone out there run across this or have any ideas for a fix?

Answer 1

You need to ask the Dropbox people about that, but I'm pretty sure that it's like having an external drive and it can't sync that precisely. It will act just like dragging and dropping a file on an external drive and back up the whole thing each time.
For that kind of syncing you need an iDisk from Apple's MobileMe service. Certain note programs, like Yojimbo, are made with idisk syncing built in, but I don't think Devonthink supports that.