Belated update on this one from another 'victim'...
Our CentOS and RHEL hosts don't have ruby-ldap, but we had the same problem,
with ldap-related assertion failures, including a couple of times outside of
a puppet run where ssh sessions would be terminated.
The fix: upgrade the version of nss_ld
I would also expect
Class["git"] -> Vcsrepo <| |>
to work, but it doesn't
Ronen
On Fri, May 27, 2011 at 12:49 AM, Ronen wrote:
> Hey,
>
> Im trying to use the puppet vcsrepo module, one of the issues I had
> with it is that its required to have a vcs installed before the plugin
> is used with
Hey,
Im trying to use the puppet vcsrepo module, one of the issues I had
with it is that its required to have a vcs installed before the plugin
is used within a class or else it fails with:
err: Could not run Puppet configuration client: Could not find a
default provider for vcsrepo
Iv solved t
Most of that is a documentation gap - you need to go under settings (in the
new version - far-right dropdown in new and old) and populate the various
forms there. Things like distributions, host groups, etc.. The #foreman
channel on freenode or the mailing list are both really good resources.
On T
On Thu, May 26, 2011 at 10:19 AM, Jake - USPS wrote:
> Maybe if you edit /foreman-location/config/settings.yaml and
> uncomment :modulepath and set it to your modulepath and then restart
> the webserver? This is just an educated guess as I use a standard
> location, but that seems like a good sta
Maybe if you edit /foreman-location/config/settings.yaml and
uncomment :modulepath and set it to your modulepath and then restart
the webserver? This is just an educated guess as I use a standard
location, but that seems like a good start. Otherwise, if you have
more questions about foreman you c
On May 26, 2011, at 1:14 PM, Douglas Garstang wrote:
> On Wed, May 25, 2011 at 1:19 PM, Brian Gupta wrote:
> Douglas,
>
> I have to concur with disconnect, now that we are using Foreman, many
> of the things we setup in the past to catch these things are now
> redundant. I don't know why you "do
On Wed, May 25, 2011 at 1:19 PM, Brian Gupta wrote:
> Douglas,
>
> I have to concur with disconnect, now that we are using Foreman, many
> of the things we setup in the past to catch these things are now
> redundant. I don't know why you "don't like" Foreman, but I have to
> say along with our ini
Thanks Patrick,
root@192:~# puppet master --no-verbose --manifest /root/tt.pp --compile
vm_0009_270e41c5-4242-416d-80ad-38dc85469076
invalid option: --no-verbose
Try 'puppet master --help'
Also tried --logdest option, but has no effect.
Thanks
-Yushu
+--
As promised yesterday, here are the results of our first planning
meeting.
Right now, we're loosely following a Scrum style of development. With
the current one-week iteration's backlog outlined below.
* #2128 - Allow arbitrary fact as node_name identifier
* #7224 - Bad english: hostname was n
On Thu, May 26, 2011 at 7:14 AM, elderdakkar wrote:
> And this
> results in one problem on the puppet side: it seems, that
> Nagios_service <<||>> locks the config file and the Nagios_host <<||>>
> process can't write its config to the same file.
Is it a requirement that all puppet-written nagios
On May 26, 2011, at 2:50 PM, M C wrote:
> Hi, I have a big problem with custom facts. I created a stub module with a
> "lib/facter" directory as stated in the official Puppet documentation.
> This is the output i get:
>
> # puppetd -t --pluginsync
> info: Retrieving plugin
> notice: /File[/var/
Hello
i'm managing nagios with exported ressources.
i have some @@nagios_host a lot of @@nagios_service ressources.
Collecting the ressouces itself works fine with Nagios_host <<||>> and
Nagios_service <<||>>.
BUT :D
i have a "special" nagios configuration layout: every host has its own
cfg file
On Wed, 25 May 2011 18:14:28 -0700, Jacob Helwig wrote:
>
> One of the largest challenges we've continually faced at Puppet labs is
> trying to find a good balance in splitting the development team's time
> between the (currently small amount of) commercial software, and the
> (much larger amount
Hi, I have a big problem with custom facts. I created a stub module with a
"lib/facter" directory as stated in the official Puppet documentation.
This is the output i get:
# puppetd -t --pluginsync
info: Retrieving plugin
notice: /File[/var/lib/puppet/lib]/mode: mode changed '755' to '775'
notice:
15 matches
Mail list logo