Re: [Puppet Users] Could not retrieve information from environment production source
On 2012年11月28日 16:50, 夏凯 wrote: On 2012年11月28日 15:43, Jakov Sosic wrote: You need to move /etc/puppet/modules/sudo/sudoers to /etc/puppet/modules/sudo/files/sudoers thanks, i'll try this later. that works, thanks again. -- 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] Could not retrieve information from environment production source
On 2012年11月28日 15:43, Jakov Sosic wrote: You need to move /etc/puppet/modules/sudo/sudoers to /etc/puppet/modules/sudo/files/sudoers thanks, i'll try this later. -- 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] upgrading puppet
Hi I have an old puppet infrastructure that runs puppet 0.24.4 (client and server) and I was finally given the go ahead to upgrade (both client and server) :-) I have a few questions: 1. To which version should I upgrade puppet to? I was thinking of upgrading to the latest 2.6 version... 2. Anyone knows of any pitfalls I should watch out for in upgrading from such an old version? TIA Paolo -- 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/-/zDDgtBsdzFkJ. 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] Report processor and available variables
Hello James, Yes, this help. I just felt confused that 'host' report variable represents in fact 'certname' value. That said, I'll have a look on PuppetDB, which I do not use for now. Thanks, Jean Baptiste On 11/26/12 5:43 AM, James Turnbull wrote: Jean Baptiste Favre wrote: Hello, I'm trying to build a custom report processor so that I can get puppet metrics into Zabbix. I found one here: https://github.com/thomasvandoren/puppet-zabbix which basically works. The problem I have is that report processor mostly use self.host as hostname. But it represent certname in puppet world. I tried @hostname, but still get certname instead of hostname. Is there any way to get the real hostname into report processor ? As you're located on the master and all that gets passed to the report processor is the the contents of the report this is a little tricky. Off the top of my head you could use the self.host value to lookup the fact values from the node, i.e. if you're using PuppetBD (http://docs.puppetlabs.com/puppetdb/1/index.html) or the Inventory Service (http://docs.puppetlabs.com/guides/inventory_service.html). Hope that helps! Regards James Turnbull -- 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: Executing puppet crash the machine
Hello John,
Thanks for your answer. I have open an issue with my hardward manufacturer
and so I will do it with my SO one.
Anyway I paste the strace listings so maybe someone can shed light on it:
server1:
BIOS: American Megatrends Inc. 1.2
SYS: Supermicro X8SIE
CPU: Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz [4 cores]
MEM:
SLOT0 2048 MB
SLOT1 2048 MB
open(/usr/lib/ruby/1.8/facter/osfamily.rb, O_RDONLY|O_LARGEFILE) = 3
close(3) = 0
open(/usr/lib/ruby/1.8/facter/osfamily.rb, O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=800, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7297000
read(3, # Fact: osfamily\n#\n# Purpose: Re..., 4096) = 800
..CRASH
server2:
BIOS: American Megatrends Inc. 1.2
SYS: Supermicro X8SIE
CPU: Intel(R) Core(TM) i3 CPU 560 @ 3.33GHz [4 cores]
MEM:
SLOT0 2048 MB
SLOT1 2048 MB
stat64(/usr/sbin/dmidecode, {st_mode=S_IFREG|0755, st_size=48408, ...}) =
0
pipe([3, 4]) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0xb74e5ba8) = 8709
close(4) = 0
fcntl64(3, F_GETFL) = 0 (flags O_RDONLY)
fstat64(3, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb725e000
_llseek(3, 0, 0xbf900930, SEEK_CUR) = -1 ESPIPE(Illegal seek)
fstat64(3, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
read(3, # dmidecode 2.9\nSMBIOS 2.6 prese..., 1024) = 1024
read(3, oot is supported\n\t\tBIOS boot spe..., 1024) = 1024
read(3, tate: Safe\n\tThermal State: Safe\n..., 1024) = 1024
read(3, Maximum Size: 128 KB\n\tSupported ..., 1024) = 1024
read(3, e 5, 28 bytes\nMemory Controller ..., 1024) = 1024
read(3, Installed\n\tError Status: OK\n\nHa..., 1024) = 1024
read(3, type 8, 9 bytes\nPort Connector ..., 1024) = 1024
read(3, ternal Reference Designator: LPT..., 1024) = 1024
read(3, nal Reference Designator: Not Sp..., 1024) = 1024
read(3, nator: Not Specified\n\tExternal C..., 1024) = 1024
read(3, or Type: None\n\tPort Type: Other\n..., 1024) = 1024
read(3, ector Information\n\tInternal Refe..., 1024) = 1024
read(3, \tLength: Short\n\tID: 1\n\tCharacter..., 1024) = 1024
read(3, escriptor 5: POST error\n\tData Fo..., 1024) = 1024
read(3, ype 19, 15 bytes\nMemory Array Ma..., 1024) = 1024
read(3, Width: Unknown\n\tSize: No Module..., 1024) = 1024
read(3, ry Device Mapped Address\n\tStarti..., 1024) = 1024
read(3, on Handle: Not Provided\n\tTotal W..., 1024) = 1024
--- SIGCHLD (Child exited) @ 0 (0) ---
read(3, \n\nHandle 0x0039, DMI type 20, 19..., 1024) = 1024
read(3, on-recoverable Threshold: 6\n\nHan..., 1024) = 1024
read(3, UT OF SPEC\n\tCooling Unit Group:..., 1024) = 1024
read(3, ed: Yes\n\tHot Replaceable: No\n\tCo..., 1024) = 669
read(3, , 1024) = 0
close(3) = 0
munmap(0xb725e000, 4096) = 0
rt_sigaction(SIGHUP, {SIG_IGN}, {0xb77388f0, [HUP], SA_RESTART}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_IGN}, {0xb77388f0, [QUIT], SA_RESTART}, 8) = 0
rt_sigaction(SIGINT, {SIG_IGN}, {0xb77388f0, [INT], SA_RESTART}, 8) = 0
waitpid(8709, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0) = 8709
rt_sigaction(SIGHUP, {0xb77388f0, [HUP], SA_RESTART}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGQUIT, {0xb77388f0, [QUIT], SA_RESTART}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGINT, {0xb77388f0, [INT], SA_RESTART}, {SIG_IGN}, 8) = 0
sigprocmask(SIG_SETMASK, [], NULL) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_SETMASK, [], NULL) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
.
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_SETMASK, [], NULL) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
.
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
...CRASH
2012/11/26 jcbollinger john.bollin...@stjude.org
On Thursday, November 22, 2012 6:23:06 AM UTC-6, Mon wrote:
Hello all,
We have a problem with puppet and certain kind of machines from our farm
(+300), those with Supermicro X8SIE motherboard. Sometime when running
puppet the machine crashes, we lose access to it and logging through IPMI
doesn't show anything in the console, the only thing we can do is a cold
reboot. Then if we run puppet again, nothing happens. If we run puppet
several days after it could be another crash or not, it is random.
I debugged the problem and got the conclusion that the cause was when
running facter, running it in a mpssh session caused 7 or 8 crashes in
different machines.
Soft Version:
S.O: ubuntu 8.04
facter** 1.5.4-1ubuntu1
puppet 0.25.1-2
After upgrading to facter -1.6.11-1 crashes continued.
Re: [Puppet Users] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc
I ran puppet master --verbose --debug --trace --no-daemonize --logdest console and I get the same as Fabrice: Error: allocator undefined for Proc /usr/lib/ruby/1.8/yaml.rb:133:in `transfer' /usr/lib/ruby/1.8/yaml.rb:133:in `node_import' /usr/lib/ruby/1.8/yaml.rb:133:in `load' /usr/lib/ruby/1.8/yaml.rb:133:in `load' /usr/lib/ruby/site_ruby/1.8/puppet/util/rails/reference_serializer.rb:6:in `unserialize_value' /usr/lib/ruby/site_ruby/1.8/puppet/rails/param_value.rb:64:in `find_all_params_from_host' /usr/lib/ruby/site_ruby/1.8/puppet/rails/param_value.rb:63:in `each' /usr/lib/ruby/site_ruby/1.8/puppet/rails/param_value.rb:63:in `find_all_params_from_host' /usr/lib/ruby/site_ruby/1.8/puppet/rails/host.rb:232:in `find_resources_parameters' /usr/lib/ruby/site_ruby/1.8/puppet/rails/host.rb:119:in `find_resources_parameters_tags' /usr/lib/ruby/site_ruby/1.8/puppet/rails/host.rb:101:in `merge_resources' /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:23:in `debug_benchmark' /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:13:in `railsmark' /usr/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/core_ext/benchmark.rb:8:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:13:in `railsmark' /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:23:in `debug_benchmark' /usr/lib/ruby/site_ruby/1.8/puppet/rails/host.rb:100:in `merge_resources' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/active_record.rb:25:in `save' /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:13:in `railsmark' /usr/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/core_ext/benchmark.rb:8:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:13:in `railsmark' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/active_record.rb:24:in `save' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/store_configs.rb:24:in `save' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:195:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:108:in `do_find' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:71:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:71:in `process' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick/rest.rb:24:in `service' /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:33:in `listen' /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:30:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:26:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:26:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:92:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:104:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:136:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:199:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:148:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:438:in `plugin_hook' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:500:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:87:in `execute' /usr/bin/puppet:4 Tried a complete reboot of the puppet master and this does not fix the problem. On 27 November 2012 18:44, Jeff McCune j...@puppetlabs.com wrote: On Tue, Nov 27, 2012 at 9:06 AM, Lee Boynton l...@lboynton.com wrote: Sorry, just looked in the puppet.conf file. It is indeed the storeconfigs option. I guess I should just go ahead and use PuppetDB. PuppetDB could be a viable work around, but this is the second time I've heard of someone running into this error with Storedconfigs. We do still support the storedconfigs feature in Puppet 3.0, so these issues concern me. Fabrice mentioned that restarting the puppet master helped with this issue. Could you please bounce the puppet master and see if that helps resolve this issue? Could you also enable the --verbose --debug and --trace options on your Puppet master and paste any stack traces that show up
Re: [Puppet Users] StackOverflow when running Puppet agent -t
The problem disappeared after a reboot of the client. I saw your answer too
late so I haven't had the chance to run the agent with --debug and
--trace... I'll update this thread once it will be back again.
meanwhile, and after a couple of agent run, I'm now getting a different
message, here is the full stack trace: http://pastebin.com/yLdBhcyN
I don't know if this is related or not, and if it would be better to create
a new thread.
Thanks!
Le mardi 27 novembre 2012 19:47:42 UTC+1, Jeff McCune a écrit :
On Tue, Nov 27, 2012 at 8:36 AM, Med75 mohamed...@viavoo.comjavascript:
wrote:
Hi all,
I'm getting the floowing error when I run Puppet agent -t
[...]
Finished catalog run in 209.01 seconds
Error: Could not send report: Could not render to yaml: Stack overflow
in
regexp matcher: /\A(?: # ?: non-capturing group (grouping with no back
references)
[\x09\x0A\x0D\x20-\x7E]# ASCII
| [\xC2-\xDF][\x80-\xBF] # non-overlong
2-byte
| \xE0[\xA0-\xBF][\x80-\xBF]# excluding
overlongs
| [\xE1-\xEC\xEE\xEF][\x80-\xBF]{2} # straight 3-byte
| \xED[\x80-\x9F][\x80-\xBF]# excluding
surrogates
| \xF0[\x90-\xBF][\x80-\xBF]{2} # planes 1-3
| [\xF1-\xF3][\x80-\xBF]{3} # planes 4-15
| \xF4[\x80-\x8F][\x80-\xBF]{2} # plane 16
)*\z/mxn
Could you please run the agent with the --trace --verbose --debug
options turned on and then paste the complete stack trace that results
in this error? This information will help me diagnose this further.
Thanks,
-Jeff
--
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/-/KGt7j0sm2d0J.
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 3.0 Puppet labs repo package problem on rhel5
On Tuesday, November 27, 2012 8:37:22 PM UTC-6, Brian Jolly wrote: I am experiencing the same problem with a 3.0.1 install. If I set enable_inventory_service: false there are no problems. ruby: symbol lookup error: /usr/lib/ruby/gems/1.8/gems/json-1.5.1/ext/json/ext/json/ext/parser.so: undefined symbol: RSTRING_PTR ruby 1.8.7 (2012-06-29 patchlevel 370) [x86_64-linux] # ldd /usr/lib/ruby/gems/1.8/gems/json-1.5.1/ext/json/ext/json/ext/parser.so linux-vdso.so.1 = (0x7fff7f92) libruby.so.1.8 = /usr/lib64/libruby.so.1.8 (0x2aeccf1a9000) libpthread.so.0 = /lib64/libpthread.so.0 (0x2aeccf4a7000) libdl.so.2 = /lib64/libdl.so.2 (0x2aeccf6c3000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x2aeccf8c7000) libm.so.6 = /lib64/libm.so.6 (0x2aeccfaff000) libc.so.6 = /lib64/libc.so.6 (0x2aeccfd83000) librt.so.1 = /lib64/librt.so.1 (0x2aecd00da000) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x2aecd02e3000) /lib64/ld-linux-x86-64.so.2 (0x2aecced7c000) rpm -q -f /usr/lib64/libruby.so.1.8 rpm -q -f /usr/lib/ruby/gems/1.8/gems/json-1.5.1/ext/json/ext/json/ext/parser.so rpm -q -f $(which ruby) 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/-/lJ3CjIOVbBsJ. 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 3.x load balancer
what load balancer are you using? On Thursday, November 22, 2012 4:42:56 AM UTC-5, Heriyanto wrote: Hi Jeff, thanks for reply, I also read that book, its work for puppet 2.x, but now i try with puppet 3 with puppetdb, Ruby (Rack) application could not be started, Error message: undefined method `settings' for Puppet:Module Exception class: NoMethodError Application root: /etc/puppet/rack/puppetmaster Backtrace: # File Line Location 0 /usr/lib/ruby/site_ruby/1.8/puppet/application.rb 273 in `run_mode' 1 /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb 5 2 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb 36 in `gem_original_require' 3 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb 36 in `require' 4 config.ru 7 5 /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/builder.rb 51 in `instance_eval' 6 /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/builder.rb 51 in `initialize' 7 config.ru 1 in `new' 8 config.ru 1 Regards, Heri On Sun, Nov 11, 2012 at 7:57 AM, Jeff McCune je...@puppetlabs.comjavascript: wrote: The Pro Puppet book has a whole chapter on setting up Puppet with a load balancer. The information pertains to Puppet 2.6, 2.7, and 3.0. The only difference in 3.0 is the requirement to specify --confdir and --vardir in your rack up config file. docs.puppetlabs.com should also have some information migrated from the redmine wiki. HTH, -Jeff On Nov 9, 2012, at 4:32 AM, shell heriyanto shell.h...@gmail.comjavascript: wrote: Dear All, I just plan want to migrate puppetmaster from 2.6 to puppet 3.0 in production, can you give me some advice about load balancer, because now im still using mongrel. Somebody have experience migrating puppet 2.6.x or 2.7.x to puppet 3.0.x on production?. Thanks. Regards, Heriyanto -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.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 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/-/5QE9IDFXru0J. 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] passenger used in puppet 3.0?
ran across this, what do you think about Mongrel? http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel On Tuesday, November 27, 2012 9:45:28 AM UTC-5, Matthew Burgess wrote: On Tue, Nov 27, 2012 at 2:27 PM, Dominic James domini...@gmail.comjavascript: wrote: Question: on my current puppet setup 2.7.3-0 rhel 6.2 centos - passenger is used to provide the throughput for the heavy delivery that puppet could not do by itself, was this fix in version 3.0 puppet? I will be upgrading to 3.0 and will like puppet master to push to multiple of clients without being clobbered, Can I just use puppet transport agent by itself instead of using apache/passenger? You'll have to stick with Apache/Passenger for any non-trivial number of nodes. Webrick (the HTTP server used by the puppetmaster) is single-threaded, so can only handle one client checking in at a time. Regards, Matt. -- 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/-/apWzJosOSKUJ. 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: What is the best way for creating users in puppet/hiera ?
thx Elison, my users are now created via the create_resources function, and
it works like a charm.
and thx jcbollinge,
you show me the right way in using puppet/hiera.
I have now a lot of work to normalize my modules ;-)
Le lundi 26 novembre 2012 20:20:12 UTC+1, jcbollinger a écrit :
On Monday, November 26, 2012 5:00:17 AM UTC-6, AnOnJoe wrote:
Hello,
I have recently discover hiera, and I would like to use it for creating
users on my node.
I first think of someting like that :
common.yaml
lusers : - jodoe
- jadoe
classes : - users
serv01.foo.com.yaml
lusers : - Alice
- Bob
modules/users/manifest/init.pp
define users ($user = hiera($lusers)) {
user { $user:
ensure = present,
shell = '/bin/bash',
home= /home/$user,
managehome = true,
}
}
But I don't know how I can call my def type like that.
What about you ? How do you create your users in puppet / hiera ?
A module's init.pp, if non-empty, should contain only the definition of a
class (not a definition) sharing the name of the module. That's what you
want in this case anyway:
modules/users/manifests/init.pp:
class users {
$users = flatten(hiera_array('lusers'))
user::user { $users: }
}
modules/users/manifests/user.pp
define user::user () {
user { $name:
ensure = present,
shell = '/bin/bash',
home = /home/$name,
managehome = true
}
}
Notes:
1. To collect values for the same key from multiple levels of your
data hierarchy, you need to use either hiera_array() or hiera_hash(). The
plain hiera() function will give you only the value from the
highest-priority level.
2. The flatten() function comes from the stdlib add-on module. You
would
need it in the example because, with the data as given, hiera_array() will
return an array of arrays, whereas you want a single array whose elements
are the usernames.
3. The only reason you need a defined type is that you want to
explicitly declare the home directory name based on the username. If none
of the properties were derived from the username then you could just use
native User resources directly.
4. All quoting (and non-quoting) in the example is exactly as you
should have it. In several cases, adding quotes or changing the quote
type
will change the meaning.
5. You would use the example by via include 'users'
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/-/g33IHWw3G44J.
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] passenger used in puppet 3.0?
On 11/28/2012 6:11 AM, DJames wrote: ran across this, what do you think about Mongrel? http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel It's a more complex config and system for no benefit. Are you having any problems with Passenger/Apache? It's the simplest and most common way to run a Puppet master. I would however recommend going through the extra work to install Passenger 3.x if your distro does not ship with it. Ramin -- 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] [hiera] Hierarchy modification takes long time to be effective
Hello,
I've something strange :
When I modify my hierarchy in my hiera.yaml, it can take up to several
hours, for the modification to work.
eg : I create a subdir in my hieradata, move all the concerned files into,
modify my hiera.yaml
from :
:hierarchy:
- %{operatingsystem}
to :
:hierarchy:
- *os/*%{operatingsystem}
but the changes don't work immediatly.
--
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/-/_XXDRci826kJ.
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: problems with exported exec resources
On Tuesday, November 27, 2012 8:55:47 PM UTC-6, go8ose wrote:
On Tuesday, November 27, 2012 2:56:45 AM UTC+11, jcbollinger wrote:
This looks like http://projects.puppetlabs.com/issues/11049. You can
vote for that issue. To work around the it, I think you'll need to arrange
for the host that collects those resources to declare its own
nagios_service and nagios_host resources as ordinary instead of exported
resources. Of course, that's a bust if more than one node needs to collect
those resources.
There are probably other workarounds, but they depend on details of your
site. Many of them involve substituting something else for exported
resources; the rest involve collecting onto a node that does not export
(and therefore is not affected by the bug), and then sharing the result
somehow.
John
Thanks for the reply John. I think the bug report you mention (but 11049)
isn't relevant for my situation. Perhaps I shouldn't have mentioned my
working nagios resources in my original post. They aren't part of my
problem, they are just illustrating that I have some exported resources and
collection working.
In my situation I want to collect the exec's on a different host to the
hosts that are exporting these execs.
So you're saying that *none* of the collected Execs are running? In that
case, check the cached catalog to see whether it contains those Execs at
all. That will establish whether it is a problem with resource collection
or with the individual resources. It should also allow you to verify the
resource parameters.
As for the individual resources, you would be well advised to use curly
brackets around variable names inside strings. Especially, you should use
them in /srv/mnt/.${hostname}_commvault_backed_up and similar strings
(else Puppet will think you want the variable named
$hostname_commvault_backed_up), but it's a good habit to use curly brackets
in every variable reference.
Actually, the brackets are probably your issue: you presumably don't define
a variable named $hostname_commvault_backed_up, so it interpolates as
nothing. That means what you've written is equivalent to creates =
'/srv/mnt/.', which is in turn equivalent to creates = '/srv/mnt'.
Since that directory already exists, applying the Execs will not result in
their commands running.
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/-/57dgbGqke24J.
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: [hiera] Hierarchy modification takes long time to be effective
On Wednesday, November 28, 2012 8:38:37 AM UTC-6, AnOnJoe wrote:
Hello,
I've something strange :
When I modify my hierarchy in my hiera.yaml, it can take up to several
hours, for the modification to work.
eg : I create a subdir in my hieradata, move all the concerned files into,
modify my hiera.yaml
from :
:hierarchy:
- %{operatingsystem}
to :
:hierarchy:
- *os/*%{operatingsystem}
but the changes don't work immediatly.
Did you restart your master?
--
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/-/go2xg_VMKAAJ.
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: [hiera] Hierarchy modification takes long time to be effective
Thx, i'm feeling stupid, it was that
Le mercredi 28 novembre 2012 15:41:53 UTC+1, llowder a écrit :
On Wednesday, November 28, 2012 8:38:37 AM UTC-6, AnOnJoe wrote:
Hello,
I've something strange :
When I modify my hierarchy in my hiera.yaml, it can take up to several
hours, for the modification to work.
eg : I create a subdir in my hieradata, move all the concerned files
into, modify my hiera.yaml
from :
:hierarchy:
- %{operatingsystem}
to :
:hierarchy:
- *os/*%{operatingsystem}
but the changes don't work immediatly.
Did you restart your master?
--
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/-/i6EkEJsVkq8J.
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] Could not request certificate: Retrieved certificate does not match private key; please remove certificate from server and regenerate it with the current key
Hi, I have installed puppet master and puppet agent in two redhat linux machines. After that, I have updated server details in agent machine /etc/hosts file. While executing the ping servername in agent machine, I am getting below response. = [root@ip-10-244-162-253 files]# ping puppet PING server.puppet.com (10.203.34.103) 56(84) bytes of data. 64 bytes from server.puppet.com (10.203.34.103): icmp_seq=1 ttl=61 time=0.723 ms 64 bytes from server.puppet.com (10.203.34.103): icmp_seq=2 ttl=61 time=0.570 ms 64 bytes from server.puppet.com (10.203.34.103): icmp_seq=3 ttl=61 time=0.617 ms == Then While executing one of the below commands puppetd --test or puppetd --server puppet --waitforcert 60 --verbose --test I am getting an error message like below *err: Could not request certificate: Retrieved certificate does not match private key; please remove certificate from server and regenerate it with the current key* I tried after cleaning certificates in both the machines by using puppetca --clean --all also, same error I am getting. Can any one provide a way to come out of this issue. With Regards, Krishna Bhaskara Rao. -- 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/-/m5485BQZLKsJ. 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: Is it possible to run functions at run time ?
On Tuesday, November 27, 2012 4:23:50 PM UTC-6, Yanis Guenane wrote: Within mycon template I have a variable 'test' that depending if the package was installed from source of from the package will have a different path. Issue is that the function get_test_path() seems to be done at compile time, so the first time I run it will always result in an erroneous answer. After a second run it will be fine. To answer the question posed by the thread subject, no, it is not possible to make puppet functions be evaluated by the puppet agent during catalog application. They are always evaluated by the master during catalog compilation. Any dynamic behavior you want to happen on the agent side must be performed by your resources. Often you don't actually need agent-side dynamism beyond what Puppet already provides, but when you do, you generally need either to use an Exec resource, or to write a custom provider for an existing resource type, or to write a whole custom type / provider pair. 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/-/7FI9BFD4LB0J. 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: subscribe = Package
On Tuesday, November 27, 2012 5:37:09 PM UTC-6, Erik Dalén wrote: Actually, if you notify a class or define you will notify every resource contained inside it, causing services to be restarted and refresh only execs to be executed. My bad. Nevertheless, that's all the more reason why the OP's code ought to work, if that's all there is to it. 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/-/xeV7M1Q38NcJ. 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] passenger used in puppet 3.0?
current dev system is using passenger, but production (babystage) is using 3.0 version, and we have 1800+ servers (prod) that will be clients is passenger the way to go still? On Wednesday, November 28, 2012 9:34:52 AM UTC-5, Ramin K wrote: On 11/28/2012 6:11 AM, DJames wrote: ran across this, what do you think about Mongrel? http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel It's a more complex config and system for no benefit. Are you having any problems with Passenger/Apache? It's the simplest and most common way to run a Puppet master. I would however recommend going through the extra work to install Passenger 3.x if your distro does not ship with it. Ramin -- 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/-/1-jnBxPyaLwJ. 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: Right way to implement roles in hiera/puppet
On Tuesday, November 27, 2012 6:32:23 AM UTC-6, Bret Wortman wrote:
I'm looking to implement a hiera backend for our Puppet installation, as
we routinely deploy systems that are of varying hardware, OS, and which may
have multiple roles they fill.
I've figured out, I think, how to handle the OS question through facter,
but implementing server roles isn't quite so clear. I want to maintain that
information on the server, not on the clients, but everything hiera-related
seems to use the facts for a given system. Installing a file containing the
roles on the client seems like a kludge. Is there a more hiera-ish,
puppet-ish way to accomplish this?
Suppose you define one class for each role (each of which may declare any
number of resources and other classes). In Puppet 3, I think you can do
this:
# An array of the names of the needed role classes
$role_classes = hiera('role_classes')
# Declare those classes
include ${role_classes}
If I recall correctly, though, you can accomplish the same thing, even in
Puppet 2.[67], with
hiera_include('role_classes')
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/-/NeueswuE5i8J.
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] Puppetdb source install on Solaris. Agents complain about invalid encoding (UTF-8//IGNORE, UTF-8)
On Tue, Nov 27, 2012 at 9:27 PM, Ryan Cunningham ryan.cunningham.xy...@gmail.com wrote: Hi all, I'm having an issue on the master I'm using in my staging environment with getting storeconfigs to work with puppetdb. I should say up front that my staging environment is probably a little uncommon. I'm running OpenIndiana which is a distribution of the open source fork of OpenSolaris. I installed puppet (3.0), facter and hiera using `gem` on this system and have gotten the master working, servicing some test clients without too much trouble but I'm having some real trouble getting puppetdb integrated with my master. Puppetdb is running on the puppet master and I can access the dashboard on the default port of 8080 without issue, I've followed all the instructions at http://docs.puppetlabs.com/puppetdb/1/connect_puppet_master.html quite closely but if I have storeconfigs set to true and puppetdb as my backend I get the following output from a puppet agent --test: Info: Retrieving plugin Info: Loading facts in /var/puppet/lib/facter/last_run.rb Info: Loading facts in /var/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/puppet/lib/facter/pe_version.rb Info: Loading facts in /var/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/puppet/lib/facter/root_home.rb Info: Loading facts in /var/puppet/lib/facter/puppi_projects.rb Error: Could not retrieve catalog from remote server: Error 400 on SERVER: invalid encoding (UTF-8//IGNORE, UTF-8) Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run I've tried Googling but haven't turned up anyone else reporting the same exact issue. I checked out puppetdb using git and got *most* of the way through building with Rake (it stopped while building some of the Debian-specific stuff) -- I got the jar file I'm using from there and I copied the files I believe I was supposed to from puppetdb's puppet/lib/puppet into /var/ruby/1.8/gem_home/gems/puppet-3.0.1/lib/puppet/ on this system. Verbose output from the copy command follows... The code in question is trying to transcode your catalog to UTF-8 before sending it to PuppetDB (because the wire format is JSON, and JSON is UTF-8). On Ruby 1.8, we rely on the iconv Ruby library, which is basically just a pass-through to libiconv. The error message seems to indicate that your libiconv doesn't know about UTF-8 which is strange...though I admit to not knowing exactly how (and with what flags) Ruby or iconv is compiled for OpenIndiana. Using the same Ruby you run your puppetmasters with, can you do: ruby -e require 'iconv'; puts Iconv.list.sort That should dump out the list of available encodings. That should help us at least more properly triangulate the issue. deepak -- 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 3.0 Puppet labs repo package problem on rhel5
On Tue, Nov 27, 2012 at 3:53 PM, Alaric paxindust...@gmail.com wrote: Swing and a miss... even after verifying and manually removing any gems, and any cached gems, reinstalling effected packages and verifying, I still get the same error... Are you able to reduce this down to a specific module or class that triggers this issue? I've now got a fresh centos 5.8 VM with an out of the box puppet-3.0.1 install on it with all dependencies met via puppetlabs' repo. I can't trigger it with a simple module, but am willing to try to reproduce it for you. Thanks, Matt. -- 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] passenger used in puppet 3.0?
On 11/28/2012 09:53 AM, DJames wrote: current dev system is using passenger, but production (babystage) is using 3.0 version, and we have 1800+ servers (prod) that will be clients is passenger the way to go still? I was previously using passenger and just recently switched to using nginx/unicorn. I like the setup a lot better - I can't really quantify why other than the architecture of the way it does it seems better to me, and getting passenger working was a pain under RHEL6. General instructions here: http://projects.puppetlabs.com/projects/1/wiki/using_unicorn Some notes: 1) I ended up symlinking /etc/puppet to ~puppet/.puppet to fix the issue where puppet master not running as root will not look in the right place for it's config. 2) I couldn't find unicorn packages for RHEL - I ended up using gem2rpm and tweaking it to build. 3) I used supervisord instead of god because I'm more familiar with it. Again you'll likely need to build packages for it - I just updated the spec here: https://github.com/easel/supervisor-rpm There's a good puppet module to manage supervisord here: https://github.com/plathrop/puppet-module-supervisor Thanks, Jason -- 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: Executing puppet crash the machine
On Wednesday, November 28, 2012 4:49:13 AM UTC-6, Mon wrote:
Hello John,
Thanks for your answer. I have open an issue with my hardward manufacturer
and so I will do it with my SO one.
Anyway I paste the strace listings so maybe someone can shed light on it:
server1:
BIOS: American Megatrends Inc. 1.2
SYS: Supermicro X8SIE
CPU: Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz [4 cores]
MEM:
SLOT0 2048 MB
SLOT1 2048 MB
open(/usr/lib/ruby/1.8/facter/osfamily.rb, O_RDONLY|O_LARGEFILE) = 3
close(3) = 0
open(/usr/lib/ruby/1.8/facter/osfamily.rb, O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=800, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7297000
read(3, # Fact: osfamily\n#\n# Purpose: Re..., 4096) = 800
..CRASH
server2:
BIOS: American Megatrends Inc. 1.2
SYS: Supermicro X8SIE
CPU: Intel(R) Core(TM) i3 CPU 560 @ 3.33GHz [4 cores]
MEM:
SLOT0 2048 MB
SLOT1 2048 MB
stat64(/usr/sbin/dmidecode, {st_mode=S_IFREG|0755, st_size=48408, ...})
= 0
pipe([3, 4]) = 0
clone(child_stack=0,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0xb74e5ba8) = 8709
close(4) = 0
fcntl64(3, F_GETFL) = 0 (flags O_RDONLY)
fstat64(3, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb725e000
_llseek(3, 0, 0xbf900930, SEEK_CUR) = -1 ESPIPE(Illegal seek)
fstat64(3, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
read(3, # dmidecode 2.9\nSMBIOS 2.6 prese..., 1024) = 1024
read(3, oot is supported\n\t\tBIOS boot spe..., 1024) = 1024
read(3, tate: Safe\n\tThermal State: Safe\n..., 1024) = 1024
read(3, Maximum Size: 128 KB\n\tSupported ..., 1024) = 1024
read(3, e 5, 28 bytes\nMemory Controller ..., 1024) = 1024
read(3, Installed\n\tError Status: OK\n\nHa..., 1024) = 1024
read(3, type 8, 9 bytes\nPort Connector ..., 1024) = 1024
read(3, ternal Reference Designator: LPT..., 1024) = 1024
read(3, nal Reference Designator: Not Sp..., 1024) = 1024
read(3, nator: Not Specified\n\tExternal C..., 1024) = 1024
read(3, or Type: None\n\tPort Type: Other\n..., 1024) = 1024
read(3, ector Information\n\tInternal Refe..., 1024) = 1024
read(3, \tLength: Short\n\tID: 1\n\tCharacter..., 1024) = 1024
read(3, escriptor 5: POST error\n\tData Fo..., 1024) = 1024
read(3, ype 19, 15 bytes\nMemory Array Ma..., 1024) = 1024
read(3, Width: Unknown\n\tSize: No Module..., 1024) = 1024
read(3, ry Device Mapped Address\n\tStarti..., 1024) = 1024
read(3, on Handle: Not Provided\n\tTotal W..., 1024) = 1024
--- SIGCHLD (Child exited) @ 0 (0) ---
read(3, \n\nHandle 0x0039, DMI type 20, 19..., 1024) = 1024
read(3, on-recoverable Threshold: 6\n\nHan..., 1024) = 1024
read(3, UT OF SPEC\n\tCooling Unit Group:..., 1024) = 1024
read(3, ed: Yes\n\tHot Replaceable: No\n\tCo..., 1024) = 669
read(3, , 1024) = 0
close(3) = 0
munmap(0xb725e000, 4096) = 0
rt_sigaction(SIGHUP, {SIG_IGN}, {0xb77388f0, [HUP], SA_RESTART}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_IGN}, {0xb77388f0, [QUIT], SA_RESTART}, 8) = 0
rt_sigaction(SIGINT, {SIG_IGN}, {0xb77388f0, [INT], SA_RESTART}, 8) = 0
waitpid(8709, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0) = 8709
rt_sigaction(SIGHUP, {0xb77388f0, [HUP], SA_RESTART}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGQUIT, {0xb77388f0, [QUIT], SA_RESTART}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGINT, {0xb77388f0, [INT], SA_RESTART}, {SIG_IGN}, 8) = 0
sigprocmask(SIG_SETMASK, [], NULL) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_SETMASK, [], NULL) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
.
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_SETMASK, [], NULL) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
.
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
...CRASH
I'm supposing that ...CRASH means more of the same syscall, with
similar results, until the trace ends on account of a system crash.
The second trace says nothing useful, as far as I can tell. The last thing
it shows before all the signal mask handling is the successful completion
of a fact evaluation.
The first trace is not much more helpful. The last thing it shows is
Facter reading the Ruby code for the 'osfamily' fact. That might indicate
that it is during evaluation of that fact that the system crashed, but it's
too far removed from fact evaluation for me to have any confidence in that.
My bet would be that the crash cuts off communication before its cause is
reported in the trace, as I warned might
[Puppet Users] Containment issue
I'm pretty sure I ran into the infamous containment issue
(http://projects.puppetlabs.com/issues/8040) I have some questions regarding
this issue as well as the proposed work-around… anchors.
First off if all of the classes you are trying to contained are owned by you
could you not just use require instead of include? For example:
class foo {
resouce { 'name':
require = Class[bar]
}
}
class bar {
include a
include b
include c
}
The above snipped will cause a problem if the resource in Foo depends on a,b
and c being completed. Couldn't you just do this instead?
class bar {
require a
require b
require c
}
I believe the above would work, but then again this is only if you own the
classes you are trying to include.. i.e., this won't work with external modules
that were downloaded from puppet forge. So, other than the use case when you
are trying to create a dependency on classes/modules you don't own, you could
just use require instead of anchors. Is this correct?
Ok now for my question on anchors. Well its more of a request then a question.
Could someone please post a simplified version of the work around using anchors
for the above situation? I tried to read though the wiki but I didn't fully
grasp how anchors worked. Didn't help that someone told me in the IRC room that
the example on the wiki has a bug in it.
Thanks for you help!
- M
--
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] Custom reource download to client does not work
Hello Everyone, I have some issues with something that definately worked for me before. When I create a custom resource and put it into a $libdir it does not get downloaded on a client. Instead, after running puppet agent, I receive an unknown resource error. The resource works just fine on my local machine where I created it. Funny thing is that even my old custom resources that were downloaded in the past are not downloaded both on a new client or if I delete the resource from the old one. Restarting puppet does not help. I am not aware of any changes nor to master or clients so I am without a clue what might have gone wrong. Any idea would be appreciated. Thanks, Jian -- 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/-/RsBDjrsAnc8J. 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 agent cache files used in exec?
Hi all,
my problem is described below
puppet agent do Exec :
exec {create-${user}-${host}-${database}-user-mycnf:
creates = $outfile,
cwd = /tmp,
command = ${outscript},
provider = shell
}
of shell script $outscipt :
#!/bin/bash
mysql -e grant all on mydb.* to 'myuser'@'%' identified by '$pw';
touch $outfile
mysql uses password in /root/.my.cnf
it was failing for a long time.
Today I restarted agent (actually upgraded to 2.7.20)
after restart of agent Exec was run sucessfully
my.cnf was changed a long time ago ($outfile was removed in that time
also). I suppose Exec started to fail after changing mysql password.
Could puppet cache /root/.my.cnf and reread it only after reboot.
I see no other explanation. Is it bug?
thanks in advance
--
Best regards,
Vasil Mikhalenya
--
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: Executing puppet crash the machine
Hello John,
Your assumption is ok.
I can not do the facter loop because we are in a production environment.
Every time I run puppet on this machines I make sure I can reach its IPMI
interface so I can reboot the machine in few minutes.
Thanks for you help
Regards.
2012/11/28 jcbollinger john.bollin...@stjude.org
On Wednesday, November 28, 2012 4:49:13 AM UTC-6, Mon wrote:
Hello John,
Thanks for your answer. I have open an issue with my hardward
manufacturer and so I will do it with my SO one.
Anyway I paste the strace listings so maybe someone can shed light on it:
server1:
BIOS: American Megatrends Inc. 1.2
SYS: Supermicro X8SIE
CPU: Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz [4 cores]
MEM:
SLOT0 2048 MB
SLOT1 2048 MB
open(/usr/lib/ruby/1.8/**facter/osfamily.rb, O_RDONLY|O_LARGEFILE) = 3
close(3) = 0
open(/usr/lib/ruby/1.8/**facter/osfamily.rb, O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=800, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7297000
read(3, # Fact: osfamily\n#\n# Purpose: Re..., 4096) = 800
..CRASH
server2:
BIOS: American Megatrends Inc. 1.2
SYS: Supermicro X8SIE
CPU: Intel(R) Core(TM) i3 CPU 560 @ 3.33GHz [4 cores]
MEM:
SLOT0 2048 MB
SLOT1 2048 MB
stat64(/usr/sbin/dmidecode, {st_mode=S_IFREG|0755, st_size=48408, ...})
= 0
pipe([3, 4]) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|**CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0xb74e5ba8) = 8709
close(4) = 0
fcntl64(3, F_GETFL) = 0 (flags O_RDONLY)
fstat64(3, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb725e000
_llseek(3, 0, 0xbf900930, SEEK_CUR) = -1 ESPIPE(Illegal seek)
fstat64(3, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
read(3, # dmidecode 2.9\nSMBIOS 2.6 prese..., 1024) = 1024
read(3, oot is supported\n\t\tBIOS boot spe..., 1024) = 1024
read(3, tate: Safe\n\tThermal State: Safe\n..., 1024) = 1024
read(3, Maximum Size: 128 KB\n\tSupported ..., 1024) = 1024
read(3, e 5, 28 bytes\nMemory Controller ..., 1024) = 1024
read(3, Installed\n\tError Status: OK\n\nHa..., 1024) = 1024
read(3, type 8, 9 bytes\nPort Connector ..., 1024) = 1024
read(3, ternal Reference Designator: LPT..., 1024) = 1024
read(3, nal Reference Designator: Not Sp..., 1024) = 1024
read(3, nator: Not Specified\n\tExternal C..., 1024) = 1024
read(3, or Type: None\n\tPort Type: Other\n..., 1024) = 1024
read(3, ector Information\n\tInternal Refe..., 1024) = 1024
read(3, \tLength: Short\n\tID: 1\n\tCharacter..., 1024) = 1024
read(3, escriptor 5: POST error\n\tData Fo..., 1024) = 1024
read(3, ype 19, 15 bytes\nMemory Array Ma..., 1024) = 1024
read(3, Width: Unknown\n\tSize: No Module..., 1024) = 1024
read(3, ry Device Mapped Address\n\tStarti..., 1024) = 1024
read(3, on Handle: Not Provided\n\tTotal W..., 1024) = 1024
--- SIGCHLD (Child exited) @ 0 (0) ---
read(3, \n\nHandle 0x0039, DMI type 20, 19..., 1024) = 1024
read(3, on-recoverable Threshold: 6\n\nHan..., 1024) = 1024
read(3, UT OF SPEC\n\tCooling Unit Group:..., 1024) = 1024
read(3, ed: Yes\n\tHot Replaceable: No\n\tCo..., 1024) = 669
read(3, , 1024) = 0
close(3) = 0
munmap(0xb725e000, 4096) = 0
rt_sigaction(SIGHUP, {SIG_IGN}, {0xb77388f0, [HUP], SA_RESTART}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_IGN}, {0xb77388f0, [QUIT], SA_RESTART}, 8) = 0
rt_sigaction(SIGINT, {SIG_IGN}, {0xb77388f0, [INT], SA_RESTART}, 8) = 0
waitpid(8709, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0) = 8709
rt_sigaction(SIGHUP, {0xb77388f0, [HUP], SA_RESTART}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGQUIT, {0xb77388f0, [QUIT], SA_RESTART}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGINT, {0xb77388f0, [INT], SA_RESTART}, {SIG_IGN}, 8) = 0
sigprocmask(SIG_SETMASK, [], NULL) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_SETMASK, [], NULL) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
.
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_SETMASK, [], NULL) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
.
sigprocmask(SIG_BLOCK, NULL, []) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
...CRASH
I'm supposing that ...CRASH means more of the same syscall, with
similar results, until the trace ends on account of a system crash.
The second trace says nothing useful, as far as I can tell. The last
thing it shows before all the signal mask handling is the successful
completion of a fact evaluation.
The first trace is not much more helpful. The last thing it shows is
Facter reading the Ruby code for the
[Puppet Users] anyway to inherit the argument list from a puppet define?
Is there anyway to inherit the argument list from a puppet define so that
a wrapping define does not have to declare the same variables twice?
For example
define my_define($arg1, $arg2, $arg3){
...
}
define wrapper {
#modify arg2
...
#call my_define passing args 1-3
}
#Now call the wrapper and pass in args for my_define
wrapper{'example': arg1 = 1,
arg2 = 2,
arg3 = 3}
--
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/-/d6--guFPI7gJ.
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 3.0 Puppet labs repo package problem on rhel5
Jakov, I'm really sorry to step in on this one but our ruby should fully support gems installed using the gem command. I understand it's not ideal and that RPM's are definitely preferable. I encourage people to use RPMs whenever possible in this situation. However, I'm deeply concerned that we may be replacing the system ruby, which does support gem install, with something that does not. To this end, I'd like to clarify that if you run into this problem and you're using gem install instead of yum, and we find out there's a bug here, then this issue should also be resolved for you and your deployment scenario. Please keep troubleshooting the issue even if you're using gems and not RPMs. -Jeff On Nov 27, 2012, at 11:47 PM, Jakov Sosic jso...@srce.hr wrote: On 11/27/2012 03:09 PM, Alaric wrote: Yup, I get the same error: /usr/bin/ruby: symbol lookup error: /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so: undefined symbol: RSTRING_PTR Upgrade to the ruby provided by puppetlabs repo (RHEL 5 has older version), and don't mix GEMs with RPMs... use only RPMs. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] [facter]Bug can't get : ipaddress_ethX
Hello, I have a problem with facter : eg: facter |grep ipaddress_eth1 ipaddress_eth0 = 192.168.0.254 works but facter ipaddress_eth1 return nothing Do you know how I can work with this ? thx -- 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/-/gscIz-LmC3oJ. 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: [facter]Bug can't get : ipaddress_ethX
sorry there is a typo : Le mercredi 28 novembre 2012 18:06:54 UTC+1, AnOnJoe a écrit : Hello, I have a problem with facter : eg: facter |grep ipaddress_eth1 ipaddress_eth*1* = 192.168.0.254 works but facter ipaddress_eth1 return nothing Do you know how I can work with this ? thx -- 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/-/db0413060ncJ. 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] anyway to inherit the argument list from a puppet define?
On 2012-28-11 17:43, Ben Schofield wrote:
Is there anyway to inherit the argument list from a puppet define so
that a wrapping define does not have to declare the same variables twice?
No. Sorry.
For example
define my_define($arg1, $arg2, $arg3){
...
}
define wrapper {
#modify arg2
...
#call my_define passing args 1-3
}
#Now call the wrapper and pass in args for my_define
wrapper{'example': arg1 = 1,
arg2 = 2,
arg3 = 3}
--
- henrik
--
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] StackOverflow when running Puppet agent -t
On Wed, Nov 28, 2012 at 5:42 AM, Med75 mohamed.hadr...@viavoo.com wrote: The problem disappeared after a reboot of the client. I saw your answer too late so I haven't had the chance to run the agent with --debug and --trace... I'll update this thread once it will be back again. meanwhile, and after a couple of agent run, I'm now getting a different message, here is the full stack trace: http://pastebin.com/yLdBhcyN I don't know if this is related or not, and if it would be better to create a new thread. How much memory does the machine have, and how much memory free? It looks like the system is running dry: Cannot allocate memory - fork FYI, In Puppet 3 we're now using fork when doing catalog runs, which may increase memory utilization relative to previous versions of Puppet. -Jeff -- 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 3.0 Puppet labs repo package problem on rhel5
On Fri, Nov 23, 2012 at 2:46 PM, Alaric paxindust...@gmail.com wrote: Hi, I'm having a weird issue and was wondering if anyone else had run into it. I recently upgraded from puppet 2.7 - 3.0.1 After cleaning up some gems on my puppet master everything seemed to be working ok. I had originally used the EPEL repo's to deploy puppet, but switched to the Puppet Labs repos so I could upgrade to 2.7 then 3. On RHEL5 only, I get a RSTRING_PTR error if I upgrade to the Puppet Labs version (1.4.6) if I roll back to the EPEL veriosn of rubygem-json (1.4.3) Everything works again. Has anyone affected by this issue seen https://bugzilla.redhat.com/show_bug.cgi?id=634380 ? This information leads me to believe the rubygem-json package from Puppet Labs may not be carrying the same patch that the rubygem-json 1.4.3 package from the Fedora Project is carrying. This difference may be the cause of the error. Can anyone confirm? -Jeff -- 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 agent cache files used in exec?
Could puppet cache /root/.my.cnf and reread it only after reboot. I see no other explanation. Is it bug? No, puppet does nothing like that. It's strange that it works *now* but I would say the problem is definitely somewhere else. ~pete signature.asc Description: OpenPGP digital signature
[Puppet Users] 1.8.7 = 1.9.3 migration, compilation times raised twice!?
i've made a migration on our puppetmasters yesterday, hoping it will run faster and/or make less load on machines with newer ruby. but actual result is just opposite, our compilation times went up a lot, ie: Nov 27 14:30:12 punch puppet-master[15293]: Compiled catalog for lb1 in environment production in 183.42 seconds Nov 27 15:38:42 punch puppet-master[24399]: Compiled catalog for lb1 in environment production in 158.49 seconds Nov 27 15:51:19 punch puppet-master[11963]: Compiled catalog for lb1 in environment production in 175.00 seconds Nov 27 16:04:15 punch puppet-master[15264]: Compiled catalog for lb1 in environment production in 120.36 seconds Nov 27 19:25:52 punch puppet-master[552]: Compiled catalog for lb1 in environment production in 281.54 seconds Nov 27 20:20:19 punch puppet-master[2273]: Compiled catalog for lb1 in environment production in 239.05 seconds Nov 27 22:26:03 punch puppet-master[4919]: Compiled catalog for lb1 in environment production in 275.38 seconds Nov 28 00:55:24 punch puppet-master[12293]: Compiled catalog for lb1 in environment production in 267.91 seconds guess when migration has occured. this machine (lb1) has ~2000 resources. i'm a bit worried about scalability... we can go back to 1.8.7 now, but it won't be supported in 7 months (ie. no security updates). -- 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/-/NV-H40aVfrcJ. 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] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc
I am also seeing this bug on one of my nodes (worryingly, the puppet master itself!) The relevant output of puppet agent -t --debug --trace --verbose matches what Fabrice and Lee have also reported: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:65:in `deserialize' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:121:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:191:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:243:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:348:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:347:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:242:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:67:in `retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:107:in `prepare_and_retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:159:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:20:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:119:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:42:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:84:in `run_in_fork' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:175:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:175:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:339:in `onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:312:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:438:in `plugin_hook' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:500:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:87:in `execute' /usr/bin/puppet:4 Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run I am also using a MySQL DB as my storeconfig. On Tuesday, November 27, 2012 1:45:15 PM UTC-5, Jeff McCune wrote: On Tue, Nov 27, 2012 at 9:06 AM, Lee Boynton l...@lboynton.comjavascript: wrote: Sorry, just looked in the puppet.conf file. It is indeed the storeconfigs option. I guess I should just go ahead and use PuppetDB. PuppetDB could be a viable work around, but this is the second time I've heard of someone running into this error with Storedconfigs. We do still support the storedconfigs feature in Puppet 3.0, so these issues concern me. Fabrice mentioned that restarting the puppet master helped with this issue. Could you please bounce the puppet master and see if that helps resolve this issue? Could you also enable the --verbose --debug and --trace options on your Puppet master and paste any stack traces that show up in your logs or on the console. This will help me diagnose this issue further. Thanks, -Jeff -- 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/-/_g4_Ggww240J. 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: Containment issue
On Wednesday, November 28, 2012 10:09:10 AM UTC-6, Smashed wrote:
I'm pretty sure I ran into the infamous containment issue (
http://projects.puppetlabs.com/issues/8040) I have some questions
regarding this issue as well as the proposed work-around… anchors.
First off if all of the classes you are trying to contained are owned by
you could you not just use require instead of include? For example:
class foo {
resouce { 'name':
require = Class[bar]
}
}
class bar {
include a
include b
include c
}
The above snipped will cause a problem if the resource in Foo depends on
a,b and c being completed. Couldn't you just do this instead?
class bar {
require a
require b
require c
}
Yes, you can do that and it should work for your scenario. It is not
equivalent to applying the anchor pattern, however. In particular, it is
no help at all when you use before = Class['bar'], whereas the anchor
pattern works for that case, too.
I believe the above would work, but then again this is only if you own
the classes you are trying to include.. i.e., this won't work with external
modules that were downloaded from puppet forge. So, other than the use case
when you are trying to create a dependency on classes/modules you don't
own, you could just use require instead of anchors. Is this correct?
Either way, you need to own class Bar (because you're creating / modifying
it), but you do not *need* to own classes 'a', 'b', and 'c' for the pattern
to work. It is risky to attempt to contain classes you do not own,
however, because you can easily introduce cyclic resource relationships
that way.
Ok now for my question on anchors. Well its more of a request then a
question. Could someone please post a simplified version of the work around
using anchors for the above situation? I tried to read though the wiki but
I didn't fully grasp how anchors worked. Didn't help that someone told me
in the IRC room that the example on the wiki has a bug in it.
Anchors make use of the fact that relationships with classes are
effectively propagated to their resources (such as anchor resources), even
though they are not propagated to referenced classes. There is nothing
special about the anchor resource type that makes the pattern work; the
same can be done with any other resource, and where there is another
resource that fills that role naturally it is better to use that. Anchors
serve principally to clarify, as they have no other purpose than to
participate in ordering relationships.
Here is how your example might look with anchors:
class bar {
include a
include b
include c
anchor { 'bar_start':
before = [ Class['a'], Class['b'], Class['c'] ]
}
anchor { 'bar_end':
require = [ Class['a'], Class['b'], Class['c'] ]
}
}
If there were ordering relationships among classes 'a', 'b', and 'c', then
the anchors' 'before' and 'require' parameters could be simpler. Also, you
can write the relationships in other ways, such as using the chain
operators, but it all amounts to the same thing as long as you set up the
same relationships.
The point is that anything that has a 'before' relationship with
Class['bar'], thereby has a 'before' relationship with Anchor['bar_start']
(and Anchor['bar_end']), and Anchor['bar_start']'s 'before' relationship
with the contained classes ensures that it is applied before the resources
belonging to those classes. Similarly for 'require' relationships and
Anchor['bar_end'].
Note well that you should apply that pattern only where the nature of class
bar calls for it. In many cases, there is no particular need for
containment or even relative ordering of the classes declared by a given
class.
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/-/di1U2ZXmphUJ.
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 3.0 Puppet labs repo package problem on rhel5
The problem was that our el5 rubygem-json package was the el6 src rebuilt, without the patch, against ruby 1.8.5. Rebuilding the rubygem-json package against the ruby 1.8.7 packages in our dependencies repo resolved the parser.so linking errors. I've included the ldd of the parser.so before and after below as well. The updated package is now available in our dependencies repo. Please let us know if this doesn't address your problem. Apologies for the problems this caused you and thanks much for bringing the issue to our attention. Here is the ldd of parser.so with the broken rubygem-json package ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so undefined symbol: RSTRING_PTR (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so) undefined symbol: RSTRING_LEN (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so) linux-vdso.so.1 = (0x2ae120f0c000) libruby.so.1.8 = /usr/lib64/libruby.so.1.8 (0x2ae12131b000) libpthread.so.0 = /lib64/libpthread.so.0 (0x2ae121619000) libdl.so.2 = /lib64/libdl.so.2 (0x2ae121835000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x2ae121a39000) libm.so.6 = /lib64/libm.so.6 (0x2ae121c71000) libc.so.6 = /lib64/libc.so.6 (0x2ae121ef5000) librt.so.1 = /lib64/librt.so.1 (0x2ae12224c000) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x2ae122455000) /lib64/ld-linux-x86-64.so.2 (0x2ae120ef) And the ldd of parser.so from the rebuilt package ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so linux-vdso.so.1 = (0x7fff02dfc000) libruby.so.1.8 = /usr/lib64/libruby.so.1.8 (0x2b58c627f000) libpthread.so.0 = /lib64/libpthread.so.0 (0x2b58c657d000) librt.so.1 = /lib64/librt.so.1 (0x2b58c6799000) libdl.so.2 = /lib64/libdl.so.2 (0x2b58c69a2000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x2b58c6ba6000) libm.so.6 = /lib64/libm.so.6 (0x2b58c6ddf000) libc.so.6 = /lib64/libc.so.6 (0x2b58c7062000) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x2b58c73b9000) /lib64/ld-linux-x86-64.so.2 (0x2b58c5e54000) On Wed, Nov 28, 2012 at 9:59 AM, Jeff McCune j...@puppetlabs.com wrote: On Fri, Nov 23, 2012 at 2:46 PM, Alaric paxindust...@gmail.com wrote: Hi, I'm having a weird issue and was wondering if anyone else had run into it. I recently upgraded from puppet 2.7 - 3.0.1 After cleaning up some gems on my puppet master everything seemed to be working ok. I had originally used the EPEL repo's to deploy puppet, but switched to the Puppet Labs repos so I could upgrade to 2.7 then 3. On RHEL5 only, I get a RSTRING_PTR error if I upgrade to the Puppet Labs version (1.4.6) if I roll back to the EPEL veriosn of rubygem-json (1.4.3) Everything works again. Has anyone affected by this issue seen https://bugzilla.redhat.com/show_bug.cgi?id=634380 ? This information leads me to believe the rubygem-json package from Puppet Labs may not be carrying the same patch that the rubygem-json 1.4.3 package from the Fedora Project is carrying. This difference may be the cause of the error. Can anyone confirm? -Jeff -- 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. -- Matthaus Owens Release Manager, 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.
Re: [Puppet Users] passenger used in puppet 3.0?
we have f5's load balancer can it be used instead of Nginx? On Wednesday, November 28, 2012 10:30:24 AM UTC-5, jmslagle wrote: On 11/28/2012 09:53 AM, DJames wrote: current dev system is using passenger, but production (babystage) is using 3.0 version, and we have 1800+ servers (prod) that will be clients is passenger the way to go still? I was previously using passenger and just recently switched to using nginx/unicorn. I like the setup a lot better - I can't really quantify why other than the architecture of the way it does it seems better to me, and getting passenger working was a pain under RHEL6. General instructions here: http://projects.puppetlabs.com/projects/1/wiki/using_unicorn Some notes: 1) I ended up symlinking /etc/puppet to ~puppet/.puppet to fix the issue where puppet master not running as root will not look in the right place for it's config. 2) I couldn't find unicorn packages for RHEL - I ended up using gem2rpm and tweaking it to build. 3) I used supervisord instead of god because I'm more familiar with it. Again you'll likely need to build packages for it - I just updated the spec here: https://github.com/easel/supervisor-rpm There's a good puppet module to manage supervisord here: https://github.com/plathrop/puppet-module-supervisor Thanks, Jason -- 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/-/air1UqX5oMkJ. 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: [facter]Bug can't get : ipaddress_ethX
Which facter version are you seeing this on? (`facter --version`) On Wed, Nov 28, 2012 at 9:14 AM, AnOnJoe anon...@gmail.com wrote: sorry there is a typo : Le mercredi 28 novembre 2012 18:06:54 UTC+1, AnOnJoe a écrit : Hello, I have a problem with facter : eg: facter |grep ipaddress_eth1 ipaddress_eth1 = 192.168.0.254 works but facter ipaddress_eth1 return nothing Do you know how I can work with this ? thx -- 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/-/db0413060ncJ. 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. -- Matthaus Owens Release Manager, 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.
Re: [Puppet Users] Puppet 3.0 Puppet labs repo package problem on rhel5
That worked for me. Thanks!!! On Wed, Nov 28, 2012 at 11:18 AM, Matthaus Owens matth...@puppetlabs.comwrote: The problem was that our el5 rubygem-json package was the el6 src rebuilt, without the patch, against ruby 1.8.5. Rebuilding the rubygem-json package against the ruby 1.8.7 packages in our dependencies repo resolved the parser.so linking errors. I've included the ldd of the parser.so before and after below as well. The updated package is now available in our dependencies repo. Please let us know if this doesn't address your problem. Apologies for the problems this caused you and thanks much for bringing the issue to our attention. Here is the ldd of parser.so with the broken rubygem-json package ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so undefined symbol: RSTRING_PTR (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so) undefined symbol: RSTRING_LEN (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so) linux-vdso.so.1 = (0x2ae120f0c000) libruby.so.1.8 = /usr/lib64/libruby.so.1.8 (0x2ae12131b000) libpthread.so.0 = /lib64/libpthread.so.0 (0x2ae121619000) libdl.so.2 = /lib64/libdl.so.2 (0x2ae121835000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x2ae121a39000) libm.so.6 = /lib64/libm.so.6 (0x2ae121c71000) libc.so.6 = /lib64/libc.so.6 (0x2ae121ef5000) librt.so.1 = /lib64/librt.so.1 (0x2ae12224c000) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x2ae122455000) /lib64/ld-linux-x86-64.so.2 (0x2ae120ef) And the ldd of parser.so from the rebuilt package ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so linux-vdso.so.1 = (0x7fff02dfc000) libruby.so.1.8 = /usr/lib64/libruby.so.1.8 (0x2b58c627f000) libpthread.so.0 = /lib64/libpthread.so.0 (0x2b58c657d000) librt.so.1 = /lib64/librt.so.1 (0x2b58c6799000) libdl.so.2 = /lib64/libdl.so.2 (0x2b58c69a2000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x2b58c6ba6000) libm.so.6 = /lib64/libm.so.6 (0x2b58c6ddf000) libc.so.6 = /lib64/libc.so.6 (0x2b58c7062000) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x2b58c73b9000) /lib64/ld-linux-x86-64.so.2 (0x2b58c5e54000) On Wed, Nov 28, 2012 at 9:59 AM, Jeff McCune j...@puppetlabs.com wrote: On Fri, Nov 23, 2012 at 2:46 PM, Alaric paxindust...@gmail.com wrote: Hi, I'm having a weird issue and was wondering if anyone else had run into it. I recently upgraded from puppet 2.7 - 3.0.1 After cleaning up some gems on my puppet master everything seemed to be working ok. I had originally used the EPEL repo's to deploy puppet, but switched to the Puppet Labs repos so I could upgrade to 2.7 then 3. On RHEL5 only, I get a RSTRING_PTR error if I upgrade to the Puppet Labs version (1.4.6) if I roll back to the EPEL veriosn of rubygem-json (1.4.3) Everything works again. Has anyone affected by this issue seen https://bugzilla.redhat.com/show_bug.cgi?id=634380 ? This information leads me to believe the rubygem-json package from Puppet Labs may not be carrying the same patch that the rubygem-json 1.4.3 package from the Fedora Project is carrying. This difference may be the cause of the error. Can anyone confirm? -Jeff -- 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. -- Matthaus Owens Release Manager, 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. -- 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 3.0 Puppet labs repo package problem on rhel5
For me as well! Thanks for all the help!! On Nov 28, 2012, at 2:37 PM, Brian Jolly br...@brianjolly.com wrote: That worked for me. Thanks!!! On Wed, Nov 28, 2012 at 11:18 AM, Matthaus Owens matth...@puppetlabs.com wrote: The problem was that our el5 rubygem-json package was the el6 src rebuilt, without the patch, against ruby 1.8.5. Rebuilding the rubygem-json package against the ruby 1.8.7 packages in our dependencies repo resolved the parser.so linking errors. I've included the ldd of the parser.so before and after below as well. The updated package is now available in our dependencies repo. Please let us know if this doesn't address your problem. Apologies for the problems this caused you and thanks much for bringing the issue to our attention. Here is the ldd of parser.so with the broken rubygem-json package ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so undefined symbol: RSTRING_PTR (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so) undefined symbol: RSTRING_LEN (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so) linux-vdso.so.1 = (0x2ae120f0c000) libruby.so.1.8 = /usr/lib64/libruby.so.1.8 (0x2ae12131b000) libpthread.so.0 = /lib64/libpthread.so.0 (0x2ae121619000) libdl.so.2 = /lib64/libdl.so.2 (0x2ae121835000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x2ae121a39000) libm.so.6 = /lib64/libm.so.6 (0x2ae121c71000) libc.so.6 = /lib64/libc.so.6 (0x2ae121ef5000) librt.so.1 = /lib64/librt.so.1 (0x2ae12224c000) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x2ae122455000) /lib64/ld-linux-x86-64.so.2 (0x2ae120ef) And the ldd of parser.so from the rebuilt package ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so linux-vdso.so.1 = (0x7fff02dfc000) libruby.so.1.8 = /usr/lib64/libruby.so.1.8 (0x2b58c627f000) libpthread.so.0 = /lib64/libpthread.so.0 (0x2b58c657d000) librt.so.1 = /lib64/librt.so.1 (0x2b58c6799000) libdl.so.2 = /lib64/libdl.so.2 (0x2b58c69a2000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x2b58c6ba6000) libm.so.6 = /lib64/libm.so.6 (0x2b58c6ddf000) libc.so.6 = /lib64/libc.so.6 (0x2b58c7062000) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x2b58c73b9000) /lib64/ld-linux-x86-64.so.2 (0x2b58c5e54000) On Wed, Nov 28, 2012 at 9:59 AM, Jeff McCune j...@puppetlabs.com wrote: On Fri, Nov 23, 2012 at 2:46 PM, Alaric paxindust...@gmail.com wrote: Hi, I'm having a weird issue and was wondering if anyone else had run into it. I recently upgraded from puppet 2.7 - 3.0.1 After cleaning up some gems on my puppet master everything seemed to be working ok. I had originally used the EPEL repo's to deploy puppet, but switched to the Puppet Labs repos so I could upgrade to 2.7 then 3. On RHEL5 only, I get a RSTRING_PTR error if I upgrade to the Puppet Labs version (1.4.6) if I roll back to the EPEL veriosn of rubygem-json (1.4.3) Everything works again. Has anyone affected by this issue seen https://bugzilla.redhat.com/show_bug.cgi?id=634380 ? This information leads me to believe the rubygem-json package from Puppet Labs may not be carrying the same patch that the rubygem-json 1.4.3 package from the Fedora Project is carrying. This difference may be the cause of the error. Can anyone confirm? -Jeff -- 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. -- Matthaus Owens Release Manager, 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at
Re: [Puppet Users] Puppet 3.0 Puppet labs repo package problem on rhel5
Thanks Jeff for pointing out that the EPEL maintainer and the puppet labs maintainer should have been coordinating on rubygem-json. (It's the same guyme. I'm an idiot). Mike On Wed, Nov 28, 2012 at 11:37 AM, Brian Jolly br...@brianjolly.com wrote: That worked for me. Thanks!!! On Wed, Nov 28, 2012 at 11:18 AM, Matthaus Owens matth...@puppetlabs.comwrote: The problem was that our el5 rubygem-json package was the el6 src rebuilt, without the patch, against ruby 1.8.5. Rebuilding the rubygem-json package against the ruby 1.8.7 packages in our dependencies repo resolved the parser.so linking errors. I've included the ldd of the parser.so before and after below as well. The updated package is now available in our dependencies repo. Please let us know if this doesn't address your problem. Apologies for the problems this caused you and thanks much for bringing the issue to our attention. Here is the ldd of parser.so with the broken rubygem-json package ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so undefined symbol: RSTRING_PTR (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so) undefined symbol: RSTRING_LEN (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so) linux-vdso.so.1 = (0x2ae120f0c000) libruby.so.1.8 = /usr/lib64/libruby.so.1.8 (0x2ae12131b000) libpthread.so.0 = /lib64/libpthread.so.0 (0x2ae121619000) libdl.so.2 = /lib64/libdl.so.2 (0x2ae121835000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x2ae121a39000) libm.so.6 = /lib64/libm.so.6 (0x2ae121c71000) libc.so.6 = /lib64/libc.so.6 (0x2ae121ef5000) librt.so.1 = /lib64/librt.so.1 (0x2ae12224c000) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x2ae122455000) /lib64/ld-linux-x86-64.so.2 (0x2ae120ef) And the ldd of parser.so from the rebuilt package ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so linux-vdso.so.1 = (0x7fff02dfc000) libruby.so.1.8 = /usr/lib64/libruby.so.1.8 (0x2b58c627f000) libpthread.so.0 = /lib64/libpthread.so.0 (0x2b58c657d000) librt.so.1 = /lib64/librt.so.1 (0x2b58c6799000) libdl.so.2 = /lib64/libdl.so.2 (0x2b58c69a2000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x2b58c6ba6000) libm.so.6 = /lib64/libm.so.6 (0x2b58c6ddf000) libc.so.6 = /lib64/libc.so.6 (0x2b58c7062000) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x2b58c73b9000) /lib64/ld-linux-x86-64.so.2 (0x2b58c5e54000) On Wed, Nov 28, 2012 at 9:59 AM, Jeff McCune j...@puppetlabs.com wrote: On Fri, Nov 23, 2012 at 2:46 PM, Alaric paxindust...@gmail.com wrote: Hi, I'm having a weird issue and was wondering if anyone else had run into it. I recently upgraded from puppet 2.7 - 3.0.1 After cleaning up some gems on my puppet master everything seemed to be working ok. I had originally used the EPEL repo's to deploy puppet, but switched to the Puppet Labs repos so I could upgrade to 2.7 then 3. On RHEL5 only, I get a RSTRING_PTR error if I upgrade to the Puppet Labs version (1.4.6) if I roll back to the EPEL veriosn of rubygem-json (1.4.3) Everything works again. Has anyone affected by this issue seen https://bugzilla.redhat.com/show_bug.cgi?id=634380 ? This information leads me to believe the rubygem-json package from Puppet Labs may not be carrying the same patch that the rubygem-json 1.4.3 package from the Fedora Project is carrying. This difference may be the cause of the error. Can anyone confirm? -Jeff -- 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. -- Matthaus Owens Release Manager, 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send
Re: [Puppet Users] Managing ssh server's keys?
On 11/26/2012 08:54 PM, Matt Zagrabelny wrote:
On Mon, Nov 26, 2012 at 1:47 PM, Jakov Sosic jso...@srce.hr wrote:
Hi.
I'm wondering is there a way to manage ssh servers, in a way that every
machine has it's own key?
I've used the private file server mechanism to serve out node sensitive
files.
Thank you for the idea. Now only problem that is left is how to call a
script to generate keys if files are not accessible in private section :-/
I know one can do something like this:
file { '/etc/ssh/ssh_host_rsa_key.pub':
ensure = file,
mode= 0644,
source = [
'puppet:///private/etc/ssh/ssh_host_rsa_key.pub',
'puppet:///modules/sshd/ssh_host_rsa_key.pub',
],
require = Package['openssh-server'],
notify = Service['sshd'],
}
and put some blank default files in there, but I would much prefer to
build the keys if they are not there, and I presume I need some puppet
magic here :-/
Any ideas?
--
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] check if if file exists on client an master
Hi pupper community, I am working with puppet on Windows and have an issue. I want to check what version of a package is installed. My idea was to add a file in the package package28112012.txt and while running the manifest check if that package28112012.txt exists on the agent? Can I define a variable reading this filename on the master? Regards and thanks in advance, Romain -- 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/-/tuum3dQXrYoJ. 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] upgrading puppet
In regard to: [Puppet Users] upgrading puppet, Paolo said (at 2:08am on Nov...: I have an old puppet infrastructure that runs puppet 0.24.4 (client and server) and I was finally given the go ahead to upgrade (both client and server) :-) I have a few questions: 1. To which version should I upgrade puppet to? I was thinking of upgrading to the latest 2.6 version... I think the answer is, it depends. I personally would want to upgrade to puppet 3.0.x. Since you're going to go through the pain of upgrading anyway, it would be best to upgrade to what's current, so you avoid a separate upgrade from 2.6 or 2.7 to 3.x. Of course, there's always a chance that doing separate upgrades will be less work overall, but I'm skeptical about that in this case. The main gotcha is that 3.x introduces a number of incompatible, so it might require changes to some of your classes to upgrade to 3.x than it would to go to 2.6. It all depends on what features you've made use of and how your classes are written. If you don't decide to upgrade to 3.x, you should at least consider 2.7. I can't think of any compelling reason to choose 2.6 over 2.7, at this point. 2. Anyone knows of any pitfalls I should watch out for in upgrading from such an old version? Scoping with variable names and facts is probably the big one. Another one that we had to adjust is classes with a - in the name. That even breaks in some of the later 2.7 versions, though there's a setting in 2.7.20 that allows it to work again. My recommendation is that you install 3.0.x somewhere, install puppet-lint, and use puppet-lint and puppet parser validate on your manifests. Study the output from both, and adjust accordingly. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- 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] check if if file exists on client an master
I think you would want to create a fact that publish that state to the master. On Wed, Nov 28, 2012 at 3:26 PM, Romain Gales romain.ga...@gmail.comwrote: Hi pupper community, I am working with puppet on Windows and have an issue. I want to check what version of a package is installed. My idea was to add a file in the package package28112012.txt and while running the manifest check if that package28112012.txt exists on the agent? Can I define a variable reading this filename on the master? Regards and thanks in advance, Romain -- 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/-/tuum3dQXrYoJ. 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] Managing ssh server's keys?
On Wed, Nov 28, 2012 at 1:50 PM, Jakov Sosic jso...@srce.hr wrote:
On 11/26/2012 08:54 PM, Matt Zagrabelny wrote:
On Mon, Nov 26, 2012 at 1:47 PM, Jakov Sosic jso...@srce.hr wrote:
Hi.
I'm wondering is there a way to manage ssh servers, in a way that every
machine has it's own key?
I've used the private file server mechanism to serve out node sensitive
files.
Thank you for the idea. Now only problem that is left is how to call a
script to generate keys if files are not accessible in private section :-/
I know one can do something like this:
file { '/etc/ssh/ssh_host_rsa_key.pub':
ensure = file,
mode= 0644,
source = [
'puppet:///private/etc/ssh/ssh_host_rsa_key.pub',
'puppet:///modules/sshd/ssh_host_rsa_key.pub',
],
require = Package['openssh-server'],
notify = Service['sshd'],
}
and put some blank default files in there, but I would much prefer to
build the keys if they are not there, and I presume I need some puppet
magic here :-/
Any ideas?
Part of our server bootstrapping process is to copy over the ssh keys
to the puppetmaster after puppet has installed openssh-server.
As far as generating the keys, that should be pretty straightforward
using ssh-keygen.
-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] Managing ssh server's keys?
On 11/28/2012 09:10 PM, Matt Zagrabelny wrote: Part of our server bootstrapping process is to copy over the ssh keys to the puppetmaster after puppet has installed openssh-server. So how do you do that with puppet? Or you use cobbler/FAI or that kind of tool for that particular task? As far as generating the keys, that should be pretty straightforward using ssh-keygen. I know that but I want to generate it only if keys are not in folder... -- 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: [facter]Bug can't get : ipaddress_ethX
Havent read the code yet... But cmd facter xx executes the xx plugin and print the return value. the ipaddress_ethX are part of the ipaddress plugin that is the one that should be executed. Nonetheless as the ipaddress plugin register the ipaddress_ethX facters they would not show either. On Wed, Nov 28, 2012 at 2:59 PM, Matthaus Owens matth...@puppetlabs.comwrote: Which facter version are you seeing this on? (`facter --version`) On Wed, Nov 28, 2012 at 9:14 AM, AnOnJoe anon...@gmail.com wrote: sorry there is a typo : Le mercredi 28 novembre 2012 18:06:54 UTC+1, AnOnJoe a écrit : Hello, I have a problem with facter : eg: facter |grep ipaddress_eth1 ipaddress_eth1 = 192.168.0.254 works but facter ipaddress_eth1 return nothing Do you know how I can work with this ? thx -- 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/-/db0413060ncJ. 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. -- Matthaus Owens Release Manager, 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. -- 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] Managing ssh server's keys?
On Wed, Nov 28, 2012 at 2:14 PM, Jakov Sosic jso...@srce.hr wrote: On 11/28/2012 09:10 PM, Matt Zagrabelny wrote: Part of our server bootstrapping process is to copy over the ssh keys to the puppetmaster after puppet has installed openssh-server. So how do you do that with puppet? Or you use cobbler/FAI or that kind of tool for that particular task? Copy+paste. Not all of our processes are automated...yet. As far as generating the keys, that should be pretty straightforward using ssh-keygen. I know that but I want to generate it only if keys are not in folder... Whatever is generating your node manifest (on the master) could also perform either: 1) scp ssh keys from the node to master or 2) run ssh-keygen on master Unless you are using the default node, this should work. -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] Re: [facter]Bug can't get : ipaddress_ethX
*facter --version* *1.5.7* 2012/11/28 Matthaus Owens matth...@puppetlabs.com Which facter version are you seeing this on? (`facter --version`) On Wed, Nov 28, 2012 at 9:14 AM, AnOnJoe anon...@gmail.com wrote: sorry there is a typo : Le mercredi 28 novembre 2012 18:06:54 UTC+1, AnOnJoe a écrit : Hello, I have a problem with facter : eg: facter |grep ipaddress_eth1 ipaddress_eth1 = 192.168.0.254 works but facter ipaddress_eth1 return nothing Do you know how I can work with this ? thx -- 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/-/db0413060ncJ. 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. -- Matthaus Owens Release Manager, 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. -- 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] Unable to configure Puppet-dashboard using opensource package
Hi I'm trying to configure Puppet-dashboard after installing Puppet from the open source package. But there was no issues when using the Enterprise package. Do you have any solutions for the below error? I'm trying to configure Puppet-dashboard. # rake RAILS_ENV=production db:migrate NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /opt/puppet-dashboard/vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /opt/puppet-dashboard/vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rubygems/source_index.rb:91. - # ruby -v ruby 1.9.3p194 (2012-04-20 revision 35410) [i686-linux] -- rack (1.4.1, 1.3.5, 1.1.0) rack-cache (1.2) rack-openid (1.3.1) rack-ssl (1.3.2) rack-test (0.6.1) rails (3.2.6) railties (3.2.6) raindrops (0.10.0) rake (0.9.2.2) rdoc (3.12, 3.9.4) ruby-openid (2.1.8) rubygems-update (1.6.2) -- 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/-/qzczRWW_O6YJ. 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] Managing ssh server's keys?
On 11/28/2012 09:19 PM, Matt Zagrabelny wrote: Whatever is generating your node manifest (on the master) could also perform either: 1) scp ssh keys from the node to master or 2) run ssh-keygen on master Unless you are using the default node, this should work. I have an idea about #2. I won't copy keys from nodes, but generate it on the master if they are not there already. If I succeed I will post solution. -- 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: [facter]Bug can't get : ipaddress_ethX
I have upgraded my facter version : facter --version 1.6.9 It's now working like a charm Thx. -- 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/-/4729ePmYnU4J. 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] check if if file exists on client an master
there is what i tried:
# getpfoleproxyver.rb
#
Facter.add(:getpfoleproxyver) do
setcode do
Facter::Util::Resolution.exec('basename `ls
/softw4pc/Misc/pfoleproxy/pfoleproxy*.txt`')
end
end
the fact is working fine, but how to use this in my manifest?
i tried a lot but it was always empty?
$getpfoleproxyver should be correct, no?
On Wednesday, 28 November 2012 21:09:40 UTC+1, showy wrote:
I think you would want to create a fact that publish that state to the
master.
On Wed, Nov 28, 2012 at 3:26 PM, Romain Gales
romain...@gmail.comjavascript:
wrote:
Hi pupper community,
I am working with puppet on Windows and have an issue.
I want to check what version of a package is installed.
My idea was to add a file in the package package28112012.txt and while
running the manifest check if that package28112012.txt exists on the agent?
Can I define a variable reading this filename on the master?
Regards and thanks in advance,
Romain
--
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/-/tuum3dQXrYoJ.
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/-/XuJnHGC4BHYJ.
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] variable not replace when come from hiera
Hi Craig,
Your solution solve my problem.
Thank a lot.
I use this path because i want to seperate statics files and data hiera
from puppet module (for versionning and test).
And i want also have different data with each environment.
My fileserver.conf :
[developpement]
path /etc/puppet/puppetData/developpement/fichiers
allow *
[production]
path /etc/puppet/puppetData/production/fichiers
allow *
When i try this, it don't work
[fichiers]
path /etc/puppet/puppetData/%{environment}/fichiers (or
$environment)
allow *
May be not the best solution but it work now.
Thank again.
Fred
Le dimanche 25 novembre 2012 00:45:27 UTC-10, Craig Dunn a écrit :
On 23/11/2012 23:03, fpommier wrote:
Hi,
I use puppet 2.7.16
i try to use hiera to store file data
yaml file :
apt:
'/etc/apt/preferences.d':
ensure: directory
recurse: true
source: puppet:///$environment/$module_name/preferences.d
Try this with;
source: puppet:///%{environment}/%{module_name}/preferenced.d
Your source path confuses me a bit anyway, surely your environment
dictates your modulepath and this should just be
puppet:///modules/%{module_name}/preferences.d ?
Regards
Craig
--
Craig Dunn
Professional Services
Puppet Labs Inc.http://www.puppetlabs.com
--
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/-/SwJNXsz318IJ.
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: Facter 1.6.15 available
Facter 1.6.15 is a maintenance release in the 1.6.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.15.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/facter-1.6.15.dmg See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads Please report feedback via the Puppet Labs Redmine site, using a affected version of 1.6.15: http://projects.puppetlabs.com/projects/facter/ Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki Fixes targeted at this version in our bug tracker: http://projects.puppetlabs.com/versions/341 = ## Facter 1.6.15 Changelog ## = Alex Harvey (1): 0e72145 (#11612) Add support for processorX facts on HP-UX Francis Gulotta (1): 6b9ce2e (#17177) Add MTU information to interfaces Jeff McCune (4): b973caf (maint) Add .yardopts file 0d66362 (#16511) Do not call arp -an on Solaris nodes 6ef8cce Fixup whitespace in (#17177) Add MTU information to interfaces d46b42a (#17177) Fix spec failure when running on Mac OS X Josh Cooper (2): e3da3c7 (#17493) Safer handling of EC2 'open' calls b336259 (#17493) Merge rescue blocks Matthaus Owens (3): 4b2baab (maint) Remove hard dependency on rspec from Rakefile 7aaee5e Updating FACTERVERSION for 1.6.15-rc1 6e7ab44 Updating FACTERVERSION to 1.6.15 Moses Mendoza (3): bcbaffd Update ips ruby libdir to use sitelibdir instead of rubylibdir 2a9c78a Turn on IPS building for facter c31cca5 install.rb doesn't support sbindir, so remove it from ips rules -- 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] 1.8.7 = 1.9.3 migration, compilation times raised twice!?
On Wed, Nov 28, 2012 at 10:34 AM, asq asqu...@gmail.com wrote: i've made a migration on our puppetmasters yesterday, hoping it will run faster and/or make less load on machines with newer ruby. but actual result is just opposite, our compilation times went up a lot, ie: Nov 27 14:30:12 punch puppet-master[15293]: Compiled catalog for lb1 in environment production in 183.42 seconds Nov 27 15:38:42 punch puppet-master[24399]: Compiled catalog for lb1 in environment production in 158.49 seconds Nov 27 15:51:19 punch puppet-master[11963]: Compiled catalog for lb1 in environment production in 175.00 seconds Nov 27 16:04:15 punch puppet-master[15264]: Compiled catalog for lb1 in environment production in 120.36 seconds Nov 27 19:25:52 punch puppet-master[552]: Compiled catalog for lb1 in environment production in 281.54 seconds Nov 27 20:20:19 punch puppet-master[2273]: Compiled catalog for lb1 in environment production in 239.05 seconds Nov 27 22:26:03 punch puppet-master[4919]: Compiled catalog for lb1 in environment production in 275.38 seconds Nov 28 00:55:24 punch puppet-master[12293]: Compiled catalog for lb1 in environment production in 267.91 seconds guess when migration has occured. this machine (lb1) has ~2000 resources. i'm a bit worried about scalability... we can go back to 1.8.7 now, but it won't be supported in 7 months (ie. no security updates). What version of Puppet are you on? Where did you get your 1.9.3? -- 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/-/NV-H40aVfrcJ. 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] StackOverflow when running Puppet agent -t
the system still have free memory, here is what get when I run free command: total used free sharedbuffers cached Mem:609600 455840 153760 0 1256 105236 -/+ buffers/cache: 349348 260252 Swap:0 0 0 2012/11/28 Jeff McCune j...@puppetlabs.com On Wed, Nov 28, 2012 at 5:42 AM, Med75 mohamed.hadr...@viavoo.com wrote: The problem disappeared after a reboot of the client. I saw your answer too late so I haven't had the chance to run the agent with --debug and --trace... I'll update this thread once it will be back again. meanwhile, and after a couple of agent run, I'm now getting a different message, here is the full stack trace: http://pastebin.com/yLdBhcyN I don't know if this is related or not, and if it would be better to create a new thread. How much memory does the machine have, and how much memory free? It looks like the system is running dry: Cannot allocate memory - fork FYI, In Puppet 3 we're now using fork when doing catalog runs, which may increase memory utilization relative to previous versions of Puppet. -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announcing stdlib 3.2.0 and 2.6.0
Hello, We're pleased to announce the release of the stdlib module at version 3.2.0 [1] and 2.6.0 [2]. Please keep in mind stdlib 2 is compatible with Puppet 2.6 and 2.7 while stdlib 3 is compatible with Puppet 2.7 and 3. [1] http://forge.puppetlabs.com/puppetlabs/stdlib/3.2.0 [2] http://forge.puppetlabs.com/puppetlabs/stdlib/2.6.0 The module may be installed from the Forge using the puppet-module tool: puppet module install puppetlabs-stdlib Thank you to the following contributors. Both of these minor release versions add the following new and backwards compatible functionality: Chad Metcalf * Add an ensure_packages function. (8a8c09e) Joe Julian * Add function, uriescape, to URI.escape strings. Redmine #17459 (70f4a0e) Peter Meier * Add reject() function (a79b2cd) * (#14670) autorequire a file_line resource's path (dfcee63) Erik Dalén * (#17797) min() and max() functions (9954133) Wil Cooley * (#13974) Add predicate functions for interface facts (f819417) Gary Larizza * Add the pick() function (ba6dd13) Joshua Harlan Lifton * Add join_keys_to_values function (ee0f2b3) * Extend delete function for strings and hashes (7322e4d) Cheers, -Jeff McCune -- 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] Penn State Looking for RHEL Sysadmin with DevOps Puppet training/experience
Hi, Thank you for letting me post this to the community. It is not spam. I am a real RHEL sysadm in for the online campus at Penn State. We are looking to expand our group and are committed to DevOps using Puppet. If anyone is interested in this position, please check out the employment site for the University. The job is located in University Park and supports the fastest growing (revenue and enrollments) campus of the University. We currently support complex multi-datacenter Drupal systems, and are expanding in that area. This job is to be part of a team that makes that happen. BTW we also work with some awesome Drupal people. The site to find out more and apply is http://psu.jobs/Search/Opportunities.html Search for the following description. Systems Administrator (Red Hat) Campus/Location: University Park CampusDate Announced: 11/28/2012 Work Unit: OutreachJob Number: 38237 Department: Outreach Technology ServicesLevel/Salary Band/Classification: 02 - J - Non-exempt 03 - K - Exempt 04 - L - Exempt Penn State Outreach Technology Services seeks an experienced Systems Administrator with Drupal and Word Press experience to join our innovative Web Services team. This team works closely with both Outreach Marketing and Learning Design Drupal developers, to innovate and collaborate on cutting edge solutions. The role will lead in the development, implementation, management, testing, and support of a LAMP (Linux, APACHE, MySQL, PHP) environment. This position will be responsible for creating and implementing technical specifications, will be the primary specialized contact, and will be responsible for the day-to-day operation of Outreach’s web-based Marketing servers including load balancing technologies and SSL certificate management. This job will be filled as a level 2, level 3, or level 4, depending upon the successful candidate's competencies, education, and experience. Typically requires an Associate’s degree or higher plus two years of related experience, or an equivalent combination of education and experience for a level 2. Additional experience and/or education and competencies are required for higher level jobs. Preferred Certifications in Red Hat Certified System Administrator (RHCSA), Red Hat Certified Engineer (RHCE, VMware Certified Professional (VCP),) Puppet Professional Certification. Candidate must be experienced in requirements gathers, performing needs analysis, evaluating and recommending vendors, and developing specialized design specifications for new hardware and software systems. The successful candidate will have advanced knowledge and experience in Server Administration and Linux Red Hat operating system including ensuring proper operation/configuration of servers, ensuring proper operation of and managing software, upgrades, patches, as well as monitoring server performance. Candidate should have strong documentation skills and familiarity with change control processes and have ability to work effectively with business organizations, understanding their needs and showing tact and judgment in developing specialized solutions and analyzing/diagnosing specialized issues. This position requires some after-hours work for emergency support and participation on an On Call rotation. This is a fixed-term appointment funded for one year from date of hire with excellent possibility of re-funding. We seek candidates who are able to demonstrate experience and ability to advance Outreach's diversity initiative. -- 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/-/qOPO1xXlz3UJ. 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 update a managed directory?
I have a managed directory defined in one class. I need the ability to update a subset of files in the managed directory from a puppet define. I would like to simply define a new file resource that is a directory and have the files from this new resource simply overlay the existing managed directory. Of course I get a duplication declaration error since the File titles would be the same. Is there anyway to achieve this? I realize I could just update the source files but I need the flexibility to install to select nodes. -- 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/-/YaSW5VHM0VsJ. 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] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc
On Wed, Nov 28, 2012 at 10:55 AM, John Lamb lam...@wfu.edu wrote: I am also seeing this bug on one of my nodes (worryingly, the puppet master itself!) The relevant output of puppet agent -t --debug --trace --verbose matches what Fabrice and Lee have also reported: OK, there's definitely a bug somewhere... I'm going to work on reproducing this issue tomorrow. Before then, could anyone affected by this allocator undefined for Proc error please let me know what exact versions of the operating system, Ruby, and Puppet they're running? If possible, if you could just privately email me the output of facter from an affected Puppet master that would be greatly helpful in reproducing this issue. Finally, could you please send me (privately) a copy and paste of all exported resources in your manifests? You can probably find them easiest with a recursive grep against @@. This will help me populate the storedconfigs database so I can reproduce this issue. Thanks, -Jeff -- 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] Could not find default node or by name with 'ip-10-195-207-236.ec2.internal, ip-10-195-207-236.ec2, ip-10-195-207-236' on node ip-10-195-207-236.ec2.internal
Hi,
I am new to puppet. I have configured puppet master and agent.
1. Executed this *puppetca --sign ip-10-194-18-145.ec2.internal* command
in puppet master instance. It returns an output like
* notice: Signed certificate request for ip-10-194-18-145.ec2.internal*
* notice: Removing file Puppet::SSL::CertificateRequest
ip-10-194-18-145.ec2.internal at
'/var/lib/puppet/ssl/ca/requests/ip-10-194-18-145.ec2.internal.pem'*
* *Is there any issue with this error ?
2. Created one site.pp file in *puppet master /etc/puppet/manifests* folder
with below content.
node 'client' {
file { /root/files/test:
source = puppet:///files/test
}
}
3 Added below content in *puppet master /etc/puppet/fileserver.conf*
path /etc/puppet/files
allow *.puppet.com
allow *.internal
4 When I am trying to execute command *puppet apply site.pp* in manifests
folder, I am getting an error message like below.
*Could not find default node or by name with
'ip-10-195-207-236.ec2.internal, ip-10-195-207-236.ec2, ip-10-195-207-236'
on node ip-10-195-207-236.ec2.internal*
I am trying to resolve this issue such a long time.Can any one help me to
resolve this issue as early possible?,
Thanks in advance.
With Regards,
Krishna Bhaskar.
--
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/-/wlox7r2apVAJ.
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: problems with exported exec resources
On Thursday, November 29, 2012 1:40:01 AM UTC+11, jcbollinger wrote:
So you're saying that *none* of the collected Execs are running? In that
case, check the cached catalog to see whether it contains those Execs at
all. That will establish whether it is a problem with resource collection
or with the individual resources. It should also allow you to verify the
resource parameters.
As for the individual resources, you would be well advised to use curly
brackets around variable names inside strings. Especially, you should use
them in /srv/mnt/.${hostname}_commvault_backed_up and similar strings
(else Puppet will think you want the variable named
$hostname_commvault_backed_up), but it's a good habit to use curly brackets
in every variable reference.
Actually, the brackets are probably your issue: you presumably don't
define a variable named $hostname_commvault_backed_up, so it interpolates
as nothing. That means what you've written is equivalent to creates =
'/srv/mnt/.', which is in turn equivalent to creates = '/srv/mnt'.
Since that directory already exists, applying the Execs will not result in
their commands running.
Of course! Thanks for that John, you are correct. I was having these
problems because I hadn't used braces in the use of the variable. When I
changed that, I got the behaviour I expected.
Thanks!
Geoff
--
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/-/q_xaX5fPFBwJ.
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.15-rc1 available
Puppet Dashboard 1.2.15-rc1 is a maintenance and bugfix release candidate of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.15-rc1.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.15-rc1: http://projects.puppetlabs.com/projects/dashboard Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html == ## Puppet Dashboard 1.2.15-rc1 Bug Fixes ## == (#16333) Override AR MySQL connector to set sql_mode Currently if there is a problematic sql_mode set globally it will end up breaking things. This patch overrides the configure_connection function of the MySQL connector to explicitly set the sql_mode to traditional for the session so that if something that breaks the queries used by the console (like ANSI_QUOTES) is set globally, it won't affect it. Handles bogus pagination inputs. If you visit your local puppet dashboard at /nodes?per_page=whaaa you get an exception. If you visit /nodes?page=1 you will get no matching nodes. With this change, an invalid per_page uses the default per_page. A too-large page number will show the last page, and a too-small or invalid page number will show the first page. == ## Puppet Dashboard 1.2.15-rc1 Changelog ## == Aaron Stone (3): 251674b Handle out-of-range and bogus pagination inputs. 5b4d83f Unit tests for out-of-bounds-pagination. 8133354 In will_paginate 2.x, default per_page is hardcoded 30. Jeff Weiss (2): 0aadf88 (maint) fix session killing 757c518 (maint) fix failing tests Jill Burrows (1): 4ca7363 Verbosity++ for puppet:plugin:install rake task Ken J (2): b11c36a (#16333) Override AR MySQL connector to set sql_mode 54b9714 Modified to add the additional behavior in a saner way per dpittman's suggestion. Matthaus Owens (1): 87b4bad Update CHANGELOG, VERSION for 1.2.15-rc1 Moses Mendoza (1): 3c80866 Now that we ship 1.8.7, we can build for el5 Vlastimil Holer (1): 6dfb877 Make SQL status query more PostgreSQL-friendly. -- 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] Status of STONITH support in the puppetlabs corosync module?
Hi, 2012/11/27 SirDiesALot aal...@envysion.com Greetings - Hoping to hear from hunner or one of the other maintainers of the puppetlabs corosync module - there is a note on the git project page that there is currently no way to configure STONITH. Is this information current? It is. If so, has anybody come up with a simple method of managing STONITH with corosync via puppet? -- Dominik Żyła -- 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.
