Puppet users - Jun 2012 - Not using expired node for targethost from cache; expired

Hi,

When I execute *puppet agent --test --debug --verbose* on the target host, 
I receive the following error message:

err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Could not find class pe_accounts for targethost on node targethost
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

I enabled debugging for the Puppet Master, and whenI look at the logs I get 
the following output:

Jun  5 16:25:12 puppet puppet-master[29802]: Expiring the node cache of 
targethost
Jun  5 16:25:12 puppet puppet-master[29802]: Not using expired node for 
targethost from cache; expired at Tue Jun 05 16:24:12 -0700 2012
Jun  5 16:25:12 puppet puppet-master[29802]: Caching node for targethost
Jun  5 16:25:12 puppet puppet-master[29802]: Could not find class 
pe_accounts for targethost on node targethost
Jun  5 16:25:12 puppet puppet-master[29802]: Could not find class 
pe_accounts for targethost on node targethost

I have 4 nodes that are effectively the same and 3 of the 4 work as 
expected.  Someone trying to help has said:

"The only thing i can derive from that is there is no 
''modules/pe_accounts/manifests/init.pp'' in any of the path
elements in
`puppet master --configprint modulepath` on your server, for the 
environment that client is"

It was my understanding from reading that the pe_accounts was a part of the 
core classes that comes with puppet.  The version of puppet I am working 
with is PE 2.5.1 on Solaris 10 non-global zones.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/P5jlyGgbfBsJ.
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.

Or the class is failing to compile for some reason. You have to check the logs
on the master to find out why. It only tells you once.

On Jun 5, 2012, at 4:43 PM, Berry Sizemore wrote:
> When I execute puppet agent --test --debug --verbose on the target host, I
receive the following error message:
> 
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find class pe_accounts for targethost on node targethost
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
> 
> I enabled debugging for the Puppet Master, and whenI look at the logs I get
the following output:
> 
> Jun  5 16:25:12 puppet puppet-master[29802]: Expiring the node cache of
targethost
> Jun  5 16:25:12 puppet puppet-master[29802]: Not using expired node for
targethost from cache; expired at Tue Jun 05 16:24:12 -0700 2012
> Jun  5 16:25:12 puppet puppet-master[29802]: Caching node for targethost
> Jun  5 16:25:12 puppet puppet-master[29802]: Could not find class
pe_accounts for targethost on node targethost
> Jun  5 16:25:12 puppet puppet-master[29802]: Could not find class
pe_accounts for targethost on node targethost
> 
> I have 4 nodes that are effectively the same and 3 of the 4 work as
expected.  Someone trying to help has said:
> 
> "The only thing i can derive from that is there is no
''modules/pe_accounts/manifests/init.pp'' in any of the path
elements in `puppet master --configprint modulepath` on your server, for the
environment that client is"
> 
> It was my understanding from reading that the pe_accounts was a part of the
core classes that comes with puppet.  The version of puppet I am working with is
PE 2.5.1 on Solaris 10 non-global zones.
> 
> -- 
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/P5jlyGgbfBsJ.
> 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.
-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



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

Does it matter that it is a core class that comes with Puppet Enterprise?

