Sync problems and ACL issues

Similar issue

Task: Disk-to-disk clone (-psn_0_561289)
Source: iMac Intel Duo (/dev/disk0s2, )
    Mount point: /
    Filesystem: hfs
    Capacity: 999.86 GB 
    Used: 104.19 GB 
    Available: 895.67 GB 
    Mac OS X version: 10.6.3

Target: OWC FW (/Volumes/OWC FW/ [/dev/disk3s2, ])
    Mount point: /Volumes/OWC FW
    Filesystem: hfs
    Capacity: 319.73 GB 
    Used: 425.50 MB 
    Available: 319.30 GB 
    Mac OS X version: 10.6.3

Bootability: This volume will be bootable.

Cloning method: Backup everything
    Delete items on target that aren't on the source: Yes


16:17:46    Warning user about performing a destructive action.
16:17:48    User chose to proceed with destructive action.
16:17:48    The target volume has ownership enabled.
16:17:48    The target volume has Access Control Lists enabled.
16:17:48    Authenticating...
16:17:48    Initiating synchronization engine...
16:17:54    Cloning...
16:23:32    rsync: send_files failed to open "/private/tmp/kactd.txt": Permission denied (13) (51)
16:23:47    CCC Synchronization Engine: Some errors were encountered during the backup., Error code: 51
16:23:48    Sync Engine warnings: (
    "rsync: send_files failed to open \"/private/tmp/kactd.txt\": Permission denied (13)",
    "rsync error: some files/attrs were not transferred (see previous errors) (code 23) at /Volumes/Home/Users/bombich/Development/Bombich_Software/rsync/rsync-3.0.6/main.c(1044) [sender=3.0.6]"
)
================================================================================

Carsten:

Do you have any special access controls applied to this file?:

Daten/alpha portfolio advisors/Projekte/Kunden/HH Pensionsverwaltung/Absolute Return Managerauswahl 2010/Quantanalysen/Performanceanalyse_Absolute Return 2010.xlsm

If so, do they "look right"? The log indicates that the user and group ids are "128", which isn't an ordinary user or group id on Mac OS X.

David:

Your error is mostly unrelated, though there is a slight relation. Do you happen to still have that file? You can get to it by choosing "Go to folder" from the Finder's Go menu, then type "/tmp" and hit return. "Get Info" on the file and see if there are any special access controls on that file.

Thanks,
Mike

Carsten/David:

Can either of you offer some insight on the files that were involved with these errors?

Thanks,
Mike

It was a complete backup and all info was included in post I made

Hi David:

Actually, I was hoping you could give me some more information about the file indicated in the error message, "/private/tmp/kactd.txt". That file has probably been deleted by the system's periodic cleanup tasks by now, have you seen this issue recur in the last couple days?

Mike

kactd.txt zero KB

Both system and everyone - No Access - it was created yesterday and modifed yesterday same time - Kind: plain txt

also this is what showed up on the latest backup

==================== Carbon Copy Cloner (v. 3.3): 2010-05-13 00:34:33 -0400 ====================

Operating System:   Version 10.6.3 (Build 10D573)

Hardware:
hw.machine: i386
hw.model: iMac10,1
hw.logicalcpu: 2
hw.physmem: 2147483648
vm.loadavg: { 0.09 0.29 0.54 }


Task: Disk-to-disk clone (-psn_0_307275)
Source: iMac Intel Duo (/dev/disk0s2, 8B47F64C-62F8-3026-9FBA-0C1A31571D6C)
    Mount point: /
    Filesystem: hfs
    Capacity: 999.86 GB 
    Used: 105.16 GB 
    Available: 894.70 GB 
    Mac OS X version: 10.6.3

Target: OWC FW (/Volumes/OWC FW/ [/dev/disk3s2, 95C5717A-2285-3DE6-BC43-544EA4461172])
    Mount point: /Volumes/OWC FW
    Filesystem: hfs
    Capacity: 319.73 GB 
    Used: 103.96 GB 
    Available: 215.77 GB 
    Mac OS X version: 10.6.3

Bootability: This volume will be bootable.

Cloning method: Backup everything
    Delete items on target that aren't on the source: Yes


