NFS Home Directories not acquiring permissions

Hi there. We have recently upgraded our labs to 10.5.4 from 10.4.11. We mount user home directories via NFS and have for some time without an issue. Now, though, I can create the mount using either fstab or Directory Services and it works, however when a new user logs in who does not have a home directory, the profile gets copied to the NFS server but does not acquire the correct permissions. THe home directory is owned by root and not the logged in user. Have any of you seen this? Are there any solutions or something that I might have done wrong? Any help would be appreciated and if this is the wrong section, point me to where I can post and I'll repost there.
Thanks
Jason

The NFS mounts are being shared off of a NetApp. We didn't have any issues with this in the past, only with Leopard.

Similar Messages

  • NFS Home Directories Yosemite

    Has anyone successfully used NFS home directories for network logins?
    This used to work in 10.6.8 Server but I am having a hard time setting it up in Yosemite.  I need to enable fast user switching with multiple logins to our server which appears to be impossible using AFP.
    I'd appreciate any tips on how to accomplish this.  All clients and server are running clean Yosemite installs.

    Apple stopped officially supporting NFS based home directories when Lion and Server.app was released. I have not done extensive testing but I certainly find two sessions using fast user switching and AFP works with Mavericks clients.
    As far as I can see if a Snow Leopard server was connected to a Mavericks or Yosemite OD server it would still be possible for the Snow Leopard server to register an NFS home directory share in to Open Directory. This suggests that it might be possible to do the same even with a Mavericks or Yosemite server but that one would have to do all the work by hand in the command line. The logic for this conclusion is that Mavericks and Yosemite still include NFS even if they do not provide a GUI means to configure it and OD itself would appear to still be able to store records relating to NFS locations.
    I have used NFS home directories in the past and found it solved a number of issues including -
    Completely getting round Adobe's long time issues with network home directories
    The same for some other third-party applications
    Allowed 20+ users all on the same server to be logged in to their individual home directories in a Mac Terminal Server setup
    This was all back in the days of using Snow Leopard Server.
    I get the impression Apple secretly added the ability to use Fast User Switching for network logins with Lion or later to compensate for removing NFS support. This may have been at the behest of the developers of the two Mac Terminal Server products.

  • NFS for portable home directories not working

    I just recently tried to move our PHD's over to NFS instead of AFP to allow for fast user switching and some other reasons.
    However it doesn't work at all... The automount seems to work fine, as I can browse to /Network/Servers/servername/Users/ fine, but when the user tries to sync, a dialog pops up:
    The sync could not complete because your network home at "nfs://servername/Users" is currently unavailable.
    Try again later when it is available.
    and then in the console it shows:
    com.apple.SystemUIServer.agent[14236] mount_nfs: /Volumes/Users: Operation not permitted
    HomeSync[14369] HomeSync.syncNow: Unable to mount server URL at 'nfs://servername/Users', status = 65.
    com.apple.SystemUIServer.agent[14236] HomeSync[14369:903] HomeSync.syncNow: Unable to mount server URL at 'nfs://servername/Users', status = 65.
    It seems like its trying to mount it at /Volumes/Users, but it can't (because a normal user can't mount nfs volumes?(..as far as i know))...and furthermore I don't know why it needs to mount it at /Volumes/Users when it's already automounted at /Network/Servers/servername/Users

    I just managed to get my first sync to work.
    My server exports /opt/home/<user> but not /opt/home since each user has a separate lvm volume. What worked was the following:
    dscl . -delete /Users/<user> dsAttrTypeStandard:OriginalHomeDirectory
    dscl . -append /Users/<user> dsAttrTypeStandard:OriginalHomeDirectory "<homedir><url>nfs://find/opt/home/<user></url><path></path></homedir>"
    This is similar to what I saw on http://managingosx.wordpress.com/2009/02/19/leopard-mobileaccounts-and-nfs-homes / except putting the users name (in place of <user> as part of the url instead of part of the path.
    The value for dsAttrTypeStandard:OriginalHomeDirectory was formerly /Network/Servers/<server>/opt/home/<user> which is a perfectly good directory, but not a url. I don't know why it wouldn't use the directory and manufactured a url instead.
    By changing the value back to default and making my server export /opt/home, I'm still able to sync. Naturally I like this solution much better.
    Doesn't seem like this solution will help you much if a given user can sync on some machines and not others, unless maybe you have different export rules to different machines in your network.

  • Home Directories not mounting

    I'm setting up an OS X network for the first time.
    I've got Open Directory based network logins working, but I can't get the home directories to mount over the network. When logging in, a dialog box says that an error occurred and that the home direcotry is mounted via SMB or AFP.
    So I log in as a local user on the client machine to poke around. I don't see the server listed in /Network/Servers, but I can manually do a Connect To Server and put in afp://server.dom.ain/Users/usename and it's fine. This afp:// URL is the same as is specified as the user's home directory.
    I have verified that /Users is exported on the server.
    Do I need to go in to every client and create an automount map for this or is there something else I've forgotten?
    Thanks...
    various   Mac OS X (10.4.9)   10.4.9 server and clients

    The first thing to do when you're having any kind of login problem is to ssh in to the client machine and tail -f /var/log/system.log, then log in to the client machine and watch for clues.
    Step by step:
    1. make sure Remote Login is enabled in the Sharing preferences on the client machine (you can turn it off when you're done if you're paranoid)
    2. on any other mac (or ssh equipped PC) run Terminal (in /Applications/Utilities) and type "ssh username@IP-of-client-machine" obviously replacing "username" and "IP-of-client" with your values, and no quotes of course. Note that "username" needs to be an administrative user. If you haven't logged in with Terminal before, keep in mind that it does not echo back characters when you type in the password. Just type it and press enter. You may have to type "yes" after that to set up the initial trust relationship between the two computers.
    3. Once you're logged in to the client machine, type "tail -f /var/log/system.log" (again, no quotes) and leave it like that. You now have one computer watching another computer's logs in "real time" -- VERY handy when you're troubleshooting a reproducible error.
    4. Go back to the client computer and log in with the problematic account. The other computer will show you everything being logged in system.log. Watch for clues that something is wrong. (something couldn't be found, access denied, anything that doesn't sound too friendly)
    5. Figure out what they mean or copy/paste 'em here! The part that counts is anything that came up on the watching computer's screen from the moment you clicked "Log In" on the client computer to the moment you are at your regular (deficient) desktop, confident it's not gonna do anything else.

  • Home directories not being created

    Hi,
    I am having trouble creating home directories for users on my OSX Server Tiger 10.4.4 running on a mac mini.
    Home directoried do not seem to be created for users on my Open Directory.
    I have configured my server to be an Open Directory master. I have no other Open Directory replicas/Servers running.
    I have set up and configured DNS. It appearts to be working correctly and can resolve my server name to the local IP (10.1.1.X) and give me a fully qualified domain name.
    When accessing users on my OpenDirectory via the work group manager the directory name comease up as "LDAPv3/127.0.0.1" (local host possibly the problem).
    When I click on the "Create Home Now" button and hit save, the home dirs are not created.
    I have checked to make sure that the home directory is shared (owner root) and it seems okay.
    I have read some other threads on topics similar to this, but have had no luck. I would appreciate any help in trying to fix this problem.
    Please let me know if any further information s required.
    Cheers

    I had the same issues you've described in this thread. It turned out that I had named my server "morris", and when the client machines went to mount a user's home folder, they attempted to mount /Network/Servers/morris/Users/whoever. When I went to the Finder, I clicked on the Network icon, then the Servers icon, and listed under there was "morris.domain.com" (where domain.com is your own local domain), but not "morris". So it appeared that there was a name mismatch.
    The fix was easy. I started up Server Admin, clicked the machine I wanted to fix, clicked the Settings tab in the right pane, the Network tab up top, and changed the "Computer Name:" field from "morris" to "morris.domain.com". From that point on, my login problems went away.
    It seems that the Server Admin-set "Computer Name" has to match the machine's FQDN in DNS.

  • Mobile Home Directories not syn'g address book on login/out

    Mobile Home Directories should be sync'g ~/Library on login and logout .. but its not syn'g anything in !/Library .. so address book changes are not being sync'd.
    Any ideas?
    /s

    If you're managing the Portable Homes (home sync) preferences via Workgroup Manager, you need to adjust the items that are excluded on login/logout. Look in Workgroup Manager > Preferences > (select user, computer, computer group, or group) > Click Mobility. Then look in the Rules section for Login & Logout Sync. By default, ~/Library is excluded from background sync, but not from login/logout sync. (Did you exclude it there?)
    Another possibility is that you're excluding ~/Library/Application Support/Sync Services, which contains the Address Book data. That item *is excluded* from login/logout sync by default.
    --Gerrit

  • Problem mounting NFS home directories of NIS users.

    Only on one of client (rest on all clients working fine), the Local directories under /home is getting mounted instead of NFS shared home directories of NIS users. Able to manually mount the NFS shared directories but they also get automatically unmount after some ideal time. Want that the NFS shared directories gets automatically mount when the NIS user gets login as it is happening on all other clients.
    Scenario:_
    NIS user: user1
    NFS Shared home directory: /export/home/user1 (which should get mount as /home/user1 when user1 gets login)
    Local directory: /home/user1 (which is getting mounted when user1 is getting login)
    [CLIENT]/--->ps -ef | grep automount
    root 23369 1 0 Mar 19 ? 1:58 /usr/lib/autofs/automountd
    [CLIENT]/--->cat /etc/auto_master
    /xfn -xfn
    /net -hosts -nosuid,nobrowse
    /- auto_direct -intr
    /- auto_home -intr
    [CLIENT]/--->ypcat -k auto.home
    /home/user1 NFS_SERVER:/export/home/user1
    /home/user2 NFS_SERVER:/export/home/user2
    [NFS_SERVER]-->cat /etc/dfs/dfstab
    share -F nfs -d "user home dir" /export/home
    [NIS_SERVER]--->cat /etc/auto_master
    /xfn -xfn
    /net -hosts -nosuid,nobrowse
    /- auto_direct -intr
    /- auto_home -intr
    Please let me know if any other information is required.

    add this entry as the first non-comment line in /etc/auto_master on the client:
    +auto_master                                                                                                                                                                                       

  • NFS home directories

    It appears that using AFP home directories in ML server means that Fast User Swtiching cannot work anymore.
    And it sounds like the solution is to dump AFP and use NFS.  Anyone have information on how to set that up?

    The NFS mounts are being shared off of a NetApp. We didn't have any issues with this in the past, only with Leopard.

  • Home directories not fully created - AD with OSX server

    Hope this makes sense.
    I'm setting up a network in a school. We've an Xserve running Mac OS X Server 10.6.4. So that students can move seamlessly between our windows network and this, we've extended the AD schema and have the Server bound to AD. Clients are running 10.6.4, bound in a triangle with the Mac Open Directory and AD. So far, so good, all works fine.
    I've been able to set preferences and network home paths with no major issues and scripted to get around problems with using iMovie. However as we've been awaiting some replacement hard drives to set up a new RAID, the home paths have been set to the share automatically created for Users - so afp://SERVER/Users
    Now our new hard drives have turned up. The RAID is setup and working. I've created a new folder to store home paths - just to test with one user initially. I shared this path 'StaffData', enabled it for automount via afp, in protocol I've enabled guest access for afp. I copied the permissions set for the original /Users directory we were using. In WGM I've changed the home path for this user to afp://SERVER/StaffData, saved, then rebooted the client.
    When I then login with this user it created the top level home directory - afp://SERVER/StaffData/USERNAME - and then a subfolder for /Library and /Desktop. No other folders are created (Music, Movies, Photos, Documents are all missing). I'm able to get it to generate Music when I load iTunes, but the same doesn't happen for iMovie or iPhoto.
    I'm guessing its a permissions issue? When I switch the home folder back to the server's /User directory it creates all the home folders without any issues. Can anyone point me in the direction of a solution to this?

    Yep, I always get an error "The home directory could not be created because an error occurred". Always had that, even on the original /Users share that worked.
    Kind of found a way around, have written a script to run at login that checks to see if Pictures, Movies, etc folders are present, and if it doesn't it just makes a new directory with that name. It's a bit of a bodge, but seems to still work. Would still love to have another proper fix eventually, but for the time being it's solved the immediate problem I had!
    Thanks for your advice.

  • Problem with home directories NOT in Users and Workgroup manager

    I am setting up a Leopard server (10.5.3) with the users directories in /h1. This is mounted as /Volumes/h1.
    It is exported under AFP as /h1.
    When I try to get Workgroup manager to create a home directory, I can enter the home directory as:
    afp://quattro.innocon.com/h1
    path is 'user'
    Full path is:
    /Network/Servers/quattro.innocon.com/Volumes/h1
    However, when I try to log in as this this user, it says that the directory /Network/Servers/quattro.innocon.com/h1/username does not exist.
    I cannot seem to figure out why the 'Volumes' part of the full path is being lost.
    Any ideas on how to get this right?

    have you checked to see if /Network/Servers/quattro.innocon.com exists?
    I'm having ALOT of issues with automount not picking up on the mount-maps set by Open Directory.. If anyone has any solutions on this it would be great.

  • NFS Network Home Directories

    Hi,
    I am able to authenticate the iMAC through an LDAP directory on a Linux machine but the home directories do not get mounted - can someone help me to get the NFS home directories from the server to mount dynamically on boot? There are around 300+ users and putting each user into a seperate line is not an option.
    Thank you in advance!

    This page came up in Google:
    http://coewww.rutgers.edu/www1/linuxclass2005/lessons/lesson5/sec_10.html
    I believe that the automount daemon is normally running on Mac OS X, so you don't need to start it, but I think you do need to define the master mapping. You also need to create a mount point directory such as /mnt or /home as an empty directory.

  • Multiple simutaneously logged in users accessing AFP home directories?

    Hi,
    Many of our problems are described in this guy's blog:
    http://alblue.blogspot.com/2006/08/rantmac-migrating-from-afp-to-nfs.html
    The basic capability we want is to have multiple simultaneously logged in users to have access to their AFP mounted home directory, which is configured in a sane, out-of-the box setup using WGM and Server Admin.
    Multiple user access could take the form of FUS (fast user switching), or simply allowing a user to SSH into a machine that another user is already logged into and expect to be able to manipulate the contents of her home directory.
    From my extensive searches, I have no reason to believe this is currently possible with 10.4 Server and AFP.
    (here's the official word from apple: http://docs.info.apple.com/article.html?artnum=25581)
    I've read that using NFS home directories will work, though.
    I want to believe that Apple has a solution for this by now (it's been almost a year since we first had difficulty), or at least a sanctioned workaround. If Apple doesn't have one, maybe someone else has come up with something clever. I find it hard to believe that more people haven't wanted this capability! (not being able to easily search the discussion boards doesn't help, though...)
    Thanks for your help!
    Adam

    Parallels Issue. Track at http://forum.parallels.com/showthread.php?p=135585

  • Portable Home Directories, FileSyncAgent, and Case-sensitive drives

    I have a 10.5.3 Server machine that is serving (via NFS) home directories to a mixed group of Leopard (10.5.3) and Linux clients. The drive containing user home directories is formatted to be case-sensitive. I also use Portable Home Directories and mobile accounts on all the Leopard clients. Many of the client machines have case-insensitive drives.
    FileSyncAgent is dying on the client machines with a lot of "Reverification failed" messasges in ~/Library/Logs/FileSyncAgent.log. The files being verified often have mixed case file names, while the error messages show lower case file names.
    Anyone else seeing FileSyncAgent dying on every home sync?

    Hi Guys, So far I have found what seems to be a fix for this issue. I was also having the issue happen to me around some iphoto file but that seems to be coincidental. I will detail what I did below but please first backup the mobile account on the local machine as you will need to recreate it.
    Backup the local mobile home folder
    Log into a admin account and delete the mobile account under the Accounts Pane in System Prefs
    Log into the users Network account on the notebook
    Delete all the following items
    ~/Library/Application Support/SyncServices
    ~/Library/Mirrors
    ~/Library/Preferences/ByHost/com.apple.syncservices.*
    ~/Library/Preferences/com.apple.filesync.plist
    ~/Library/Preferences/com.apple.homesync.plist
    ~/Library/Preferences/com.apple.LaunchServices.plist
    ~/Library/Preferences/com.apple.syndication.plist
    ~/Library/Preferences/Syndication
    Logout of the Network account and then back in
    Recreate the Mobile Account
    From this point on I have not seen any issues with the FileSyncAgent crashing. Omit any of the files listed above that do not exist. I generally have the notebooks sync on login and logout and I forced a sync while logged in to make sure everything was okay and so far so good. Hope this helps.

  • Home directories from GUI work but not from command line

    I'm having trouble accessing home directories through SSH. After significant trouble, I reinstalled OS 10.4.6 Server on each of my 24 XServes. This is a HPC with an XServe RAID providing the storage space. I promoted the first XServe to an Open Directory master and created 2 test users. I created a two sharepoints from the XServe RAID--one for general data and one for home directories. I enabled AFP on both, granted R/W access to the default group "staff" (of which my two test users are members) and set the home directory sharepoint ("HomeDir") to automount using AFP for users' home directories through WGM. If I use Remote Desktop to login to one of the cluster nodes, the home directory seems to mount correctly. However, if I try to access the same user account through the command line--the home directory cannot be found.
    I can cd to /Network/Servers/headnode.domain.com/Volumes/HomeDir; but I cannot see any of the folders listed there. On the head node, I can verify that the user's home directory has been created--it seems to be fully populated. I've checked permissions, and they seem to be correct; but the fact that I cannot access it from the command line seems to suggest that there's a greater permissions issue.
    I've tried doing the identical setup using an NFS automount instead of AFP with no success. I can't find any answers for command line/SSH access to this problem. Any help would be appreciated.
    Thanks,
    CF

    I've discovered something else in the course of troubleshooting this problem. If I login as a test user through remote desktop to, say, node1.domain.com; the home directory mounts correctly; and, as long as I do not reboot either headnode.domain.com or node1.domain.com, I can login via SSH and access my home directory.
    Of course, if I do reboot--access no longer works. I've browsed through dozens of other posts and tried to follow other users' suggestions. I've manually created a hosts file, which I've uploaded to /etc/hosts on each node. I've double and triple checked DNS and DHCP--I have LDAP propagated through autodiscovery on DHCP; I have each node statically assigned; and I have DNS entries for each node. I also have computer entries in WGM; and I've used the FQDN of each node (node#.domain.com) for everything across the board.
    I'm also hitting the "authentication error" when I try to access my other AFP sharepoint. I can't figure this out.

  • Word 2008 for Mac and NFS mounted home directories "Save File" issues

    Greetings everyone,
    (Long time lurker, first time poster here)
    I admin a small network (under 20 workstaitons) with a centralized NFS server, with user home directories mounted via NFS upon login.  Users are authenticated via LDAP.  This is all working fine, there is no problem here.  The problem lies when my users use Microsoft Word 2008 for Mac.  When they attempt to save a file to thier Desktop (or Documents or any folder under thier home dir) they are met with the following message:
    (dialog box popup)
    "Word cannot save or create this file.  The disk maybe be full or write-protected.  Try one or more of the following: * Free more memory. * Make sure the disk you want to save the file on is not full, write-protected or damaged. (document-name.ext)"
    This happens regardless of file format (Doc, Docx, Txt) and regardless of saved location under the network mounted dir.  I've noticed that when saving Word creates a .tmp file in the target directory, which only further confuses me to the underlying cause of the issue.
    When users logon to a local machine account and attempt the save, there is no issue.
    I have found many posts in other commuity forums, including this one, indicating that the issue is a .TempoaryItems folder in the root of the mounted directory.  This folder already exists and is populated with entries such as "folder.2112" (where 2112 is the uid of the LDAP user).  I find other posts indicating that this is an issue with Word:2008 and OSX10.8, with finger pointing in either direction, but no real solution.
    I have installed all Office for Mac updates from Microsoft (latest version 12.3.6).
    I have verified permissions of the user's home dir.
    I have also ensured that this issue effects ONLY Microsoft Office 2008 for Mac apps, LibreOffice and other applications have no issue.
    Does *ANYONE* have a solution or workaround for this issue?  While we're trying to phase Microsoft products out, getting users to ditch Word and Excel is difficult without removing them from systems completely.  So any pointers or help would be greatly appreciated.
    Thanks.
    ~k

    I can't tell you how to fix bugs in an obsolete version of Office, but a possible workaround is to use mobile home directories under OS X Server. The home directories are hosted locally and synced with the server.

Maybe you are looking for