search for: site_rubi

Well imitation is the highest form of flattery they say. So I''m surprised to see these packages neatly built to install into /opt/csw correctly and yet they exist somewhere else and have nothing to do with us here at Blastwave. fascinating. I guess we can always send an email to the person doing this and just ask if they want those packages in testing and then into the catalog for

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

We use puppet with two environments: [main] and [development]. These environments have different locations for their puppet manifests and modules (see puppet.conf below). Whenever I change/update a file in the directories belonging to the “main” environment, puppetmaster notices these changes and reacts to them w/o any hiccups. In contrast to this – if I change/touch a file in a directory

Hi again, puppetd started to hang with 100% CPU usage all of the sudden. Strace just keeps repeating these 2 lines: --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- sigreturn() = ? (mask now []) In logs it hangs with this message: debug: Calling fileserver.describe But lots of these fileserver.describe calls prior to hang are successful. If I run it with puppetd

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 =>

After upgrading my puppetmaster server to 0.22.2 using David''s src RPM''s for RHEL4 rebuilt for x86_64 i am getting the following error when puppetd attempts a configuration run. Mon Mar 26 10:05:43 EST 2007 Puppet (err): Could not run Puppet::[1]Network::Client::Master: Invalid value ''nil'' for noop When puppetd is started the initial run is

Hi, I have a puppet infrastructure running 2.6.14 under Passenger with about 30 nodes. I''m just spinning up a new Cent 6.3, puppet 2.7.19 master. Right now I have the master built and configured using the same configuration as my 2.6.14 setup, with a few tweaks for the new version. Puppet on the master built itself fine. I have puppetd stopped on the master. I tried pointing one

Hello, I am trying to install RubyGems on Ubuntu and i''m having trouble. I''ve downloaded rubygems 1.3.1 and when i run the sudo ruby setup.rb command I get the problem mentioned below. I''d really appreciate if someone can help me out. Thanks mkdir -p /usr/local/lib/site_ruby/1.8 mkdir -p /usr/bin install -c -m 0644 rbconfig/datadir.rb

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

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

This has been a much-requested feature, and is now a reality (in svn trunk): There is a new option, --ignoreimport, that will (surprisingly) ignore import statements. This is really only useful when using -- parseonly in a commit hook, and note that you''ll have to add the option to --parseonly, none of the puppet executables will add it for you. You should be able to

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

Hi, I am trying to install fog which is required for cloud provisioner. > gem install fog -v 0.7.2 I am getting the following error Building native extensions. This could take a while... ................ ERROR: Error installing fog: ERROR: Failed to build gem native extension. /usr/bin/ruby extconf.rb creating Makefile make

I''m trying to run puppetmasterd the first time with --mkusers. It fails with the following error message: 001 # /usr/bin/puppetmasterd --mkusers Could not configure for running; got 1 failure(s) Adding --verbose and --debug does nothing to improve the output. How do I begin to debug this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

I am trying to install some application using gem, but I keep on getting the error. I tried with ''gem clean'' and ''gem update''. The latter gives the following error (the same error is replicable when I try any ruby applications): # gem update --debug Exception `Errno::ENOENT'' at /usr/lib/ruby/site_ruby/1.8/rubygems/config_file.rb:51 - No such file or

Hi I''m having the following problem and tried already several workarounds, as well benp- tried to help me on irc. I copied the ntp modul from DavidS repo and adapted it in the Service part to run as well under openbsd. Which was just adding some binary if openbsd is the operatingsystem. However then I wanted to run it as well on a gentoo system (on centos, debian and openbsd it was

This is particularly nasty, since it''s on the puppetmaster itself: [root@puppet tmp]# rpm -q yum puppet puppet-server yum-3.0.5-1.el5.centos.5 puppet-0.24.0-2.el5 puppet-server-0.24.0-2.el5 [root@puppet tmp]# cat /etc/issue CentOS release 5 (Final) Here''s the output of puppetd --debug: notice: Starting catalog run debug: Loaded state in 0.01 seconds debug: Prefetching rpm

How do I debug errors with external nodes? When my client connects, the following appears on the puppetmaster when running in debug mode. It''s not feasible to always be running the pupeptmaster in debug mode. debug: importing ''/etc/puppet/modules/yum/manifests/client.pp'' in environment production info: Automatically imported yum::client from yum/client into production

I''m having an issue installing rubygems-0.8.11 on 2 different boxes but get the same error on both. The first box is a host environment where I am cross-compiling things for the arm-linux architecture. It is a debian sarge box using the ruby1.8 package which is ruby-1.8.2. I successfully cross-compiled ruby 1.8.4 for the arm-linux architecture and it runs well on the embedded

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