Hello,
maybe this is a bug. But if puppetd cannot find host puppet ( default
hostname ) it will try to get certificate and load goes automatically
to 100%. I am starting puppetd with parameter -w 0 and this is in my
syslog:
Feb 16 10:49:54 myhostname puppetd[2853]: Could not find server
puppet:
Your puppet client is tryng to contact a server named "puppet". Find
out where it is using puppet as the server name in the configs and
replace it with the hostname of your puppetmaster and you should be set.
-Jason
On Feb 16, 2009, at 3:08 AM, Andy wrote:
>
> Hello,
>
> maybe this is a bug.
Hi all,
I've got a problem and I can't figure out why. Here is the error
message
warning: Not using cache on failed catalog
warning: Configuration could not be instantiated: Could not find
dependency Exec[modprobebonding] for File[/etc/sysconfig/network-
scripts/ifcfg-bond0] at /file/xy.
And be
Hi there,
Does any one present on this list live around wellington NZ?
Martial
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.co
On Mon, Feb 16, 2009 at 3:31 PM, babatoko wrote:
> Could not find dependency Exec[modprobebonding]
> ...
> exec { "modprobe bonding":
You'll want to avoid using spaces as the names/titles of classes,
files, exec statements, etc. etc.
--
Jake Paulus
jakepau...@gmail.com
--~--~-~--
And nope, it doesn't:
Feb 17 04:29:03 wrath puppetd[20155]: [ID 702911 daemon.warning] Configuration
could not be instantiated: Could not find schedule nightly at
/staging/puppet/common/modules/deadly/manifests/init.pp:15
Feb 17 04:46:51 wrath puppetd[20449]: [ID 702911 daemon.warning] Configur
I've got a directory (a webapps directory for a Java app server) that
I'd like to ensure all of the contents are world readable. As puppet
is not really suitable for application deployment, I'd like to manage
the permissions of this directory and all of it's contents. Something
like:
find . -ty
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A new Facter release is available - 1.5.4.
This is a maintenance release that will be the last of the 1.5.x branch.
It combines a number of fixes, a new fact - physicalprocessorcount,
and support for flavours of Oracle Linux.
Full list of change
On Feb 7, 2009, at 11:35 AM, peter wrote:
>
> hello,
> I installed puppet-server package for centos 5.2.
>
> when I tried to start it, it now gets the error:
> Starting puppetmaster: Certificate retrieval failed: Invalid pattern
> install
> [FAILED]
>
> how to fix it?
I've never seen or heard of
On Feb 10, 2009, at 5:34 AM, Arnau Bria wrote:
>
> Hi all,
>
> I've followed http://reductivelabs.com/trac/puppet/wiki/UsingMongrel
> for configuring my puppet with mongrel.
>
> Al seems to work fine, except that, after a reinstall of 40 nodes
> atone
> time, I got many kind of errors like:
>
>
On Feb 10, 2009, at 4:25 AM, Keith Edmunds wrote:
>
> I'm just starting a roll out of Puppet and I'm seeing a problem on
> maybe
> 25% of client nodes. The symptoms are that the clients stop
> updating. In
> the Puppetmaster log, I'm seeing things like:
>
> Feb 9 20:10:23 vs4 puppetmasterd[1
On Feb 12, 2009, at 4:43 AM, Trevor Vaughan wrote:
>
> The speed benefits of Ruby 1.9 are amazing overall and I was wondering
> if Puppet, as it stands, is deliberately compatible.
>
> I've tried digging through the mailing lists and might just be missing
> it, if so, I apologize for the oversigh
On Feb 14, 2009, at 8:16 PM, Eric Gerlach wrote:
>
> I'm having a bit of an odd problem with exported resources. It
> seems like if
> an resource is already in the stored configs database, then a host
> checks in an
> exports that resource, then it doesn't get exported.
>
> Deleting storedco
On Feb 16, 2009, at 5:39 PM, Matt McLeod wrote:
>
> And nope, it doesn't:
>
> Feb 17 04:29:03 wrath puppetd[20155]: [ID 702911 daemon.warning]
> Configuration could not be instantiated: Could not find schedule
> nightly at /staging/puppet/common/modules/deadly/manifests/init.pp:15
> Feb 17 04
Luke Kanies wrote:
> I've not seen this before, and I just verified that finding a schedule
> shouldn't be at all related to the order in which resources get
> instantiated on the client or anything silly like that.
>
> This is just happening on a single node?
It's happened on the two nodes
file {
"/top/level/dir":
owner => user,
group => usergroup,
ensure => directory,
mode => "0664", #whatever
recurse => true;
}
something like that may work
If that doesn't then you should be able to use an exec of your find
commands and onlyif mtime/md5 of the dir tree but that may take a
whil
I Have scheduling working quite well for many different OS's.
I'm using something like that ina class inhertied by all machines.
class host-base::schedule {
# maintance schedule, run only once a day, between 2-4
schedule { maint:
range => "2 - 4",
period => daily,
r
The one that's failing is defined in a module which is included
by the node definition. It is, essentially:
schedule {blah: ...}
define {blahpkg: ..., schedule=>blah}
class blahclass {
blahpkg{somepackage}
}
in the module 'blahclass' and then in the node defintion file:
node somenode inherit
18 matches
Mail list logo
