similar to: undefined method `initvars'

Hi, I''m trying to install puppet as a client on a new machine. I received this weird error when trying to start up as /etc/init.d/ puppet start : /usr/lib/ruby/1.8/openssl/cipher.rb:22: Cipher is not a module (TypeError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 36:in `gem_original_require'' from

I just installed the latest rc 1.7 to solve another issue I had. It solved the issue, but I''m getting a different issue. I''m running it interactively from an administrator command prompt. It connects to the master puppet server, processes the configuration items then gives an error. The interesting thing is that it never returns to the command prompt. It just hangs. I have

Anyone know what this is? It doesn''t seem related to puppet but I''m stumped. info: Loading facts in dmidecode info: Loading facts in cpuinfo debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in `deserialize'' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in

Hello, we have one puppet server managing approx servers, all FreeBSD. The problem is that the puppet clients all hangs, one by one, eventually. They will run for anything between an hour up to a week. But eventually the all hang. We really like puppet and want to keep using it. But the way it is now is completely unusable. We''ve tried many versions, from 24.x, and now 2.6.1rc1. But

I am using Ubuntu LTS 10.04 with the backported puppet 2.6.1-0ubuntu2~lucid1 I am trying to create user with the following manifests but at the end always getting the Could not find user git error message: What am i missing, seems the manifest not creating the missing git user. /etc/modules/git/manifests/user.pp class git::user { user{''install'': name

Hello Everybody, I am trying to install the puppetdb on the same machine as am running my puppetmaster. I am getting the following error when am trying to connect the agent: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit ''replace facts'' command for ftldwshost180.wsdev.citrix.com to PuppetDB at

I have this: class foo::foobar ($version) { } which is called like this: class facility::sanjose inherits facility::common { class { foo::foobar: version => "1.3.13" } } puppet complains with this on the client: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find parent resource type ''facility::sanjose'' of type hostclass in

Anybody knows what this error, bellow, means, the target file, C:/Splunk/etc/system/local/inputs.conf, does exist. sometimes, if I delete the file, it does actually create it, but never update it if it exists and changed... The resource is defined as:     file { "splunk_inputs":        owner   => SYSTEM,        group => SYSTEM,        mode    => 664,        require =>

Hi everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don''t have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins]

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

CentOS Errata and Security Advisory 2010:0166 Moderate Upstream details at : http://rhn.redhat.com/errata/RHSA-2010-0166.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 2eb372ef4dd9da7e03c2fcffbb932b9f gnutls-1.4.1-3.el5_4.8.i386.rpm 4710b94e81afacb90722cb8bf4eda618 gnutls-1.4.1-3.el5_4.8.x86_64.rpm

Both the server and the client in this example are running 2.6.5: One class seems to be causing the error: debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using b64_zlib_yaml /var/lib/gems/1.8/gems/puppet-2.6.5/lib/puppet/resource.rb:396:in

I''m being a good boy and using the puppetdoc tool to document my classes, however I''m hitting a minor annoyance. The top level documentation for a module (let''s call it "example) is pulled from example/README (not example/manifests/init.pp), okay I can cope with that. The documentation for the class in example/manifests/init.pp ends up as example::example (hmm,

CentOS Errata and Security Advisory 2010:0166 Moderate Upstream details at : http://rhn.redhat.com/errata/RHSA-2010-0166.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 0336d624dee8cd33c04e0fab51d8656d gnutls-1.4.1-3.el5_4.8.i386.rpm c53d51ecb020b9532641e7640dd41d41 gnutls-devel-1.4.1-3.el5_4.8.i386.rpm

I am working on building a facter tag based node classifier similar to https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/. However, I have run into an issue where I cannot use puppet''s require file ability to push the yaml file containing the facts file to the client because it would require two runs of puppet to pickup changes. Consequently, I have written into

Hi, I''m serving the puppetmaster application with its config.ru through unicorn - proxied by nginx. I''m using unix sockets, 4 workers, and 2048 backlog. The clients - after their typical "puppet run" - send back a report to the master in YAML. Some clients whose reports tend to be large (close to 2mb) get a 502 bad gateway error and error out. nginx log: 2010/10/22

Hi folks, When I enabled stored configs on my puppet master, it began keeping lots of open connections to the MySQL server (as far as I understand it opened one connection for each client run and never closed them). I set up the server to close idle connections after 5 minutes. Now the database server does close the connections but the puppet master keeps them in CLOSE_WAIT state and eventually

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi all, Getting some troubles installing bind: I''m working on debian squeeze, both client and server are 2.6.2, mod_passenger added. in my class definition: class conf_bind_nshost { include motd motd::register{"${name}": } #Register in motd module package { "bind9": ensure => "1:9.7.2.dfsg.P3-1.1", } file {"dns": require