Re: [Puppet Users] Deprecating PostgreSQL versions 8.4 for use with PuppetDB
Hi deepak! Coming from the ruby/rails community this is an super friendly ahead-of-time deprecation idea notice.. On Wed, Jan 02, 2013 at 02:21:21PM -0800, Deepak Giridharagopal wrote: Hello! We'd like to deprecate some fairly old and crusty PostgreSQL versions (anything older than 8.4) for use with PuppetDB. There are a few reasons we want to do this: On one hand, this is probably how it should be with infrastructure projects like this. On the other hand, I just like both the reasoning and the tone. Thanks! Matthias Viehweger -- Serververwaltung und Softwareentwicklung https://www.heute-kaufen.de Prinzessinnenstraße 20 - 10969 Berlin signature.asc Description: Digital signature
[Puppet Users] Re: inspect resources that are already added to a manifest
On Wednesday, January 2, 2013 3:51:37 PM UTC, jcbollinger wrote:
On Saturday, December 22, 2012 12:20:10 PM UTC-6, Luke Bigum wrote:
Hi all,
Does anyone know of a way to inspect resources that are already parsed in
a node's manifest during catalog compilation? This would certainly need
some serious Ruby Fu.
This is a bad idea. If your the Puppet circuits in your brain didn't trip
over inspect, they certainly should have sounded the alarm over serious
Ruby Fu. You are fighting against the tool.
As an example, imagine I have a number of arbitrary files defined by
multiple classes and it is impossible to get an all encompassing list of
these files:
file { 'woof': }
file { 'cows': }
file { 'meow': }
...
$all_files = inline_template(...)
I would like to be able to gather those file names into a Puppet variable
- this would be parse order dependent. It would be fantastic if it could
handle exported resources that have just been collected as well.
And parse-order dependent? Of course it is. You need a
Puppet-bogometer.
So what configuration objective are you actually trying to accomplish
here? There is likely a more robust, less Rubyriffic way to accomplish it.
Ohh don't worry, John, my bogometer was going off like crazy, the needle
almost broke ;-)
I'm taking shortcuts in my spare time with a tool that's probably 70% right
for the job. It's for monitoring - I really like the idea of a Puppet
module to describe or advertise how to monitor itself, it keeps them very
self contained.
Just a bit more on this - I generally see three categories of monitoring
tools. Ones that are configured separately from your CRM and end up being a
source of truth on their own are in my mind the worst. The next level up
are ones either defined from or derived from your CRM. The best are
auto-discovery, but they cost an absolute fortune. I'm trying to move my
team from the first one to the second one with as little new tools as
possible, which is where the 70% right for the job comment comes from.
I'm using exported resources to describe how modules are monitored. The
problem is that exported resources are not the equivalent of raw
information passing. So when I want to start doing trickier things like
group and analyse what is collected, exported resources don't cut it
because it's not what they are designed for.
Specifically what I was trying to do was collect exported resources of the
same type and group them on the monitoring server. There is no predefined
list of service names anywhere (unless you parse the node definitions) so
that's why I wanted to go from resource collection to Array of Strings. A
colleague has managed to reduce my 300 lines to 50 though so the need for
craziness is reduced somewhat. We still need to do the Export a File
trick and run a script on the monitoring server to build the complex
configuration that exported resources are not designed to handle.
The next iteration of this work might be to scrap resource collection in
favour of querying PuppetDB directly to figure out what to monitor, but
that's a lot more work than I'm prepared to do at this stage. Maybe in a
few months... ;-)
-Luke
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/OLpl0Bx1q5kJ.
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 keeps spawning new child processes
When having more than one process...
ps faux | grep puppet master | grep -v grep
puppet5100 92.0 2.7 427180 329728 ? Rsl 09:22 119:27
/usr/bin/ruby /usr/bin/puppet master
puppet 11957 99.9 1.6 300168 200224 ? R10:07 83:53 \_
/usr/bin/ruby /usr/bin/puppet master
... strace-ing first process shows lot of system calls going on
strace -v -p 5100 21 | head -n100
Process 5100 attached - interrupt to quit
ioctl(8, FIONREAD, [89])= 0
recvfrom(8,
\30\244\205\200\0\1\0\1\0\0\0\0\003224\003150\00220\003172\7in-a...,
1024, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr(172.20.60.12)}, [16]) = 89
close(8)= 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
getsockname(6, {sa_family=AF_INET, sin_port=htons(8140),
sin_addr=inet_addr(172.20.150.201)}, [16]) = 0
open(/etc/hosts, O_RDONLY|O_CLOEXEC) = 8
fstat(8, {st_dev=makedev(253, 0), st_ino=2490395, st_mode=S_IFREG|0644,
st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=158,
st_atime=2013/01/03-11:06:35, st_mtime=2010/01/12-14:28:22,
st_ctime=2012/10/24-12:05:48}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fd177a16000
read(8, 127.0.0.1 localhost localhost, 4096) = 158
read(8, , 4096) = 0
close(8)= 0
munmap(0x7fd177a16000, 4096)= 0
socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 8
connect(8, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr(172.20.60.12)}, 16) = 0
poll([{fd=8, events=POLLOUT}], 1, 0)= 1 ([{fd=8, revents=POLLOUT}])
sendto(8,
\364\266\1\0\0\1\0\0\0\0\0\0\003201\003150\00220\003172\7in-a..., 45,
MSG_NOSIGNAL, NULL, 0) = 45
poll([{fd=8, events=POLLIN}], 1, 5000) = 1 ([{fd=8, revents=POLLIN}])
ioctl(8, FIONREAD, [90])= 0
recvfrom(8,
\364\266\205\200\0\1\0\1\0\0\0\0\003201\003150\00220\003172\7in-a...,
1024, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr(172.20.60.12)}, [16]) = 90
close(8)= 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
select(6, [5], [], [], {0, 0}) = 1 (in [5], left {0, 0})
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
select(6, [5], [], [], {0, 0}) = 1 (in [5], left {0, 0})
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
select(6, [5], [], [], {0, 0}) = 1 (in [5], left {0, 0})
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
accept(5, {sa_family=AF_INET, sin_port=htons(58015),
sin_addr=inet_addr(172.20.150.232)}, [16]) = 8
fcntl(8, F_GETFL) = 0x2 (flags O_RDWR)
fstat(8, {st_dev=makedev(0, 6), st_ino=81435612, st_mode=S_IFSOCK|0777,
st_nlink=1, st_uid=52, st_gid=52, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=0, st_mtime=0, st_ctime=0}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fd177a16000
lseek(8, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
fcntl(8, F_GETFL) = 0x2 (flags O_RDWR)
fstat(8, {st_dev=makedev(0, 6), st_ino=81435612, st_mode=S_IFSOCK|0777,
st_nlink=1, st_uid=52, st_gid=52, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=0, st_mtime=0, st_ctime=0}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fd177a15000
lseek(8, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
fcntl(8, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(8, F_SETFL, O_RDWR|O_NONBLOCK)= 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
Re: [Puppet Users] Re: puppet master keeps spawning new child processes
- Original Message - From: a...@gmx.de To: puppet-users@googlegroups.com Sent: Thursday, January 3, 2013 10:36:35 AM Subject: [Puppet Users] Re: puppet master keeps spawning new child processes When having more than one process... ps faux | grep puppet master | grep -v grep puppet5100 92.0 2.7 427180 329728 ? Rsl 09:22 119:27 /usr/bin/ruby /usr/bin/puppet master puppet 11957 99.9 1.6 300168 200224 ? R10:07 83:53 \_ /usr/bin/ruby /usr/bin/puppet master ... strace-ing first process shows lot of system calls going on you'd probably have to strace it around the time it does the fork to get useful information. Do you have any custom parser functions perhaps that might be running external commands? or use the generate() function much? I am not sure if the generate function actually forks like this but it's worth seeing if you use it. -- 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 and installing packages from source
I understand the points you mentioned, but as long as software is still being distributed as source packages I think it should be supported at some level by Puppet. That being said, I'm off to learn some packaging techniques. Thanks for all the help. Magic. On Wednesday, January 2, 2013 7:30:01 PM UTC+2, jcbollinger wrote: On Wednesday, January 2, 2013 3:32:55 AM UTC-6, magi...@gmail.com wrote: Hello Everyone, I'm looking for a way to install packages from source via puppet, I was able to locate maybe 5 posts on this subject which is very strange, as I would expect people to still use ./configure with their own customized options. Why would you expect that? Responsible sysadmins use packages wherever possible. The alternative is madness. Moreover, if you continue with the puppet-controlled build approach, you will find that you have to go to a fair amount of effort to ensure that the program is built and installed only at need. Then, eventually you may find that it's even trickier to fit updates into the picture. And you may discover that you need to explicitly manage dependencies -- hopefully before something breaks unexpectedly. Relying on your package manager makes all this a lot easier to deal with. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/8TpS7e3N-aIJ. 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 keeps spawning new child processes
Am Donnerstag, 3. Januar 2013 11:41:21 UTC+1 schrieb R.I. Pienaar: - Original Message - From: al...@gmx.de javascript: To: puppet...@googlegroups.com javascript: Sent: Thursday, January 3, 2013 10:36:35 AM Subject: [Puppet Users] Re: puppet master keeps spawning new child processes When having more than one process... ps faux | grep puppet master | grep -v grep puppet5100 92.0 2.7 427180 329728 ? Rsl 09:22 119:27 /usr/bin/ruby /usr/bin/puppet master puppet 11957 99.9 1.6 300168 200224 ? R10:07 83:53 \_ /usr/bin/ruby /usr/bin/puppet master ... strace-ing first process shows lot of system calls going on you'd probably have to strace it around the time it does the fork to get useful information. I'll try to do that... somehow... Do you have any custom parser functions perhaps that might be running external commands? or use the generate() function much? I am not sure if the generate function actually forks like this but it's worth seeing if you use it. Not that I know of... AFAIK I don't have any custom parser functions and I must admit that I don't even know what the generate() function is or does. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/9oHHYLDYCuMJ. 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 and installing packages from source
- Original Message - From: magic rh magic...@gmail.com To: puppet-users@googlegroups.com Sent: Thursday, January 3, 2013 10:52:55 AM Subject: [Puppet Users] Re: Puppet and installing packages from source I understand the points you mentioned, but as long as software is still being distributed as source packages I think it should be supported at some level by Puppet. I think the problem here is that you think they are source packages they are not packages at all, they are source. Sources used as input to creating packaged means of deploying code tailored to suit the needs of your distribution Just as you cannot consider bread and flour to be the same thing or say flour has the same properties as bread or offer the same advantages and usage models you cannot consider source a form of package. That being said, I'm off to learn some packaging techniques. Thanks for all the help. Magic. On Wednesday, January 2, 2013 7:30:01 PM UTC+2, jcbollinger wrote: On Wednesday, January 2, 2013 3:32:55 AM UTC-6, magi...@gmail.com wrote: Hello Everyone, I'm looking for a way to install packages from source via puppet, I was able to locate maybe 5 posts on this subject which is very strange, as I would expect people to still use ./configure with their own customized options. Why would you expect that? Responsible sysadmins use packages wherever possible. The alternative is madness. Moreover, if you continue with the puppet-controlled build approach, you will find that you have to go to a fair amount of effort to ensure that the program is built and installed only at need. Then, eventually you may find that it's even trickier to fit updates into the picture. And you may discover that you need to explicitly manage dependencies -- hopefully before something breaks unexpectedly. Relying on your package manager makes all this a lot easier to deal with. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/8TpS7e3N-aIJ. 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] Puppet cloud provisioning and VMware mac address allocation?
Thanks Ohad - much appreciated - I will have a look into that! M. On Sunday, December 30, 2012 7:37:05 PM UTC, ohad wrote: On Sun, Dec 30, 2012 at 7:58 PM, mbi...@edrans.com javascript: wrote: Hi all, I've been working on fully automating the VM provisioning for some months now and one piece I could not resolve yet is to automate the dhcp/dns automation and just because I cannot obtain the VM mac address that vsphere/vcenter will allocate to a new vm. I am aware of 3rd party tools such as foreman, but in fact, I am concerned they do not follow puppet release cycle, or it's not their priority ;) Do you mind mentioning what do you mean? The foreman team care a lot about our users and puppet community in general I am sure that I am not the first one facing this bottleneck when ~200/300 VMs needs to be created. For theas reason I would like to know from those faced this issue and how they worked it out in an efficient manner. Thanks for sharing your thoughts! Best, Martin -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Y5EdQWBTcbMJ. To post to this group, send email to puppet...@googlegroups.comjavascript: . To unsubscribe from this group, send email to puppet-users...@googlegroups.com javascript:. 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/CpkEtQmzKbwJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] How to automate agent installation on nodes
Hello Everyone Can anyone please let me know once I am done with VM provisioing with vmware how to allocate hostname and install puppet agent on that node automatically. Thanks :) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/35pXckQzOCoJ. 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 keeps spawning new child processes
After monitoring the Father process a bit more I realized that it often happens that new processes are created - usually they don't live long. strace -f -v -p 5100 -o /tmp/strace.5100.log Process 5100 attached with 2 threads - interrupt to quit Process 18702 detached Process 19996 attached Process 19997 attached Process 19998 attached Process 19998 detached Process 20160 attached (waiting for parent) Process 20160 resumed (parent 19996 ready) Process 20160 detached Process 19996 detached Process 19997 detached Process 20636 attached Process 20637 attached Process 20638 attached Process 20638 detached Process 20814 attached Process 20814 detached Process 20636 detached Process 20637 detached Process 20925 attached (waiting for parent) Process 20925 resumed (parent 5100 ready) Process 20926 attached Process 20927 attached Process 20927 detached Process 21119 attached (waiting for parent) Process 21119 resumed (parent 20925 ready) Process 21119 detached Process 21125 attached (waiting for parent) Process 21125 resumed (parent 20925 ready) Process 21125 detached Process 20925 detached [... and so on... ] I just killed this Child-Process using kill -9 - Puppetmaster still runs... no complains in the log. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Orxl9SeNKlMJ. 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 keeps spawning new child processes
On Jan 3, 2013, at 5:39 AM, a...@gmx.de wrote: Any other idea about how to find out what process 11957 actually is doing? There's another flag to strace, -f, if I recall correctly, that will follow forks of children. -- 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: Error on building basic agent-master
I found a work around for the same, I reverted to the earliest snapshot which I took when I imported the learning puppet VM and set the date to current date and time for making the SSL certificate valid. Then is started to work. On Wed, Jan 2, 2013 at 5:37 AM, Balasubramaniam Natarajan bala150...@gmail.com wrote: The closest I came to see a same kind of error in the link http://projects.puppetlabs.com/issues/9702 Here they have mentioned to delete the database and have puppet recreate it once again. Could some one give me more points as to how to delete the database ? -- Regards, Balasubramaniam Natarajan www.blog.etutorshop.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-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. attachment: Capture.PNG
[Puppet Users] Failed when searching for node some agent: Failed to find some agent via exec: Execution of '/usr/share/puppet-dashboard/bin/external_node some agent
Seeing this a lot lately, restarting puppet master service usually resolves it: Jan 3 13:17:01 puppet master puppet-master[24120]: (//some agent/Puppet) Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node some agent: Failed to find some agent via exec: Execution of '/usr/share/puppet-dashboard/bin/external_node some agent' returned : Any idea what causes this? In the posted configs *some company internals are masked*. cat /etc/puppet/puppet.conf [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl modulepath = /opt/masked/puppet/modules manifestDir = /opt/masked/puppet/manifests manifest = /opt/masked/puppet/manifests/site.pp [development] logdir = /opt/masked/log/puppet modulepath = /opt/masked/dev/puppet/modules manifestDir = /opt/masked/dev/puppet/manifests manifest = /opt/masked/dev/puppet/manifests/site.pp [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig server = masked report = true listen = true splaylimit = 0 runinterval = 30 [master] certname=masked reports = http,log reportdir = /var/lib/puppet/reports/upload reporturl = http://masked:3000/reports node_terminus = exec external_nodes = /usr/share/puppet-dashboard/bin/external_node Used packages: rpm -qa | egrep puppet|ruby rubygem-rake-0.8.7-2.1.el6.noarch ruby-mysql-2.8.2-1.el6.x86_64 libselinux-ruby-2.0.94-5.3.el6.x86_64 puppet-3.0.2-1.el6.noarch puppet-dashboard-1.2.16-1.el6.noarch ruby-1.8.7.352-7.el6_2.x86_64 ruby-irb-1.8.7.352-7.el6_2.x86_64 rubygems-1.3.7-1.el6.noarch ruby-augeas-0.4.1-1.el6.x86_64 ruby-shadow-1.4.1-13.el6.x86_64 puppet-server-3.0.2-1.el6.noarch puppetlabs-release-6-6.noarch ruby-libs-1.8.7.352-7.el6_2.x86_64 ruby-rdoc-1.8.7.352-7.el6_2.x86_64 rubygem-json-1.4.6-1.el6.x86_64 Any ideas? Thanks in advance! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/FnkowIcBME4J. 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 keeps spawning new child processes
There's another flag to strace, -f, if I recall correctly, that will follow forks of children. straced father process (pid 14850) using -f, caught the moment when a process was spawned that didn't go away and stayed at 100% cpu load (pid 18915). It's a lot output so I grep'ed for child process pid 18915 and piped it to | sort -u for a first look. Sorted/uniqued output: http://pkqs.net/~cf/strace_14850_child-18915_sort-u.log Whole output just grep'ed for child process pid: http://pkqs.net/~cf/strace_14850_child-18915.log -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/nSRz8zeVVP4J. 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] How to automate agent installation on nodes
What do you use to provision ? I am still working with non-virtual servers and I use Cobbler to install / configure Puppet “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin Hobbes) - Original Message - From: Nilesh nilesh.chaudha...@gmail.com To: puppet-users@googlegroups.com Sent: Thursday, January 3, 2013 6:13:23 AM Subject: [Puppet Users] How to automate agent installation on nodes Hello Everyone Can anyone please let me know once I am done with VM provisioing with vmware how to allocate hostname and install puppet agent on that node automatically. Thanks :) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/35pXckQzOCoJ . 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: file copy, multiple ignore doesn't work
On Wednesday, January 2, 2013 3:17:39 PM UTC-6, iamauser wrote:
I am trying the following to recursively copy a dir while ignoring things
like .hg and a few others.
file {
/etc/work-related-dir :
source = /path/to/masterfiles/work-related-dir,
recurse = 'inf',
owner = '0',
group = '0',
ignore = '{.hg,*.conf~}',
checksum = 'mtime',
backup = false;
}
Running a noop mode tries to copy everything including the one that
matches .hg, *.conf~. If I specify only a single parameter value for
ignore, i.e. .hg, then it doesn't try the copy of .hg directory and works
as expected.
Following an earlier post about this, I checked Ruby's globing options,and
found that the pattern I am providing matches multiple files in the source
area.
When you say you checked Ruby's globbing options, do you mean you
actually ran the glob against the target directory using the same Ruby that
the master runs on? It should be pretty easy to do that via irb, just to
be sure, though I don't actually see a problem with your glob. Since the
type docs specifically say that the ignore pattern is interpreted via
Ruby's globbing engine, I suggest you file a ticket if Puppet is including
files that genuinely match your 'ignore' glob.
Meanwhile, the Puppet type documentation subtly hints that you may be able
to pass an array of ignore patterns. I don't know whether that actually
works, but you could try it instead of glob alternation, i.e. ignore =
['.hg', '*.conf~'].
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/MkatCFwc9OQJ.
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: inspect resources that are already added to a manifest
On Thursday, January 3, 2013 4:08:54 AM UTC-6, Luke Bigum wrote: I'm taking shortcuts in my spare time with a tool that's probably 70% right for the job. It's for monitoring - I really like the idea of a Puppet module to describe or advertise how to monitor itself, it keeps them very self contained. Just a bit more on this - I generally see three categories of monitoring tools. Ones that are configured separately from your CRM and end up being a source of truth on their own are in my mind the worst. The next level up are ones either defined from or derived from your CRM. The best are auto-discovery, but they cost an absolute fortune. I'm trying to move my team from the first one to the second one with as little new tools as possible, which is where the 70% right for the job comment comes from. I'm using exported resources to describe how modules are monitored. The problem is that exported resources are not the equivalent of raw information passing. So when I want to start doing trickier things like group and analyse what is collected, exported resources don't cut it because it's not what they are designed for. Specifically what I was trying to do was collect exported resources of the same type and group them on the monitoring server. There is no predefined list of service names anywhere (unless you parse the node definitions) so that's why I wanted to go from resource collection to Array of Strings. A colleague has managed to reduce my 300 lines to 50 though so the need for craziness is reduced somewhat. We still need to do the Export a File trick and run a script on the monitoring server to build the complex configuration that exported resources are not designed to handle. The next iteration of this work might be to scrap resource collection in favour of querying PuppetDB directly to figure out what to monitor, but that's a lot more work than I'm prepared to do at this stage. Maybe in a few months... ;-) Querying PuppetDB in fact sounds like a good approach. One alternative I see would be to extend the main Puppet engine. Possibly that could take the form of a new Puppet face (which, now that I think of it, might just end up a front end to the DB query). You could also inspect the master's catalog cache instead of hooking directly into compilation. That would give you all the information you want, without parse-order issues. You could monitor the cache directory for changes to make the system nearly as immediate as what you you're doing now. Or if you have a list of known systems to monitor, then you can generate catalogs for them at any time via the puppet catalog face. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/BbIJAdmSA7gJ. 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] Exec command timeout
Hi list,
I've writed this module to deploy the public key of our debian repository :
file
{
/etc/apt/repos-public.key:
ensure = present,
mode = 440,
owner = root,
group = root,
source = puppet://puppet/apt/repos-public.key,
notify = Exec[install-key];
}
exec
{
install-key:
command = /usr/bin/apt-key add /etc/apt/repos-public.key
/usr/bin/apt-get update,
unless = /usr/bin/apt-key list | /bin/grep 'Private Repos',
}
So, it works fine, the key is correctly installed on all the nodes, but,
randomly, during the compilation, the command isn't executed and lock the
system during the timeout period (300s). It appear on all puppet
compilation of the node, and the only way to resolve it is to reboot. This
issue affect the nodes randomly, with an average of 1/month.
I've launch a manual compilation on a node actually impacted, with debug
option, and I only have this error :
debug: /Stage[main]/Apt/Exec[install-key]: Executing check
'/usr/bin/apt-key list | /bin/grep 'Private Repos''
debug: Executing '/usr/bin/apt-key list | /bin/grep 'Private Repos''
err: /Stage[main]/Apt/Exec[install-key]/unless: Check /usr/bin/apt-key
list | /bin/grep 'Private Repos' exceeded timeout
If I try to exec the apt-key list command, it will works correctly :
[toad2]~ # time /usr/bin/apt-key list | /bin/grep 'Private Repos'
uid Private Repos (priv) support@tld
real 0.023 user 0.000 sys 0.000 pcpu 0.00
I don't see any error in the system log files.
Have you any idea about this issue ?
For information, puppetmaster and the clients runs on Debian Squeeze.
Puppet version is 2.6.2 .
Thanks a lot !
Anthony
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/0k1VEfT7uu4J.
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] Configuration is not applied notice: Finished catalog run in 0.01 seconds
Hi guys, I am fairly new to puppet and I am having a problem with one of the clients. I recently installed a new server that should get config from puppet master. All similar servers I recently installed didn't have any problem. I installed puppet agent on the server and sent a sign request. SSL cert is signed but when I run puppetd manually I get the following: info: Retrieving plugin info: Caching catalog for client4 info: Applying configuration version '1357214285' notice: Finished catalog run in 0.01 seconds Even though it says catalog run finish nothing is applied. The strange thing is that I recently installed the same OS on the same machine and didn't get any problem. I tried various debug options but searching the output didn't help. debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderLdap: true value when expecting false debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Failed to load library 'rubygems' for feature 'rubygems' debug: Failed to load library 'selinux' for feature 'selinux' debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows is missing debug: Failed to load library 'ldap' for feature 'ldap' debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/public_keys/client4.pem]: Autorequiring File[/etc/puppet/ssl/public_keys] debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/state/classes.txt]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/certs/client4.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/private_keys/client4.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state] debug: Finishing transaction 70254557004780 debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/private_keys/client4.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /File[/etc/puppet/ssl/public_keys/client4.pem]: Autorequiring File[/etc/puppet/ssl/public_keys] debug: /File[/etc/puppet/ssl/certs/client4.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] debug: Finishing transaction 70254556183860 debug: Using cached certificate for ca debug: Using cached certificate for client4 debug: Finishing transaction 70254557715260 debug: Loaded state in 0.00 seconds info: Retrieving plugin debug: Loaded state in 0.00 seconds debug: Using cached certificate for ca debug: Using cached certificate for client4 debug: Using cached certificate_revocation_list for ca debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson debug: /File[/var/lib/puppet/lib]: Storing
Re: [Puppet Users] Exec command timeout
Note: I didn't follow this thread from the beginning, so this comment
might be out of place.
On Thu, Jan 3, 2013 at 8:59 AM, Anthony BRODARD
brodard.anth...@gmail.com wrote:
Hi list,
I've writed this module to deploy the public key of our debian repository :
file
{
/etc/apt/repos-public.key:
ensure = present,
mode = 440,
owner = root,
group = root,
source = puppet://puppet/apt/repos-public.key,
notify = Exec[install-key];
}
exec
{
install-key:
command = /usr/bin/apt-key add /etc/apt/repos-public.key
/usr/bin/apt-get update,
unless = /usr/bin/apt-key list | /bin/grep 'Private Repos',
}
So, it works fine, the key is correctly installed on all the nodes, but,
randomly, during the compilation, the command isn't executed and lock the
system during the timeout period (300s). It appear on all puppet compilation
of the node, and the only way to resolve it is to reboot. This issue affect
the nodes randomly, with an average of 1/month.
I've launch a manual compilation on a node actually impacted, with debug
option, and I only have this error :
debug: /Stage[main]/Apt/Exec[install-key]: Executing check
'/usr/bin/apt-key list | /bin/grep 'Private Repos''
debug: Executing '/usr/bin/apt-key list | /bin/grep 'Private Repos''
err: /Stage[main]/Apt/Exec[install-key]/unless: Check /usr/bin/apt-key
list | /bin/grep 'Private Repos' exceeded timeout
If I try to exec the apt-key list command, it will works correctly :
[toad2]~ # time /usr/bin/apt-key list | /bin/grep 'Private Repos'
uid Private Repos (priv) support@tld
real 0.023 user 0.000 sys 0.000 pcpu 0.00
I don't see any error in the system log files.
Have you any idea about this issue ?
For information, puppetmaster and the clients runs on Debian Squeeze. Puppet
version is 2.6.2 .
For our Squeeze installs, I perform the following:
class apt::config {
file { /etc/apt/sources.list.d/umd.list:
source = puppet:///modules/apt/etc/apt/sources.list.d/umd.list,
}
file { /etc/apt/trusted.gpg.d/umd.gpg:
source = puppet:///modules/apt/etc/apt/trusted.gpg.d/umd.gpg,
}
exec { update_apt_for_new_sources:
command = apt-get -q=2 update,
refreshonly = true,
subscribe = [
File[/etc/apt/sources.list.d/umd.list],
File[/etc/apt/trusted.gpg.d/umd.gpg],
],
}
}
Perhaps that will help.
-mz
--
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] Schedule yum update not found
Hello,
I resolved the structure inside my init.pp, but the command in the puppet agent
fails:
[………]
Jan 3 12:25:45 mail2 puppet-agent[31902]: (/Stage[main]/Updateso/Exec[yum
--exclude=drbd* --exclude=kernel* --exclude=mysql* --exclude=php* update
-y]/returns) change from notrun to 0 failed: yum --exclude=drbd*
--exclude=kernel* --exclude=mysql* --exclude=php* update -y returned 1 instead
of one of [0] at /etc/puppet/modules/updateso/manifests/init.pp:13
[………]
My class updateso
[………]
class updateso {
schedule{ daily:
range = 10 - 15,
repeat = 2,
}
exec { yum --exclude=drbd* --exclude=kernel* --exclude=mysql* --exclude=php*
update -y: #LINE 13
schedule = daily,
path = /usr/local/bin/:/bin/:/usr/bin/,
# refreshonly = true,
# command = yum --exclude=kernel* --exclude=mysql* --exclude=php*
update -y,
}
#}
}
[………]
The line 13 is the command yum --exclude ……
Thanks!
El 02-01-2013, a las 16:53, Kazor miguelc...@gmail.com escribió:
Hello guys,
I'm creating class for update my servers these are Centos (RedHat Family) .
But when i run from puppet client, only apply update version but the command
yum update declared within in my class not found .
My class updateso (/etc/puppet/modules/updateso/manifests/init.pp) :
[.]
class updateso {
#operatingsystem = CentOS
#operatingsystemrelease = 5.8
#osfamily = RedHat
#architecture = x86_64
if $osfamily == 'RedHat' {
schedule { daily:
period = daily,
range = 12 - 17,
repeat = 1,
}
exec { Update SO:
user = root,
command = /usr/bin/yum --exclude=kernel* --exclude=mysql*
--exclude=php* update -y,
schedule = daily,
refreshonly = true,
}
}
} #End class
[.]
My instance site.pp
[.]
node 'mail.example.com' {
include updateso
}
[.]
From agent:
[.]
[root@correo ~]# puppet agent --test
info: Caching catalog for mail.example.com
info: Applying configuration version '1357155391'
notice: Finished catalog run in 0.12 seconds
[.]
¿Any suggestions?
Thanks!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/CoiasMKiwMQJ.
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] Exec command timeout
Hi Matt,
Thanks for your answer. I will try your module, it seems better that mine :)
But I don't think that the module is the problem, because it works fine on
all the node. Just, I don't know why, it suddenly fail, and works again
after reboot.
Anthony
Le jeudi 3 janvier 2013 16:27:40 UTC+1, Matt Zagrabelny a écrit :
Note: I didn't follow this thread from the beginning, so this comment
might be out of place.
On Thu, Jan 3, 2013 at 8:59 AM, Anthony BRODARD
brodard...@gmail.com javascript: wrote:
Hi list,
I've writed this module to deploy the public key of our debian
repository :
file
{
/etc/apt/repos-public.key:
ensure = present,
mode = 440,
owner = root,
group = root,
source = puppet://puppet/apt/repos-public.key,
notify = Exec[install-key];
}
exec
{
install-key:
command = /usr/bin/apt-key add /etc/apt/repos-public.key
/usr/bin/apt-get update,
unless = /usr/bin/apt-key list | /bin/grep 'Private Repos',
}
So, it works fine, the key is correctly installed on all the nodes, but,
randomly, during the compilation, the command isn't executed and lock
the
system during the timeout period (300s). It appear on all puppet
compilation
of the node, and the only way to resolve it is to reboot. This issue
affect
the nodes randomly, with an average of 1/month.
I've launch a manual compilation on a node actually impacted, with debug
option, and I only have this error :
debug: /Stage[main]/Apt/Exec[install-key]: Executing check
'/usr/bin/apt-key list | /bin/grep 'Private Repos''
debug: Executing '/usr/bin/apt-key list | /bin/grep 'Private Repos''
err: /Stage[main]/Apt/Exec[install-key]/unless: Check /usr/bin/apt-key
list | /bin/grep 'Private Repos' exceeded timeout
If I try to exec the apt-key list command, it will works correctly :
[toad2]~ # time /usr/bin/apt-key list | /bin/grep 'Private Repos'
uid Private Repos (priv) support@tld
real 0.023 user 0.000 sys 0.000 pcpu 0.00
I don't see any error in the system log files.
Have you any idea about this issue ?
For information, puppetmaster and the clients runs on Debian Squeeze.
Puppet
version is 2.6.2 .
For our Squeeze installs, I perform the following:
class apt::config {
file { /etc/apt/sources.list.d/umd.list:
source =
puppet:///modules/apt/etc/apt/sources.list.d/umd.list,
}
file { /etc/apt/trusted.gpg.d/umd.gpg:
source = puppet:///modules/apt/etc/apt/trusted.gpg.d/umd.gpg,
}
exec { update_apt_for_new_sources:
command = apt-get -q=2 update,
refreshonly = true,
subscribe = [
File[/etc/apt/sources.list.d/umd.list],
File[/etc/apt/trusted.gpg.d/umd.gpg],
],
}
}
Perhaps that will help.
-mz
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/S2dc4TXrQTMJ.
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: file copy, multiple ignore doesn't work
When you say you checked Ruby's globbing options, do you mean you actually ran the glob against the target directory using the same Ruby that the master runs on? It should be pretty easy to do that via irb, just to be sure, though I don't actually see a problem with your glob. Since the type docs specifically say that the ignore pattern is interpreted via Ruby's globbing engine, I suggest you file a ticket if Puppet is including files that genuinely match your 'ignore' glob. Yes, I used irb to test the matching files with the patterns. Meanwhile, the Puppet type documentation subtly hints that you may be able to pass an array of ignore patterns. I don't know whether that actually works, but you could try it instead of glob alternation, i.e. ignore = ['.hg', '*.conf~']. That worked... Thanks for the tips... I believe I tried this earlier, but missing a comma somewhere ;) John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/DJeBsPq6gooJ. 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-dashboard load balanced report processing issues.
Even an nfs share will not fix this. We tried it. We had to make dashboard active - passive to fix it. Otherwise lots of dashboard errors result which must be cleared via rake task or the dashboard slows to a crawl. On Jan 2, 2013 1:56 PM, jemmorey jor...@obsecurities.com wrote: Looks like there is no current method to prevent multiple dashboard nodes from stomping on each others reports, the delayed_jobs table does have a locked_by, but that is only used during the actual event processing. mysql describe delayed_jobs; ++--+--+-+-++ | Field | Type | Null | Key | Default | Extra | ++--+--+-+-++ | id | int(11) | NO | PRI | NULL| auto_increment | | priority | int(11) | YES | MUL | 0 || | attempts | int(11) | YES | | 0 || | handler| longtext | YES | | NULL|| | last_error | text | YES | | NULL|| | run_at | datetime | YES | | NULL|| | locked_at | datetime | YES | | NULL|| | failed_at | datetime | YES | | NULL|| | locked_by | varchar(255) | YES | | NULL|| | created_at | datetime | YES | | NULL|| | updated_at | datetime | YES | | NULL|| ++--+--+-+-++ 11 rows in set (0.00 sec) I suppose I will open this as an RFE. If anyone has any other ideas how to do this (other than the dreaded NFS share) please let me know. Thanks! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/KufkHt4fpc8J. 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-mysql module
Hello All, I'm never really sure whether to email the maintainers for modules or the list so I figure posting to the list is a good place to start;-) So I've started testing out the puppetlabs-mysql module today and I like what I'm seeing but have a few questions/critiques/concerns regarding the types/providers. I'm finding the names, database, database_user, and database_grant rather generic. Unless there are plans to merge mysql, postgresql, etc, into a single database module shouldn't they be a bit more specific like mysql_db, mysql_user, and mysql_grant? Also, what about supplying my.cnf instead of creating from a template which is the default action? I see you can use mysql::server::config, which I haven't tried yet, to add additional params but I'm thinking that could lead to a rather large/unwieldy manifest given the vast number of options available. Nice work and I hope to see my pull request for SuSE support accepted soon;-) -- Later, Darin -- 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] Configuration is not applied notice: Finished catalog run in 0.01 seconds
Hi,
First thing I would is check where I think this node is declared and stick a
notify there to spit out a message on the run.
node nodename {
notify {some message and maybe a $var or $::fact
}
Then use that same kind of message to trace through your code and find out the
path your node travels.
That should get you further along.
Den
On 04/01/2013, at 2:08, Aleksandar Nikolic aleksniko...@gmail.com wrote:
Hi guys,
I am fairly new to puppet and I am having a problem with one of the clients.
I recently installed a new server that should get config from puppet master.
All similar servers I recently installed didn't have any problem. I installed
puppet agent on the server and sent a sign request. SSL cert is signed but
when I run puppetd manually I get the following:
info: Retrieving plugin
info: Caching catalog for client4
info: Applying configuration version '1357214285'
notice: Finished catalog run in 0.01 seconds
Even though it says catalog run finish nothing is applied. The strange thing
is that I recently installed the same OS on the same machine and didn't get
any problem. I tried various debug options but searching the output didn't
help.
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does
not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Failed to load library 'rubygems' for feature 'rubygems'
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature
microsoft_windows is missing
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys/client4.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state/classes.txt]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/client4.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys/client4.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: Finishing transaction 70254557004780
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys/client4.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
debug: /File[/etc/puppet/ssl/public_keys/client4.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/certs/client4.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: Finishing transaction
Re: [Puppet Users] Re: Puppet 3.0: Not authorized to call find on /file_metadata, more issues?
I see the ChangeLog in 3.0.2 and this bug is still not addressed? Is there a technical problem that is not yet resolved, or is this just a matter of priority and time. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/aoZ7BtDcqwwJ. 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] Announce: Puppet-Dashboard 1.2.17 Available [ Security Release ]
Puppet Dashboard 1.2.17 is now available. This release of Puppet Dashboard addresses CVE 2012-5664. All users are strongly encouraged to update when possible. CVE-2012-5664 affects Ruby on Rails, specifically in all versions of ActiveRecord. The vulnerability exposes ActiveRecord to arbitrary SQL Injection. More information on the vulnerability can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5664 Downloads RPM packages for are available at https://yum.puppetlabs.com/el or /fedora Debian packages are available at https://apt.puppetlabs.com Source can be downloaded from https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.17.tar.gz, along with the accompanying signature file, https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.17.tar.gz.asc . See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet 1.2.17 Security Fixes Aaron Stone (1): 5b7bdca Patch for CVE-2012-5664: options hashes should only be extracted if there are extra parameters -- 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] Rails ActiveRecord vulnerability Puppet legacy storeconfigs [ security ]
Good day, A security vulnerability has been discovered in Ruby on Rails, specifically in all versions of ActiveRecord. It is assigned CVE-2012-5664. The vulnerability exposes ActiveRecord to arbitrary SQL Injection. CVE details can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5664 If you currently use Puppet's ActiveRecord-based storeconfigs, you will mostly likely want to update your ActiveRecord version or patch your version to address the risk (or even better, use PuppetDB, a drop-in replacement: http://docs.puppetlabs.com/puppetdb/). See the following post for more information on the vulnerability: https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/DCNTNp_qjFM Regards, Moses Mendoza Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Enterprise hotfixes for ActiveRecord vulnerability [ CVE-2012-5664 ]
Good day, A security vulnerability has been discovered in Ruby on Rails, specifically in all versions of ActiveRecord. It is assigned CVE-2012-5664. The vulnerability exposes ActiveRecord to arbitrary SQL Injection. CVE details on the vulnerability can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5664 Additional detailed information can be found in the following post: https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/DCNTNp_qjFM Puppet Labs has generated security hotfixes patching the vulnerability for the latest in the 1.x series and 2.x series of Puppet Enterprise. These can be downloaded from the Puppet Labs security page: http://puppetlabs.com/security/cve/cve-2012-5664/. These security fixes will also be included in the forthcoming patch releases of Puppet Enterprise, versions 1.2.6 (security only) and 2.7.1 (security and bug fix). If you have any questions or comments, please get in touch with Puppet Labs Support. We always want your feedback! Regards, Moses Mendoza Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Have Puppet *call* REST APIs
Hi, I hope this is just not my Google-fu lacking, but can you configure Puppet modules to make REST API calls inherently with Puppet? I'm talking about 3rd party REST APIs, not Puppet's API. I'm thinking of rolling my own plugin, but wondered if I'm missing something here. Thanks in advance, Rob -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/JDygUj18h2EJ. 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] How to automate agent installation on nodes
Thanks for the reply :) I am using vCenter as a provisioing engin . I will try this option and let you know ... On Thursday, January 3, 2013 7:25:01 PM UTC+5:30, Ygor wrote: What do you use to provision ? I am still working with non-virtual servers and I use Cobbler to install / configure Puppet “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin Hobbes) - Original Message - From: Nilesh nilesh.c...@gmail.com javascript: To: puppet...@googlegroups.com javascript: Sent: Thursday, January 3, 2013 6:13:23 AM Subject: [Puppet Users] How to automate agent installation on nodes Hello Everyone Can anyone please let me know once I am done with VM provisioing with vmware how to allocate hostname and install puppet agent on that node automatically. Thanks :) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/35pXckQzOCoJ . To post to this group, send email to puppet...@googlegroups.comjavascript:. To unsubscribe from this group, send email to puppet-users...@googlegroups.com javascript:. 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/fROc8zavh8oJ. 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.