00:34:33    Warning user about performing a destructive action.
00:34:42    User chose to proceed with destructive action.
00:34:42    The target volume has ownership enabled.
00:34:42    The target volume has Access Control Lists enabled.
00:34:42    Authenticating...
00:34:46    Initiating synchronization engine...
00:34:48    Cloning...
00:41:39    rsync: send_files failed to open "/private/tmp/kactd.txt": Permission denied (13) (51)
00:42:04    CCC Synchronization Engine: Some errors were encountered during the backup., Error code: 51
00:42:05    Sync Engine warnings: (
    "rsync: send_files failed to open \"/private/tmp/kactd.txt\": Permission denied (13)",
    "rsync error: some files/attrs were not transferred (see previous errors) (code 23) at /Volumes/Home/Users/bombich/Development/Bombich_Software/rsync/rsync-3.0.6/main.c(1044) [sender=3.0.6]"
)
================================================================================

Hi David:

Do you have any idea what application might be creating/modifying this file? My Google search turned up only this discussion when I searched for that file.

Also, can you run this command in the Terminal application (copy and paste should work fine):

sudo ls -le@ /tmp/kactd.txt

and paste the resulting text back here? You will be prompted to type your login password.

If you don't know what the file is for or associated with, and if it is 0 bytes in size and no one has access to it, and that it is in a temporary directory whose contents will be purged on a weekly basis, I'd say it would be safe to delete the file to get past this error. FWIW, CCC is copying everything else just fine, so your backup is in good shape. The error is annoying though, I'm sure.

Thanks,
Mike

iMac-Intel:~ davidmarshall$ sudo ls -le@ /tmp/kactd.txt

WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:
---x------ 1 root wheel 0 May 13 09:52 /tmp/kactd.txt iMac-Intel:~ davidmarshall$

Well that's a strange little file. If I create a file identical to that on my test system (empty file with those permissions and ownership), it doesn't affect the transfer at all. I would try deleting that file. If it comes back, I'd try to figure out what app is creating it. If you ever find out, please let me know, because it's a mystery to me how it could be causing this error.

I suppose that one last thing to check would be for any special flags on the file. Typically files with special flags can be copied just fine, it's certain flags that would prevent them from being subsequently deleted or overwritten. I'm still curious though. Can you run this in Terminal:

ls -lOe@ /tmp/kactd.txt

That's a capital "O" (Oh), and that should display file flags.

Thanks,
Mike

Last login: Fri May 14 11:06:53 on console
iMac-Intel:~ davidmarshall$ ls -lOe@ /tmp/kactd.txt
---x------ 1 root wheel - 0 May 14 11:06 /tmp/kactd.txt iMac-Intel:~ davidmarshall$

No flags. I'm officially stumped, that file shouldn't cause any trouble at all. Do you get any errors after deleting that file? And do you have any leads on what application is creating it?

Thanks,
Mike

I cannot change the permissions on system but I can on everyone. It
could be a COD4, teamspeak 3 or blackfire file.

Carsten:

If you are still affected by this issue, can you let me know if it is resolved in the 3.3.3-b2 that I posted a moment ago? To get the update, choose "Update CCC" from the Carbon Copy Cloner menu, check the "Inform me of beta updates" box, then click on the "Check for updates now" button and follow the instructions provided to apply the update.

Thanks,
Mike

Came across this discussion because I'm getting the exact same error using SuperDuper. I completed a "smart update" earlier in the evening with no problems. I deleted a folder, uninstalled the beta of ESET Nod32 for Mac and installed a newer version of the beta. I emptied the trash and tried to smart update again. No I get the error. I suspect the files are related to NOD32, though I can't be sure. Hope this helps.

I'm pretty sure NOD32 created the file. Several others were created in /tmp at the same time, including kacta.txt and esets.sock and esetsx.sock. They have some custom permission and I can't delete them, even using sudo in terminal.

I uninstalled the NOD32 antivirus program, and the problem files were removed. Ran the copy procedure again, this time without incident. Hope this info helps!

Jeff

Hi Jeff,

that is very helpful, thanks. I just posted an article about antivirus software issues last week, this will be a good reference for that article.

Mike

All issues reported here should be resolved in 3.3.4-b1, available today. If you would like to verify that the update resolves these issues, choose "Update CCC" from the Carbon Copy Cloner menu, check the "Inform me of beta updates" box, then click on the "Check for updates now" button and follow the instructions provided to apply the update. Let me know if that doesn't resolve things.

I am marking this discussion as "Resolved". If the matter is not resolved, please don't hesitate to reply to reopen the discussion.

Thanks,
Mike