jamf binary spitting up Console Errors

ToriAnneke
Contributor II

Hey all,

Just noticed this on a brand new out-of-the-box MacBook Pro 10.9.5 and JSS 9.5 in the console logs this morning.

Tue Oct 21 13:11:38 ams-mp585 jamf[11842]: Failed to set the attributes of /Users/macadmin/Library/Preferences/com.jamfsoftware.selfservice.plist: Error Domain=NSCocoaErrorDomain Code=4 "The file “com.jamfsoftware.selfservice.plist” doesn’t exist." UserInfo=0x7a940f80 {NSFilePath=/Users/macadmin/Library/Preferences/com.jamfsoftware.selfservice.plist, NSUnderlyingError=0x7a93c180 "The operation couldn’t be completed. No such file or directory"}

I see it over and over especially after a Re-occuring Check-in, or policy runs or if I click a self service.

Any thoughts?

Thanks as always,
-pat

7 REPLIES 7

Chris
Valued Contributor

Is "macadmin"'s home actually in /Users/macadmin?
I was getting the same when logged in as a user that had his home folder in a location other than /Users.
Contacted support and got D-007509

ToriAnneke
Contributor II

Yes it is there.

It's the first 501 account that is set up.

Just check my machine and am seeing the same error. Different user name and path, but never the less, same error.

Should I contact support also?

-pat

ToriAnneke
Contributor II

OK.. so after looking around my machines.

At first setup the 501 account, in my case called macadmin, is in /Users/macadmin and therefore the above error isn't appearing.

We move our macadmin account after set up to /var/macadmin and change the UID to 101. I begin to get the error above.

This has only appeared after upgrading my jss to 9.52. Previously version of jss never gave this error since hiding our macadmin account is what we've been doing for many years now.

The error is looking specifically for that plist in the default users path /Users/blah-blah. So the error does make sense.

But why is it spitting up this error now when it never did before?

GaToRAiD
Contributor II

@pvader, Why hide your admin account? When you do an OS upgrade you will loose this account since it is hidden and you will no longer have an admin account on the system? Just curious to your workflow on how you accomplish OS upgrades while hiding the account? Unless just prior to the upgrade you switch it back to 501, then back to 101.

ToriAnneke
Contributor II

I hide it because one of our users opened SysPrefs > Users & Groups and deleted my local admin account.
When asked why he did it? He shrugged his shoulders and said, "I don't know, I felt like doing it. So, can you fix my computer now? I got a meeting in a few minutes."

This has happened a few times also with other users.
All my users are admins of their accounts (yes, I know I know) but it just gotta be this way in my shop or they will storm my door with pitchforks in hand and screaming, "We want the monster!!!!"

When I have upgraded from 10.8 to 10.9 it never clobbered my hidden macadmin account. Small point upgrades also have no impact.

I haven't tested any 10.9 to 10.10 yet.

mpermann
Valued Contributor II

@GaToRAiD, I don't believe there is any issue anymore with hidden accounts getting messed up. At least that has been my experience when upgrading to either Mavericks or Yosemite.

NightFlight
New Contributor III

Nice derail guys.

I have the same error clogging my /var/log/jamf.log on 9.72 at the hourly check-in. Looks like the com.jamfsoftare.selfservice.plist is failing to set an attribute, but in my case its trying to access it at path: Library/Preferences/com.jamfsoftware.selfservice.plist. No /Users/<username> referenced at all.