Re: [Puppet Users] Error while installing/configuring foreman-proxy 1.12: Invalid parameter dns_realm on Class[Foreman_proxy]
On 6 December 2016 at 19:40, Sankara wrote: > While running “puppet agent -t” (to install and configure foreman-proxy) , I am getting the below error on my node. Can you please help me to find what could be the issue? > > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter dns_realm on Class[Foreman_proxy] at /dev/modules/fmanproxy/manifests/config.pp:128 on node poc-agent.local > Warning: Not using cache on failed catalog > Error: Could not retrieve catalog; skipping run Looking at https://github.com/theforeman/puppet-foreman_proxy/blob/master/manifests/init.pp the $dns_realm parameter isn't exposed for configuration - it's only used within params.pp to set $dns_tsig_principal (which *is* available in init.pp). Feel free to submit a bug or even send a patch if you feel that behaviour is wrong :) Cheers Greg -- Greg Sutcliffe Community Lead, Foreman IRC: gwmngilfen -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE%3D3ySCn1%2BVMGyGn-FD1JcwGKbZvNBo4vU7HdaYuSn1pt58k9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Deploy bacula with puppet and foreman
On 2 February 2016 at 18:31, Timotheus Titus wrote: > As far as I see I have to call bacula::director::client somehow as it > defines the client-config. > > But the question is: How can I do that? > > I'm not familiar with the bacula module, but bacula::director::client seems to be a define rather than a class. ENCs (which is what Foreman is to Puppet) cannot directly declare defines, they can can only declare classes and parameters. The common pattern for this is to use a wrapper class, taking hash of data that you can use with create_resources. We get this question a lot on the Foreman mailing list, so we have a wiki page detailing some examples. See http://projects.theforeman.org/projects/foreman/wiki/Instantiate_Puppet_resources Hope that helps! Greg -- Greg Sutcliffe IRC: gwmngilfen -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE%3D3ySANqg%3DaOhpZ9CYbQXtcsJL7Vu4SToVtubgbhZ89pKndSQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Can I just edit the dashboard widgets?
On 13 October 2015 at 15:54, UK_beginner wrote: > I'm wanting to make some changes to the conditions used in building the > dashboard lists - is it possible to just edit the erb files in > app/views/dashboard? > > I've tried editing one of the conditions in the _status_widget.html.erb but > even after restarting foreman & logging out and back in, the dashboard > doesn't reflect the changes? I'm guessing this is a Foreman-specific question? You might have more luck getting replies on the Foreman Users list - https://groups.google.com/forum/#!forum/foreman-users since not everyone here uses Foreman. Cheers, Greg -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE%3D3ySCLjK6SXQ_YLVCu8X1JfYZzbSG7MCeSxvAFhAJxKi4wcw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: puppetdb, foreman, one particular node has a problem
On 16 October 2013 14:39, Steve Wray wrote: > Your response is encouraging, thanks. > > I wasn't using sqlite, I was using postgresql. I have about 100 nodes (and > growing) sqlite quickly became unusable. > Ah ok. There are changes to the ENC script (which also registers new Hosts in the Foreman interface) in 1.3, but due to a variety of reasons, the ENC (/etc/puppet/node.rb) isn't packaged. So potentially, that needed an update to fix your host registration problem. One of the things I tried was aptitude install with =version but this > didn't work, apparently it couldn't find the old versions in the repo. I > started downloading the .debs to install the old versions manually but > realised it would be quicker to just uninstall foreman, we had just > commissioned a bunch of servers, and more arriving all the time, so I > really had to just get a move on. > Understandable, I've been in those firefighting situations. It's interesting that this didn't work for you though - I was using that syntax this very morning to test the sqlite3 error fixes :) > > Honestly, if it hadn't been a Debian-based system, say CentOS, I'd have > been a LOT more cautious about the 8upgrade but I've got so used to things > just not breaking in stable (last time anything like that bit me was when > someone decided to apply a 'security' patch to sudo). > > When I have some breathing room I'll do some more tests with the newer > version of foreman. > Looking forward to your feedback. See you on foreman-users :) -- 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.
Re: [Puppet Users] Re: puppetdb, foreman, one particular node has a problem
On 16 October 2013 11:48, Steve Wray wrote: > Sure, I'm using this repository > > deb http://deb.theforeman.org/ precise stable > > it looks as if the upgrade didn't make the required changes to the > database, or something like that. I dropped the db and recreated it and the > error about the missing column went away but still couldn't enroll new > nodes. > Firstly, as the deb package maintainer for Foreman, I'm sorry you had issues. Thanks also for the bug report - we've just tracked down and fixed an issue which specifically affects sqlite3 upgrades (I'm not sure if you are on sqlite3, but your symptoms fit, I think). 1.3.0-2 is now in the repo with the fix. With regards to upgrades not breaking things, I agree. We spent some time discussing the state of the Debian Foreman repo a few weeks ago[1] and one outcome of that was that we would create a repo for each major version (eg http://deb.theforeman.org/ precise 1.2) and that 'stable' would track the latest release. This was done, and as 1.3 was released on Monday, 'stable' now points to 1.3. The 1.2 repo allows people who wish to be conservative to lock themselves to a particular release. An unavoidable side-effect of this is that since we only had "stable" before, everyone is currently using it. I accept we could have done a better job of publicising the existence of the 1.2 repo before 1.3 came out though. I've just sent a mail to our users and announce lists to make people more aware of the new repos. Once again, apologies for your troubles, and thanks for the feedback. Greg [1]https://groups.google.com/d/msg/foreman-dev/76A7LmuPzLM/O8ob4aEX3VAJ -- 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.
Re: [Puppet Users] Re: Puppet calls the ENC twice for some nodes.
On 20 Sep 2013 18:05, "Greg Sutcliffe" wrote: > the should authoritatively be in. Gah, phone keyboard. "The *client* should authoritatively..." Sorry Greg -- 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.
Re: [Puppet Users] Re: Puppet calls the ENC twice for some nodes.
Is this puppet3? As I recall, in puppet3, the master makes a separate call to the enc to determine the environment the should authoritatively be in. Once that's established, it makes a second call to get the classes and parameters. Hth, Greg On 20 Sep 2013 13:46, "pierra mathieu" wrote: > Thanks for the answers and sorry for my late one, > > I've only one agent process running : > >> ps -aef | grep puppet >> root 4080 2811 0 14:14 pts/000:00:00 grep puppet >> root 18328 1 0 Sep12 ? 00:00:02 /usr/bin/ruby >> /usr/bin/puppet agent > > > And the agent cycle isn't really fast, something like 5-10 sec. > > I was thinking about adding an acknowledgment the first time a class is > requested by a node, so i'd like to choose which class to return for *each > * request. > Moreover, I'm curious and this comportment from puppet seems a little bit > weird/useless. > > > For information, here is my agent puppet.conf: > >> [main] >> logdir = /var/log/puppet >> rundir = /var/run/puppet >> ssldir = $vardir/ssl >> pluginsync = true >> [agent] >> classfile = $vardir/classes.txt >> localconfig = $vardir/localconfig >> server= >> report = true >> usecacheonfailure = false > > > Commenting *pluginsync* or *report* doesn't change anything. > > Any other ideas ? > > Thanks. > > Le lundi 9 septembre 2013 13:26:26 UTC+2, pierra mathieu a écrit : >> >> Hi everyone, >> >> I have an issue setting up Puppet with an ENC. >> For some nodes, puppet calls my ENC twice with a 2 sec interval. >> >> All my agents share the same configuration file. >> >> >> Considering this very basic ENC : >> >> #!/bin/bash >>> nodeName=$1 >>> echo `date` $nodeName >> /tmp/encCalls >>> echo "--- >>> classes: >>> testClass:" >> >> >> >> Here is the content of /tmp/encCalls after a few run on two nodes. >> >> Mon Sep 9 11:36:15 CEST 2013 : host1 >>> Mon Sep 9 11:36:17 CEST 2013 : host1 >>> Mon Sep 9 11:41:04 CEST 2013 : host2 >>> Mon Sep 9 11:42:04 CEST 2013 : host1 >>> Mon Sep 9 11:42:06 CEST 2013 : host1 >>> Mon Sep 9 11:45:13 CEST 2013 : host2 >> >> >> >> Anybody knows why two calls are made ? >> >> Thanks. >> > -- > 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.
Re: [Puppet Users] apt repository appears to have dependency issue with latest release (3.2.1)
On 24 May 2013 21:55, Eric Sorenson wrote: > Hi Greg, thanks for the info -- I slightly disagree that the docs should > describe manual installation; IMO they should describe supported/official > ways to do things, because anything that's documented gets interpreted as > being supported and official :) > Amen to that ;) > That said, we could punch up the importance of including the deps > repository. It's been necessary for EL users for a long time, but this was > the first Puppet release that pulled in a hard dependency for Debian-based > systems. > I'll snip here as I broadly agree with you anyway ;) I think it would be fine to have an "Advanced" or "Manual APT" section that's away from the recommended route. I don't object to a recommended route _at all_ but I do feel the information should be there for those that want to find it. As of today (I think) one cannot find mention of the additional repo in the docs. Greg freenode: gwmngilfen -- 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: apt repository appears to have dependency issue with latest release (3.2.1)
On 23 May 2013 22:25, Eric Sorenson wrote: > Quick question for those of you affected by this -- what did you to do to > add the puppetlabs apt repo? > > Did you do it through the method described here: > http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu > > .. or some other way? I'm trying to suss out whether the docs / packages > are messing people up. > I've hit this, but it's because I have the main Puppetlabs repo in my preseed file for new virtual machines, so it's available within the installer environment. That's just text, so I only have a line for "deb http://apt.puppetlabs.com main" I think the "install a deb which sets up the repos" is good for most people, but there should always be the docs for the manual apt setup for those going a different route. As of right now, I don't see a "dependencies" repo mentioned anywhere on the page you linked, Eric I'll also add a voice the question on the logic behind a separate dependencies repo, although only because you're adding work to your documentation requirements ;) Cheers, Greg -- 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] Best practices on puppet installation
On 25 November 2012 21:36, Ugo Bellavance wrote: > Ok, but it looks like foreman is not fully puppet-3 compatible up to now. I > think I'll wait for that. We have all the required changes for puppet-3 compatibility in the develop branches of foreman and foreman-proxy - hoping to get a release candidate out soon, so stay tuned :) Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Can Puppet alert about dead nodes?
This post to the list concerns PuppetLabs ceasing development on Dashboard - https://groups.google.com/forum/#!msg/puppet-users/j44EbTJY7HI/EQSJgh-g1fgJ A few people have expressed interest in taking Dashboard on, but I've seen no announcement that this has officially happened. Perhaps I missed it though... I'd love to be corrected if so. Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Can Puppet alert about dead nodes?
On 1 November 2012 17:54, Lucas Vickers wrote: > I am currently using the open source edition so I have no dashboard. > Puppet Dashboard is opensource, so you could use it, but it's being deprecated (last I heard, anyway). You could also checkout The Foreman, which will display nodes out-of-sync (and email you about it, if you like). Greg -- 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] Using Exported Resources in nginx loadbalancer conf
On 25 September 2012 12:03, Jon Ward wrote: > Hi all, > > I'm attempting to use exported resources to dynamically generate an nginx > config file. What I'd like to do if have all my web servers export their > hostname inside a file resource, and have these collected by my loadbalancer > and used in the config file, restarting nginx if anything has changed. Nginx can do include directives, right? Can you do something like: include conf.d/upstream/*.conf and then have each host export a file in conf.d/upstream/$hostname.conf containing $hostname:$port (or whatever is needed). Not sure if that will work, my nginx is a little rusty... -- 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] Creating a system module path (starting with Telly)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 here As a distribution packager, a clear place to put things specific to the distribution is a big win for me. I've struggled in the past decided whether to package the clean upstream sources, or to add my own tweaks as well. To date, I've kept it clean, but this makes it easier to mix-and-match the two, and still be able to trace whether a problem lies in my distribution module or somewhere in the Puppet core. Greg - -- IRC: gwmngilfen www.github.com/GregSutcliffe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ea0EACgkQ8O7RN8oK65O7ywCfYkmbP04gwn2x9641D0p3B0cf ZRAAn3RpalobnbuyvQBcodGTY6tS7ULq =Pix6 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Templating DHCP3-Server Need To Loop Through Subnets
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu 26 Apr 2012 17:24:17 BST, Brian Carpio wrote:
> $subnet = [ 192.168.10.0, 192.168.20.0, 192.168.30.0 ]
> $range = [ 192.168.10.115 192.168.10.120 ]
Sounds like you need a Hash here:
$subnets = { '192.168.10.0' => '192.168.10.115 192.168.10.120',
'192.168.20.0' => '192.168.20.105
192.168.20.130',
}
Then access it with something like:
<% subnets.each do |subnet,range| -%>
subnet <%= subnet %>
range <%= range %>
<% end -%>
Hope that helps,
Greg
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+ZexQACgkQ8O7RN8oK65P3DACeNr38heQ8cILSbEgbGW1CMhng
ESsAniVsAJpfAoWklmCk+6qDCAwji/7d
=M9cK
-END PGP SIGNATURE-
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Does one puppet master support multiply users to manage their resources?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri 13 Apr 2012 12:01:13 BST, Sans wrote: > I'm not entirely sure but I don't think you can do that with single > server - Puppet is actually for that. Someone please correct me if I'm > wrong. But, as Puppet can maintain itself, all your users can use > their machine as puppet-master and puppet-agent at the same time and > can do whatever they want. Cheers!! > > > On Apr 13, 4:06 am, runner wrote: >> Hi, >> >> I am a new user of puppet. We want every user of our group to manage >> software in his/her machines. How can puppet support this? Thank you. >> >> BR/Peng Yong > I'd say there's a few ways to achieve that. Sans describes one of them - - local catalogs with local masters (or just puppet apply) If you want to run a standard master/slaves setup, the you could either keep the manifests in a version control system (say, git) and give your devs access to git. For more fine-grained control, put the lists of packages into some form of external data source (an ENC, or an external plugin like Hiera) and give your devs access to the lists on their machine. Of course, the latter reuires that your modules are (re)written to get their data appropriately. Cheers, Greg - --- OpenPGP -> KeyID: CA0AEB93 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+IH+kACgkQ8O7RN8oK65ONxgCfQOdwmmu/8PmONPz3f8Wci1SE Ph8AoJLNzc/TwWyCdnVG9Lu8lWR7xwnE =gf7z -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Win32API error with 2.7.8
Hi Josh, Thanks for clearing that up - given that it's benign, then I won't worry too much about it :) I'm pretty much stuck with whatever Arch decide to give me for Ruby versions. I guess that makes us Arch users the canary testers for Puppet. So far nothing seems broken - every message I get is only a warning. Are PuppetLabs interested in reports on what 1.9.3 errors I come across, or do you have your own roadmap for future ruby versions? I don't want to open a bunch of tickets if they'll be closed because of unsupported ruby versions - that'll just annoy everyone involved :) Cheers again, Greg -- 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/-/648iPhGyshYJ. 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] Win32API error with 2.7.8
Hi Josh, I think I've found it. I fired up a spare (clean) Debian VM for testing - and no errors. So I poked further... A while back, I was plagued by this on my arch clients: Could not load confine test 'operatingsystem': cannot load such file -- puppet/provider/confine/operatingsystem Intrigued why it was only on Arch, I copied operatingsystem.rb from another system into lib/puppet/provider/confine in one of my modules. When I removed it, 2.7.8 started working fine - on both OSes. So that's the initial panic over... Any idea on a proper fix for the new (old? :P) issue? Greg -- 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/-/5XnrfVI9BK0J. 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] Win32API error with 2.7.8
Hi Josh, I'll give you both in case it matters (since one is ruby 1.8 and one is 1.9) Master - http://pastie.org/2993476 Agent - http://pastie.org/2993486 I'm on IRC in #puppet (gwmngilfen) at the moment if you want to real-time the troubleshooting. Not a problem if you've got other priorities :) Greg -- 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/-/FGFXVfWuIngJ. 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] Win32API error with 2.7.8
Hi Josh, Of course. I'll pastie so as not to spam the list :) Here's an Arch client - http://pastie.org/2993397 Here's the Debian running "puppet master -- trace --debug" - http://pastie.org/2993401 Cheers, Greg -- 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/-/CLQ7bWd9wbAJ. 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] Win32API error with 2.7.8
Hi all, I've just started testing 2.7.8 after the release today, and almost immediately hit a problem: err: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: uninitialized constant Module::Win32API This occurs on multiple machines, under both "puppet agent" and "puppet master". Master is Debian Wheezy, clients are Archlinux. Last line of the trace seems to point the finger here: /usr/local/lib/site_ruby/1.8/puppet/util/adsi.rb:30:in `computer_name' I've had a quick poke about in the requires but I can;t work out why two different OSes are trying to execute Windows code any pointers? Cheers, Greg -- 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/-/2ivDJd7hp4YJ. 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: SSL issues on ruby1.9
On 25 November 2011 12:18, linuxbsdfreak wrote: > Hi Greg, > > There are some problems with SSL and ruby 1.9.2. Please visit the > link below for solving the issue. > > http://urgetopunt.com/puppet/2011/09/14/puppet-ruby19.html Hi Kevin, Thanks for the reply. As I stated in my original post, I've tried this workaround (your link links back to the link I posted in the first place), and it doesn't solve the problem for me, so I'm now looking at how to debug this further. Cheers, Greg -- 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] SSL issues on ruby1.9
Hi all, I'm having issues with getting a client to request a certificate from my master when using Ruby 1.9. The error message is: "err: Could not request certificate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed" I saw earlier messages on this topic (https://groups.google.com/d/topic/puppet-users/-knxubNs6sY/discussion) but the workaround suggested there (to create a hashed link to the CA) doesn't seem to solve the problem for me. Some details of my setup: Master: Debian Wheezy, Puppet 2.7.6, Ruby 1.8.7, Passenger Client: Archlinux, Puppet 2.7.6, Ruby 1.9.3 As stated, copying and hashing the ca from the Debian machine to the Arch machine doesn't solve the problem. I thought I might have an issue with differing versions of ruby, so I fired up a second Archlinux machine (so Ruby 1.9.3 / Puppet 2.7.6 again, but Webrick this time) and even then still got the same behaviour - with or with out the pre-hashed ca, I get the same error. For completeness, it should be said that this second Arch box can create it's own ca, and run as an agent against itself. I'm stumped. Presently I'm waiting for ruby1.8 to compile for Arch. I know this will solve the issue, but I'd really like to get 1.9 working since it's the default in Arch. I plan to try and find out what 1.8 is doing that 1.9 is not (or vice-versa) but if anyone has encountered this or wants to give me some tips on where to look, that would be appreciated... Cheers, Greg -- 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] Concat::Fragment collection broken in 2.7.5
On Friday, 7 October 2011 15:12:08 UTC+1, Bruno Leon wrote: > > sorry for the delay, I did a few tests and found out that the puppet > master does not even go as far a querying the database. > Starting from a clean query log (mysql), there is no sign of > Concat::Fragment (tried small case as well). > I concur - I'm using Foreman, which complicates the mysql trace, but as best I can see, it's not querying the databse for the exported resources at all. Since Dan asked for traces, here they are, master and node: http://pastie.org/2682017 Here's hoping the regression fixes in 2.7.6 fix this too :) Cheers, Greg -- 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/-/OAiJdI2v2eoJ. 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] Concat::Fragment collection broken in 2.7.5
Almost a "me-too" post, I should try to avoid that... This sounds like the mail I sent on Monday - I can certainly confirm Bruno's findings for collecting exported custom defines. I get the same error message, and I'm also using a remote MySQL database (no queueing agent, just direct access). I'd love to help with the debugging but I'm on a training course this week, and the connection is waaay too slow for database debugging. If you've not solved it by Monday, I'll dive in and provide some debug logs and db traces. Watching this thread with interest :) Greg -- 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/-/1mwaNRX2OX0J. 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] Problems with exported resources after upgrade to 2.7.5
Hi all,
I use a number of exported resources, some of which are exported custom
definitions.Since
upgrading to 2.7.5, I've seen an issue which is driving me up the wall
trying to debug it. Hopefully
someone can help :)
Consider the following three snippets of code:
*$modulepath/ntp/manifests/ntp_register.pp:*
define basics::ntp_register ($content="", $order=10) {
concat::fragment{"ntp_conf_$name":
target => "/etc/ntp.conf",
content => "$content",
order => "$order"
}
}
$modulepath/servers/manifests/ntp_server.pp
class servers::ntp_server {
@@basics::ntp_register { "Server Ntp $domain": content => "stuff here\n" }
}
*$modulepath/servers/manifests/ntp_client.pp*
class servers::ntp {
Basics::Ntp_register <<| title == "Server Ntp $domain" |>>
}
So we have a defined resource, an export of that resource, and a collection
of it. In 2.7.3, this worked fine,
however, in 2.7.4 and 2.7.5 I get
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find type
Basics::Ntp_register on node client.foo.bar
I'm not sure what's changed that's causing this. I've read some stuff about
loading order, but they seem
to be old bugs that were fixed ages ago. I can see that rewriting this as a
local definition containing an
exported resource might work, but I'd rather understand what's wrong with my
approach first.
Thanks in advance,
Greg
--
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/-/D2Ou_f59FIoJ.
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] Skipped schedule resources in reports
Hi all, Since upgrading a few test machines from 2.6.7 to 2.7.3, I've noticed something slightly odd. Every single run reports 6 skipped resources, yet the reports are empty - they only state the execution time as per usual). On digging further it seems that the auto-generated Schedule resources (type/schedule.rb, line 307) are the entities being skipped, presumably because I'm not using them in any of my manifests. This is leading to a lot of reports with spurious data in them - since I don't use schedules, why should I care that Puppet skipped the default ones? This wouldn't be an issue, but I'm processing the reports and producing emails which summarize activity in the last hour, so for every 2.7.3 node, I'm seeing 12 skipped resources per hour, which is noise that swamps the real data of resources that have changed for good reason. Is there a way to disable these default schedules, or the reporting of them? I tried "--ignoreschedules" on the commandline, but I get the impression that this causes other resources to run outside their normal schedule, rather than disabling the schedules themselves. As a hack, I added "return Array.new" to the self.mkdefaultschedules listed above, which stops the resources being generated, but this seems an ugly hack, and one I seem to have to make on every node. Is there a better way? Regards, Greg -- 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/-/KUcUT4hu148J. 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] Dashboard and remote MySQL BDD
On 21 July 2011 11:19, david ramblewski wrote: > Hi, > > I've installed Dashboard on my server and I aim to remotely request > the MySQL Database. > All documentations read explain the way to roll out using Dashboard > and MySQL Database on the same server. > > I am looking for any information to achieve that because I haven't > found any from the time being and I wonder if it's just possible. > > Thanks you, > > David Perfectely possible - I had Puppet, Dashboard, and MySQL on 3 separate machines. Dashboard is a rails app - so you configure the db in config/database.yml. I had the following: production: host: dbserver.domain database: dashboard username: dashboarduser password: mydbpass encoding: utf8 adapter: mysql Hope that helps :) Greg -- 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] Concat Module posted to Onyx Point Github.
Hi again, After an hour or three of hacking, I've managed to add the insync? checks to both the build and fragment types. It's the first time I've ever really messed with types and providers, so it's very ugly (and probably has bugs), however I'm happy to share my patches. Would that be best a) here b) in puppet-dev, or c) direct to Onyx Point? Cheers, Greg -- 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/-/bDJFMXd4Q0VFMG9K. 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] Concat Module posted to Onyx Point Github.
Hi Trevor, I'll add my thanks to the pile, this is pretty awesome stuff! I compared the --graph results with the old concat moule, and this one - impressive difference :) As Larry says, the fact that it executes Concat_build on every run is a stopper for us, since the dependant services get restarted and we get report emails of any changes. Also, I can't see any way to hook into the filebucket for backups. I managed to hack in a "cp file file.bak" type functionality just before it actually cp's the newly-built file. However, my Ruby-fu isn't up to pulling in the filebucket stuff yet - might be worth adding to the todo list. Thanks again for the great module though :) Greg -- 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/-/OXRxUlV4QnVxU3NK. 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: Managing Switches.
I think there's two answers, actually :) The first is that you're not reading it wrong. Since the implementation executes the commands from the puppet client, the standard duplicate resource problem applies. However, as I learned at PuppetCamp, some work has recently been merged in to work around this problem, but I don't know how to configure it yet. It's on my list of things to play with soon. Until then, hopefully Masterzen can tell us more... Cheers, Greg -- 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: issue with exported resources and subscribe
Hi,
In my exported resource manifests, if using code like:
File <<| tag == "nagios::target" |>> { notify => Service["nagios3"] }
Does that work for you?
Cheers,
Greg
--
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: How to setup database for Inventory Service
Heya, I've merged both approaches. First, I dropped the db on my development server, and then let puppet recreate it. Since I don;t want to lose my historical data in production, I then dumped and compared the schema's from the dev (2.6.7) and prod (2.6.2) environments. I then upgraded prod to 2.6.7 and applied the diff. For what it's worth, here's the SQL I had to execute. Usual disclaimers on you mileage here :) ALTER TABLE resources ADD KEY `exported_restype_title` (`exported`,`restype`,`title`(50)); CREATE TABLE `inventory_facts` ( `node_id` int(11) NOT NULL, `name` varchar(255) NOT NULL, `value` text NOT NULL, UNIQUE KEY `index_inventory_facts_on_node_id_and_name` (`node_id`,`name`) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `inventory_nodes` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) NOT NULL, `timestamp` datetime NOT NULL, `updated_at` datetime DEFAULT NULL, `created_at` datetime DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `index_inventory_nodes_on_name` (`name`) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8; I can see data going into the DB from the latest runs, and I can curl the inventory service, so it seems ok. Setting up Dashboard 1.1.0 as we speak :) HTH, Greg -- 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] Problem defining exported resources
On Thursday, March 17, 2011 2:41:06 PM UTC, Felix.Frank wrote: > > I call possible bug on this one. I don't see an open issue that sounds > quite like this, so you may want to report this. > > http://projects.puppetlabs.com/projects/puppet/issues/new > > Cheers, > Felix > Thanks Felix - nice to know I'm not going mad. I'll double check it later today on the latest Puppet to make sure it's still an issue, and then get it filed. Cheers, Greg -- 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] Problem defining exported resources
Hi all,
I'm learning all about exported resources, and I've encountered an
issue. Put simply, two things which logically should be same result in
one working and one not working. I'm sure I'm missing something
obvious, but I can't see it, so I'm someone can spot my error.
The situation: I'm running stock Debian 2.6.2 on master and client. I'm
defining a simple File export which creates a directory on another
machine. Here's the code that works:
class client {
@@file{ "/mnt/backups/$hostname":
ensure => directory,
owner => "remotebackup",
group => "users",
tag => "rsync::coreserver::$region",
}
}
class server {
File <<| tag == "rsync::coreserver::$region" |>>
}
This works exactly as expected - the "server" machine creates a
directory named as per the client's hostname. However, if I wrap this
in a define(), it all goes wrong. Here's the code:
class client {
@@rsync::target{ "$hostname": tag => "rsync::coreserver::$region" }
}
class server {
Rysnc::Target <<| tag == "rsync::coreserver::$region" |>>
}
define rsync::target() {
file{ "/mnt/backups/$name":
ensure => directory,
owner => "remotebackup",
group => "users",
}
}
The define just wraps up the file definition so it's easier for me to
collect the right resources in the server class. But it doesn't work.
The server doesn't create any directories, although I can see entries
in the storeconfig db for the rsync::target resource type. What am I
missing?
Many thanks,
Greg Sutcliffe
--
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.
