Re: [Puppet Users] Ruby 1.8.7 manifest
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi If you have used a public accessible manifest for ruby 1.8.7 ree or you are willing to share ... I am looking for one! I would look on how to generate packages for your distro for REE (if they aren't yet available) put them in a local repository and install them simply by using the package provider. scripting ./configure;make;make install with puppet exec resources is imho a bad idea. ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4RXAIACgkQbwltcAfKi39yeACgpRYf6gISbB/y1uCFsRD6MqK1 mckAn3Nz6WBIva+ANtCeWdp1H0OU9mF9 =uNG0 -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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Bug or Feature
On Fri, Jul 01, 2011 at 11:41:17AM -0700, Craig White wrote: I had a number of symbolic links for file resources and didn't consider the impact. source = puppet:///modules/$some_module/some_file_which_is_a_symbolic_link would actually transfer the link and not the content of the source link. Moving it to templates and appending .erb to the names handled things fine but I thought I should toss this out there because it was unexpected. I guess it is supposed to be feature but in my opinion its only value is when you copy a directory structure recursivly and there are possible links in that directory. However, you should get around this when you specify links = follow instead of links = manage (which appears to be the default). See http://docs.puppetlabs.com/references/stable/type.html#links -Stefan pgpdbo3Za7rEy.pgp Description: PGP signature
Re: [Puppet Users] Bug or Feature
On 07/01/2011 08:41 PM, Craig White wrote: Moving it to templates and appending .erb to the names handled things fine I think that's gratuitous. You can use templates without .erb names. Also, the file() function would be more appropriate given the circumstances. Of course, the right way is probably what Stefan wrote. Cheers, Felix -- 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] puppet master and puppet client running very slow
hi all, I have configured puppet 0.25.4 setup. since last few days , puppet master and client running very slow .It seems puppet client taking soo much time in taking configuration from master (compilation manifest ) ,specially for those node(puppet client ) for which large manifest class to be compiled and to be deployed . what can i do to over come this issue ? Thanks, Sanjiv Singh Impetus Infotech -- 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.
Re: [Puppet Users] puppet master and puppet client running very slow
On 07/04/2011 02:46 PM, sanjiv.singh wrote: hi all, I have configured puppet 0.25.4 setup. since last few days , puppet master and client running very slow .It seems puppet client taking soo much time in taking configuration from master (compilation manifest ) ,specially for those node(puppet client ) for which large manifest class to be compiled and to be deployed . what can i do to over come this issue ? What sorts of steps have you already taken in order to investigate the problem? Does the Puppetmaster have enough RAM? It is otherwise overloaded from a system load perspective? What about those two factors on the client(s)? In other words, have you eliminated all of the standard system-based considerations? If so, I would recommend running the client manually with test and debug enabled, and taking a look at the output there. As well, if it's possible, you may wish to do the same for the master daemon - that will give you a much better idea of where along the process any potential hangs are occurring. Good luck ! -- Daniel Maher « makin' plans now to live on Mars 'cuz I got Earth on lock. » -- 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: puppet master and puppet client running very slow
On Jul 4, 6:12 pm, Daniel Maher dma...@milestonelab.com wrote: On 07/04/2011 02:46 PM, sanjiv.singh wrote: hi all, I have configured puppet 0.25.4 setup. since last few days , puppet master and client running very slow .It seems puppet client taking soo much time in taking configuration from master (compilation manifest ) ,specially for those node(puppet client ) for which large manifest class to be compiled and to be deployed . what can i do to over come this issue ? What sorts of steps have you already taken in order to investigate the problem? Does the Puppetmaster have enough RAM? It is otherwise overloaded from a system load perspective? What about those two factors on the client(s)? In other words, have you eliminated all of the standard system-based considerations? If so, I would recommend running the client manually with test and debug enabled, and taking a look at the output there. As well, if it's possible, you may wish to do the same for the master daemon - that will give you a much better idea of where along the process any potential hangs are occurring. Good luck ! -- Daniel Maher makin' plans now to live on Mars 'cuz I got Earth on lock. Hi Daniel, I tried to run puppet client /usr/sbin/puppetd --test --debug there are more entries as following : . . . . debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson its throwing same entries for long time (in minutes), prior it take few seconds to get catalog from server and get deployed. and even when i fired puppetrun on master. it takes long time to trigger puppet client (listening to master). what cuold be the issue? thanks, Sanjiv singh -- 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.
Re: [Puppet Users] Re: puppet master and puppet client running very slow
How big are these manifests (ie. number of files, total lines for all files that get imported)? For example - are you pulling in a large file of all your nodes or something? I recall there has been problems in the past with parsing large files - its fixed now though. The obvious suggestion is to upgrade :-). ken. On Mon, Jul 4, 2011 at 2:35 PM, sanjiv.singh sanjiv.si...@impetus.co.in wrote: On Jul 4, 6:12 pm, Daniel Maher dma...@milestonelab.com wrote: On 07/04/2011 02:46 PM, sanjiv.singh wrote: hi all, I have configured puppet 0.25.4 setup. since last few days , puppet master and client running very slow .It seems puppet client taking soo much time in taking configuration from master (compilation manifest ) ,specially for those node(puppet client ) for which large manifest class to be compiled and to be deployed . what can i do to over come this issue ? What sorts of steps have you already taken in order to investigate the problem? Does the Puppetmaster have enough RAM? It is otherwise overloaded from a system load perspective? What about those two factors on the client(s)? In other words, have you eliminated all of the standard system-based considerations? If so, I would recommend running the client manually with test and debug enabled, and taking a look at the output there. As well, if it's possible, you may wish to do the same for the master daemon - that will give you a much better idea of where along the process any potential hangs are occurring. Good luck ! -- Daniel Maher makin' plans now to live on Mars 'cuz I got Earth on lock. Hi Daniel, I tried to run puppet client /usr/sbin/puppetd --test --debug there are more entries as following : . . . . debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson its throwing same entries for long time (in minutes), prior it take few seconds to get catalog from server and get deployed. and even when i fired puppetrun on master. it takes long time to trigger puppet client (listening to master). what cuold be the issue? thanks, Sanjiv singh -- 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. -- 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] puppetlabs-firewall gsub error
Hi, I am testing https://github.com/puppetlabs/puppetlabs-firewall and get this error: err: Could not prefetch firewall provider 'iptables': private method `gsub' called for nil:NilClass I don't know ruby so any help appreciated! -- Bjørge Solli -- 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] puppet master and puppet client running very slow
hi all, i m using puppet 0.25.4 . since last few days, client and master are very slow puppet client taking more time in geeting configuration from puppet master. specially for those servers for which long manifest to be deployed . thanks, Sanjiv Singh Impetus Infotech -- 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: puppet master and puppet client running very slow
Hi Ken, my manifest contains number of file (flat and templete ) and for pulling some jars on client. prior few days , same manifest took 2-3 minutes , now its taking 20 minutes on all puppet clients. it seems(not sure), puppet client is not bottleneck . puppet master is an issue , bcuz all puppet client facing same problem. and there is sufficient RAM and storage on puppet master. and puppet master hardly serving few (4-5) puppet client at a time in my environment. feel free to ask , if some in put require to solve issue thanks, Sanjiv Singh On Jul 4, 6:46 pm, Ken Barber k...@puppetlabs.com wrote: How big are these manifests (ie. number of files, total lines for all files that get imported)? For example - are you pulling in a large file of all your nodes or something? I recall there has been problems in the past with parsing large files - its fixed now though. The obvious suggestion is to upgrade :-). ken. On Mon, Jul 4, 2011 at 2:35 PM, sanjiv.singh sanjiv.si...@impetus.co.in wrote: On Jul 4, 6:12 pm, Daniel Maher dma...@milestonelab.com wrote: On 07/04/2011 02:46 PM, sanjiv.singh wrote: hi all, I have configured puppet 0.25.4 setup. since last few days , puppet master and client running very slow .It seems puppet client taking soo much time in taking configuration from master (compilation manifest ) ,specially for those node(puppet client ) for which large manifest class to be compiled and to be deployed . what can i do to over come this issue ? What sorts of steps have you already taken in order to investigate the problem? Does the Puppetmaster have enough RAM? It is otherwise overloaded from a system load perspective? What about those two factors on the client(s)? In other words, have you eliminated all of the standard system-based considerations? If so, I would recommend running the client manually with test and debug enabled, and taking a look at the output there. As well, if it's possible, you may wish to do the same for the master daemon - that will give you a much better idea of where along the process any potential hangs are occurring. Good luck ! -- Daniel Maher makin' plans now to live on Mars 'cuz I got Earth on lock. Hi Daniel, I tried to run puppet client /usr/sbin/puppetd --test --debug there are more entries as following : . . . . debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson its throwing same entries for long time (in minutes), prior it take few seconds to get catalog from server and get deployed. and even when i fired puppetrun on master. it takes long time to trigger puppet client (listening to master). what cuold be the issue? thanks, Sanjiv singh -- 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.
Re: [Puppet Users] puppetlabs-firewall gsub error
Hey Bjørge, Looks like a bug ... can you create an issue here? https://github.com/puppetlabs/puppetlabs-firewall/issues Can you supply the output of the command iptables-save as well in the ticket? It looks like its having trouble parsing that. ken. 2011/7/4 Bjørge Solli bjorge.so...@gmail.com: Hi, I am testing https://github.com/puppetlabs/puppetlabs-firewall and get this error: err: Could not prefetch firewall provider 'iptables': private method `gsub' called for nil:NilClass I don't know ruby so any help appreciated! -- Bjørge Solli -- 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. -- 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.
Re: [Puppet Users] Re: puppet master and puppet client running very slow
my manifest contains number of file (flat and templete ) and for pulling some jars on client. I guess I was looking to find out the specifics of how big these manifests and templates are in total on the nodes you are having specific performance issues with. You say 'big manifests' but this is a relative statement :-). If 'nothing has changed' (please confirm this with your svn/git history) then it must be something else other then content or puppet itself Without seeing your content its a hard one to trace via a mailing list, there could be a network issue and some function you are trying to execute could be lagging or having trouble resolving dns etc. Try running your puppetmasterd in the foreground using something like: puppetmasterd --no-daemonize --debug --trace --logdest console And as you do a single run, see if it gives you any clues as to what its blocking on during those 20 minutes. ken. -- 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] Puppet Module Confusions
Hello together, I have problems with my Puppet installation. I use example42 Modules as the base of my own Modules for automated deployment of Rational Application Developer. Now I have overlaps between the modules. As example. I run Puppet on the Puppetmaster. He has included the following classes as the node configuration: include dashboard include general One of my Nodes is an tomcat server with the following includes include mysql::client include tcserver include general An other Node is a client for Rational Application developer with following Includes include rad include general Now, if i run puppet on the puppet master and tomcat server I get some overlaps with the rad class. It looks like this: PuppetMaster: rad::reqdir/File[/opt/software]/ensure: created ... These are Directories only for rad class, but not for the others. TomcatServer: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate definition: Package[redhat-lsb] is already defined in file /var/data/puppet/environments/production/puppet4set/modules/ rad/manifests/reqpkg.pp at line 44; cannot redefine at /var/data/ puppet/environments/production/puppet4set/modules/tcserver/manifests/ init.pp:33 on node v00404.sbb.ch Is there maybe a bug in version 2.6.9? Thanks imase -- 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: Puppet Module Confusions
On Jul 4, 3:48 pm, imase igor.ma...@googlemail.com wrote: Hello together, I have problems with my Puppet installation. I use example42 Modules as the base of my own Modules for automated deployment of Rational Application Developer. One of my Nodes is an tomcat server with the following includes include mysql::client include tcserver include general An other Node is a client for Rational Application developer with following Includes include rad include general Now, if i run puppet on the puppet master and tomcat server I get some overlaps with the rad class. It looks like this: PuppetMaster: rad::reqdir/File[/opt/software]/ensure: created ... These are Directories only for rad class, but not for the others. Looks like your Tomcat v00404.sbb.ch node is somehow getting a include rad, which is causing the duplicate Package clash in the tcserver module, confirm this by running the following on the v00404.sbb.ch node: grep rad /var/lib/puppet/classes.txt Is the rad module something you wrote yourself? Does general include rad? Can you post your node definitions (site.pp / node.pp). It's not a bug, basically you're going to have to crawl through your node and class definitions and find out how rad is included on the same node as tcserver. A better idea is to make your rad module (assuming it's yours and not Example42) fit better with tcserver by pulling Package[redhat- lsb] out into a separate class. TomcatServer: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate definition: Package[redhat-lsb] is already defined in file /var/data/puppet/environments/production/puppet4set/modules/ rad/manifests/reqpkg.pp at line 44; cannot redefine at /var/data/ puppet/environments/production/puppet4set/modules/tcserver/manifests/ init.pp:33 on node v00404.sbb.ch Is there maybe a bug in version 2.6.9? Thanks imase -- 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: puppet master and puppet client running very slow
On Jul 4, 7:36 pm, Ken Barber k...@puppetlabs.com wrote: my manifest contains number of file (flat and templete ) and for pulling some jars on client. I guess I was looking to find out the specifics of how big these manifests and templates are in total on the nodes you are having specific performance issues with. You say 'big manifests' but this is a relative statement :-). If 'nothing has changed' (please confirm this with your svn/git history) then it must be something else other then content or puppet itself Without seeing your content its a hard one to trace via a mailing list, there could be a network issue and some function you are trying to execute could be lagging or having trouble resolving dns etc. Try running your puppetmasterd in the foreground using something like: puppetmasterd --no-daemonize --debug --trace --logdest console And as you do a single run, see if it gives you any clues as to what its blocking on during those 20 minutes. ken. Hi Ken, thanks for quick reply. as per yr suggestion , sudo /usr/sbin/puppetmasterd --no-daemonize --debug --trace --logdest console fired in puppet master there is noting seems wrong in debug trace, only taking time to do stuff. these is some clue for you that may help you to find out root cause. i have configured puppet master to log in file /var/log/puppet/ masterhttp.log . . . . . [2011-07-04 10:57:18] DEBUG close: 10.122.130.1:45575 [2011-07-04 10:57:24] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked. [2011-07-04 10:57:24] 209.251.184.24 - - [04/Jul/2011:10:57:24 EDT] GET/production/file_metadata/production/tomcat-web.xml HTTP/1.1 200 391 [2011-07-04 10:57:24] - - /production/file_metadata/production/tomcat- web.xml [2011-07-04 10:57:24] DEBUG close: 209.251.184.24:20132 [2011-07-04 10:57:24] DEBUG accept: 10.122.130.1:8767 [2011-07-04 10:56:33] ERROR OpenSSL::SSL::SSLError: /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 44:in `accept' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 44:in `listen' /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 42:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `listen' /usr/lib/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 38:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:131:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:146:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:128:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/application/ puppetmasterd.rb:122:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/sbin/puppetmasterd:66 there are in log repetted error trace for each file puppet master serving to client. thanks, Sanjiv singh -- 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: puppet master and puppet client running very slow
Sanjiv, How long does your master think that catalog compilation is taking? Look for these lines: Jul 4 15:13:53 puppetmaster puppet-master[26138]: Compiled catalog for puppetclient in environment live in 0.12 seconds And then the time for the agents applying that catalog: Jul 4 15:13:55 puppetclient puppet-agent[24198]: Finished catalog run in 1.22 seconds -Luke On Jul 4, 4:13 pm, sanjiv.singh sanjiv.si...@impetus.co.in wrote: On Jul 4, 7:36 pm, Ken Barber k...@puppetlabs.com wrote: my manifest contains number of file (flat and templete ) and for pulling some jars on client. I guess I was looking to find out the specifics of how big these manifests and templates are in total on the nodes you are having specific performance issues with. You say 'big manifests' but this is a relative statement :-). If 'nothing has changed' (please confirm this with your svn/git history) then it must be something else other then content or puppet itself Without seeing your content its a hard one to trace via a mailing list, there could be a network issue and some function you are trying to execute could be lagging or having trouble resolving dns etc. Try running your puppetmasterd in the foreground using something like: puppetmasterd --no-daemonize --debug --trace --logdest console And as you do a single run, see if it gives you any clues as to what its blocking on during those 20 minutes. ken. Hi Ken, thanks for quick reply. as per yr suggestion , sudo /usr/sbin/puppetmasterd --no-daemonize --debug --trace --logdest console fired in puppet master there is noting seems wrong in debug trace, only taking time to do stuff. these is some clue for you that may help you to find out root cause. i have configured puppet master to log in file /var/log/puppet/ masterhttp.log . . . . . [2011-07-04 10:57:18] DEBUG close: 10.122.130.1:45575 [2011-07-04 10:57:24] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked. [2011-07-04 10:57:24] 209.251.184.24 - - [04/Jul/2011:10:57:24 EDT] GET/production/file_metadata/production/tomcat-web.xml HTTP/1.1 200 391 [2011-07-04 10:57:24] - - /production/file_metadata/production/tomcat- web.xml [2011-07-04 10:57:24] DEBUG close: 209.251.184.24:20132 [2011-07-04 10:57:24] DEBUG accept: 10.122.130.1:8767 [2011-07-04 10:56:33] ERROR OpenSSL::SSL::SSLError: /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 44:in `accept' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 44:in `listen' /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 42:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `listen' /usr/lib/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 38:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:131:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:146:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:128:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/application/ puppetmasterd.rb:122:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/sbin/puppetmasterd:66 there are in log repetted error trace for each file puppet master serving to client. thanks, Sanjiv singh -- 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: puppet master and puppet client running very slow
Hi luke, thanks for quick reply. as i m able to see that puppet master taking around 7-8 seconds to compiler catalog and puppet client taking around 1106 second to apply catalog . seems strange , because some manifest and configuration (on both master and client) working fine with dozens of servers concurrently. Since Sunday getting strange behavior feel free to ask, if some more input required to resolve d issue. thanks, Sanjiv Singh On Jul 4, 8:32 pm, Luke Bigum luke.bi...@lmax.com wrote: Sanjiv, How long does your master think that catalog compilation is taking? Look for these lines: Jul 4 15:13:53 puppetmaster puppet-master[26138]: Compiled catalog for puppetclient in environment live in 0.12 seconds And then the time for the agents applying that catalog: Jul 4 15:13:55 puppetclient puppet-agent[24198]: Finished catalog run in 1.22 seconds -Luke On Jul 4, 4:13 pm, sanjiv.singh sanjiv.si...@impetus.co.in wrote: On Jul 4, 7:36 pm, Ken Barber k...@puppetlabs.com wrote: my manifest contains number of file (flat and templete ) and for pulling some jars on client. I guess I was looking to find out the specifics of how big these manifests and templates are in total on the nodes you are having specific performance issues with. You say 'big manifests' but this is a relative statement :-). If 'nothing has changed' (please confirm this with your svn/git history) then it must be something else other then content or puppet itself Without seeing your content its a hard one to trace via a mailing list, there could be a network issue and some function you are trying to execute could be lagging or having trouble resolving dns etc. Try running your puppetmasterd in the foreground using something like: puppetmasterd --no-daemonize --debug --trace --logdest console And as you do a single run, see if it gives you any clues as to what its blocking on during those 20 minutes. ken. Hi Ken, thanks for quick reply. as per yr suggestion , sudo /usr/sbin/puppetmasterd --no-daemonize --debug --trace --logdest console fired in puppet master there is noting seems wrong in debug trace, only taking time to do stuff. these is some clue for you that may help you to find out root cause. i have configured puppet master to log in file /var/log/puppet/ masterhttp.log . . . . . [2011-07-04 10:57:18] DEBUG close: 10.122.130.1:45575 [2011-07-04 10:57:24] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked. [2011-07-04 10:57:24] 209.251.184.24 - - [04/Jul/2011:10:57:24 EDT] GET/production/file_metadata/production/tomcat-web.xml HTTP/1.1 200 391 [2011-07-04 10:57:24] - - /production/file_metadata/production/tomcat- web.xml [2011-07-04 10:57:24] DEBUG close: 209.251.184.24:20132 [2011-07-04 10:57:24] DEBUG accept: 10.122.130.1:8767 [2011-07-04 10:56:33] ERROR OpenSSL::SSL::SSLError: /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 44:in `accept' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 44:in `listen' /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 42:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `listen' /usr/lib/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 38:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:131:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:146:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:128:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/application/ puppetmasterd.rb:122:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/sbin/puppetmasterd:66 there are in log repetted error trace for
Re: [Puppet Users] Re: puppet master and puppet client running very slow
Can you try the puppet run with the setting --summarize and show us the result ... (not sure if that flag was round then). ken. On Mon, Jul 4, 2011 at 5:12 PM, sanjiv.singh sanjiv.si...@impetus.co.in wrote: Hi luke, thanks for quick reply. as i m able to see that puppet master taking around 7-8 seconds to compiler catalog and puppet client taking around 1106 second to apply catalog . seems strange , because some manifest and configuration (on both master and client) working fine with dozens of servers concurrently. Since Sunday getting strange behavior feel free to ask, if some more input required to resolve d issue. thanks, Sanjiv Singh On Jul 4, 8:32 pm, Luke Bigum luke.bi...@lmax.com wrote: Sanjiv, How long does your master think that catalog compilation is taking? Look for these lines: Jul 4 15:13:53 puppetmaster puppet-master[26138]: Compiled catalog for puppetclient in environment live in 0.12 seconds And then the time for the agents applying that catalog: Jul 4 15:13:55 puppetclient puppet-agent[24198]: Finished catalog run in 1.22 seconds -Luke On Jul 4, 4:13 pm, sanjiv.singh sanjiv.si...@impetus.co.in wrote: On Jul 4, 7:36 pm, Ken Barber k...@puppetlabs.com wrote: my manifest contains number of file (flat and templete ) and for pulling some jars on client. I guess I was looking to find out the specifics of how big these manifests and templates are in total on the nodes you are having specific performance issues with. You say 'big manifests' but this is a relative statement :-). If 'nothing has changed' (please confirm this with your svn/git history) then it must be something else other then content or puppet itself Without seeing your content its a hard one to trace via a mailing list, there could be a network issue and some function you are trying to execute could be lagging or having trouble resolving dns etc. Try running your puppetmasterd in the foreground using something like: puppetmasterd --no-daemonize --debug --trace --logdest console And as you do a single run, see if it gives you any clues as to what its blocking on during those 20 minutes. ken. Hi Ken, thanks for quick reply. as per yr suggestion , sudo /usr/sbin/puppetmasterd --no-daemonize --debug --trace --logdest console fired in puppet master there is noting seems wrong in debug trace, only taking time to do stuff. these is some clue for you that may help you to find out root cause. i have configured puppet master to log in file /var/log/puppet/ masterhttp.log . . . . . [2011-07-04 10:57:18] DEBUG close: 10.122.130.1:45575 [2011-07-04 10:57:24] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked. [2011-07-04 10:57:24] 209.251.184.24 - - [04/Jul/2011:10:57:24 EDT] GET/production/file_metadata/production/tomcat-web.xml HTTP/1.1 200 391 [2011-07-04 10:57:24] - - /production/file_metadata/production/tomcat- web.xml [2011-07-04 10:57:24] DEBUG close: 209.251.184.24:20132 [2011-07-04 10:57:24] DEBUG accept: 10.122.130.1:8767 [2011-07-04 10:56:33] ERROR OpenSSL::SSL::SSLError: /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 44:in `accept' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 44:in `listen' /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 42:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 41:in `listen' /usr/lib/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: 38:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:131:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:146:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:128:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/application/ puppetmasterd.rb:122:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
Re: [Puppet Users] Re: err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target File[]
Forgive my cluelessness, but why is it so difficult for Puppet to at least tell me what file this came from like 90% of other errors I've encountered? On Sat, Jul 2, 2011 at 12:33 PM, vagn scott vagnsc...@gmail.com wrote: On 07/02/2011 03:20 PM, Eric Sorenson wrote: This is usually because somewhere you have a File resource whose name is a variable, and the variable's undefined. And a common reason for that to happen is that you've mistyped the variable name. Your design could be just fine. This is a good reason to test early and often. It reduces the search space to those files you recently touched. -- vagn -- 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 puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://groups.google.com/group/puppet-users?hl=en . -- Michael T. Halligan | DevOps Evangelist | @mhalligan | 415.722.1101 -- 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.
Re: [Puppet Users] Re: puppet master and puppet client running very slow
On Jul 4, 2011, at 6:35 AM, sanjiv.singh wrote: On Jul 4, 6:12 pm, Daniel Maher dma...@milestonelab.com wrote: On 07/04/2011 02:46 PM, sanjiv.singh wrote: hi all, I have configured puppet 0.25.4 setup. since last few days , puppet master and client running very slow .It seems puppet client taking soo much time in taking configuration from master (compilation manifest ) ,specially for those node(puppet client ) for which large manifest class to be compiled and to be deployed . what can i do to over come this issue ? What sorts of steps have you already taken in order to investigate the problem? Does the Puppetmaster have enough RAM? It is otherwise overloaded from a system load perspective? What about those two factors on the client(s)? In other words, have you eliminated all of the standard system-based considerations? If so, I would recommend running the client manually with test and debug enabled, and taking a look at the output there. As well, if it's possible, you may wish to do the same for the master daemon - that will give you a much better idea of where along the process any potential hangs are occurring. Good luck ! -- Daniel Maher makin' plans now to live on Mars 'cuz I got Earth on lock. Hi Daniel, I tried to run puppet client /usr/sbin/puppetd --test --debug there are more entries as following : . . . . debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson its throwing same entries for long time (in minutes), prior it take few seconds to get catalog from server and get deployed. I'm pretty sure those entries you are looking at are file resources. In general, file resources scale very poorly with webrick. Even without webrick, they still tend to perform poorly. My advice: Stop using webrick Take a look at recuse=remote if you use recursive file copies a lot Make sure you're not swapping and that you have enough ram Consider copying big files or directories with a lot of files with a package or tar+wget. -- 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.
Re: [Puppet Users] Re: puppet master and puppet client running very slow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 as i m able to see that puppet master taking around 7-8 seconds to compiler catalog and puppet client taking around 1106 second to apply catalog . run the client with --summarize and see on which resource types it is spending most of the time, then you can probably figure out what is wrong. also analyzing the reports with something like the dashboard or the foreman can help to trace these issues. Certainly something within your environment or its dependencies has changed. Puppet is heavily calling out to tools like facter, package managers, service scripts etc. which all can easily affect your puppet runs. ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4R+mcACgkQbwltcAfKi3/d/QCeODSqHvF8OxULMcbw6gfuEOT9 noMAn2b0DySrqrZ27kA6Xfvb1WaVWKdX =pHX/ -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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target File[]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/04/2011 08:49 PM, Michael Halligan wrote: Forgive my cluelessness, but why is it so difficult for Puppet to at least tell me what file this came from like 90% of other errors I've encountered? I don't think there is a particular reason. Did you look for bugreports and/or submitted an error message improvement request? ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4SNOoACgkQbwltcAfKi38J0wCaA6xk3UiaUEXrxu3gVKbKYO2l UHMAnRFfJc4icgV7Srt6Darz2Q54cqQO =L6+R -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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target File[]
On 07/04/2011 02:49 PM, Michael Halligan wrote: Forgive my cluelessness, but why is it so difficult for Puppet to at least tell me what file this came from OK, I'll take a crack at an answer. --- typical compiler versus parser problem. If the parser saw this, it could stop immediately and say , hey, look here! This ain't right! File[ $foo But, the parser sees this, which is perfectly OK. File[ $foo ] Much later, after all the files are read and the details of syntax forgotten, it is finally evaluated by the compiler as something not OK. File[ ] But, where is the error? Is it that $foo was not set? Or was $foo dependent on something else, far removed, that failed to be set or evaluated? What should the compiler say about this? $foo = inline_template( ... ) $baz = inline_template( ... ) File[ $foo$baz ] -- vagn -- 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: puppet master and puppet client running very slow
On Jul 4, 10:37 pm, Peter Meier peter.me...@immerda.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
as i m able to see that puppet master taking around 7-8 seconds to
compiler catalog
and puppet client taking around 1106 second to apply catalog .
run the client with --summarize and see on which resource types it is
spending most of the time, then you can probably figure out what is wrong.
also analyzing the reports with something like the dashboard or the
foreman can help to trace these issues.
Certainly something within your environment or its dependencies has
changed. Puppet is heavily calling out to tools like facter, package
managers, service scripts etc. which all can easily affect your puppet runs.
~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
iEYEARECAAYFAk4R+mcACgkQbwltcAfKi3/d/QCeODSqHvF8OxULMcbw6gfuEOT9
noMAn2b0DySrqrZ27kA6Xfvb1WaVWKdX
=pHX/
-END PGP SIGNATURE-
Hi Peter,
thanks for quick reply .
as per yr suggestion , i have tried --summarize option on both puppet
master and client.
here is all the details,
(on puppet master)
sudo /usr/sbin/puppetrun -c generic::pb11-8Maintenance --summarize
generic::pb11-8Maintenance: pb11-8.puppet.com
Triggering pb11-8.puppet.com
pb11-8.puppet.com finished with exit code 0
Finished
but , it took around 5-6 minutes only to trigger puppet client(listen
for puppet master).
(on puppet client )
sudo /usr/sbin/puppetd --test --debug --summarize
.
.
.
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/content: Executing 'diff -u /var/lib/dmb/conf/
memcached.properties /tmp/puppet-diffing.8146.0'
--- /var/lib/dmb/conf/memcached.properties 2011-07-04
12:55:13.0 -0400
+++ /tmp/puppet-diffing.8146.0 2011-07-04 23:13:08.0 -0400
@@ -1,4 +1,4 @@
-memcached.servers=10.122.215.42:11211,10.122.215.41:11211
+memcached.servers=pb11-9:10.122.215.42,pb11-8:10.122.215.41:11211
memcached.weights=2
memcached.init.connections=5
memcached.min.connections=5
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]: Changing checksum,content
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]: 2 change(s)
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/checksum: Replacing /var/lib/dmb/conf/
memcached.properties checksum {md5}c428ee9bfadf4893267d39585ecac0fd
with {md5}496f78a690517e9d4a3a05c7248de0b2
notice: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/checksum: checksum changed '{md5}
c428ee9bfadf4893267d39585ecac0fd' to '{md5}
496f78a690517e9d4a3a05c7248de0b2'
info: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]: Filebucketed /var/lib/dmb/conf/
memcached.properties to puppet with sum
496f78a690517e9d4a3a05c7248de0b2
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/checksum: Replacing /var/lib/dmb/conf/
memcached.properties checksum {md5}496f78a690517e9d4a3a05c7248de0b2
with {md5}c428ee9bfadf4893267d39585ecac0fd
notice: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/content: content changed '{md5}
496f78a690517e9d4a3a05c7248de0b2' to 'unknown checksum'
..
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
.
.
.
.
.
debug: Time for triggering 1 events to
[Puppet Users] proposed syntax: order { }
Sometimes things just have to happen in sequence.
It is the simplest of relations, but puppet really
has no convenient, non-fiddly way to express it.
So, how about
class x {
order { z:
file { a:
...
}
exec {
b: ... ;
c: ... ;
d: ... ;
e: ... ;
}
}
}
Things inside order { } happen in the order
that they appear. They implicitly have before
dependency assigned according to their position.
--
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.
Re: [Puppet Users] proposed syntax: order { }
I take it you're not familiar with the `requires' parameter.
On Mon, Jul 4, 2011 at 8:40 PM, vagn scott vagnsc...@gmail.com wrote:
Sometimes things just have to happen in sequence.
It is the simplest of relations, but puppet really
has no convenient, non-fiddly way to express it.
So, how about
class x {
order { z:
file { a:
...
}
exec {
b: ... ;
c: ... ;
d: ... ;
e: ... ;
}
}
}
Things inside order { } happen in the order
that they appear. They implicitly have before
dependency assigned according to their position.
--
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 puppet-users%2bunsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/**
group/puppet-users?hl=enhttp://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.
Re: [Puppet Users] proposed syntax: order { }
On 07/04/2011 11:42 PM, Scott Smith wrote: I take it you're not familiar with the `requires' parameter. I'm familiar with requires subscribe notifies - - before which are great for specifying relations between non-adjacent things. But they are annoying to use for resources close together in a text file. It just reads like noise. -- 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.
Re: [Puppet Users] proposed syntax: order { }
Ignoring the fact that noise is very subjective... it doesn't. In Puppet, position in a file has no bearing on order. It's not an imperative language. On Mon, Jul 4, 2011 at 8:46 PM, vagn scott vagnsc...@gmail.com wrote: On 07/04/2011 11:42 PM, Scott Smith wrote: I take it you're not familiar with the `requires' parameter. I'm familiar with requires subscribe notifies - - before which are great for specifying relations between non-adjacent things. But they are annoying to use for resources close together in a text file. It just reads like noise. -- 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 puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://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.
Re: [Puppet Users] Re: err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target File[]
Why would you pass the output from inline_template as the title of a resource? On Mon, Jul 4, 2011 at 8:03 PM, vagn scott vagnsc...@gmail.com wrote: $foo = inline_template( ... ) $baz = inline_template( ... ) File[ $foo$baz ] -- vagn -- 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 puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://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.
Re: [Puppet Users] proposed syntax: order { }
On 07/04/2011 11:51 PM, Scott Smith wrote:
Ignoring the fact that noise is very subjective... it doesn't. In
Puppet, position in a file has no bearing on order. It's not an
imperative language.
I understand. What I am saying is that another way to express this
file { a:
path = aaa ,
before = Exec[ b ],
}
exec { b:
command = bbb,
before = File[ c ],
}
file { c:
path = ccc ,
before = Exec[ d ],
}
would be this:
order {
file { aaa:
}
exec { bbb:
}
file { ccc:
}
}
--
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.
Re: [Puppet Users] proposed syntax: order { }
On 07/04/2011 11:56 PM, vagn scott wrote:
On 07/04/2011 11:51 PM, Scott Smith wrote:
Ignoring the fact that noise is very subjective... it doesn't. In
Puppet, position in a file has no bearing on order. It's not an
imperative language.
Oops, that should be:
file { a:
path = aaa ,
before = Exec[ b ],
}
exec { b:
command = bbb,
before = File[ c ],
}
file { c:
path = ccc ,
}
same as:
order { z:
file { aaa:
}
exec { bbb:
}
file { ccc:
}
}
With the added benefit that you could do
Order[ z ] - Something[ foo ]
--
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: puppet master and puppet client running very slow
some times puppet client fails with following...
debug: Loaded state in 0.01 seconds
debug: Using cached certificate for ca
debug: Using cached certificate for pb11-9.domain.local
debug: Using cached certificate_revocation_list for ca
debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml;
using pson
err: Could not retrieve catalog from remote server: Could not intern
from pson: expected value in object at 'File[/var/lib/'!
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
thanks,
Sanjiv Singh
On Jul 5, 8:35 am, sanjiv.singh sanjiv.si...@impetus.co.in wrote:
On Jul 4, 10:37 pm, Peter Meier peter.me...@immerda.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
as i m able to see that puppet master taking around 7-8 seconds to
compiler catalog
and puppet client taking around 1106 second to apply catalog .
run the client with --summarize and see on which resource types it is
spending most of the time, then you can probably figure out what is wrong.
also analyzing the reports with something like the dashboard or the
foreman can help to trace these issues.
Certainly something within your environment or its dependencies has
changed. Puppet is heavily calling out to tools like facter, package
managers, service scripts etc. which all can easily affect your puppet runs.
~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
iEYEARECAAYFAk4R+mcACgkQbwltcAfKi3/d/QCeODSqHvF8OxULMcbw6gfuEOT9
noMAn2b0DySrqrZ27kA6Xfvb1WaVWKdX
=pHX/
-END PGP SIGNATURE-
Hi Peter,
thanks for quick reply .
as per yr suggestion , i have tried --summarize option on both puppet
master and client.
here is all the details,
(on puppet master)
sudo /usr/sbin/puppetrun -c generic::pb11-8Maintenance --summarize
generic::pb11-8Maintenance: pb11-8.puppet.com
Triggering pb11-8.puppet.com
pb11-8.puppet.com finished with exit code 0
Finished
but , it took around 5-6 minutes only to trigger puppet client(listen
for puppet master).
(on puppet client )
sudo /usr/sbin/puppetd --test --debug --summarize
.
.
.
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/content: Executing 'diff -u /var/lib/dmb/conf/
memcached.properties /tmp/puppet-diffing.8146.0'
--- /var/lib/dmb/conf/memcached.properties 2011-07-04
12:55:13.0 -0400
+++ /tmp/puppet-diffing.8146.0 2011-07-04 23:13:08.0 -0400
@@ -1,4 +1,4 @@
-memcached.servers=10.122.215.42:11211,10.122.215.41:11211
+memcached.servers=pb11-9:10.122.215.42,pb11-8:10.122.215.41:11211
memcached.weights=2
memcached.init.connections=5
memcached.min.connections=5
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]: Changing checksum,content
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]: 2 change(s)
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/checksum: Replacing /var/lib/dmb/conf/
memcached.properties checksum {md5}c428ee9bfadf4893267d39585ecac0fd
with {md5}496f78a690517e9d4a3a05c7248de0b2
notice: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/checksum: checksum changed '{md5}
c428ee9bfadf4893267d39585ecac0fd' to '{md5}
496f78a690517e9d4a3a05c7248de0b2'
info: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]: Filebucketed /var/lib/dmb/conf/
memcached.properties to puppet with sum
496f78a690517e9d4a3a05c7248de0b2
debug: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/checksum: Replacing /var/lib/dmb/conf/
memcached.properties checksum {md5}496f78a690517e9d4a3a05c7248de0b2
with {md5}c428ee9bfadf4893267d39585ecac0fd
notice: //templatebasedapplicationconfigs/File[/var/lib/dmb/conf/
memcached.properties]/content: content changed '{md5}
496f78a690517e9d4a3a05c7248de0b2' to 'unknown checksum'
..
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata
Re: [Puppet Users] Re: puppet master and puppet client running very slow
Is the client healthy? File system not full? No errors in log files, like a disk might be failing? Load average reasonable? Any network changes? Do you have a switch plugged into itself? what does tcpdump show? Normal activity? -- vagn On 07/05/2011 12:11 AM, sanjiv.singh wrote: some times puppet client fails with following... debug: Loaded state in 0.01 seconds debug: Using cached certificate for ca debug: Using cached certificate for pb11-9.domain.local debug: Using cached certificate_revocation_list for ca debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson err: Could not retrieve catalog from remote server: Could not intern from pson: expected value in object at 'File[/var/lib/'! warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run thanks, Sanjiv Singh -- 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.
Re: [Puppet Users] Re: err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target File[]
Because the name depends on other parameters in a non-trivial way. But that's neither here nor there. remeber the context: We were talking about parser v compiler error reporting. -- vagn On 07/04/2011 11:53 PM, Scott Smith wrote: Why would you pass the output from inline_template as the title of a resource? On Mon, Jul 4, 2011 at 8:03 PM, vagn scott vagnsc...@gmail.com mailto:vagnsc...@gmail.com wrote: $foo = inline_template( ... ) $baz = inline_template( ... ) File[ $foo$baz ] -- 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.
Re: [Puppet Users] proposed syntax: order { }
Thinking about this some more, I like block better,
with order optional:
class c {
block { x:# any order
package { ... }
file { aaa: }
exec { bbb: }
file { ccc: }
include foo
}
block { y:# order matters
$ordered = true # default is false
file { ddd: }
exec { eee: }
include baz
file { fff: }
}
block { z: # any order
file { ggg: }
exec { hhh: }
file { iii: }
}
Block[ x ] - Block[ y ] - Block[ z ]
}
meaning all in x before any in y, then y in sequence,
before any in z
--
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.
Re: [Puppet Users] proposed syntax: order { }
Whatever problem you are trying to solve is most likely best handled outside
of Puppet.
On Mon, Jul 4, 2011 at 9:59 PM, vagn scott vagnsc...@gmail.com wrote:
Thinking about this some more, I like block better,
with order optional:
class c {
block { x:# any order
package { ... }
file { aaa: }
exec { bbb: }
file { ccc: }
include foo
}
block { y:# order matters
$ordered = true # default is false
file { ddd: }
exec { eee: }
include baz
file { fff: }
}
block { z: # any order
file { ggg: }
exec { hhh: }
file { iii: }
}
Block[ x ] - Block[ y ] - Block[ z ]
}
meaning all in x before any in y, then y in sequence,
before any in z
--
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 puppet-users%2bunsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/**
group/puppet-users?hl=enhttp://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.
Re: [Puppet Users] proposed syntax: order { }
On 07/05/2011 01:08 AM, Scott Smith wrote: Whatever problem you are trying to solve is most likely best handled outside of Puppet. The problem I'm trying to solve is one of expressiveness in the language. I'm not adding any functionality that is not already in puppet. I'm just suggesting there are better (more readable, less tedious) ways to express it. -- vagn -- 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.
