Puppet users - Dec 2008 - I give up: why does the Augeas type hate me?

I''ve installed augeas-0.3.4, facter-1.5.2, and puppet-0.24.7 from
their respective tarballs.  I''ve installed ruby-augeas-0.2.0.gem.
All of these things seem to work, but no matter what I do:

err: Could not retrieve catalog: Could not find resource type augeas
at /etc/puppet/manifests/site.pp:38 on node [snip]

I''ve also tried the puppet-0.24.7.gem gem; no different.

Help?

-Robin

-- 
They say:  "The first AIs will be built by the military as weapons."
And I''m thinking:  "Does it even occur to you to try for something
other than the default outcome?" -- http://shorl.com/tydruhedufogre
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi
> I''ve installed augeas-0.3.4, facter-1.5.2, and puppet-0.24.7 from
> their respective tarballs.  I''ve installed ruby-augeas-0.2.0.gem.
> All of these things seem to work, but no matter what I do:
> 
> err: Could not retrieve catalog: Could not find resource type augeas
> at /etc/puppet/manifests/site.pp:38 on node [snip]
> 
> I''ve also tried the puppet-0.24.7.gem gem; no different.

can you provide a trace & debug output of a client run? I assume you
updated the master as well?! Maybe as well a debug/trace of the master.
Did you restart it?

cheers pete

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Mon, Dec 22, 2008 at 10:06:56AM +0100, Peter Meier
wrote:
> 
> Hi
> 
> > I''ve installed augeas-0.3.4, facter-1.5.2, and puppet-0.24.7
> > from their respective tarballs.  I''ve installed
> > ruby-augeas-0.2.0.gem. All of these things seem to work, but no
> > matter what I do:
> > 
> > err: Could not retrieve catalog: Could not find resource type
> > augeas at /etc/puppet/manifests/site.pp:38 on node [snip]
> > 
> > I''ve also tried the puppet-0.24.7.gem gem; no different.
> 
> 
> can you provide a trace & debug output of a client run? I assume
> you updated the master as well?! Maybe as well a debug/trace of
> the master. Did you restart it?
Debug output of the client run follows.  No, I didn''t update the
master; why would I do that?  This is about functionality on the
client, not the master.  Is it actually necessary that the *master*
have Augeas when it never uses it?

-Robin

$ puppetd --debug --test
debug: Creating default schedules
debug: Failed to load library ''ldap'' for feature
''ldap''
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/certs/box.compute-1.internal.pem]:
Autorequiring File[/var/lib/puppet/ssl/certs]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/lib/puppet/state/classes.txt]:
Autorequiring File[/var/lib/puppet/state]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/ssl]:
Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/private_keys]:
Autorequiring File[/var/lib/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/private]:
Autorequiring File[/var/lib/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/private_keys/box.compute-1.internal.pem]:
Autorequiring File[/var/lib/puppet/ssl/private_keys]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/etc/puppet/puppet.conf]:
Autorequiring File[/etc/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/certs/ca.pem]:
Autorequiring File[/var/lib/puppet/ssl/certs]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/public_keys]:
Autorequiring File[/var/lib/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/lib]:
Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/state]:
Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/facts]:
Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/lib/puppet/state/state.yaml]:
Autorequiring File[/var/lib/puppet/state]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/csr_box.compute-1.internal.pem]:
Autorequiring File[/var/lib/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/lib/puppet/state/puppetdlock]:
Autorequiring File[/var/lib/puppet/state]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/public_keys/box.compute-1.internal.pem]:
Autorequiring File[/var/lib/puppet/ssl/public_keys]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/certs]:
Autorequiring File[/var/lib/puppet/ssl]
debug: Finishing transaction -604761988 with 0 changes
debug: Loaded state in 0.01 seconds
debug: Puppet::Network::Client::File: defining fileserver.describe
debug: Puppet::Network::Client::File: defining fileserver.list
debug: Puppet::Network::Client::File: defining fileserver.retrieve
info: Retrieving plugins
debug: Calling fileserver.list
debug: Calling fileserver.describe
debug: Finishing transaction -607371628 with 0 changes
info: Retrieving facts
debug: Calling fileserver.list
debug: Calling fileserver.describe
debug: Finishing transaction -607775008 with 0 changes
debug: Retrieved facts in 7.88 seconds
debug: Retrieving catalog
debug: Calling puppetmaster.getconfig
err: Could not retrieve catalog: Could not find resource type augeas at
/etc/puppet/manifests/site.pp:38 on node box.compute-1.internal
warning: Not using cache on failed catalog


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi
> Debug output of the client run follows.  No, I didn''t update the
> master; why would I do that?  This is about functionality on the
> client, not the master.  Is it actually necessary that the *master*
> have Augeas when it never uses it?
well the master has to compile the manifest with all it''s dependencies
and it will send the evaluated manifest down to the client. IMHO
therefore it have to know the new type.
However I might be wrong, but afair there is anyway the suggested best
practice to always update first the master and then all the clients. As
only the master will guarantee backward compatibility to older clients.

@James: If I''m correct with the above, I thought to remember that this
have been mentioned here:
http://reductivelabs.com/trac/puppet/wiki/UPGRADE but I can''t find it
anymore anywhere.

cheers pete

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Meier wrote:
> well the master has to compile the manifest with all it''s
dependencies
> and it will send the evaluated manifest down to the client. IMHO
> therefore it have to know the new type.
> However I might be wrong, but afair there is anyway the suggested best
> practice to always update first the master and then all the clients. As
> only the master will guarantee backward compatibility to older clients.
Correct.  The configuration is compiled on the master and then sent to
the client.  Hence the master needs to be up-to-date.
> @James: If I''m correct with the above, I thought to remember that
this
> have been mentioned here:
> http://reductivelabs.com/trac/puppet/wiki/UPGRADE but I can''t find
it
> anymore anywhere.
> 
It was mentioned somewhere.  It''s def. in the book somewhere I think.
Let me big through my notes and if not I''ll add it somewhere.

