Issue #3710 has been updated by Nigel Kersten.
Roy, is there any chance we could get this info from you for actual Mac hardware rather than a VMware install? There are some weird things that get reported via system profiler for virtual instances, and I'd like to check how the 99% case looks for this situation. You can see how the info for some of this info isn't really correct under 10.5.6 for the virtual instance, and I have a feeling from memory that the info is actually malformed in that situation and we may simply have to fail gracefully in Facter. ---------------------------------------- Bug #3710: Facter not working on Mac 10.5.x http://projects.puppetlabs.com/issues/3710 Author: Allan Marcus Status: Accepted Priority: High Assigned to: Nigel Kersten Category: Target version: Keywords: mac Branch: It appears puppetd is not working properly on Mac OS X 10.5.6 (latest 10.5.x DVD shipped from Apple). It appears puppetd is not able to create /etc/puppet/ssl or /var/puppet/* We tried with 0.25.1 and 0.25.5rc2 bash-3.2# puppetd --debug debug: Failed to load library 'selinux' for feature 'selinux' debug: Failed to load library 'shadow' for feature 'libshadow' debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUseradd: file useradd does not exist debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing 2010-05-03 09:19:05.095 system_profiler[1034:10b] Exception while calling [SPPlatformReporter updateDictionary:] *** -[NSCFArray objectAtIndex:]: index (3) beyond bounds (2) err: Could not create resources for managing Puppet's files and directories in sections [:main, :puppetd, :ssl]: undefined method `each' for nil:NilClass /Library/Ruby/Site/1.8/puppet/util/pidlock.rb:33:in `initialize': No such file or directory - /var/lib/puppet/run/puppetd.pid (Errno::ENOENT) from /Library/Ruby/Site/1.8/puppet/util/pidlock.rb:33:in `open' from /Library/Ruby/Site/1.8/puppet/util/pidlock.rb:33:in `lock' from /Library/Ruby/Site/1.8/puppet/daemon.rb:46:in `create_pidfile' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/sync.rb:229:in `synchronize' from /Library/Ruby/Site/1.8/puppet/daemon.rb:45:in `create_pidfile' from /Library/Ruby/Site/1.8/puppet/daemon.rb:21:in `daemonize' from /Library/Ruby/Site/1.8/puppet/application/puppetd.rb:233:in `run_setup' from /Library/Ruby/Site/1.8/puppet/application.rb:216:in `run' from /Library/Ruby/Site/1.8/puppet/application.rb:306:in `exit_on_fail' from /Library/Ruby/Site/1.8/puppet/application.rb:216:in `run' from /usr/sbin/puppetd:160 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
