Rinaldo wrote:
> I am on Solaris(x86) and using an older version from Blastwave. I am
> considering doing a package for Sun's new IPS packaging system. I need
> to understand how it all works before I package it up. I have two
> nodes and I get the following errors, I have the host names in /etc/
> hosts
>
> bash-3.2# /opt/csw/bin/puppetmasterd --verbose
> info: Starting server for Puppet version 0.23.2
> info: Parsed manifest in 0.01 seconds
> info: Listening on port 8140
> notice: Starting Puppet server version 0.23.2
> err: Could not find ndc2test02.network.com with names
> ndc2test02.network.com, ndc2test02
Okay - 0.23.2 is reasonably old. I'd recommend something in the 0.24.x
releases - the latest being 0.24.7.
> bash-3.2# puppetd --server ndc2test01.network.com --verbose
> warning: Individual config files are deprecated; remove /etc//opt/csw/
> puppet/puppetd.conf and use puppet.conf
> notice: Starting Puppet client version 0.23.2
> err: Could not retrieve configuration: Could not find
> ndc2test02.network.com with names ndc2test02.network.com, ndc2test02
> err: Could not retrieve configuration: Cannot connect to server and
> there is no cached configuration
Remove the puppetd.conf configuration file. All configuration now goes
in the puppet.conf file.
Do you have a node defined? Can you show us your manifests and
configuration?
> When I try to start the master on the Mac I get the following error
>
> Got 9 failure(s) while initializing: Tried to get name field for silly
> id 4294967294; Tried to get name field for silly id 4294967294; change
> from absent to directory failed: Could not find user(s) 4294967294;
> Tried to get name field for silly id 4294967294; Tried to get name
> field for silly id 4294967294; change from absent to directory failed:
> Could not find user(s) 4294967294; Tried to get name field for silly
> id 4294967294; Tried to get name field for silly id 4294967294; change
> from absent to directory failed: Could not find user(s) 4294967294
>
This is a known bug on 0.23.2:
http://reductivelabs.com/trac/puppet/ticket/1169
It's fixed in later versions.
Regards
James Turnbull
- --
Author of:
* Pulling Strings with Puppet
(http://www.amazon.com/gp/product/1590599780/)
* Pro Nagios 2.0
(http://www.amazon.com/gp/product/1590596099/)
* Hardening Linux
(http://www.amazon.com/gp/product/1590594444/)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJZbEw9hTGvAxC30ARAlQCAJ9MzhnVcOgwjLdbUPjsx2IUtlDOLQCgrGJO
2RR5n9DyRBkQm7kJiGXHRTo=
=h6/D
-----END PGP SIGNATURE-----
Hello,
My first post, just joined the group. Thanks for the well thought out
approach in puppet. I am trying to get the simple example from the
getting started guide to work.
I am on Solaris(x86) and using an older version from Blastwave. I am
considering doing a package for Sun's new IPS packaging system. I need
to understand how it all works before I package it up. I have two
nodes and I get the following errors, I have the host names in /etc/
hosts
bash-3.2# /opt/csw/bin/puppetmasterd --verbose
info: Starting server for Puppet version 0.23.2
info: Parsed manifest in 0.01 seconds
info: Listening on port 8140
notice: Starting Puppet server version 0.23.2
err: Could not find ndc2test02.network.com with names
ndc2test02.network.com, ndc2test02
bash-3.2# puppetd --server ndc2test01.network.com --verbose
warning: Individual config files are deprecated; remove /etc//opt/csw/
puppet/puppetd.conf and use puppet.conf
notice: Starting Puppet client version 0.23.2
err: Could not retrieve configuration: Could not find
ndc2test02.network.com with names ndc2test02.network.com, ndc2test02
err: Could not retrieve configuration: Cannot connect to server and
there is no cached configuration
>
> I'm having the exact same problem getting the initial puppet install
> going on a Mac. I've tried installing it from the packages on Nigel's
> site as well as with Ruby Gems, both times on a completely clean
> system using the latest build (0.24.7). I get the same error messages
> about "Got 9 failure(s) while initializing: Tried to get name field
> for silly id 4294967294;" etc.
>
> Any thoughts on why this might still be going on? I'm excited about
> Puppet. I think it will be great for our OS X clusters and
> workstations so I'd love to get this working.
This is because OS X uses a 'nobody' user with an id of '-2', but only
some of the OS X tools produce negative numbers, the others produce
the unsigned int, which is 64bit, so you get this gigantic positive
number instead of a small negative number.
If you run with --debug, you'll see which files are failing. Most
likely, those are owned by 'nobody' or something similar, so you could
chown them to root and probably be up and running.
--
Writing is not necessarily something to be ashamed of, but do it in
private and wash your hands afterwards. --Robert Heinlein
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com