similar to: Could not request certificate: Neither PUB key nor PRIV key

I downloaded the latest version of puppet 2.6.0 today, and still can''t get parameterised classes to work. At least, I think it''s 2.6.0... the version number in the RPM spec file says 0.25.5. This simple example: /etc/puppet/manifests/nodes/pax/name01.pax.xxx.com.pp: node ''name01.pax.xxx.com'' { class { amodule::afunc: version => "1.0" } }

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

All, First attempt at running foreman. [pax] prov01 /usr/share/foreman/script:# ./server -e production => Booting WEBrick => Rails 2.3.5 application starting on http://0.0.0.0:3000 /usr/share/foreman/vendor/rails/activesupport/lib/active_support/dependencies.rb:443:in `old_load_missing_constant'': uninitialized constant Puppet::Rails (NameError) from

Hi, I had a 'domain' called APP03. I was performing auto snapshots each night using /usr/bin/virsh snapshot-create APP03 . I then wanted the domain to be called APP01 for clarity's sake, so I did virsh dumpxml APP03 > APP03.xml, edited the name to APP01 and changed the ID. I then did virsh define APP03.xml to get APP01. I have now realised that the qcow2 images are huge (1.1TB

----- Original Message ----- From: "Eric Blake" <eblake@redhat.com> To: "Adam King" <kinga@sghs.org.uk>, libvirt-users@redhat.com Sent: Thursday, August 21, 2014 3:17:09 AM Subject: Re: [libvirt-users] virsh snapshot On 08/20/2014 06:34 PM, Adam King wrote: > Hi, > [Can you convince your mailer to wrap long lines?] > > I had a 'domain' called

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

All, I have --confdir=/etc/puppet/common in my /etc/init.d/puppetmaster and /etc/init.d/puppet files, vardir set to /var/lib/puppet in /etc/puppet/common/puppet.conf, and yet, every time I run puppetca it creates /etc/puppet/ssl. Anyone know why? Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email

Hello, I've just tries make && make install on a fresh CVS tree, and get: llvm[0]: Installing include files /bin/sh: line 1: pax: command not found Two questions. 1. Why install process requires some nonstandard tool? Is it possible to get away without it. 2. autoconf/configure.ac has this: AC_PATH_PROG(PAX, [pax], [pax]) but Makefile.rules uses plain 'pax',

Vladimir, I believe I've corrected this situation with version 1.299 of Makefile.rules. It now only uses find and install to do the installation of the header files. pax isn't used any more. Hopefully this helps you. Reid. On Wed, 2005-02-16 at 04:18, Vladimir Prus wrote: > Hello, > I've just tries make && make install on a fresh CVS tree, and get: > >

I just upgraded puppet from 0.25.5 to 0.26, and I''m getting this: (/Stage[main]/Repo::Livegamer_software_base/Yumrepo[Livegamer-Software-Base]) Could not evaluate: File /etc/yum.conf does not contain a main section However, my /etc/yum.conf contains this. What''s wrong with that? Is puppet smoking crack? [main] cachedir=/var/cache/yum keepcache=0 debuglevel=2

Hello, I'm having some routing issue with my tinc setup. I'm running a fairly basic VPN configuration between two networks: ------- Site A: ------- --- tinc-up --- #!/bin/sh /sbin/ifconfig tap0 hs ether fe:fd:00:00:00:00 /sbin/ifconfig tap0 10.11.1.2 netmask 255.0.0.0 /sbin/ifconfig tap0 -arp ---- tinc.conf --- Name = orca Hostnames = no InterfaceIP = 63.108.71.7 KeyExpire =

On Wed, 2005-02-16 at 04:18, Vladimir Prus wrote: > Hello, > I've just tries make && make install on a fresh CVS tree, and get: > > llvm[0]: Installing include files > /bin/sh: line 1: pax: command not found > This is a known issue. We plan to make the makefiles not depend on pax. > Two questions. > > 1. Why install process requires some nonstandard

I've paraphrased the OS X installer developer's comments: there's a bug in Installer that is preventing the archive from working right. Below is the fix for the problem. First (obviously) run the installer. Since the executables are in the archive.pax.gz file in the installer package, first do a "show package contents" on the package file, then unstuff the enclosed

On Mon, 25 Oct 2004, zhou feng wrote: > I have some questions about LLVM > 1. I recently compiled LLVM on my X86 machine correctly. But when I use > the built LLVm compiling programs(in the getting started guide), I got > an warning saying can not find library "lc" (something like that). Yet > LLVM did yeild a execution native code and it runs correctly except with > a

hi, all I have some questions about LLVM 1. I recently compiled LLVM on my X86 machine correctly. But when I use the built LLVm compiling programs(in the getting started guide), I got an warning saying can not find library "lc" (something like that). Yet LLVM did yeild a execution native code and it runs correctly except with a waring saying something like "__main**"(I

I don''t know what it is with puppet''s certificates, but once again, they are behaving strangely. Client is reporting: debug: Using cached certificate for auth01.fre.livegamer.com /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb:166:in `certificate'' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb:227:in `wait_for_cert''

On 08/20/2014 06:34 PM, Adam King wrote: > Hi, [Can you convince your mailer to wrap long lines?] > > I had a 'domain' called APP03. I was performing auto snapshots each night using /usr/bin/virsh snapshot-create APP03 . This creates an internal snapshot, where the state of the snapshot is stored in the same qcow2 file as the current state. > I then wanted the domain to

On 08/21/2014 12:51 AM, Adam King wrote: > > ----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> > To: "Adam King" <kinga@sghs.org.uk>, libvirt-users@redhat.com > Sent: Thursday, August 21, 2014 3:17:09 AM > Subject: Re: [libvirt-users] virsh snapshot Including this blurb in the reply was overkill. > >> > I then

Hey All, [NOTE: crossposting between freebsd-current@, freebsd-security@, and freebsd-stable at . Please forgive me if crossposting is frowned upon.] Address Space Layout Randomization, or ASLR for short, is an exploit mitigation technology. It helps secure applications against low-level exploits. A popular secure implementation is known as PaX ASLR, which is a third-party patch for Linux. Our

Hey All, [NOTE: crossposting between freebsd-current@, freebsd-security@, and freebsd-stable at . Please forgive me if crossposting is frowned upon.] Address Space Layout Randomization, or ASLR for short, is an exploit mitigation technology. It helps secure applications against low-level exploits. A popular secure implementation is known as PaX ASLR, which is a third-party patch for Linux. Our