[Puppet Users] Report processor failed: String can't be coerced into Fixnum
I'm trying to make the custom report process (described here https://puppetlabs.com/blog/when-puppet-reports-part-2/) work on my agent, but keep getting this error in master log: Report processor failed: String can't be coerced into Fixnum I'm out of ideas why could it fail. Will appreciate any help. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Report processor failed: String can't be coerced into Fixnum
For some reason Puppet doesn't like the self.configuration_version On Saturday, April 6, 2013 10:43:24 AM UTC+3, Andriy Yurchuk wrote: I'm trying to make the custom report process (described here https://puppetlabs.com/blog/when-puppet-reports-part-2/) work on my agent, but keep getting this error in master log: Report processor failed: String can't be coerced into Fixnum I'm out of ideas why could it fail. Will appreciate any help. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Problem on live-management - Node list missing - User -Find Resources not working
edit:
they just send an email that its a bug you can download the bugfixes here:
https://puppetlabs.com/puppet-enterprise-hotfixes-2-8-0/?utm_campaign=pe280updateutm_medium=emailutm_source=peusersutm_content=hotfixesmkt_tok=3RkMMJWWfF9wsRokvazNZKXonjHpfsX67OsuW6G1lMI%2F0ER3fOvrPUfGjI4CTMZkI%2FqLAzICFpZo2FFID%2FCFeZRM%2B%2FdO
original text i got via email:
Hi there,
We've found an issue in Puppet Enterprise 2.8.0 that keeps live management
from functioning and prevents MCollective from using filters.
We have prepared a partial upgrade package that fully resolves this issue.
If you have installed 2.8.0, you can download the package fix
herehttp://email.puppetlabs.com/track?type=clickenid=bWFpbGluZ2lkPXB1cHBldGxhYnNCZXRhY3VzdC0yNjA0LTc1MTgtMC0zMDQ2LXByb2QtNTQxNyZtZXNzYWdlaWQ9MCZkYXRhYmFzZWlkPTU0MTcmc2VyaWFsPTEyNjU1NjIzNDgmZW1haWxpZD1sb2VrZW5AaW50ZXJuZXR6Lm1lJnVzZXJpZD0yNzczMjYzJmV4dHJhPSYmJg==https://puppetlabs.com/puppet-enterprise-hotfixes-2-8-0/?utm_campaign=pe280updateutm_medium=emailutm_source=peusersutm_content=hotfixesmkt_tok=3RkMMJWWfF9wsRokvazNZKXonjHpfsX67OsuW6G1lMI%2F0ER3fOvrPUfGjI4CTMZkI%2FqLAzICFpZo2FFID%2FCFeZRM%2B%2FdO
.
We have also temporarily pulled PE 2.8.0 from our download
pagehttp://email.puppetlabs.com/track?type=clickenid=bWFpbGluZ2lkPXB1cHBldGxhYnNCZXRhY3VzdC0yNjA0LTc1MTgtMC0zMDQ2LXByb2QtNTQxNyZtZXNzYWdlaWQ9MCZkYXRhYmFzZWlkPTU0MTcmc2VyaWFsPTEyNjU1NjIzNDgmZW1haWxpZD1sb2VrZW5AaW50ZXJuZXR6Lm1lJnVzZXJpZD0yNzczMjYzJmV4dHJhPSYmJg==https://puppetlabs.com/misc/pe-files/?utm_campaign=pe280updateutm_medium=emailutm_source=peusersutm_content=downloadpagemkt_tok=3RkMMJWWfF9wsRokvazNZKXonjHpfsX67OsuW6G1lMI%2F0ER3fOvrPUfGjI4CTMZkI%2FqLAzICFpZo2FFID%2FCFeZRM%2B%2FdO,
and plan to release a fixed PE 2.8.1 sometime next week. We will notify you
about the availability of PE 2.8.1 when it is released.
If you have additional questions or concerns, you are welcome to contact us
at
supp...@puppetlabs.comhttp://email.puppetlabs.com/track?type=clickenid=bWFpbGluZ2lkPXB1cHBldGxhYnNCZXRhY3VzdC0yNjA0LTc1MTgtMC0zMDQ2LXByb2QtNTQxNyZtZXNzYWdlaWQ9MCZkYXRhYmFzZWlkPTU0MTcmc2VyaWFsPTEyNjU1NjIzNDgmZW1haWxpZD1sb2VrZW5AaW50ZXJuZXR6Lm1lJnVzZXJpZD0yNzczMjYzJmV4dHJhPSYmJg==mailto:supp...@puppetlabs.com?mkt_tok=3RkMMJWWfF9wsRokvazNZKXonjHpfsX67OsuW6G1lMI%2F0ER3fOvrPUfGjI4CTMZkI%2FqLAzICFpZo2FFID%2FCFeZRM%2B%2FdO
.
Best,
The Puppet Enterprise Support Team
Am Sonntag, 31. März 2013 00:13:00 UTC+1 schrieb Juan Pablo Baudoin:
Hello
I'm testing Puppet Enterprise 2.7 and I'm having the following problem.
When I go to live-management, the node list sometimes is missing.
https://lh3.googleusercontent.com/-r3mhNTK8CH8/UVdw3AaHfjI/APs/T6i_Pg4hufM/s1600/err_nodes_missing.png
This behavior is random, but when It happend I find the following error on
the logs:
== pe-httpd/error.log ==
INFO Sat Mar 30 20:04:09 -0300 2013: memcached saving
[raw_agent_inventory] [4940e0b29c08b35a29d4e4b0c63d1304] -
[[#MCollective::RPC::Result:0x7f33fa190250
@results={:data={:agents=[{:agent=discovery, :license=Apache
License, Version 2, :version=unknown, :url=unknown,
:description=unknown, :name=discovery, :author=R.I.Pienaar x
, :] [3631]
INFO Sat Mar 30 20:04:09 -0300 2013: memcached retrieving [empty_filter]
[7bc4614f5252e68308196a74a0cac980] = [nil] [3]
Stomp::Error::NoCurrentConnection - no current connection exists:
/opt/puppet/lib/gems/1.8/gems/stomp-1.2.3/lib/stomp/connection.rb:334:in
`publish'
/opt/puppet/libexec/mcollective/mcollective/connector/stomp.rb:189:in
`send'
/opt/puppet/lib/site_ruby/1.8/mcollective/client.rb:65:in `sendreq'
/opt/puppet/lib/ruby/1.8/timeout.rb:67:in `timeout'
When the list appears, and I try to use the Find Resources buton under
User, It stay wiht the message: Finding user resources
https://lh5.googleusercontent.com/-gp9pnq3REzI/UVdw6a3wUkI/AP0/Nl4QyvQFDRQ/s1600/err_find_resources.png
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet on Xen Server
Hi Zane, Because you installed from gems you do not have the config files set up for you. You need to place a config in /etc/puppet/puppet.conf to control the binary. Also create an init script in /etc/init.d/puppet for the start stop restart. Just out of curiosity are you using Citrix Xenserver or opensource xen? 2013/4/6 Zane Williamson zane.william...@gmail.com Looks like I got it to install, but curious where the configuration information for puppet agent lives when installing it via ruby gems. Could you point me in the right direction? On Thursday, August 9, 2012 2:23:09 PM UTC-7, vioilly wrote: ok.. so (roughly) here's what I did to get the puppet client to install on xenserver Installed ruby from this repo http://centos.karan.org/el5/**ruby187/i386/http://centos.karan.org/el5/ruby187/i386/ you need these rpms installed for ruby rpm -qa | grep ruby ruby-libs-1.8.7.299-4.el5.kb ruby-irb-1.8.7.299-4.el5.kb ruby-ri-1.8.7.299-4.el5.kb ruby-1.8.7.299-4.el5.kb ruby-rdoc-1.8.7.299-4.el5.kb run ruby -v to check you have ruby install [user@xenserver ~]# ruby -v ruby 1.8.7 (2010-06-23 patchlevel 299) [i386-linux] installed gem using yum install rubygem-gem2rpm installed puppet using gem install puppet --no-rdoc --no-ri Hope that helps someone else. Thanks to Martin for his help on this.. On Thursday, August 9, 2012 4:51:01 PM UTC+1, mawi wrote: I install and upgrade puppet from gems gem install puppet --no-rdoc --no-ri 2012/8/9 vioilly olive...@gmail.com Hi, I am also looking at getting puppet on xenserver I used this repo http://centos.karan.org/el5/**ruby187/i386/http://centos.karan.org/el5/ruby187/i386/and ran wget on each of the 5 rpms and then used rpm -i not a pretty way of doing things but I do have ruby installed now, then same as martin. However hitting brick walls with yum install puppet using the puppetlabs repo Anyone else got a solution to this thread.. would help others i assume? Vioilly On Tuesday, June 12, 2012 4:49:45 PM UTC+1, John Guthrie wrote: Martin, Thank you for providing that information. We were wondering which repository you were using to get those RPMs. We used yum to search for those RPMs on XenServer 5.6 (the earliest that we have) and we weren't able to find any of those RPMs. We weren't able to find them on our distribution CDs either. Thanks again. John Guthrie jgut...@book.com On 2012-05-31 19:34, Martin Willemsma wrote: Hi John, We have puppet running on Xenserver. Please note that Citrix can start complaining about 'unsupported custom modifications' to the host in case you have a technical support contract. ruby -v ruby 1.8.7 (2010-06-23 patchlevel 299) [i386-linux] I have these packages installed on XenServer release 5.5.0 rpm -qa | grep ruby ruby-libs-1.8.7.299-4.el5.kb ruby-irb-1.8.7.299-4.el5.kb ruby-ri-1.8.7.299-4.el5.kb ruby-1.8.7.299-4.el5.kb ruby-rdoc-1.8.7.299-4.el5.kb cat /etc/redhat-release XenServer release 5.5.0-15119p (xenenterprise) Also rolled our own for CentOS those are not installed yet on this machine. --- Best regards Martin 2012/6/1 Timothy Suttont...@synthist.net: I've only ever installed a handful of 3rd-party tools on XenServer, but it was usually a matter of finding EL5-compatible rpms from an external repo and installing those. Tim On 2012-05-31, at 1:59 PM, John Guthriejgut...@book.com wrote: Has anyone had any luck installing puppet on Citrix Xenserver? It appears that there is no ruby package for the OS itself, and we ran into dependency issues when we tried to compile our own ruby. Thanks. John Guthrie jgut...@book.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@** 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...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@** 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. This electronic mail message contains information that (a) is or may be CONFIDENTIAL, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named herein. If you are not an intended recipient, please contact the sender immediately and take the steps necessary to delete the message completely from your computer system. Not Intended as a Substitute for a
Re: [Puppet Users] puppet on Xen Server
Thanks Marin, I have XCP 1.6 installed now. I wanted to see if I could use my default puppet manifests on it but it appears it will be a pain to integrate. -Zane On Sat, Apr 6, 2013 at 5:55 AM, Martin Willemsma mwillem...@gmail.comwrote: Hi Zane, Because you installed from gems you do not have the config files set up for you. You need to place a config in /etc/puppet/puppet.conf to control the binary. Also create an init script in /etc/init.d/puppet for the start stop restart. Just out of curiosity are you using Citrix Xenserver or opensource xen? 2013/4/6 Zane Williamson zane.william...@gmail.com Looks like I got it to install, but curious where the configuration information for puppet agent lives when installing it via ruby gems. Could you point me in the right direction? On Thursday, August 9, 2012 2:23:09 PM UTC-7, vioilly wrote: ok.. so (roughly) here's what I did to get the puppet client to install on xenserver Installed ruby from this repo http://centos.karan.org/el5/**ruby187/i386/http://centos.karan.org/el5/ruby187/i386/ you need these rpms installed for ruby rpm -qa | grep ruby ruby-libs-1.8.7.299-4.el5.kb ruby-irb-1.8.7.299-4.el5.kb ruby-ri-1.8.7.299-4.el5.kb ruby-1.8.7.299-4.el5.kb ruby-rdoc-1.8.7.299-4.el5.kb run ruby -v to check you have ruby install [user@xenserver ~]# ruby -v ruby 1.8.7 (2010-06-23 patchlevel 299) [i386-linux] installed gem using yum install rubygem-gem2rpm installed puppet using gem install puppet --no-rdoc --no-ri Hope that helps someone else. Thanks to Martin for his help on this.. On Thursday, August 9, 2012 4:51:01 PM UTC+1, mawi wrote: I install and upgrade puppet from gems gem install puppet --no-rdoc --no-ri 2012/8/9 vioilly olive...@gmail.com Hi, I am also looking at getting puppet on xenserver I used this repo http://centos.karan.org/el5/**ruby187/i386/http://centos.karan.org/el5/ruby187/i386/and ran wget on each of the 5 rpms and then used rpm -i not a pretty way of doing things but I do have ruby installed now, then same as martin. However hitting brick walls with yum install puppet using the puppetlabs repo Anyone else got a solution to this thread.. would help others i assume? Vioilly On Tuesday, June 12, 2012 4:49:45 PM UTC+1, John Guthrie wrote: Martin, Thank you for providing that information. We were wondering which repository you were using to get those RPMs. We used yum to search for those RPMs on XenServer 5.6 (the earliest that we have) and we weren't able to find any of those RPMs. We weren't able to find them on our distribution CDs either. Thanks again. John Guthrie jgut...@book.com On 2012-05-31 19:34, Martin Willemsma wrote: Hi John, We have puppet running on Xenserver. Please note that Citrix can start complaining about 'unsupported custom modifications' to the host in case you have a technical support contract. ruby -v ruby 1.8.7 (2010-06-23 patchlevel 299) [i386-linux] I have these packages installed on XenServer release 5.5.0 rpm -qa | grep ruby ruby-libs-1.8.7.299-4.el5.kb ruby-irb-1.8.7.299-4.el5.kb ruby-ri-1.8.7.299-4.el5.kb ruby-1.8.7.299-4.el5.kb ruby-rdoc-1.8.7.299-4.el5.kb cat /etc/redhat-release XenServer release 5.5.0-15119p (xenenterprise) Also rolled our own for CentOS those are not installed yet on this machine. --- Best regards Martin 2012/6/1 Timothy Suttont...@synthist.net: I've only ever installed a handful of 3rd-party tools on XenServer, but it was usually a matter of finding EL5-compatible rpms from an external repo and installing those. Tim On 2012-05-31, at 1:59 PM, John Guthriejgut...@book.com wrote: Has anyone had any luck installing puppet on Citrix Xenserver? It appears that there is no ruby package for the OS itself, and we ran into dependency issues when we tried to compile our own ruby. Thanks. John Guthrie jgut...@book.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@** 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...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@** 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. This electronic mail message contains information that (a) is or may be CONFIDENTIAL, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for
Re: [Puppet Users] Using Puppet for Application package installation
Greetings, We are using Puppet to deploy application packages, so it can indeed be done. However, you need to do some work around Puppet to enable the use cases you've mentioned: * Something builds the package * Something publishes the package to the yum repo * Something kicks Puppet on the node(s) you want to install on (either starting it up in daemon mode or executing it) * Someone (or something) ensures that package declarations are properly assigned to your node. * At this point, Puppet takes over, figures out what packages need to be installed/upgraded, and handles that for you, in addition to whatever configuration and service control you've specified. In short: you need a build/deployment system that uses Puppet configuration management at its core. In our case, we glued this together ourselves. Some things to be aware of: * To use the YUM package provider, Puppet must run as root. Therefore, whatever kicks Puppet has to run as root as well. We use MCollective for this, which involves a root agent running as a daemon on the endpoint. * Puppet's RPM/YUM providers install packages as root into the standard system RPMDB. So, you can see, by going this route your application packages are going to be handled just like any other system package. In other words, the key to making this easy is this: though the user doesn't have root access on the node, the deployment system does. You control who can do what to the node through authentication and authorization in the deployment system itself, and by constraining the set of operations that the deployment system supports. Let's say this solution isn't a possibility: for example, you use a custom user/RPMDBs/prefix/RPMRC when installing via RPM. You *can* theoretically make this work with Puppet, but you've got a lot of work on your hands, because the existing package type/providers don't support it. You have my sympathy, because that's where we've been, and over the years we've banged our head against that wall so many times, for many reasons besides Puppet. One of our tenets in moving to Puppet, however, was to stop doing things that made our life needlessly difficult. :-) If you go this way, you also need to give some thought as to how you want to upgrade an existing application on the endpoint. One way is to use 'ensure = latest' and configure the YUM repo on the node to point to a new repo with your updated packages when the time comes. Another possibility is to use 'ensure = present' and do an explicit 'yum upgrade' operation through MCollective to get the packages updated; then run Puppet to fix up the rest. Hope this helps! -- O On Apr 4, 2013, at 6:39 AM, Dhaval wrote: Hello Guys, i want to know, can we use puppet to install application packages ( not system packages ) .. if yes how , if someone can through some light .. my requirement is 1) application team can create package on their own and update in yum repo ( without root ) 2) application team can install package on their own ( without root ) to the directories mention in rpm .. let me know if anyone is aware of similar things available ? Thanks in advance ... Regards, D -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Using Puppet for Application package installation
A clarification: whatever kicks Puppet has to run as root as well could be something that doesn't run as root but does have sudo permissions! -- O On Apr 6, 2013, at 12:23 PM, Owen Smith wrote: Greetings, We are using Puppet to deploy application packages, so it can indeed be done. However, you need to do some work around Puppet to enable the use cases you've mentioned: * Something builds the package * Something publishes the package to the yum repo * Something kicks Puppet on the node(s) you want to install on (either starting it up in daemon mode or executing it) * Someone (or something) ensures that package declarations are properly assigned to your node. * At this point, Puppet takes over, figures out what packages need to be installed/upgraded, and handles that for you, in addition to whatever configuration and service control you've specified. In short: you need a build/deployment system that uses Puppet configuration management at its core. In our case, we glued this together ourselves. Some things to be aware of: * To use the YUM package provider, Puppet must run as root. Therefore, whatever kicks Puppet has to run as root as well. We use MCollective for this, which involves a root agent running as a daemon on the endpoint. * Puppet's RPM/YUM providers install packages as root into the standard system RPMDB. So, you can see, by going this route your application packages are going to be handled just like any other system package. In other words, the key to making this easy is this: though the user doesn't have root access on the node, the deployment system does. You control who can do what to the node through authentication and authorization in the deployment system itself, and by constraining the set of operations that the deployment system supports. Let's say this solution isn't a possibility: for example, you use a custom user/RPMDBs/prefix/RPMRC when installing via RPM. You *can* theoretically make this work with Puppet, but you've got a lot of work on your hands, because the existing package type/providers don't support it. You have my sympathy, because that's where we've been, and over the years we've banged our head against that wall so many times, for many reasons besides Puppet. One of our tenets in moving to Puppet, however, was to stop doing things that made our life needlessly difficult. :-) If you go this way, you also need to give some thought as to how you want to upgrade an existing application on the endpoint. One way is to use 'ensure = latest' and configure the YUM repo on the node to point to a new repo with your updated packages when the time comes. Another possibility is to use 'ensure = present' and do an explicit 'yum upgrade' operation through MCollective to get the packages updated; then run Puppet to fix up the rest. Hope this helps! -- O On Apr 4, 2013, at 6:39 AM, Dhaval wrote: Hello Guys, i want to know, can we use puppet to install application packages ( not system packages ) .. if yes how , if someone can through some light .. my requirement is 1) application team can create package on their own and update in yum repo ( without root ) 2) application team can install package on their own ( without root ) to the directories mention in rpm .. let me know if anyone is aware of similar things available ? Thanks in advance ... Regards, D -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Remove msi from windows 7
Hello,
Could someone help me to understand why the place absent, the package you
are installing is not removed?
package { 'mozilla':
ensure = absent,
provider = 'windows',
source = 'C:\packages\mozilla-firefox.msi',
}
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Revoked cert error
Hi, Not to duplicate posts; but I'm also getting the same issue. err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked I've done this as well; 1. revoke and clean on the master + rm -rf ...ssl/ on the client, generate and sign new cert 2. completely reinstall the client (which implies a repeat of 1.), with a different name that's never been used before both client and server running same versions; 2.7.11 both have same time on client/server Ben On Friday, 23 March 2012 13:41:24 UTC-7, Dave Knight wrote: I've installed many puppet nodes in the last couple of weeks, all nearly identical as the install is fully automated. Just one node gives me this error: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked I've tried: 1. revoke and clean on the master + rm -rf ...ssl/ on the client, generate and sign new cert 2. completely reinstall the client (which implies a repeat of 1.), with a different name that's never been used before Same problem. Grateful for any clues or suggestions of how to further debug. Thanks! dave -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet client not auto updating
I am new to puppet and am experimenting with some basic commands. I have a puppetmaster server and a couple or servers with puppet client. All servers are running ubuntu. I have set up the link between the master and the clients and their certs have been signed etc. The clients have had puppet started via 'service puppet start' and can confirm they are running with 'service puppet status'. When I make any changes on the master nothing happens on the servers. I have waited a couple of hours and e.g. the required package has not been installed on the client. As soon as I run on the client:- puppetd --test It will immediately install the package so I know my manifests / modules are correct as it does what I request when I manually ask it. I just need it to run periodically automatically and get the latest info from the master. Any ideas of things I can check? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet client not auto updating
Hi, I am new to puppet and am experimenting with some basic commands. I have a puppetmaster server and a couple or servers with puppet client. All servers are running ubuntu. I have set up the link between the master and the clients and their certs have been signed etc. The clients have had puppet started via 'service puppet start' and can confirm they are running with 'service puppet status'. When I make any changes on the master nothing happens on the servers. I have waited a couple of hours and e.g. the required package has not been installed on the client. As soon as I run on the client:- puppetd --test It will immediately install the package so I know my manifests / modules are correct as it does what I request when I manually ask it. I just need it to run periodically automatically and get the latest info from the master. Any ideas of things I can check? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] How does puppet fit into release cycle workflows
Hi there, I am new to puppet and try to wrap my head around things. Puppet is primarily for config management. You can however install packages with it. I get all that. What I try to understand is how it fits into repository lifecycle management. This is probably not the domain of puppet but I will ask anyway because I am very interested how others do it. I am used to Red Hat's Satellite way of life cycle management where one has repositories for dev, qa, prod, etc. Package updates enter dev. Once OK-ed, they get cloned to qa and then to prod. Hosts are assigned to these repo's. So once package updates reach prod, we can update the prod servers with the tested packages. The packages themselves are from Red Hat itself (security, bugfix, and enhancement errata), or custom packages. Now, I see some people saying they use Satellite (or spacewalk, it's upstream product) for package management alone (although it can do config file management) and puppet for configuration management. I would like to use one tool for both package (update) installations and config changes. So, how have you guys set up these workflows? Tanks for any pointers! Fred -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet and OVO/ITO/OML
On Thu, 4 Apr 2013 02:29:51 -0700 (PDT) ro...@liveperson.com wrote: Hi Stefan, I know it's an old post, but I'll be happy to hear more about how you're doing the agent installations with puppet, and maybe even get some code from you if it's possible. :) Is there an option to contact you? You can contact me by mail or just replying on this list. The repository https://github.com/stschulte/puppet-hpom is still up if you are interested in custom types. I'm happy to merge in pull request, too. About the installation itself: I do not have the code around right now but I install the agent with an exec resource from a NAS share (something along oainstall.sh -i -a -includeupdates -defer_configure). The same is true for configuration (oainstall.sh -c -a -s $server) and activation (If you have a lot of updates and hotfixes, doing the installation and configuration in seperate steps will be a *a lot* faster) I also have an if clause to check the custom fact opcagtversion against the desired version (with the versioncmp function) and trigger another exec to update the agent if necessary. If you want a more concrete example I'll check the module at work and will see what I can actually make public. -Stefan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Flush provider - Differentiating between new resource and modification?
On Fri, 5 Apr 2013 00:57:32 -0700 (PDT) Gavin Williams fatmc...@gmail.com wrote: Morning all I'm working on converting some of my NetApp providers to prefetch/flush style to try and optimize performance. I've hit an issue on my Netapp_user provider, around handling resource creation versus resource modification? What's the easiest way to differentiate? Current code is here: https://github.com/fatmcgav/fatmcgav-netapp/commit/66092978f4182c5474a60011db99ee2e3e12e689 Any tips appreciated. Regards Gavin There is no way to check *why* the flush method was called, you just now that at least one property has been updated. You do not see if `ensure` updated or let's say `passmaxage`. Does this actually cause problems? One thing I've spotted is that your create method does update the @property_hash[:ensure] value but no other value. This seems to be wrong because if the resource was absent before, @property_hash is initally an empty hash. Because when `ensure` changes no other properties are synced you don't have the desired values of all the other properties available in the `flush` method. So your `create` method should propably look like def create resource.class.validproperties.each do |property| if value = resource.should(property) @property_hash[property] = value end end end -Stefan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Problem on live-management - Node list missing - User -Find Resources not working
Lukas,
Thanks for forwarding that on. You beat me to it!
The bug mentioned in this thread affects Live Management and Mcollective in
PE 2.8.0. There are updated packages that will resolve the issue as well as
a module to aid in installing those packages. You can find more details at
https://puppetlabs.com/puppet-enterprise-hotfixes-2-8-0/.
On Sat, Apr 6, 2013 at 1:44 AM, Lukas Wenning loe...@internetz.me wrote:
edit:
they just send an email that its a bug you can download the bugfixes here:
https://puppetlabs.com/puppet-enterprise-hotfixes-2-8-0/?utm_campaign=pe280updateutm_medium=emailutm_source=peusersutm_content=hotfixesmkt_tok=3RkMMJWWfF9wsRokvazNZKXonjHpfsX67OsuW6G1lMI%2F0ER3fOvrPUfGjI4CTMZkI%2FqLAzICFpZo2FFID%2FCFeZRM%2B%2FdO
original text i got via email:
Hi there,
We've found an issue in Puppet Enterprise 2.8.0 that keeps live management
from functioning and prevents MCollective from using filters.
We have prepared a partial upgrade package that fully resolves this issue.
If you have installed 2.8.0, you can download the package fix
herehttp://email.puppetlabs.com/track?type=clickenid=bWFpbGluZ2lkPXB1cHBldGxhYnNCZXRhY3VzdC0yNjA0LTc1MTgtMC0zMDQ2LXByb2QtNTQxNyZtZXNzYWdlaWQ9MCZkYXRhYmFzZWlkPTU0MTcmc2VyaWFsPTEyNjU1NjIzNDgmZW1haWxpZD1sb2VrZW5AaW50ZXJuZXR6Lm1lJnVzZXJpZD0yNzczMjYzJmV4dHJhPSYmJg==https://puppetlabs.com/puppet-enterprise-hotfixes-2-8-0/?utm_campaign=pe280updateutm_medium=emailutm_source=peusersutm_content=hotfixesmkt_tok=3RkMMJWWfF9wsRokvazNZKXonjHpfsX67OsuW6G1lMI%2F0ER3fOvrPUfGjI4CTMZkI%2FqLAzICFpZo2FFID%2FCFeZRM%2B%2FdO
.
We have also temporarily pulled PE 2.8.0 from our download
pagehttp://email.puppetlabs.com/track?type=clickenid=bWFpbGluZ2lkPXB1cHBldGxhYnNCZXRhY3VzdC0yNjA0LTc1MTgtMC0zMDQ2LXByb2QtNTQxNyZtZXNzYWdlaWQ9MCZkYXRhYmFzZWlkPTU0MTcmc2VyaWFsPTEyNjU1NjIzNDgmZW1haWxpZD1sb2VrZW5AaW50ZXJuZXR6Lm1lJnVzZXJpZD0yNzczMjYzJmV4dHJhPSYmJg==https://puppetlabs.com/misc/pe-files/?utm_campaign=pe280updateutm_medium=emailutm_source=peusersutm_content=downloadpagemkt_tok=3RkMMJWWfF9wsRokvazNZKXonjHpfsX67OsuW6G1lMI%2F0ER3fOvrPUfGjI4CTMZkI%2FqLAzICFpZo2FFID%2FCFeZRM%2B%2FdO,
and plan to release a fixed PE 2.8.1 sometime next week. We will notify you
about the availability of PE 2.8.1 when it is released.
If you have additional questions or concerns, you are welcome to contact
us at
supp...@puppetlabs.comhttp://email.puppetlabs.com/track?type=clickenid=bWFpbGluZ2lkPXB1cHBldGxhYnNCZXRhY3VzdC0yNjA0LTc1MTgtMC0zMDQ2LXByb2QtNTQxNyZtZXNzYWdlaWQ9MCZkYXRhYmFzZWlkPTU0MTcmc2VyaWFsPTEyNjU1NjIzNDgmZW1haWxpZD1sb2VrZW5AaW50ZXJuZXR6Lm1lJnVzZXJpZD0yNzczMjYzJmV4dHJhPSYmJg==mailto:supp...@puppetlabs.com?mkt_tok=3RkMMJWWfF9wsRokvazNZKXonjHpfsX67OsuW6G1lMI%2F0ER3fOvrPUfGjI4CTMZkI%2FqLAzICFpZo2FFID%2FCFeZRM%2B%2FdO
.
Best,
The Puppet Enterprise Support Team
Am Sonntag, 31. März 2013 00:13:00 UTC+1 schrieb Juan Pablo Baudoin:
Hello
I'm testing Puppet Enterprise 2.7 and I'm having the following problem.
When I go to live-management, the node list sometimes is missing.
https://lh3.googleusercontent.com/-r3mhNTK8CH8/UVdw3AaHfjI/APs/T6i_Pg4hufM/s1600/err_nodes_missing.png
This behavior is random, but when It happend I find the following error
on the logs:
== pe-httpd/error.log ==
INFO Sat Mar 30 20:04:09 -0300 2013: memcached saving
[raw_agent_inventory] [**4940e0b29c08b35a29d4e4b0c63d13**04] -
[[#MCollective::RPC::Result:**0x7f33fa190250
@results={:data={:agents=[{:**agent=discovery, :license=Apache
License, Version 2, :version=unknown, :url=unknown,
:description=unknown, :name=discovery, :author=R.I.Pienaar x
, :] [3631]
INFO Sat Mar 30 20:04:09 -0300 2013: memcached retrieving
[empty_filter] [**7bc4614f5252e68308196a74a0cac9**80] = [nil] [3]
Stomp::Error::**NoCurrentConnection - no current connection exists:
/opt/puppet/lib/gems/1.8/**gems/stomp-1.2.3/lib/stomp/**connection.rb:334:in
`publish'
/opt/puppet/libexec/**mcollective/mcollective/**connector/stomp.rb:189:in
`send'
/opt/puppet/lib/site_ruby/1.**8/mcollective/client.rb:65:in `sendreq'
/opt/puppet/lib/ruby/1.8/**timeout.rb:67:in `timeout'
When the list appears, and I try to use the Find Resources buton under
User, It stay wiht the message: Finding user resources
https://lh5.googleusercontent.com/-gp9pnq3REzI/UVdw6a3wUkI/AP0/Nl4QyvQFDRQ/s1600/err_find_resources.png
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
Matthaus Owens
Release Manager, Puppet Labs
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from
Re: [Puppet Users] Using Puppet for Application package installation
Thank You guys, for the explaining ... I think i have to find out something .. which helps to maintain repos without SA intervention and which as authentication and authorization and then use puppet to install those packages on systems .. and i think pulp can do this .. On Sunday, 7 April 2013 00:53:29 UTC+5:30, Owen Smith wrote: Greetings, We are using Puppet to deploy application packages, so it can indeed be done. However, you need to do some work around Puppet to enable the use cases you've mentioned: * Something builds the package * Something publishes the package to the yum repo * Something kicks Puppet on the node(s) you want to install on (either starting it up in daemon mode or executing it) * Someone (or something) ensures that package declarations are properly assigned to your node. * At this point, Puppet takes over, figures out what packages need to be installed/upgraded, and handles that for you, in addition to whatever configuration and service control you've specified. In short: you need a build/deployment system that uses Puppet configuration management at its core. In our case, we glued this together ourselves. Some things to be aware of: * To use the YUM package provider, Puppet must run as root. Therefore, whatever kicks Puppet has to run as root as well. We use MCollective for this, which involves a root agent running as a daemon on the endpoint. * Puppet's RPM/YUM providers install packages as root into the standard system RPMDB. So, you can see, by going this route your application packages are going to be handled just like any other system package. In other words, the key to making this easy is this: though the *user* doesn't have root access on the node, the *deployment system *does. You control who can do what to the node through authentication and authorization in the deployment system itself, and by constraining the set of operations that the deployment system supports. Let's say this solution isn't a possibility: for example, you use a custom user/RPMDBs/prefix/RPMRC when installing via RPM. You *can* theoretically make this work with Puppet, but you've got a lot of work on your hands, because the existing package type/providers don't support it. You have my sympathy, because that's where we've been, and over the years we've banged our head against that wall so many times, for many reasons besides Puppet. One of our tenets in moving to Puppet, however, was to stop doing things that made our life needlessly difficult. :-) If you go this way, you also need to give some thought as to how you want to upgrade an existing application on the endpoint. One way is to use 'ensure = latest' and configure the YUM repo on the node to point to a new repo with your updated packages when the time comes. Another possibility is to use 'ensure = present' and do an explicit 'yum upgrade' operation through MCollective to get the packages updated; then run Puppet to fix up the rest. Hope this helps! -- O On Apr 4, 2013, at 6:39 AM, Dhaval wrote: Hello Guys, i want to know, can we use puppet to install application packages ( not system packages ) .. if yes how , if someone can through some light .. my requirement is 1) application team can create package on their own and update in yum repo ( without root ) 2) application team can install package on their own ( without root ) to the directories mention in rpm .. let me know if anyone is aware of similar things available ? Thanks in advance ... Regards, D -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To post to this group, send email to puppet...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
