similar to: Service ensuring fails on some distro (gentoo) with some packages

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

Hi, I''m testing puppet from the subversion trunk. I have a rather hacked-together system to install a CRM into one of my nodes, which worked (more or less) with version 0.19.3. When I tried to do a puppet run on a completely clean node it seemed to stall on the ''compilation'' part (I do an exec of ''perl Makefile.PL'' in the appropriate dir). When I broke

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

I am consistently getting the following error from puppetd when an exec resource is triggered by a refresh event: Apr 23 10:36:11 mailhub puppetd[37884]: Reopening log files Apr 23 10:36:11 mailhub puppetd[37884]: Starting Puppet client version 0.22.3 Apr 23 10:36:11 mailhub puppetd[37884]: Starting configuration run Apr 23 10:36:12 mailhub puppetd[37884]:

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

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

I updated to 0.22.3-1 from the dlutter repo (CentOS 4.4) and I''m still having trouble adding new nodes as others saw from the previous version, though I believe the error is different now. The procedure I used was: <client> /etc/init.d/puppet once -v <server> /usr/sbin/puppetca --sign nodename <client> /etc/init.d/puppet once -v This used to work for new nodes, now I

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

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

Hi all, Not sure if this is a bug in puppet, yum, or just something I''m doing wrong. I''m trying to use puppet to update a package to a particular version and exec a command when that update is applied. The problem is, puppet calls yum which successfully updates the package, but puppet then thinks the update has failed and hence doesn''t trigger the exec. Next

I''m rather new to puppet and I''ve been trying to get a module to work on the client servers. Right now I''m trying to get http://forge.puppetlabs.com/ghoneycutt/pam to run. When I try to run it I get these two errors: err: //pam/File[/etc/pam.d/sshd]: Failed to retrieve current state of resource: Could not retrieve information from source(s)

Hi, I just got my local yum repo setup so that I can use puppet to install packages... and it looks like something is not working. <snip> Tue Sep 19 02:13:05 PDT 2006 Puppet (notice): Starting configuration run Tue Sep 19 02:13:10 PDT 2006 //default/java/package=jdk/ensure (err): change from absent to latest failed: Could not update: Could not execute ''/usr/bin/yum -y install

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]

Hello, all. I am getting the following error on a couple of my puppet nodes when I run puppetd -v -o --no-daemonize --no-splay: err: Could not retrieve catalog: undefined method `-'' for #<XMLRPC::DateTime:0xb7c729e8> The error goes away if I add --ignorecache, but I''m not sure that''s quite the fix I''m hoping for. It will also go away if i remove my

I am new to using puppet and having trouble when updating an agent from a master which has a lot of files. Usually the updates work, but when there are a lot of files I get this error when running: sudo puppetd --test --server puppet.example.local --trace --debug >>> debug: Failed to load library ''rubygems'' for feature ''rubygems'' debug: Failed to load

Greetings. I am trying to set up a test puppet server in my environment to evaluate windows clients. On the server side, I am using puppet 2.7.14 (from the repos). I''m using the 2.7.14 windows 64 bit on the client (windows 2008 R2). I have another puppetmaster already using "puppet" hostname in DNS (running a very old version of puppet - can''t upgrade yet for various

Hi, I don''t know whether this is a ruby, puppet, or facter bug. The whole issue is one of the "really weird" ones. I first noticed the problem when working with puppet on a train, without any internet connection. In such situation, two problems appear: 1) Mildly annoying, frequent 2-second pauses followed by: Timed out seeking value for ipaddress I think this is

On Mon, Oct 02, 2017 at 04:38:01PM +0000, Wang, Wei W wrote: > On Sunday, October 1, 2017 11:19 AM, Michael S. Tsirkin wrote: > > On Sat, Sep 30, 2017 at 12:05:54PM +0800, Wei Wang wrote: > > > +static void ctrlq_send_cmd(struct virtio_balloon *vb, > > > + struct virtio_balloon_ctrlq_cmd *cmd, > > > + bool inbuf) > > > +{ > > > + struct

On Mon, Oct 02, 2017 at 04:38:01PM +0000, Wang, Wei W wrote: > On Sunday, October 1, 2017 11:19 AM, Michael S. Tsirkin wrote: > > On Sat, Sep 30, 2017 at 12:05:54PM +0800, Wei Wang wrote: > > > +static void ctrlq_send_cmd(struct virtio_balloon *vb, > > > + struct virtio_balloon_ctrlq_cmd *cmd, > > > + bool inbuf) > > > +{ > > > + struct