R: [Puppet Users] Random Yum errors during provisioning
Not puppet related, no. Every rpm deep. Solver as yum, zipper etc put a lock
for protecting the rpm db from concurrent access. So if you are using puppet be
sure to not having long running yum daemons, but if you also use some patch
management system - spacewalk, red hat satellite - this could be difficult.
Best
Messaggio originale
Da: Glenn Poston
Inviato: 28/06/2013, 15:38
A: puppet-users@googlegroups.com
Oggetto: [Puppet Users] Random Yum errors during provisioning
Running Amazon Linux (which is essentially Centos5.5).
Anyone seen random yum errors like this one? I don't think
it's necessarily related to Puppet, but it randomly fails my puppet runs
and I don't know how to fix it.
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/Package[zookeeper]/ensure: created
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/File[/var/lib/zookeeper/data]/ensure: created
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/File[/var/lib/zookeeper/data/myid]/ensure: created
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Yum_repo::Configs/File[/etc/yum.repos.d/inin-epel.repo]/ensure:
defined content as '{md5}b94171f63e31f07b8bd75444073e301c'
Jun 28 08:41:35 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/File[/etc/zookeeper/zookeeper-env.sh]/content:
content changed '{md5}cd666c7520ce5279ddbc185512b0b177' to
'{md5}5cb59b25f5e7567d94ba14b06f6e7081'
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [Error: Execution of
'/usr/bin/yum -d 0 -e 0 -y install daemonize' returned 1: Existing lock
/var/run/yum.pid: another copy is running as pid 2502.
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Another app is currently
holding the yum lock; waiting for it to exit...
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: The other application is: yum
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Memory : 40 M RSS (235 MB
VSZ)
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Started: Fri Jun 28
08:41:33 2013 - 00:03 ago
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: State : Running, pid: 2502
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Error: database disk image is
malformed
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [Error:
/Stage[main]/Mcollective/Package[daemonize]/ensure: change from absent to
present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install daemonize'
returned 1: Existing lock /var/run/yum.pid: another copy is running as pid
2502.
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Another app is currently
holding the yum lock; waiting for it to exit...
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: The other application is: yum
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Memory : 40 M RSS (235 MB
VSZ)
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Started: Fri Jun 28
08:41:33 2013 - 00:03 ago
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: State : Running, pid: 2502
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Error: database disk image is
malformed
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Zookeeper/File[/etc/zookeeper/zoo.cfg]/content: content
changed '{md5}5c543298c5572c3caf40a3d108309019' to
'{md5}31db609f6601a8a02561d411e98db12b'
Jun 28 08:41:39 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Puppet/File[/usr/local/bin/run_puppet.sh]/content: content
changed '{md5}4e9496313a0b4152c663defce5100af5' to
'{md5}49d78e473fa2202dea13e9b195e63575'
Jun 28 08:41:39 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Yum_repo::Configs/Exec[puppet_repo]/returns: executed
successfully
Jun 28 08:41:48 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Mcollective::Common/Package[mcollective-package-agent]/ensure:
created
The problem does not persist. Yum packages are installed by puppet before
and after the errors. A subsequent puppet run installs the previously
skipped packages fine.
It's as if some background process creates a lock, while updating the yum
DB, but when the lock is released, the yum DB is still in a bad state
(momentarily).
--
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.
R: [Puppet Users] "New" (i.e., posted last week) Learning Puppet chapters
Imho, should be intesting some idea on the integration of puppet in large
corporation, the possible workflow, the separation of duty. For example using
something as gitolite, the integration with quality control of some sort, the
reporting. I have read something in pro puppet : i am sorry but most of that is
discussed there in this area is very basic. Best regards
Messaggio originale
Da: Nick Fagerlund
Inviato: 19/08/2011, 20:42
A: Puppet Users
Oggetto: [Puppet Users] "New" (i.e., posted last week) Learning Puppet chapters
Slowly but surely, the Learning Puppet series [1] -- the book-in-
progress we've been building as an entry point for beginning Puppet
users -- keeps growing. I added two new chapters last week, about
templates[2] and parameterized classes[3], and I'll be working on more
soon. ("Soon" meaning after I put out the other stuff that's on fire
in the office these days.)
If you've been reading the series (or hey, even if you haven't), what
do you want to see covered in it? The next few chapters are likely
going to be about defined types, composing modules together, and some
beginning site design, and I should probably get into virtual
resources somewhere in there. And I might do a thing on data
separation with Hiera and extlookup. But after that, it's probably
onward to client/server Puppet, and I haven't decided the best way to
handle that yet. What brick walls did you run into? Would things have
been easier if you'd seriously boned up on SSL, for example?
So yeah, suggestions wanted. Let me know what's working or not working
for you, and I'll get to writing more as soon as I can. Thanks!
-N
[1]: http://docs.puppetlabs.com/learning
[2]: http://docs.puppetlabs.com/learning/templates.html
[3]: http://docs.puppetlabs.com/learning/modules2.html
--
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] I: Cloud hosting made easy with OpenStack and Puppet
Perhaps someone of this list is interested. Regards Messaggio originale Da: SearchEnterpriseLinux.com Inviato: 12/07/2011, 21:02 A: pinto.e...@gmail.com Oggetto: Cloud hosting made easy with OpenStack and Puppet SearchEnterpriseLinux.com: Enterprise Linux Advisor Linux in Production July 12, 2011 HOW TO INSTALL AN OPENSTACK NOVA COMPUTE CLOUD WITH PUPPET http://go.techtarget.com/r/14424454/5394733 James Turnbull, Contributor The open source cloud project, OpenStack, can be used to host private or public clouds. Learn how to install it using the Puppet configuration management tool on your Linux server. READ THE FULL TIP http://go.techtarget.com/r/14424455/5394733 :: ADVERTISEMENT ::: SearchEnterpriseLinux.com Sponsored by: SearchEnterpriseLinux.com A collection of the top Linux command tips http://go.techtarget.com/r/14424456/5394733 Guide to the Linux security toolbox http://go.techtarget.com/r/14424457/5394733 Linux troubleshooting fast guide http://go.techtarget.com/r/14424458/5394733 Sharing Windows files with the Linux CIFS client http://go.techtarget.com/r/14424459/5394733 Utilize SearchEnterpriseLinux's comprehensive learning guide library http://go.techtarget.com/r/14424460/5394733 :: Open Virtualization Alliance unlikely to unseat VMware http://go.techtarget.com/r/14424461/5394733 Users aren't sold that the Open Virtualization Alliance can promote KVM over VMware, the "safe" virtualization choice. READ THE FULL STORY http://go.techtarget.com/r/14424462/5394733 :: Managing Red Hat from a graphical environment over SSH with PuTTY http://go.techtarget.com/r/14424463/5394733 Red Hat Enterprise Linux administration can be conducted through a GNOME graphical interface. Learn how to remotely use these tools over an SSH connection using PuTTY. READ THE FULL TIP http://go.techtarget.com/r/14424464/5394733 :: Choosing the right virtualization management tools http://go.techtarget.com/r/14424465/5394733 Virtualization management tools that can distinguish between physical and virtual servers give IT administrators the ability to better monitor virtual machines and allocate resources. LISTEN TO THE PODCAST http://go.techtarget.com/r/14424466/5394733 -- 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.
R: Re: [Puppet Users] Managing /etc/fstab options with augeas
There is a specific example of this on the puppet Wiki iirc. Or very similar . Regards. Messaggio originale Da: Adam Heinz Inviato: 08/06/2011, 16:17 A: puppet-users@googlegroups.com Oggetto: Re: [Puppet Users] Managing /etc/fstab options with augeas On Thu, Jun 2, 2011 at 4:22 AM, Giovanni Bordello wrote: > I'm trying to manage mount options in /etc/fstab with Augeas but can't > figure out how to add more than one option. Have you looked at puppet's 'mount' type? -- 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.
R: Re: [Puppet Users] Any good documentation NGINX + Passenger + Puppet?
I have found a nice description in the new book " pro puppet " by Apress. It worth reading for other reason as well. Jmho, i have not direct interest in promoting the book. Best regards Messaggio originale Da: Aaron Grewell Inviato: 01/06/2011, 17:59 A: puppet-users@googlegroups.com Oggetto: Re: [Puppet Users] Any good documentation NGINX + Passenger + Puppet? Passenger setup is annoyingly complicated since you're having to set up Apache, configure Ruby as an application server on top of that and then install the Puppetmaster on top of that. To add to the fun, Apache configs are different between distributions, it's different between releases of Puppet and most of the instructions out there are a bit out of date. And it's very very picky about versions. I had to cobble mine together from about three different sources to make it work. Are you using a Red Hat derivative? I've never done this on the Debians. On Tue, May 31, 2011 at 6:15 PM, Luc Suryo wrote: > Hello, > > I been browsing around and can not find any good documentation how to setup > Puppet with Nginx and passenger > > I have a working Nginx with passenger support working but then what ? > Kinda confuse and wondering if maybe Passenger is not the way to go ? > Mongrel ? or something different? > any pointer appreciated . > > > > btw I have read : > > http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel_Nginx > and > http://projects/puppetlabs.com/projects/1/wiki/Using_Passenger > > > > and still I do not get it ... > > > Nginx 1.0.0, Passenger 3.0.7 and puppet 2.6.2 > > > thanks > > -- > -ls > > -- > 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. -- 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: Patch Management
Fwiw, at @rpm5.org probably there is Some interest in This. Regards -Original Message- From: donavan Sent: 06/11/2010, 04:03 To: Puppet Users Subject: [Puppet Users] Re: Patch Management On Nov 2, 7:26 am, Joel Merrick wrote: > Hi Puppeteers! > > I've just been speaking to Ohad on #theforeman about package > management, specifically about generating lists of packages : version > numbers across the estate for things like patch management. Hi Joel, It's not really an answer but there was related talk at puppetcamp. One of the ideas from puppetlabs was integration between package management databases and puppets resource modeling. I don't think there were any detailed plans, but I imagine it would make your query requirements pretty easy. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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-us...@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] Is it possible to use hierarchic LDAP entries for puppet clients and parentnodes?
-Original Message- From: puppetplayer Sent: 23/08/2010, 14:37 To: Puppet Users Subject: [Puppet Users] Is it possible to use hierarchic LDAP entries for puppet clients and parentnodes? Hi all, i want to create a network and customer parentnodes to store network and/or customer specific attributes only at one place. Therefore i created following puppet client an parentnodes within LDAP: Network specific parentnode: dn: cn=192_168_100_0,ou=profile,dc=zz,dc=example,dc=com objectClass: top objectClass: DUAConfigProfile objectClass: puppetClient objectClass: TSYSConfigProfile defaultServerList: 192.168.100.101 defaultSearchBase: dc=zz,dc=example,dc=com authenticationMethod: simple followReferrals: TRUE defaultSearchScope: sub searchTimeLimit: 30 profileTTL: 43200 credentialLevel: proxy bindTimeLimit: 10 HostEntry: 100.101.110.111:first.entry.from.zz.profile HostEntry: 200.202.220.222:second.entry.from.zz.profile cn: 192_168_100_0 Customer specific parentnode: dn: cn=zzbasenode,ou=HostConfig,dc=zz,dc=example,dc=com objectClass: top objectClass: device objectClass: puppetClient description: Puppet Base Node ZZ puppetclass: base3 cn: zzbasenode parentnode: 192_168_100_0 and the Client: dn: cn=puppetc2,ou=HostConfig,dc=zz,dc=example,dc=com objectClass: top objectClass: device objectClass: puppetClient objectClass: TSYSjumpsta objectClass: ieee802Device objectClass: iphost description: Puppet Client 2 ipHostNumber: 192.168.100.111 cn: puppetc2 parentnode: zzbasenode puppetclass: base1 HostEntry: 1.2.3.4:first.entry.from.hostconfig HostEntry: 2.3.4.5:second.entry.from.hostconfig And now, most attributes from LDAP are stored in the client catalog. But not all... You can see, that only the HostEntry Attribute from the PuppetClient "puppetc2" is stored in the yaml file, an not the HostEntry attrbiutes from the network specific parentnode "192_168_100_0": var/puppet/yaml/node$ cat puppetc2.zz.example.com.yaml --- !ruby/object:Puppet::Node classes: - base1 - base3 environment: production expiration: 20 E-mail troncato a 2,000 caratteri :::0:99e27beaa3e6afbe439312c752f74fbc:7d0 Il messaggio originale si trova sul server -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Is it possible to use hierarchic LDAP entries for puppet clients and parentnodes?
-Original Message- From: puppetplayer Sent: 23/08/2010, 14:37 To: Puppet Users Subject: [Puppet Users] Is it possible to use hierarchic LDAP entries for puppet clients and parentnodes? Hi all, i want to create a network and customer parentnodes to store network and/or customer specific attributes only at one place. Therefore i created following puppet client an parentnodes within LDAP: Network specific parentnode: dn: cn=192_168_100_0,ou=profile,dc=zz,dc=example,dc=com objectClass: top objectClass: DUAConfigProfile objectClass: puppetClient objectClass: TSYSConfigProfile defaultServerList: 192.168.100.101 defaultSearchBase: dc=zz,dc=example,dc=com authenticationMethod: simple followReferrals: TRUE defaultSearchScope: sub searchTimeLimit: 30 profileTTL: 43200 credentialLevel: proxy bindTimeLimit: 10 HostEntry: 100.101.110.111:first.entry.from.zz.profile HostEntry: 200.202.220.222:second.entry.from.zz.profile cn: 192_168_100_0 Customer specific parentnode: dn: cn=zzbasenode,ou=HostConfig,dc=zz,dc=example,dc=com objectClass: top objectClass: device objectClass: puppetClient description: Puppet Base Node ZZ puppetclass: base3 cn: zzbasenode parentnode: 192_168_100_0 and the Client: dn: cn=puppetc2,ou=HostConfig,dc=zz,dc=example,dc=com objectClass: top objectClass: device objectClass: puppetClient objectClass: TSYSjumpsta objectClass: ieee802Device objectClass: iphost description: Puppet Client 2 ipHostNumber: 192.168.100.111 cn: puppetc2 parentnode: zzbasenode puppetclass: base1 HostEntry: 1.2.3.4:first.entry.from.hostconfig HostEntry: 2.3.4.5:second.entry.from.hostconfig And now, most attributes from LDAP are stored in the client catalog. But not all... You can see, that only the HostEntry Attribute from the PuppetClient "puppetc2" is stored in the yaml file, an not the HostEntry attrbiutes from the network specific parentnode "192_168_100_0": var/puppet/yaml/node$ cat puppetc2.zz.example.com.yaml --- !ruby/object:Puppet::Node classes: - base1 - base3 environment: production expiration: 20 E-mail troncato a 2,000 caratteri :::0:99e27beaa3e6afbe439312c752f74fbc:7d0 Il messaggio originale si trova sul server -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: RPM Provider broken?
Nice to have on This list an ex rpm maintainer :)
-Original Message-
From: Paul Nasrat
Sent: 26/08/2010, 16:41
To: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] Re: RPM Provider broken?
On 26 August 2010 08:16, Christian Casar wrote:
>> If you add name => "apache2-mod_security2", it should do what you expect.
>
> Oh great :)
> That works!
> But I have to add the complete package name (apache2-
> mod_security2-2.5.9-6.2.x86_64
> ) instead of just "apache2-mod_security2"
>
You should only need what rpm thinks is the name (or the full NVR,
which will work with an rpm query)
rpm --queryformat '%{name}\n' -qp
/tmp/apache2-mod_security2-2.5.9-6.2.x86_64.rpm
Paul
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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-us...@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.