Cheers

James

- --
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

iD8DBQFJT2qW9hTGvAxC30ARAqGjAKDKncHgZ1kCJvPc1+7p49pSdjxb2gCfdATg
ZbzCFqNhhTiAP5zQnQ4jBCU=lhV0
-----END PGP SIGNATURE-----

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Mon, Dec 22, 2008 at 10:40:05AM +0100, Peter Meier
wrote:
> 
> Hi
> 
> > Debug output of the client run follows.  No, I didn''t update
the
> > master; why would I do that?  This is about functionality on the
> > client, not the master.  Is it actually necessary that the
> > *master* have Augeas when it never uses it?
> 
> well the master has to compile the manifest with all it''s
> dependencies and it will send the evaluated manifest down to the
> client. IMHO therefore it have to know the new type.
Well, that seemed to do it.  Just strikes me as odd.  Thank you!

-Robin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Mon, Dec 22, 2008 at 1:02 PM, Robin Lee Powell
<rlpowell@digitalkingdom.org> wrote:
>
> On Mon, Dec 22, 2008 at 10:40:05AM +0100, Peter Meier wrote:
>>
>> Hi
>>
>> > Debug output of the client run follows.  No, I didn''t
update the
>> > master; why would I do that?  This is about functionality on the
>> > client, not the master.  Is it actually necessary that the
>> > *master* have Augeas when it never uses it?
>>
>> well the master has to compile the manifest with all it''s
>> dependencies and it will send the evaluated manifest down to the
>> client. IMHO therefore it have to know the new type.
>
> Well, that seemed to do it.  Just strikes me as odd.  Thank you!
>
> -Robin
>
Why does it strike you as odd? The server does all the heavy lifting.
By the time it gets to the client all you have are set of directions
to be followed. The idea of a Puppet and a PuppetMaster is really an
accurate view of the system

Evan

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Mon, Dec 22, 2008 at 01:21:23PM -0600, Evan Hisey
wrote:
> 
> On Mon, Dec 22, 2008 at 1:02 PM, Robin Lee Powell
> <rlpowell@digitalkingdom.org> wrote:
> >
> > On Mon, Dec 22, 2008 at 10:40:05AM +0100, Peter Meier wrote:
> >>
> >> Hi
> >>
> >> > Debug output of the client run follows.  No, I
didn''t update the
> >> > master; why would I do that?  This is about functionality on
the
> >> > client, not the master.  Is it actually necessary that the
> >> > *master* have Augeas when it never uses it?
> >>
> >> well the master has to compile the manifest with all it''s
> >> dependencies and it will send the evaluated manifest down to the
> >> client. IMHO therefore it have to know the new type.
> >
> > Well, that seemed to do it.  Just strikes me as odd.  Thank you!
> >
> Why does it strike you as odd? The server does all the heavy
> lifting. By the time it gets to the client all you have are set of
> directions to be followed. The idea of a Puppet and a PuppetMaster
> is really an accurate view of the system
Probably because I''m used to cfengine, where all the master does is
send the files to the clients that then do what the files say.

I gather that''s not how Puppet works, but looking at
http://reductivelabs.com/trac/puppet/wiki/BigPicture
and http://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction I
see no indication to the contrary.  In fact, the latter says:

    In particular, Puppet is usually used in a star formation, with
    all of your clients talking to one or more central servers. Each
    client contacts the server periodically (every half hour, by
    default), gets its latest configuration, and makes sure it is in
    sync with that configuration. Once done, it can send a report
    back to the server indicating what, if anything, happened

which is exactly what I thought: the server delivers the
configurations, and the client does what they say.  The server, as
described there, shouldn''t care at all what the configurations
*say*.

(Neither of those pages even contain the text "master", by the way.)

So, now I "know" that puppet doesn''t work like that (proof by
existence and all that), but I have no idea what the puppetmaster
actually *does* anymore.  That is, you say "By the time it gets to
the client all you have are set of directions to be followed.",
which is what I thought, but I thought the "set of directions" was
things like:

    augeas { "no usecacheonfailure" :
        context => "/files/etc/puppet/puppet.conf",
        changes => "set main/usecacheonfailure false",
    }

that the client then dealt with themselves.

Pointers to what puppetmaster *actually* sends the clients would be
welcome.

-Robin


-- 
They say:  "The first AIs will be built by the military as weapons."
And I''m thinking:  "Does it even occur to you to try for something
other than the default outcome?" -- http://shorl.com/tydruhedufogre
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Robin Lee Powell wrote:
> Probably because I''m used to cfengine, where all the master does
is
> send the files to the clients that then do what the files say.
> 
> I gather that''s not how Puppet works, but looking at
> http://reductivelabs.com/trac/puppet/wiki/BigPicture
> and http://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction I
> see no indication to the contrary.  In fact, the latter says:
"A Puppet server is aware of the full configuration. As some
component''s
configuration aspects depend on the configuration of other components
(e.g. the firewall config includes the ports used by webservers),
generating configuration for a component *requires being aware of full
configuration*."

"Puppet Clients normally request or "pull" configuration from
their
server. The Server processes the configuration request for the host
using a *pre-generated tree model* of the classes and definitions from
the site-config."

My emphasis.

But yes not as clear as it could be.
> Pointers to what puppetmaster *actually* sends the clients would be
> welcome.
I don''t think the lifecycle is clearly documented anywhere.  But if
someone would like to string some words together I am happy to help them.

Cheers

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/)