Hi,
I am getting error as attached while trying to run
puppet agent test --noop.
Could you please help here?
[root@pagent log]$ puppet agent --test --noop
Info: csr_attributes file loading from
/etc/puppetlabs/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for pagent.a
I'm getting the following error when I run this Puppet ssh code on Freebsd.
Note, the code runs fine on Linux. Any ideas?
Debug: Service[params::sshd_service](provider=freebsd): Could not find
params::sshd_service in /etc/rc.d
Debug: Service[params::sshd_service](provider=freebsd): Could not
This is extremely confusing. Yum helper should output the entire error.
On Thursday, August 25, 2011 8:10:09 PM UTC-6, LenR wrote:
>
> You can confirm that by trying to run yum outside of puppet.
>
> On Thu, Aug 25, 2011 at 8:42 AM, R.I.Pienaar
> > wrote:
>
>>
>>
>> - Original Message -
>
Hi,
On 01/15/2014 10:15 PM, Vassiliy Vins wrote:
> Any ideas, why? where to look at? thnx
honestly - no. But I do recommend to put all your manifests and files
into modules and serve them from there. Refrain from using 'import'.
I suppose that will work better for you.
HTH,
Felix
--
You recei
Hi!
I've created 2 files:
file *test.pp* with code :
class copy {
file {"testfile":
path => "/home/vassiliy/myfile",
source => "puppet:///mpoint/client1/testfile",
mode => '644'
}
}
and file site.pp wuth code:
import "test.pp"
node client1 {
include copy
}
in fileserver.conf was created sec
On 01/23/2013 01:34 PM, Pradeep Chhetri wrote:
> err:
> /Stage[main]//Node[tcp-handler-base]/Users::Sudoers[sudoers-file]/File[/etc/sudoers]/content:
> change from {md5}0897462d4d48fb9dedaafbaf91a9ceae to
> {md5}3298e302080d0e63a5697dd39556ca66 failed: Could not rename temporary
> file /etc/sudoer
Trying to understand how puppet reports errors
Example of why I am asking the question (on a test setup environment)
Created a base-1 node
Created 2 slave nodes that inherit from base-1
Let's call those slave1 and slave2
No errors. It all works.
Created a base-2 node
created a third slave that i
Hello,
I am trying to build puppet on Amazon VPC and am getting this error pretty
consistently.
>sudo puppet agent --test --server=ip-10-0-1-83 --waitforcert 60
err: Could not retrieve catalog from remote server: SSL_connect returned=1
errno=0 state=SSLv3 read server certificate B: certificat
Hello,
I've been using puppet fairly successfully on a 10 server cluster, so I
thought I had a decent idea of what I was doing.
However, we're starting a new project using a different virtualization
system ( XenServer ), and I can't seem to get puppet to accept my previous
conf file.
The erro
You can confirm that by trying to run yum outside of puppet.
On Thu, Aug 25, 2011 at 8:42 AM, R.I.Pienaar wrote:
>
>
> - Original Message -
>
> > plugins: fastestmirror
> > Could not retrieve mirrorlist
> > http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os
> > error was
> > 12:
- Original Message -
> plugins: fastestmirror
> Could not retrieve mirrorlist
> http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os
> error was
> 12: Timeout on
> http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os:
> (28, '')
Your machine cant talk to the mirror list.
Every time a client checks in with the puppetmaster, I receive the
following error in the client logs:
Wed Aug 24 19:55:27 + 2011 Puppet (notice): Starting Puppet client
version 0.25.5
Wed Aug 24 19:56:05 + 2011 Puppet (err): Could not prefetch
package provider 'yum': Execution of '/usr/bi
On Tue, Mar 1, 2011 at 08:00, cyrus wrote:
> Every now and then I get the following error on a Puppet run:
>
> Mon Feb 28 21:19:04 -0700 2011 Puppet (err): Could not retrieve
> catalog from remote server: Error 400 on SERVER: invalid value for
> Integer: "eNp1VtmS6jgSfZ+v0NTDRHczgHfAEf0ABgw2i9kNLx
Every now and then I get the following error on a Puppet run:
Mon Feb 28 21:19:04 -0700 2011 Puppet (err): Could not retrieve
catalog from remote server: Error 400 on SERVER: invalid value for
Integer: "eNp1VtmS6jgSfZ+v0NTDRHczgHfAEf0ABgw2i9kNLxXCFmDwhuSVrx/Zhirq
\n3h4CHFYqJWWmTp5DvV4H/
8bxMW8Gxyu
On Wed, Sep 29, 2010 at 10:15:39AM +0200, Daniel Maher wrote:
> Hello,
>
> cron { foo:
> command => "/bin/date > /tmp/foo",
> user=> root,
> minute => '2,7,12,17,22,27,32,37,42,47,52,57'
> }
>
You want
cron { foo:
command => "/bin/date > /tmp/foo",
user=> root,
minute => [
Try
minute => [2,7,12,17,22,27,32,37,42,47,52,57]
Matt
-- Sent from my Palm Pre
On Sep 29, 2010 4:15, Daniel Maher wrote:
Hello,
cron { foo:
command => "/bin/date > /tmp/foo",
user=> root,
minute => '2,7,12,17,22,27,32,37,42,47,52,57'
}
Which when parse
Hello,
cron { foo:
command => "/bin/date > /tmp/foo",
user=> root,
minute => '2,7,12,17,22,27,32,37,42,47,52,57'
}
Which when parsed by puppetd produces :
err: Could not run Puppet configuration client: Parameter minute failed:
2,7,12,17,22,27,32,37,42,47,52,57 is not a valid minute
I am implementing a scheme to manage our server configuration using
Puppet + git + rsync. I run Puppet on nodes as a cron job, and I am
getting errors as follows.
/usr/local/lib/site_ruby/1.8/puppet/type/component.rb:4: [BUG]
terminated node (0xb77054c4)
ruby 1.8.7 (2010-01-10 patchlevel
18 matches
Mail list logo