The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Bug #11580

Mac OS 10.7 Lion @user password: No such file or directory - /var/db/shadow/hash

Added by Cory Logan over 4 years ago. Updated about 4 years ago.

Status:DuplicateStart date:12/27/2011
Priority:NormalDue date:
Assignee:Gary Larizza% Done:


Category:OSXEstimated time:2.00 hours
Target version:-
Affected Puppet version:2.7.9 Branch:
Keywords:Lion, Puppet

We've Moved!

Ticket tracking is now hosted in JIRA:


Howdy folks.

We’re just getting around to managing Lion machines, and one of the things we do is create an admin user on all of our machines by passing a hashed password in one of our modules. Anyway, this if failing pretty hard due to this error. And it’s true, in Lion there is no /var/db/shadow/hash…

No such file or directory - /var/db/shadow/hash Puppet error

This information has been moved as noted here:

Anyway, I’d really love to be able to keep our code the same and just upgrade puppet to work, if this is something that is going to be resolved. Writing up some exec statements might not take too too long. Does anyone know that this issue has been addressed? I haven’t found it anywhere. And is anyone else running into this? Just for reference sake, here’s what we’re doing to create our user in the manifest:

` @user { “ladmin”:

    ensure              => present,
    comment          => "Local Admin",
    home                => "/Users/.ladmin",
    shell                 => "/bin/bash",
uid                 => '420',
gid             => '20',
password    => 'the_password_hash_goes_here',


Thanks a zillion! Cory

Related issues

Duplicates Puppet - Bug #11293: Password parameter for the User resource is broke in OS X... Closed 12/08/2011


#1 Updated by Cory Logan over 4 years ago

  • Estimated time set to 2.00
  • Affected Puppet version changed from 2.7.6 to 2.7.9
  • Keywords changed from Lion to Lion, Puppet

Just updated my puppet server and clients. I’ve learned that this remains an issue. It appears not to be a problem on machines that were upgraded from 10.6, because the /var/db/shadow/SOME-GUID files already exist. I went ahead and created the file puppet wanted on one machine, and that fixed the problem. But I would be worried about this as a final solution as it might open up a security hole. Any thoughts?

#2 Updated by Anonymous over 4 years ago

  • Status changed from Unreviewed to Investigating
  • Assignee set to Gary Larizza

Gary, can you take a look at this please?

#3 Updated by Gary Larizza over 4 years ago

Yep, this is a duplicate of #11293 and I’m actually working on it at the moment. Take a look at that ticket and follow along :)

#4 Updated by James Turnbull over 4 years ago

  • Status changed from Investigating to Duplicate

Duplicate of #11293.

#5 Updated by Cory Logan over 4 years ago

Thanks a bunch! I had taken a look, but I just didn’t see it. Hopefully the taggin/choice of words on this one will help folks find the other issue.


As for now… I’ve got a hacky workaround, but hopefully it’s a temporary thing.

#6 Updated by Gary Larizza over 4 years ago

Cory, if you check out there’s a fix that’s been merged to master. Check it out and see if it works well for you (and comment on that ticket if you notice any issues). Thanks!

#7 Updated by Anonymous about 4 years ago

  • Target version deleted (2.7.x)

Also available in: Atom PDF