Re: [Puppet Users] Not using expired node for targethost from cache; expired
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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Not using expired node for targethost from cache; expired
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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Not using expired node for targethost from cache; expired
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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] How do I get a PE 2.5.1 agent to run as a non-root user in Solaris?
Hi, Some months ago I got PE 1.5.6 agent running as a non-root user on Solaris 10. I upgraded my agents to PE 2.5.1 and now I cannot successfully start them as non-root user. I get no error message or logs. Thanks -- 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/-/lMNVbvniYmoJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: How do I get a PE 2.5.1 agent to run as a non-root user in Solaris?
Or perhaps there is a designated user other than root and some random non-root user? -- 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/-/e_j5tsjt1Q8J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: How do I get a PE 2.5.1 agent to run as a non-root user in Solaris?
What didn't work yesterday works today. I suspect we were using the wrong command. Thanks for having a look. On Wednesday, May 30, 2012 10:45:38 AM UTC-7, Berry Sizemore wrote: Hi, Some months ago I got PE 1.5.6 agent running as a non-root user on Solaris 10. I upgraded my agents to PE 2.5.1 and now I cannot successfully start them as non-root user. I get no error message or logs. Thanks On Wednesday, May 30, 2012 10:45:38 AM UTC-7, Berry Sizemore wrote: Hi, Some months ago I got PE 1.5.6 agent running as a non-root user on Solaris 10. I upgraded my agents to PE 2.5.1 and now I cannot successfully start them as non-root user. I get no error message or logs. Thanks -- 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/-/QmJnBB2EBgcJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] hiera failed dependencies
Hi all. Even though hiera is working for my manifests (does what it should) the agents are complaining in their logs. http://pastebin.com/PKQDfPmN Can anyone suggest what might be going on? TIA -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: hiera failed dependencies
I found the problem. The pluginsync was not in [main]. Thanks. On Feb 9, 3:24 pm, Gary Larizza g...@puppetlabs.com wrote: Do you have an example of the code that's being run? Are you just starting to play with Hiera, or did you suddenly have issues? Are the permissions set correctly on the hiera-puppet module on your Master? I think we need a bit more information here about how you have this setup. On Thu, Feb 9, 2012 at 3:20 PM, Berry Sizemore berry.sizem...@gmail.comwrote: Hi all. Even though hiera is working for my manifests (does what it should) the agents are complaining in their logs. http://pastebin.com/PKQDfPmN Can anyone suggest what might be going on? TIA -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: tomcat module
After groking the defined types link, it everything looked good. The
issue was that the data needed to be unique for this to work. I
ensured that each of my instances had a unique name in its YAML file,
as well for the names of the apps. Now it is cruising right along.
Thanks,
Berry
On Jan 12, 5:20 pm, Berry Sizemore berry.sizem...@gmail.com wrote:
Here is a digest of a conversation on IRC:
***
I am trying to figure out why puppet builds out a tree successfully,
but fails to do it a 2nd time when I add more data into my YAML file.
I believehttp://docs.puppetlabs.com/learning/definedtypes.html
explains the problem
You cannot instantiate tomcat::war { 'foo': } twice on one node
Example YAML filehttp://pastebin.com/sRkR4nas
***
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] tomcat module
Hi, Some time ago, Nan wrote a Tomcat module for my company. I have added it to module forge here: http://forge.puppetlabs.com/users/multiverse/modules/Tomcat/releases/1 I have recently been wrestling with the behavior of the module and could use some help. [root@puppetmaster pkg]# uname -a Linux 2.6.18-238.el5xen SMP x86_64 x86_64 x86_64 GNU/Linux Note: some information is suppressed. [root@puppetmaster puppet]# puppet --version 2.6.9 (Puppet Enterprise 1.2.4) When I create new Tomcat instances for the first time, let's say there are two, the task completes excellently, including deploying/exploding my wars. When I create a third Tomcat instance, I get error messages that make no sense to me. My suspicion is that I need to use different syntax. Our goal is to reduce the amount of time that is consumed deploying new wars. Here is a snapshot I took of the initial success, and the subsequent failure. You can see the current code I am using at the forge link above. Here is the screenshot: http://www.multiverse.org/tomcat-one-run.jpg - if the link gives you 404 or redirects with 403, you may have to type it in by hand. Sorry about that! Thanks, Berry -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: tomcat module
Here is a digest of a conversation on IRC:
***
I am trying to figure out why puppet builds out a tree successfully,
but fails to do it a 2nd time when I add more data into my YAML file.
I believe http://docs.puppetlabs.com/learning/definedtypes.html
explains the problem
You cannot instantiate tomcat::war { 'foo': } twice on one node
Example YAML file
http://pastebin.com/sRkR4nas
***
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] module can't find other modules
I have these three modules with the following structure:
|-- modules
| |-- create_resources
| | |-- LICENSE
| | |-- Modulefile
| | |-- README
| | |-- lib
| | | `-- puppet
| | | `-- parser
| | | `-- functions
| | | `-- create_resources.rb
| | |-- spec
| | | |-- spec.opts
| | | |-- spec_helper.rb
| | | `-- unit
| | | `-- puppet
| | | `-- parser
| | | `-- functions
| | | `-- create_resources_spec.rb
| | `-- tests
| | `-- users.pp
| |-- hiera
| | |-- CHANGES.txt
| | |-- COPYING
| | |-- README.md
| | |-- Rakefile
| | |-- bin
| | | `-- extlookup2hiera
| | |-- example
| | | |-- README.md
| | | |-- etc
| | | | |-- hiera.yaml
| | | | |-- hieradb
| | | | | |-- common.yaml
| | | | | |-- dc1.yaml
| | | | | `-- development.yaml
| | | | `-- puppet.conf
| | | |-- modules
| | | | |-- data
| | | | | `-- manifests
| | | | | `-- common.pp
| | | | |-- ntp
| | | | | |-- manifests
| | | | | | |-- config.pp
| | | | | | `-- data.pp
| | | | | `-- templates
| | | | | `-- ntp.conf.erb
| | | | `-- users
| | | | `-- manifests
| | | | |-- common.pp
| | | | |-- dc1.pp
| | | | `-- development.pp
| | | `-- site.pp
| | |-- lib
| | | |-- hiera
| | | | |-- backend
| | | | | `-- puppet_backend.rb
| | | | `-- scope.rb
| | | `-- puppet
| | | `-- parser
| | | `-- functions
| | | |-- hiera.rb
| | | |-- hiera_array.rb
| | | |-- hiera_hash.rb
| | | `-- hiera_include.rb
| | `-- spec
| | |-- spec.opts
| | |-- spec_helper.rb
| | `-- unit
| | |-- puppet_backend_spec.rb
| | `-- scope_spec.rb
| `-- tomcat
| |-- files
| | `-- war
| | |-- jenkins_1.423.war
| | |-- jenkins_1.424.war
| | |-- jenkins_1.425.war
| | |-- snoop-servlet.war
| | |-- snoop-servlet_1.0.war
| | `-- snoop-servlet_2.0.war
| |-- manifests
| | |-- demo.pp
| | |-- init.pp
| | |-- instance.pp
| | `-- war.pp
| |-- templates
| | |-- server.xml.erb
| | |-- start.sh.erb
| | `-- stop.sh.erb
| `-- tests
| `-- init.pp
Puppet apply gives the following:
[root@puppetmaster puppet]# puppet apply -vd --noop modules/tomcat/
tests/init.pp
info: Loading facts in facter_dot_d
info: Loading facts in facter_dot_d
warning: Could not retrieve fact fqdn
warning: Host is missing hostname and/or domain: puppetmaster
debug: importing '/etc/puppetlabs/puppet/modules/tomcat/manifests/
init.pp' in environment production
debug: Automatically imported tomcat from tomcat into production
debug: Failed to load library 'selinux' for feature 'selinux'
debug: hiera(): Hiera YAML backend starting
debug: hiera(): Looking up tomcat_instance in YAML backend
debug: hiera(): Looking for data source puppetmaster
debug: importing '/etc/puppetlabs/puppet/modules/tomcat/manifests/
instance.pp' in environment production
debug: Automatically imported tomcat::instance from tomcat/instance
into production
warning: Could not find class create_resources for puppetmaster
Could not find class create_resources at /etc/puppetlabs/puppet/
modules/tomcat/tests/init.pp:3 on node puppetmaster
Init.pp looks like this in tests:
[root@puppetmaster puppet]# cat modules/tomcat/tests/init.pp
node default {
include tomcat
include create_resources
include hiera
}
I don't understand why my class doesn't find the other classes. Can
anyone shed some light?
Thanks,
Berry Sizemore
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Could not retrieve local facts: private method `split' called for nil:NilClass
I would use puppet-enterprise-1.2.3-solaris-10-sparc instead of 1.2.1, but the installer is broken. I filed this bug on the issue - http://projects.puppetlabs.com/issues/10069 - and if the package doesn't have a problem, then I have no idea what dependency we haven't satisfied. Thanks, Berry On Oct 12, 1:25 pm, Nigel Kersten ni...@puppetlabs.com wrote: On Wed, Oct 12, 2011 at 1:17 PM, Berry Sizemore berry.sizem...@gmail.comwrote: Hi all, When I set out learning Puppet I was using the free version (not PE) and was able to do all I wanted to do running the agent as the puppet user. I recently switched to Puppet Enterprise when I hit the snag this thread is about, and continued the practice of running the agent as the puppet user. Little did I know that PE employs prtdiag where the free version apparently doesn't (it could be failing silently). This must just be a version difference somewhere in what you're running. Puppet and Facter in PE are just specific versions of the open source projects. The giveaway is the error message prtdiag can only be run in the global zone, which for you beginners like me means you aren't doing this as root when you should be, but there is surely a highly technical/philosophical discussion behind my inexpert summary. Consult the documentation and/or your Solaris system administrator for a better explanation. It's fair to say that the Puppet Enterprise agent in Solaris 10 has a dependency on the root user. Thanks, Berry Sizemore On Oct 12, 11:04 am, Berry Sizemore berry.sizem...@gmail.com wrote: Adrien, Thanks for the reply. hostxyz: facter facterversion 1.6.0 hostxyz: facter prtdiag can only be run in the global zone Error: private method `split' called for nil:NilClass -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Nigel Kersten Product Manager, Puppet Labs -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Could not retrieve local facts: private method `split' called for nil:NilClass
Adrien, Thanks for the reply. hostxyz: facter facterversion 1.6.0 hostxyz: facter prtdiag can only be run in the global zone Error: private method `split' called for nil:NilClass On Oct 12, 9:56 am, Adrien Thebo adr...@puppetlabs.com wrote: You may be running afoul ofhttp://projects.puppetlabs.com/issues/7038. What does running facter by itself do? On Tue, Oct 11, 2011 at 2:59 PM, Berry Sizemore berry.sizem...@gmail.com wrote: Hello, I am installing Puppet Enterprise agent (puppet-enterprise-1.2.1- solaris-10-sparc) on a Solaris 10 64bit SPARC system. When I view the logs for the agent I see: puppet-agent[14680]: [ID 702911 daemon.error] Could not run Puppet configuration client: Could not retrieve local facts: private method `split' called for nil:NilClass The client successfully initiates a cert exchange request to my RHEL 6 (puppet-enterprise-1.2.3-el-6-x86_64) and I sign it. That's when I see the error above on the agent host. I tried to install the 1.2.3 agent onto my Solaris box, but that installation fails. Looks like something changed in that package. Thanks, Berry -- 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+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Could not retrieve local facts: private method `split' called for nil:NilClass
Hi all, When I set out learning Puppet I was using the free version (not PE) and was able to do all I wanted to do running the agent as the puppet user. I recently switched to Puppet Enterprise when I hit the snag this thread is about, and continued the practice of running the agent as the puppet user. Little did I know that PE employs prtdiag where the free version apparently doesn't (it could be failing silently). The giveaway is the error message prtdiag can only be run in the global zone, which for you beginners like me means you aren't doing this as root when you should be, but there is surely a highly technical/philosophical discussion behind my inexpert summary. Consult the documentation and/or your Solaris system administrator for a better explanation. It's fair to say that the Puppet Enterprise agent in Solaris 10 has a dependency on the root user. Thanks, Berry Sizemore On Oct 12, 11:04 am, Berry Sizemore berry.sizem...@gmail.com wrote: Adrien, Thanks for the reply. hostxyz: facter facterversion 1.6.0 hostxyz: facter prtdiag can only be run in the global zone Error: private method `split' called for nil:NilClass -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Could not retrieve local facts: private method `split' called for nil:NilClass
Hello, I am installing Puppet Enterprise agent (puppet-enterprise-1.2.1- solaris-10-sparc) on a Solaris 10 64bit SPARC system. When I view the logs for the agent I see: puppet-agent[14680]: [ID 702911 daemon.error] Could not run Puppet configuration client: Could not retrieve local facts: private method `split' called for nil:NilClass The client successfully initiates a cert exchange request to my RHEL 6 (puppet-enterprise-1.2.3-el-6-x86_64) and I sign it. That's when I see the error above on the agent host. I tried to install the 1.2.3 agent onto my Solaris box, but that installation fails. Looks like something changed in that package. Thanks, Berry -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
