Home folder access problem

Hi,
I have a problem accessing my home folder in the sidebar of Finder and in general starting the Finder from the dock. If I click on the Finder icon in the dock nothing happens, if I click on my home folder in the Finder sidebar a popup message is asking me with which application I want to open my home folder!?. Obviously Finder forgot how to open my home folder.
Finder still opens a normal Finder window if I double click on an existing folder on the desktop but not via Finder menu bar or right mouse menu on the Finder icon. I can still access my home folder via terminal "/Volumes/myname" though. And in the Finder I can still see the content if I go to Macintosh HD -> Users -> myname and then do Show Package Content. It is just the link in the PLACES section of the Finder sidebar that doesn't work.
I have also tried dragging my home folder out of the Finder sidebar and putting it back via Preferences -> Sidebar -> PLACES -> select Home and by dragging it there from Macintosh HD -> Users -> myname
In Terminal I see that my home folder has read/write/execute rights for my user and none for group and others:
drwx------ myname myname
I have not tried to rename or move my home folder! And I have tried restarting and checking and repairing Disk Permissions via Disk Utility.
The exact error message when trying to open my home folder from the sidebar now is: "The document "myhomefoldername" could not be opened!" But this only came after I picked an arbitrary application to open my home folder with since he kept on asking me which application to use. An obvious choice of course would have been to use Finder but that one doesn't show up as an application.
Any more ideas on how to fix this situation?
Thanks a lot!
Matthias
Message was edited by: therealvinz

