Q: Upgrade to 10.9.3: AFP server issue
Upgrade to 10.9.3 : I had two issues:
- XSan volume has been changed to hidden, solved via chflags nohidden /Volumes/<vol>
- afp service seems to have forgotten its HOME env variable, it is not possible to connect via afp
Jun 3 11:23:59 host com.apple.launchd.peruser.501[436] (com.apple.netauth.user.auth[8186]): The HOME environmental variable changed out from under us!
Jun 3 11:23:59 host com.apple.launchd.peruser.501[436] (com.apple.netauth.user.auth[8186]): In a future build of the OS, this error will be fatal.
Jun 3 11:23:59 host.local NetAuthSysAgent[8186]: FindValidIPAddress - connect failed socket 0, optionValue 61
Jun 3 11:23:59 host.local NetAuthSysAgent[8186]: FindValidIPAddress - connect failed socket 1, optionValue 61
Jun 3 11:23:59 host.local NetAuthSysAgent[8186]: FindValidIPAddress - connect failed socket 2, optionValue 61
Jun 3 11:23:59 host.local NetAuthSysAgent[8186]: ERROR: AFP_GetServerInfo - connect failed 64
Jun 3 11:23:59 host com.apple.launchd.peruser.501[436] (com.apple.netauth.user.gui[8187]): The HOME environmental variable changed out from under us!
Jun 3 11:23:59 host com.apple.launchd.peruser.501[436] (com.apple.netauth.user.gui[8187]): In a future build of the OS, this error will be fatal.
Jun 3 11:24:07 host.local mDNSResponder[51]: SIGHUP: Purge cache
Jun 3 11:24:07 host com.apple.launchd.peruser.501[436] (com.apple.AirPortBaseStationAgent[8193]): The HOME environmental variable changed out from under us!
Jun 3 11:24:07 host com.apple.launchd.peruser.501[436] (com.apple.AirPortBaseStationAgent[8193]): In a future build of the OS, this error will be fatal.
Jun 3 11:24:18 host.local servermgrd[143]: nsc_smb XPC: handle_event error : < Connection invalid >
how do I set the HOME env variable for the launchd.peruser (com.apple.netauth.user.gui) to the correct value ?
we have a few user configured in workgroup manager (all standard). It is possible to connect via smb.
The server has been running 10.9.2 so far in suitable and stable way prior to the upgrade to 10.9.3.
Mac Pro, OS X Mavericks (10.9.3)
Posted on Jun 3, 2014 3:56 AM
Deleting and re-adding the admin user (501) solved the problem.
Posted on Jun 23, 2014 3:41 AM