On Tuesday, June 5, 2012 5:44:55 PM UTC-7, Jo wrote:
>
> Or the class is failing to compile for some reason. You have to check the 
> logs on the master to find out why. It only tells you once.
>
> On Jun 5, 2012, at 4:43 PM, Berry Sizemore wrote:
>
> When I execute *puppet agent --test --debug --verbose* on the target 
> host, I receive the following error message:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Could not find class pe_accounts for targethost on node targethost
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
>
> I enabled debugging for the Puppet Master, and whenI look at the logs I 
> get the following output:
>
> Jun  5 16:25:12 puppet puppet-master[29802]: Expiring the node cache of 
> targethost
> Jun  5 16:25:12 puppet puppet-master[29802]: Not using expired node for 
> targethost from cache; expired at Tue Jun 05 16:24:12 -0700 2012
> Jun  5 16:25:12 puppet puppet-master[29802]: Caching node for targethost
> Jun  5 16:25:12 puppet puppet-master[29802]: Could not find class 
> pe_accounts for targethost on node targethost
> Jun  5 16:25:12 puppet puppet-master[29802]: Could not find class 
> pe_accounts for targethost on node targethost
>
> I have 4 nodes that are effectively the same and 3 of the 4 work as 
> expected.  Someone trying to help has said:
>
> "The only thing i can derive from that is there is no 
> ''modules/pe_accounts/manifests/init.pp'' in any of the
path elements in
> `puppet master --configprint modulepath` on your server, for the 
> environment that client is"
>
> It was my understanding from reading that the pe_accounts was a part of 
> the core classes that comes with puppet.  The version of puppet I am 
> working with is PE 2.5.1 on Solaris 10 non-global zones.
>
>
> -- 
> Jo Rhett
> Net Consonance : net philanthropy to improve open source and internet 
> projects.
>
>
>  
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/NEirrpSfg48J.
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 Wed, Jun 6, 2012 at 8:39 AM, Berry Sizemore <berry.sizemore@gmail.com>
wrote:
> Does it matter that it is a core class that comes with Puppet Enterprise?
Nope. That''s a just a module that comes pre-deployed to a portion of
the modulepath. Try `puppet module list --tree` or `puppet config
print modulepath` and make sure that you have a pe_accounts module in
/opt/puppet/share/puppet/modules (that path should be in your
modulepath as well).

If it had been removed somehow, you can find it in the
''modules''
folder in an expanded PE installer tarball.

HTH,

--Ryan

-- 
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 Wed, Jun 6, 2012 at 10:00 AM, Ryan Coleman <ryan@puppetlabs.com>
wrote:
> On Wed, Jun 6, 2012 at 8:39 AM, Berry Sizemore
<berry.sizemore@gmail.com> wrote:
>> Does it matter that it is a core class that comes with Puppet
Enterprise?
>
> Nope. That''s a just a module that comes pre-deployed to a portion
of
> the modulepath. Try `puppet module list --tree` or `puppet config
> print modulepath` and make sure that you have a pe_accounts module in
> /opt/puppet/share/puppet/modules (that path should be in your
> modulepath as well).
A really good way to troubleshoot this issue is to paste the following
two commands to the list:

(On the puppet master)

$ sudo puppet master --configprint modulepath
$ sudo find /opt/puppet/share/puppet/modules -iname ''*.pp''

Ryan''s intuition is correct, this is probably a module path issue.

-Jeff

-- 
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 the puppet master /opt/puppet/share/puppet/modules/pe_accounts does 
exist, but not on the either node (one that works and one that gets the 
error message).

On Wednesday, June 6, 2012 10:00:03 AM UTC-7, Ryan Coleman
wrote:
>
> On Wed, Jun 6, 2012 at 8:39 AM,  wrote: 
> > Does it matter that it is a core class that comes with Puppet 
> Enterprise? 
>
> Nope. That''s a just a module that comes pre-deployed to a portion
of
> the modulepath. Try `puppet module list --tree` or `puppet config 
> print modulepath` and make sure that you have a pe_accounts module in 
> /opt/puppet/share/puppet/modules (that path should be in your 
> modulepath as well). 
>
> If it had been removed somehow, you can find it in the
''modules''
> folder in an expanded PE installer tarball. 
>
> HTH, 
>
> --Ryan 
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/oG_MD9KH20MJ.
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 Wed, Jun 6, 2012 at 11:49 AM, Berry Sizemore
<berry.sizemore@gmail.com> wrote:
> On the puppet master /opt/puppet/share/puppet/modules/pe_accounts does
> exist, but not on the either node (one that works and one that gets the
> error message).
The module not being there is the problem.  =)

-Jeff

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

We learned more about the ENC today. When a node has been placed into the
console, but the puppet.conf for the node has report=false, the classes set for
the node continue to work. This was a janitorial task for me, and no classes for
that node had been assigned. The logs suggested pe_accounts was unavailable, and
of course, that wasn’t going to work. I hadn’t thought to check the console,
since I was never given the URL or access to it. I removed the node from the
console and the node normalized. It’s too bad the logs don’t signal the
condition, but it probably seems odd that our nodes aren’t reporting out to the
console en masse. We will be using the console in the future.

Thanks for the feedback.  Great Community!

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/fVb1jpbghx0J.
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.