therealvinz wrote:
Hi,
I have a problem accessing my home folder in the sidebar of Finder and in general starting the Finder from the dock. If I click on the Finder icon in the dock nothing happens, if I click on my home folder in the Finder sidebar a popup message is asking me with which application I want to open my home folder!?. Obviously Finder forgot how to open my home folder.
Finder still opens a normal Finder window if I double click on an existing folder on the desktop but not via Finder menu bar or right mouse menu on the Finder icon. I can still access my home folder via terminal "/Volumes/myname"
that's not the right place for your home folder.
though. And in the Finder I can still see the content if I go to Macintosh HD -> Users -> myname and then do Show Package Content.
really?! maybe that's the problem. it seems that your home folder has been converted to a package somehow. it should be a regular directory not a package. you can use setFile terminal command to remove the package bit from it so that it becomes a normal folder. You'll have to install Developer tools (they are on the leopard install DVD) to get setFile. alternatively, you can pull just the setFile command from the install DVd using [Pacifist|http://www.charlessoft.com>. Once you've got setFile installed run this in terminal
setfile -a -b ~

Similar Messages

Shared folder access problem in j2ee application

Hi,
We are using SAP Netweaver 04s JAVA system.
In our j2ee application we are trying to access shared resource(file), but ejb is giving exception. Our code is as follows:
File srcDir = new File("\machine_namefolder");
if(!srcDir.exists())
{throw new Exception("directory does not exist", srcSys);
It gives expection "FileNotFoundException".
The same j2ee application is working fine when deployed on IBM Websphere.
We trired to access same shared path from windows, it is also working.
Please help us. Thanks in advance.
--sagar

Hi,
Please follow Shared Folder acess problem in J2ee application.
-Vladimir

Home folder permissions problem in Lion

Well, there are 2 problems really, but I'm hoping that curing one will cure the other. I have an iMac and a MacBook Pro both running Lion. I can connect to the iMac from the MBP using afp but trying to connect to the MBP I get a "connection refused' warning which seems to be affecting a number of Lion users. My home folder is not shared so I can't solve the problem by unsharing it as some have. (If I turn off afp, smb works ok.)
What I have noticed though is that the permissions for the public folder and home folder on the MBP seem to be incorrect. They are:
username - read & write
unknown user - read only
everyone - read only
whereas on the iMac they are:
username - read & write
staff- read only
everyone - read only
How do I correct the permissions for my MacBook Pro's home folder? I'm hoping that this will also solve the file sharing issues.

Too bad this solution is hard to find... Let's mark it as solved so others can find it easily.
Glad it saved you a clean install!

XMII home page Accessing problem

Hi,
We tried to access the xmii server from another network outside of our LAN. we are able to access the XMII login URL. but after giving username and password it is going into goservice.jsp and showing error "Unable to load home page, java.lang.NullPointerException " and stopped.
How to solve this problem?
Regards,
Senthil

Hi,
This is some additional information to my query.
We went through the log. It is showing error in log as "Unable to read XSL document [http://<virtual IP address:port>/XMII/Stylesheets/IllumRowsetHTML.xsl]#".
But if we give this xsl URL (http://<virtual IP address:port>/XMII/Stylesheets/IllumRowsetHTML.xsl) directly in browser outside LAN network, it is showing the xsl file.
Regards,
Senthil
Edited by: senthil kumar on Nov 17, 2009 1:36 PM

Home folder Creation problem solved (for me anyway)

I have had an issue where when I asked my server to create home folders it was not making them. I also tried all the usual things like removing the share, sudo createhomedir -a and even ran the combo updater on the server again all to no avail. Upon looking at another server that was creating home folders I found that when I selected Network in the Finder SideBar there was an alias of Servers. This alias on the working server showed an alias of the server HD and in turn showed the contents of that drive. On the server that was not working the Servers alias in Network was an alias of a white document and showed nothing.
What i had to do to fix this was to open Terminal and su to root, cd /automount, rm Servers and restart. When this was done going to Network in the sidebar and selecting Servers then showed an alias of my server HD which in turn showed the contents of the drive. I then used WGM to remove the network mount for home dir's and stopped sharing the folder. I then re-enabled the share and then set the home dir mount again. After this it succesfully created the home folders in that dir when asked to and I was then able to log in and manage the account.
I hope this is of some use to others...
regards Gary.
PowerBook G4 1.67 Mac OS X (10.4.7)

great stuff, last time this happened to me i just backed up the directory and formated reinstalled restored and it worked, took 3 hours...this would take a lot less time... post this in mac os x hints to eh..
Cheers
Rob

AFP Home Folder Issue?

Well I set-up a Home Folder on the Open Directory Server and it created the Folder but when I go to login from a machine it gives me an error of: The "Home" folder for user "Jesse" cannot be found in its usual place.. So I logged into it from an admin account on the same box to see if I could just connect and see the files and it came up just fine. Any ideas or if you need more info let me know. Thanks everyone.
Powerbook G4 Mac OS X (10.4.7)

What is the OS of the client machine, and, more importantly, what does you Directory Access settings on the client look like?
You could trash /Library/Preferences/Directory Access and edu.mit.kerberos on the client and re-bind for starters. In my experience, deleting the Directory Access information does not fix network home folder login problems nearly as well.

"The home folder...isn't located in the usual place or can't be accessed" after 10.9 AD bind.

Okay a little backstory here because I'm trying to eliminate or identify what I feel might be a bug in OS X Mountain Lion and Mavericks. Just FYI, I'm not our institution's AD admin, I just have rights to bind and query for this and that, but I can't make changes or really investigate our AD domain server/s:
So we're an educational institution with lots of adjuncts that come and go each year. Recently in August, I had about 5 cases where these adjuncts couldn't log in because of a cryptic "login failed" error. I have my macs setup to create mobile accounts without confirmation. I don't want ANY syncing going on just local user accounts created, but something in the profile creation process demands access to their network home folder. Well these 5 users were brand spanking new and somehow didn't have permissions to their own network home folders that everyone else hasn't had a problem with before. I had our admins fix the permissions, and they were able to login thereafter. Our admins are still looking for what might have caused this, but still don't know....
Recently I've been testing the same AD bind script I've always used on Mavericks. It's a simple bash "dsconfigad" customized for our institution. It seems to work successfully but on the login screen I get no usual "arrow" that allows me to back out and click "Other" and login to AD. I reseated the Ethernet cord and checked the AD configuration in Directory Utility - it was all set correctly as per the script parameters. When I clicked OK and exited out to the login screen, the Other option was working correctly. I was able to login with my own credentials just fine.
I needed to tweak my image a little so I wiped and reloaded the machine with the new image (nothing relevant to binding and users was changed). Got the same "no arrow" issue and tried the same steps, which again worked after some monkeying around. I tried to login with my credentials - failed. Now I get "The home folder for user 'my username' isn't located in the usual place or can't be located." I went into a local user admin account and tried to add my home folder manually, nogo. I logged onto a windows machine and tried to mount the same home folder in Windows - access denied - this is the SAME type of thing that ended up happening to my adjuncts. I don't know if they are related but it's certainly a strange coincidence.
How could testing AD binds change my home folder permissions, or possibly even corrupt the folder altogether? The network share/home folder that our macs smb communicate with as per the bind settings are on a windows server (to the best of my knowledge). My guess previously with the adjuncts error is that despite the fact that I don't need or want the profiles created to sync, the default options turns this on for mobile accounts even though it doesn't select any actual folders for syncing, but because it still tries some sort of "handshake" or something initially, first logins fail without network home folder permissions. Now it seems like something in the initial profile creation process might actually be corrupting the network home folder or changing its permissions.
I would post the bind script but I'm not sure it's relevant, as another mac admin in a different area ran into the same error with one of his new users and he bound manually, not with a script.
I'm kind of new to this sysadmin stuff, so does anyone have any ideas or suggestions to track down the cause of this and possibly fix it? The network share admin can fix my permissions, but if I could break it when it was working once, I foresee this happening again.

Here's the script I used previously that is not connecting to AD "completely" that causes the errors mentioned (I'm replacing institution info with "xxx"):
echo -n "This computer needs to be renamed and bound to Active Directory. Please enter the XXX Inventory Number from the affixed XXX label on the machine: "
    read userinput
    echo -n "Enter the XXXAdmin password (you will still be asked to enter this for system configuration changes): "
    read -s xxxpassword
    scutil --set ComputerName $userinput
    scutil --set LocalHostName $userinput
# Active Directory Bind Script For OS X Client
    # Modified by Wade Wei according to previous popular bind script
    # Adapted for xxx by xxx
    echo "Binding to Active Directory…"
    echo -n "Enter AD admin username: "
    read adusername
    echo -n "Enter AD admin password (please wait after password submitted, do not press any keys): "
    read -s adpassword
    #Basic parameters
    computerid=$userinput
    fqdn="ad.xxx.edu"
    username=$adusername
    password=$adpassword
    #Advanced parameters
    alldomains="enable"
    localhome="enable"
    protocol="smb"
    mobile="enable"
    mobileconfirm="disable"
    useuncpath="enable"
    user_shell="/bin/bash"
    admingroups="domain admins,enterprise admins,xxx,xxx"
    namespace="domain"
    packetsign="require"
    packetencrypt="require"
    localuser="XXXAdmin"
    localpassword=$xxxpassword
    # Bind to AD
    echo "Binding to AD - do not interrupt…"
    dsconfigad -add $fqdn -username $username -password "$password" -computer $computerid -force -packetencrypt $packetencrypt -localuser $localuser -localpassword $localpassword
    sleep 5
    #Configure advanced options
    echo "Configuring AD for Mac OS X…"
    dsconfigad -localuser $localuser -localpassword $localpassword -alldomains $alldomains -localhome $localhome -groups "$admingroups" -mobile $mobile -mobileconfirm $mobileconfirm -namespace $namespace -packetsign $packetsign -useuncpath $useuncpath -protocol $protocol -shell $user_shell -nopreferred
Can anyone tell me if I need to update the script for Mavericks, and how? Or should this be working and the bug is in Mavericks itself?

Home Folder greyed out/Can't access home folder

I'm completely unable to view my home folder after a fresh install of mountain lion. I copied my user folder over and created a new user based on that folder. As you can see it will only show me the large home icon instead of my column view. It is able to be accessed from other views however... it's not consistent. There seems to be a huge finder issue with this user. I've also made a test user and everything over there works fine so it's only on this side.
Here is what it looks like from the other user:
Still greyed out... I've tried everything from help from genii at the store to friends who know UNIX well, I've reset ACLs and repaired permissions ot no avail. If you have any ideas for me please lemme know and I'll try them.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
*Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, you can’t boot in safe mode.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem(s)?
After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Target Mode, can't access my home folder

I bought a new Mac Pro and am in the process of transferring apps and data from my old iMac G5...got all my applications transferred over ok via the Target mode but then....
Ran into a problem when I tried to transfer my iPhoto Library over to new Mac Pro...
When I put the iMac into target mode and then open the disk image (now on my Mac Pro), I am unable to access much of my home folder. As I said above, my applications folder is accessible, but the other folders have a RED minus sign on them.
How do I fix this? Thanks-

You went about things a bit backwards. You should have use the Migration Assistant. See http://discussions.apple.com/thread.jspa?messageID=1872713 for details. If you just got the new machine, I'd boot it with the restore disk, erase the new machine, restore the software, hook up the iMac, and use the Migration Assistant to do the transfer.

Keep loosing access to my home folder

Hi,
Could you please help to diagnose my MBP? I've been struggling to do it for a couple of weeks now
The MacBook malfunction in two different ways:
A. Keep loosing access to my home folder (usually when I'm browsing in Safari):
1. The system stops to being responsive for 15-30 seconds, and then
2. In Finder -> Places my home folder (wk) alias is missing, and I get the error "The alias "wk" can't be opened because the original item can't be found"
3. In /Users the permissions to the folder are being changed (I haven't noted what exactly are the permissions), and I get the error "The folder "wk" can't be opened because you don't have permission to see it's contents"
4. kernel.log shows I/O errors for disk0s2
5. Disk utility verification shows the filesystems is in a perfect state, but the regular problems with /System/Library/java/* permissions won't be fixed
6. System reboot fixes the issue
B. Kernel panic (the very first I've seen happened four weeks ago, and then three followed during the previous week)
1. I got the usual grey screen, and reboot
2. kernel.log shows Page Fault, in all cases with kernel as the "app in focus"
I've taken the following steps to diagnose the problems:
1. Disk Utility verification shows the filesystems is in a perfect state,
2. There're always a problem with permissions in /System/Library/java/... (always fixable)
3. Run extended AHT in a loop (no problems found) - didn't help
4. Reinstalled the OS - didn't help with problem A, although problem B hasn't happened ever since (a coincidence?)
5. Put back original RAM dice - didn't help with problem A
6. Zeroed the HDD and installed from a scratch - didn't help with problem A
7. Exchanged HDD to a brand new one (was planning to do that either way) and restored the OS from point 6. - didn't help with problem A
Hardware Overview:
Model Name:     MacBook Pro
Model Identifier:     MacBookPro5,5
Processor Name:     Intel Core 2 Duo
Processor Speed:     2.26 GHz
Number Of Processors:     1
Total Number Of Cores:     2
L2 Cache:     3 MB
Memory:     4 GB
Bus Speed:     1.07 GHz
Boot ROM Version:    MBP55.00AC.B03
SMC Version (system):     1.47f2
*** 10.6.7 with FileVault ON, no Apple Protection Plan ***

another kernel panic:
Description:     Panic (system crashes) log
Size:     7 KB
Last Modified:     11-06-23 2:58 PM
Location: [...]
Recent Contents:
Interval Since Last Panic Report: 269443 sec
Panics Since Last Report:          1
Anonymous UUID:                    [...]
Thu Jun 23 14:57:30 2011 panic(cpu 1 caller 0xffffff80002cffca): Kernel trap at 0xffffff80003094f9, type 14=page fault,
registers: [...]
Error code: 0x0000000000000002
BSD process name corresponding to current thread: syslogd
WK-MBP:~ wk$ egrep "error|jnl" /private/var/log/kernel.log
Jun 21 07:10:59 WK-MBP kernel[0]: disk0s2: I/O error.
Jun 21 07:13:33 WK-MBP kernel[0]: disk0s2: I/O error.
Jun 21 07:13:33 WK-MBP kernel[0]: disk0s2: I/O error.
Jun 21 07:21:42 WK-MBP kernel[0]: disk0s2: I/O error.
Jun 21 07:22:13 WK-MBP kernel[0]: disk0s2: I/O error.
Jun 21 07:22:43 WK-MBP kernel[0]: disk0s2: I/O error.
Jun 22 08:59:44 WK-MBP kernel[0]: disk0s2: I/O error.
Jun 23 07:39:53 WK-MBP kernel[0]: jnl: disk2s2: replay_journal: from: 59983872 to: 61315072 (joffset 0x1d1a000)
Jun 23 07:39:53 WK-MBP kernel[0]: jnl: disk2s2: journal replay done.
Jun 23 14:57:26 localhost kernel[0]: jnl: unknown-dev: replay_journal: from: 33260544 to: 37344256 (joffset 0xe8e000)
Jun 23 14:57:26 localhost kernel[0]: jnl: unknown-dev: journal replay done.
Jun 23 14:57:47 WK-MBP kernel[0]: jnl: disk1s2: replay_journal: from: 40641024 to: 41664512 (joffset 0x1d1a000)
Jun 23 14:57:48 WK-MBP kernel[0]: jnl: disk1s2: journal replay done.
Jun 23 15:16:49 WK-MBP kernel[0]: disk0s2: I/O error.
Jun 23 15:16:49 WK-MBP kernel[0]: jnl: unknown-dev: do_jnl_io: strategy err 0x5
Jun 23 15:16:49 WK-MBP kernel[0]: jnl: unknown-dev: end_transaction: only wrote 0 of 110592 bytes to the journal!
at 07:40 I lost access to my home folder (permissions), at 14:58 the system crashed (kernel panic), at 15:16 lost access to home folder again:
WK-MBP:~ wk$ ls -l /Users
total 0
drwxrwxrwt 4 root wheel 136 16 Jun 07:58 Shared
drwx--x--x 3 root admin 102 23 Jun 14:57 wk

Users accessing admin home folder

I have two drives in my MBP. A solid state boot drive and the internal drive for all other files including the home folders. There are three users and all of their home folders reside on the internal drive, not the boot drive. My problem is that the non-admin users somehow have access to the admin home folder and all its files, while the admin cannot access the others users' home folders. In other words, the permissions are all wrong. However, I have checked the permissions and my (the admin) home folder has the same permissions as the users' home folder. Hopefully that makes sense.
I have searched for a fix and repairing the home folder permissions through the recovery partition reset password utility seemed like it could be the solution but when I tried that, it did not allow me to access the true home folders on the non-boot drive, it only allowed me to repair the permissions on the boot drive home folders, which is not where the true home folders are located.
I'm on OSX 10.9.2.
Thanks for any and all your help. Hopefully my issue is clear and someone out there knows a fix!

You are correct, it is not supported though a program or user can do it with root access. That is very strange, I would take it to an Apple Authorized Service Provider or get somebody who can actually look at it.

How I Solved My "Can't Import My Home Folder" Problem While Staying Sane

This may be a well-known work-around for Time Machine and Migration Assistant, but I didn't find any reference to it in searching in Google (which included some threads here), so I thought I'd post it in case anyone else is experiencing similar problems.
I was having problems with some program install permissions and tried fixing them in more traditional ways without success, so I decided it was a good day for an Erase and Reinstall of Leopard.
I didn't want to copy my entire Home directory's contents and I have 6 HDs (four internal and two external) totaling about 1.5TBs. So, to prepare for the reinstall, rather than use Backup, I copied all important files to my other drives and then I copied my Home directory to another drive in the machine. Satisfied that everything was backed-up, I reinstalled Leopard using the Erase and Install option and soon had a good system, fully updated.
However, when I went to copy the Home Directory I kept getting errors saying that I can't alter these files and folders, even when I drilled down into the subdirectories. I didn't try copying individual files, but then I had no desire to do so given the amount of time that would take.
I looked around but could find no good solution. However, I did come up with a workaround and this is what I did:
First, I moved my Home Folder designation to the one on the backup hard drive by:
1) Go to System Preferences
2) Click the lock to make changes and enter your user password
3) Right-Click on your User Account and select "Advanced Options"
4) From the drop-down window, to the right of the "Home Directory" box select "Choose..."
5) Navigate to the backup User Account home folder and select it and click "OK
6) Relock the Accounts pane
7) Now you can delete the "old" Home Folder under your OS drive: Users/user account
8) Now just copy the backed-up Home Folder (that is now your real Home Folder) to the OS drive: Users/user account
9) Repeat steps2, 3 and 4, this time selecting your now moved Home Folder in the OS drive: Users/user account
10) Now you can delete the backup or keep it AS a backup.
I know this is a kludgey, wrong way to do backup and that Backup is the way to go, but for those out there who don't do it or have some problem restoring it, this is a possible way around so that you don't end up having to restore everything by hand.
This workaround may have already been discussed and well-known, but I had not seen it and am posting this in the hopes that it will help someone in trouble.
JoeL

joeldm,
There is a "proper" way to do what you have done. First, one must create an account within the new installation using the exact same username and short name that was used in the old installation. Then, one enables the "root" account and logs in as root.
Within the root account, the local HOME folder that was created for the user is placed in the trash, then replaced with a (same-named) copy from the backup. THat HOME folder copy will be onwed by root, so this command must be run in Terminal:
<pre style="overflow:auto; font-family: 'Monaco'; font-size: 10px">chown -R username:staff /Users/username</pre>
In the above command, all instances of "username" are replaced with the user's short name. For example, if the user's name is "fred," the command would be typed exactly like this:
<pre style="overflow:auto; font-family: 'Monaco'; font-size: 10px">chown -R fred:staff /Users/fred</pre>
The command is executed when <RETURN> is pressed. NOTE: The specific command listed above applies only to 10.5.
One would then log out of the "root" account, and into the account in question. If all seems well, one would log back into the root account, empty the trash, then log out of and disable the root account.
Alternatively, if there is a Time Machine backup that can be used, the Time Machine interface can be used in the root account to replace the trashed HOME folder, instead of copying manually in the Finder. This would generally be a better method to use, if possible.
Scott
EDIT: If one wishes to replace/restore only certain portions of a HOME folder, this is possible. The same methods would apply to only limited segments within a HOME folder. -s

Problem syncing Mobile account home folder

I'm trying to get mobile accounts working correctly so that i can support users (including myself) having laptops and iMacs with files all in sync. My initial tests seem to go well, but when I started moving the first user account over (mine) I noticed a number of errors appear. Here is an example of what I'm currently working on (I've trimmed it down to just before the error message):
<hr>
Client ~/Library/Logs/FileSyncAgent/FileSyncAgent-verbose.log:
<Logout> 1:: \[10/06/16 15:22:57.357] <OK> network: MODIFY "Library/Preferences/com.apple.recentitems.plist" {(Priority=1, EXECUTING)}
<Logout> 1:: \[10/06/16 15:22:57.387] <OK> network: MODIFY "Library/Preferences/com.apple.systemuiserver.plist" {(Priority=1, EXECUTING)}
<Logout> 1:: \[10/06/16 15:22:57.417] <OK> network: MODIFY "Library/Preferences/com.apple.Terminal.plist" {(Priority=1, EXECUTING)}
<Logout> 0:: \[10/06/16 15:22:57.435] EXCEPTION: \[data writeToFile:'/Volumes/Users/synctest/.FileSync/PHD-R-wO-0oQq9MqC-synctest.FileS yncHistory' options:0 error:&error] (Cocoa error 512) <-\[SStoreFileOperator_FS writeFileData:] (StoreFileOperator-FS.m:1091): "(Error Domain=NSCocoaErrorDomain Code=512 UserInfo=0x102fdd8c0 "The file “PHD-R-wO-0oQq9MqC-synctest.FileSyncHistory” couldn’t be saved in the folder “.FileSync”." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=35 "The operation couldn’t be completed. Resource temporarily unavailable"))">
<Logout> 0:: \[10/06/16 15:22:57.435] USERINFO: {
<Logout> 0:: \[10/06/16 15:22:57.435] NSFilePath = "/Volumes/Users/synctest/.FileSync/PHD-R-wO-0oQq9MqC-synctest.FileSyncHistory";
<Logout> 0:: \[10/06/16 15:22:57.435] NSUnderlyingError = "Error Domain=NSPOSIXErrorDomain Code=35 \"The operation couldn\U2019t be completed. Resource temporarily unavailable\"";
<Logout> 0:: \[10/06/16 15:22:57.435] }
<Logout> 0:: \[10/06/16 15:22:57.435] BACKTRACE: {
<Logout> 0:: \[10/06/16 15:22:57.435] ? | 0x1000bc73c
<Logout> 0:: \[10/06/16 15:22:57.435] ? | 0x1000b9eec
<Logout> 0:: \[10/06/16 15:22:57.435] ? | 0x100066a00
<Logout> 0:: \[10/06/16 15:22:57.435] ? | 0x100065fe6
<Logout> 0:: \[10/06/16 15:22:57.435] ? | 0x1000c8f1a
<Logout> 0:: \[10/06/16 15:22:57.435] ? | 0x7fff800cbe8d
<Logout> 0:: \[10/06/16 15:22:57.435] ? | 0x7fff820a3456
<Logout> 0:: \[10/06/16 15:22:57.435] ? | 0x7fff820a3309
<Logout> 0:: \[10/06/16 15:22:57.435] }
<Logout> 1:: \[10/06/16 15:22:57.544] -\[SStore(protected) cleanupTree]: PHD-L-iI.arrVC0G4-synctest: required 0.0 seconds to execute
<Logout> 1:: \[10/06/16 15:22:57.557] Store "PHD-L-iI.arrVC0G4-synctest" finished syncing with root version PHD-L-iI.arrVC0G4-synctest1276714848PHD-R-wO-0oQq9MqC-synctest1276714849\[]
<Logout> 1:: \[10/06/16 15:22:57.558] -\[SStore_FS deleteStateTreeTurdFile] (Store-FS.m:481): unlink('/Users/synctest/.FileSync/store.filesyncstatetree.statetree_dirty')
<Logout> 1:: \[10/06/16 15:22:57.737] Store "PHD-R-wO-0oQq9MqC-synctest" finished syncing with root version PHD-L-iI.arrVC0G4-synctest1276714848PHD-R-wO-0oQq9MqC-synctest1276714849\[]
<Logout> 1:: \[10/06/16 15:22:59.041] Compress/upload of "/Volumes/Users/synctest/.FileSync/Store-FS-PHD-network-home.filesyncstatetree. bz2" took 1.30 seconds
<Logout> 1:: \[10/06/16 15:22:59.041] -\[SStore_FS deleteStateTreeTurdFile] (Store-FS.m:481): unlink('/Volumes/Users/synctest/.FileSync/Store-FS-PHD-network-home.filesyncsta tetree.bz2.statetree_dirty')
<Logout> 1:: \[10/06/16 15:22:59.043] 1-pass sync of "HomeSync_Mirror" took 4.75 seconds
<Logout> 0:: \[10/06/16 15:22:59.374] Finished sync of "HomeSync_Mirror".
1:: \[10/06/16 15:22:59.914] -\[MainObj shutdownAgent]
0:: \[10/06/16 15:22:59.949] EXCEPTION: User Cancelled <_incomingIPC (ipc.m:210): "'((userCanceledErr))' error -128">
0:: \[10/06/16 15:22:59.949] USERINFO: {
0:: \[10/06/16 15:22:59.949] NSLocalizedDescription = "User Cancelled";
0:: \[10/06/16 15:22:59.949] }
0:: \[10/06/16 15:22:59.949] BACKTRACE: {
0:: \[10/06/16 15:22:59.949] ? | 0x10000e2a8
0:: \[10/06/16 15:22:59.949] ? | 0x7fff82d74af1
0:: \[10/06/16 15:22:59.949] ? | 0x7fff82d0f171
0:: \[10/06/16 15:22:59.949] ? | 0x7fff82d0d84f
0:: \[10/06/16 15:22:59.949] ? | 0x1000049d9
0:: \[10/06/16 15:22:59.949] ? | 0x7fff820a3456
0:: \[10/06/16 15:22:59.949] ? | 0x7fff820a3309
0:: \[10/06/16 15:22:59.949] }
1:: \[10/06/16 15:22:59.949] _incomingIPC: caught exception _incomingIPC (ipc.m:210): "'((userCanceledErr))' error -128"
0:: \[10/06/16 15:23:00.669] Bye (PID:2246)
<hr>
Server ~/Library/Logs/FileSync-server/FileSync-server-verbose.log:
1:: \[10/06/16 15:22:54.616] PHD-R-wO-0oQq9MqC-synctest Scanning flagged directory "Library/"
1:: \[10/06/16 15:22:54.625] PHD-R-wO-0oQq9MqC-synctest Scanning flagged directory "Library/Preferences/"
1:: \[10/06/16 15:22:54.644] PHD-R-wO-0oQq9MqC-synctest Scanning flagged directory "Library/Preferences/ByHost/"
1:: \[10/06/16 15:22:54.665] Store "PHD-R-wO-0oQq9MqC-synctest" finished prepareForSync with root version PHD-L-iI.arrVC0G4-synctest1276714845PHD-R-wO-0oQq9MqC-synctest1276714849\[]
1:: \[10/06/16 15:22:54.671] -\[SStore_FS deleteStateTreeTurdFile] (Store-FS.m:481): unlink('/Users/synctest/.FileSync/Store-FS-PHD-network-home.filesyncstatetree.s tatetree_dirty')
1:: \[10/06/16 15:22:56.113] -\[SPeer_FS zip] (Peer-FS.m:361): unlink('/Users/synctest/.FileSync/Store-FS-PHD-network-home.filesyncstatetree')
0:: \[10/06/16 15:22:59.705] EXCEPTION: Unknown error 2002 <-\[SNetworkReachabilityMonitor init] (NetworkReachabilityMonitor.m:72): "(Error Domain=com.apple.SystemConfiguration Code=2002 UserInfo=0x100243d20 "The operation couldn<E2><80><99>t be completed. (com.apple.SystemConfiguration error 2002 - Configuration daemon not (no longer) available)")">
0:: \[10/06/16 15:22:59.705] USERINFO: {
0:: \[10/06/16 15:22:59.705] NSDescription = "Configuration daemon not (no longer) available";
0:: \[10/06/16 15:22:59.705] }
0:: \[10/06/16 15:22:59.705] BACKTRACE: {
0:: \[10/06/16 15:22:59.705] ?<C2><A0>|<C2><A0>0x100014831
0:: \[10/06/16 15:22:59.705] ?<C2><A0>|<C2><A0>0x100014688
0:: \[10/06/16 15:22:59.705] ?<C2><A0>|<C2><A0>0x7fff82ffb535
0:: \[10/06/16 15:22:59.705] ?<C2><A0>|<C2><A0>0x7fff8300963e
0:: \[10/06/16 15:22:59.705] ?<C2><A0>|<C2><A0>0x7fff83001eaa
0:: \[10/06/16 15:22:59.705] ?<C2><A0>|<C2><A0>0x7fff82ffa1ba
0:: \[10/06/16 15:22:59.705] ?<C2><A0>|<C2><A0>0x1000036c3
0:: \[10/06/16 15:22:59.705] ?<C2><A0>|<C2><A0>0x10007f4e0
0:: \[10/06/16 15:22:59.705] ?<C2><A0>|<C2><A0>0x2
0:: \[10/06/16 15:22:59.705] }
0:: \[10/06/16 15:22:59.705] Bye (PID:9460)
<hr>
Now I've not done much with OS X programming, but I've done quite a bit of Unix systems work. The client appears to be getting an EAGAIN error (essentially that the syscall didn't complete, but not that it failed). Ideally, it should try again, and perhaps there is something I can set that will have it do a couple of retry attempts before giving up?
However, the error on the server side is the likely culprit. I don't know what the error message regarding com.apple.SystemConfiguration means, but my googling for hints implies that it is some sort of error connecting over the network. To try and debug that, I had both machines connected to the same switch with firewalls turned off and the error continues. The previous lines imply that it is trying to delete a file that it created from the local disk. What bothers me about that is that in the WGM I set the home directory to be "afp://servername/Users" and it shows that it should be either "afp://servername/Users/synctest" or "/Network/Servers/servername/Users/synctest" but the server is accessing the home folder directly, so why an issue with network reachability?
Can anyone offer any hints as to what I should be looking for? I had hoped that PHDs would solve the whole multiple computer issue, but they don't seem to be working reliably for me. Since I get this issue consistently I'm guessing that there is something misconfigured on my end.

Shawn,
I've done the deletion of those folders a number of times, with no luck.
The most recent attempt to get this to work was:
1. Delete ~/.FileSync and ~/Library/FileSync from the server machine.
2. With a brand-new install of OS X on a laptop, create a local administrator, join the server, then login as the user account that wants a mobile account
3. Look at logs
I still get an exception on the server
0:: \[10/07/31 13:39:47.791\] EXCEPTION: Unknown error 2002 <-\[SNetworkReachabilityMonitor init\] (NetworkReachabilityMonitor.m:72): "(Error Domain=com.apple.SystemConfiguration Code=2002 UserInfo=0x10027adc0 "The operation couldn<E2><80><99>t be completed. (com.apple.SystemConfiguration error 2002 - Configuration daemon not (no longer) available)")">
0:: \[10/07/31 13:39:47.791\] USERINFO: {
0:: \[10/07/31 13:39:47.791\] NSDescription = "Configuration daemon not (no longer) available";
0:: \[10/07/31 13:39:47.791\] }
0:: \[10/07/31 13:39:47.791\] BACKTRACE: {
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x100014831
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x100014688
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x7fff82ffb535
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x7fff8300963e
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x7fff83001eaa
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x7fff82ffa1ba
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x1000036c3
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x10007f4e0
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x2
0:: \[10/07/31 13:39:47.791\] }
0:: \[10/07/31 13:39:47.792\] Bye (PID:38660)
as well as the corresponding error on the client.
I'm quite frustrated with the whole situation at this point. I'm sure some folks have gotten it to work, but since it has exceptions like this silently, it slowly corrupts the data in an account. I still want to get it to work, but am skeptical that it will.
Message was edited by: Benjamin Kuperman

Hard drive died - multiple problems with backed up home folder

My friend called me when she started having some problems with her home iMac. After we did went through a myriad of troubleshooting items, I determined that her hard drive was failing and suggested she backup her home folder immediately to another drive. She copied her home folder over to her old Mac and took the iMac into the Apple Store for further diagnostics. Sure enough, her hard drive had failed and they replaced it for her.
She reinstalled Leopard and set it up with a new account. We tried using the Migration Assistant to copy her old home folder back over but because she copied it rather than using Time Machine, Migration Assistant doesn't see it as a viable home folder. I'm very comfortable using the Terminal since I support both Macs and Linux in my department so I logged in as root and copied over her folders to the new account. That generally worked but we now have a ton of permissions problems of which Disk Utility doesn't fix. I'd like to start fresh again from her backed up home folder. So my question is if I can't use Migration Assistant to move over her old home folder, how do you make OS X see her old home folder as a viable account? (I hope this makes sense.)
Thanks in advance!

I would suggest the following.
make a new temp admin account and get rid of the new account she made already. log in as the temp user and copy the old home folder from the external to /Users. then go to system preferences->accounts and make a new account with the same short user name as the name of her old home folder. It will say that a home directory by that name already exists and ask if you want to use it. say "yes". this should recreate that user and take care of all permissions issues.

Time Machine Can't Access Home folder

I am using OS X 10.8.3 and my home folder seems to have been deleted without saving (malicious activity by family memeber with somehow gained access to his mother's account that has admin privledges). I've tried restore via Time Machine (TM) which has worked in the past for minor file recovery issues but, I cannot access the "home" folder on the backup (external) drive any longer; I can "see" the home folder, but it is lightly shaded. I also am having trouble rebuilding my iTunes library - I can see most, but not all of my tunes - other cannot be found on either the iMac-HD or the TM Backup. Finally, not all of the iTunes purchased material is accessible via the iCloud download (tunes and app downloads). So I am pretty much dead in the water. I hate bringing up stupid questions but I am not a tech sorrt of guy - I can use a hammer without having to know the physics of inelastic collisions, so my apologies. Any suggestions?

Boot into Recovery (command-R at startup) and select Restore From Time Machine Backup from the OS X Utilities screen. Select the snapshot you want to restore from. All data on the volume will be erased and replaced with data from the snapshot.

Home folder access problem

Similar Messages

Maybe you are looking for