'
from /opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:608:in
`start'
On Thu, Sep 29, 2022 at 7:05 PM JB SysAdmin wrote:
> Thanks so much for answering! I certainly restarted puppet and puppetdb
> services (using systemctl). Restarted the node, as well. The issue is that
&
ssl/ca/ca_crt.pem) I don't know if that matters; It
is present in the foreman-answers.yaml.
There are newly generated items in all those places, but I can't figure out
what remains broken...
On Wednesday, September 28, 2022 at 8:03:52 PM UTC-4 daf...@gmail.com wrote:
> On 28.09.2
All:
I bid you good fortune.
On inherited a Foreman 1.19 / Puppet (5.5.6) presence, the original, 5-year
cert (CA) expired. I found out while trying to run puppet agent on a new
node.
There was no complete documented series of steps for this combo of
versions; the one who set up the presence de
I've been unable to get puppet installed on SLES 11.2 by the recommended method.
I've set up the repo at
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP2/,
but when I do "zypper install puppet" I get multiple dependency errors, e.g.:
Problem: nothing provides rubyg
Is there a way to view the resource relationship tree for a class (or
all classes)? I'd like an easy way for our admins to see things like
what classes refer to the same resource, which classes require another
class, etc. thanks
--
You received this message because you are subscribed to the Goo
This also vexes me, I also would love to use 'all_tags', but it's not
consistent. The issues is best described in the following bug, I
believe:
http://projects.puppetlabs.com/issues/3049
On Jun 30, 10:59 am, Dan Carley wrote:
> On 30 June 2010 18:40, CraftyTech wrote:
>
> > Hello All,
>
> >
looks like a typo/omission. Add:
commands :zypper => "/usr/bin/zypper"
to zypper.rb
or change :rub to :zypper would probably be the right thing to do?
On Apr 14, 2:59 am, Alpar wrote:
> Hi,
>
> I found the zypper provider mentioned on this list in another thread,
> but it failes with the
I've setup something where I put a grants file in the data directory
of each database:
remotefile {"$db_datadir/grants":
mode => 500,
source => "db/$db_name/data/grants",
require => File["${db_datadir}"],
notify => Exec["refresh_${db_name}"]
I see your point...after looking at the classes.txt file it does have
a lot more than what I want. I'm in particular looking for classes
that affect app deployment/management for the engineers so they can
easily see what is under puppet control...they don't need to need to
see the myriad of OS lev
I'm looking for an easy way to include the list of applied classes on
a host in something like /etc/motd. using an .erb template would do
the trick if I an array exists that has all the classes in it?
Hopefully it's available?
thanks
--
You received this message because you are subscribed to th
I'm sure it's somewhere but I can't find it...
I want to put the list of applied classes for a host in /etc/
motd...I'm hoping there's an array that has this? Some way to get the
information in an .erb
thanks!
--
You received this message because you are subscribed to the Google Groups
"Puppe
In my case the developer may not have root access
On Jan 19, 12:39 pm, Trevor Vaughan wrote:
> As this would generally be a manual change, I would use 'chattr +i' on
> Linux systems.
>
> Trevor
>
>
>
>
>
> On Tue, Jan 19, 2010 at 3:14 PM, jb wrote:
&
The scenario is this: developer needs, in an emergency situation, to
edit a file that is normally under puppet control (it's a conf file
for our java servlet engine). I'm not around to help out, he may not
have root.
I'd fully want/expect this to generate a puppet error, at least in my
case, tho
I'd like others to have the option to temporarily disable puppet from
modify a file or directory...something along the lines of:
./something.conf.lock
causes
./something.conf
to NOT be modified by puppet for as long the lock file exists
it'd also be nice to be able to disable an entire directo
Thank you Silviu - I just went through a 0.25.2 installation using
passenger 2.2.8 just yesterday and had the same issues which started
this thread:
puppetmasterd[29797]: Puppet Server (Rack): Internal Server Error:
Unhandled Exception: "Host app3.chassis1 10.x.x.x) not authorized to
call fileserv
In case anybody else has found their --noop flag (and probably others)
ignored with 24.6 here's why, and while this may be a known issue I
didn't find it in the discussion board after some searching so wanted
to save others..
I can't remember why it was done, but at some point I made
puppetd.conf
It doesn't seem to work from me, bombing out if the template specified
first doesn't exist. you'd expect it to gracefully ignore and try the
next...this a bug? running puppet-0.24.6-1.1
On Jul 23, 12:31 pm, Udo Waechter
wrote:
> hmmm, right after sending the provious mail, I realised somethin
howdy,
I assign specific applications to machines via a class. Each
application has its own log files that need to be managed by our
logging system (splunk, for those who are familiar with it). This
basically entails adding a line to a config file. How do you do
this? ie, manage the config
18 matches
Mail list logo
