Hi,
If I understand your use case, you actually don't need to read the file in
java, you just need to place properties files under puppet control,
meaning, ask Puppet to either deploy the files (if missing) or ensure its
content is equal to the one on the Puppetmaster.
The real issue is that (up
Hi ,
I am sure by default puppetmaster has a inbuilt CA , but since i may have
more than 1 puppetmaster ( 1 each in each colo ) i need to disable to CA on
all other puppetmaster except for one which acts as both CA master . how
can i do this .
puppetmasterd --no-ca dint help as i was still
It works for me. thx
在 2013年2月24日星期日UTC-5下午6时03分51秒，Kpox写道：
I had to do 'yum clean all' to clear out the el5 packages erroneously
installed, before I could successfully install el6 puppet packages.
On Saturday, February 16, 2013 3:36:24 PM UTC+9, Arun kv wrote:
Hi,
I have faced the same
PuppetDB isn't an ENC. PuppetDB does, however, use Postgres (unless you
use the embedded database, which you shouldn't). Puppet Dashboard is an
ENC, but ironically, uses MySQL not Postgres.
Stuart,
Starting *another* ENC thread a day later isn't likely to get you many
more responses than the
I believe vagrant has gotten vmware support - so one can use it to disperse
vms in vmware esx servers.
It's not a free extension though: http://www.vagrantup.com/vmware#learn-more
But it's fairly simple powershell scripting to create vms - so one could
rather easily write a powershell script,
You can use concat fragments to specify the order of stanzas or lines.
Forgive the pseudo code below but you should be able to get the idea
concat::fragment { original_file:
order = 10,
}
concat::fragment { other_stuff:
order = 50,
}
concat::fragment { last_line:
On 12/04/2013 08:22 AM, Felix Frank wrote:
Hi,
I must be missing an essential piece here.
All three of your puppet stack nodes must be present in each instance,
no? The production master manages all three masters, normally. To change
monitoring of either of them, you update the production
Ah, so this is the meat of your problem. I think I get it now.
Tough call. Seeing as running multiple puppetdbs in parallel is not
really an expected scenario, there is quite possibly no way to share the
required resources between them.
Are nagios resources being actively removed from your
Hi Ryan,
Were you able to get something figured out regarding Nagios XI + Puppet? I
am also looking for a clean way to incorporate the two. So far the WebUI
for Nagios XI is disjointed, but convenient compared to config files for
some. But it is not as clear cut to me on how to automate
I am mostly using Puppet for Linux nodes, but I have started deploying it
on a handful of Windows nodes, but seem to run into SSL problems every time
on the initial deployment. I think I have hit this error on all three nodes
so far, but currently two are working and one is not. All three nodes
I'm looking to deploy several hundred ARM based machines in the near
future. At this point the puppet agent version available via apt (Debian 6)
is 2.6.
I tried adding the apt.puppetlabs.com repository but it won't install on my
systems as the CPU type isn't supported.
What are my options
I am working toward pitching a move from Open Source Puppet to Puppet
Enterprise.
One of the driving points is that Where-I-Work has just made a huge investment
in hardware/software in the form of a VMWare local cloud.
In trying to figure out how to plug my current Puppet setup into it, I
*using sudo:*
~ sudo puppet apply -e 'file { /tmp/adhoc: content = Written from
puppet on $hostname\n }'
Error: Cached facts for awsomepuppet failed: Could not find terminus
puppetdb for indirection facts
Error: Could not run: Could not retrieve facts for awsomepuppet: Could not
find
*using sudo:*
~ sudo puppet apply -e 'file { /tmp/adhoc: content = Written from
puppet on $hostname\n }'
Error: Cached facts for awsomepuppet failed: Could not find terminus
puppetdb for indirection facts
Error: Could not run: Could not retrieve facts for awsomepuppet: Could not
find
*using sudo:*
~ sudo puppet apply -e 'file { /tmp/adhoc: content = Written from
puppet on $hostname\n }'
Error: Cached facts for awsomepuppet failed: Could not find terminus
puppetdb for indirection facts
Error: Could not run: Could not retrieve facts for awsomepuppet: Could not
find
Resolved:
Found this resolution. Thanks Scott Mcintyre
---
Ran into the following error when setting up one of our new internal puppet
servers with puppetdb.
Oct 13 11:40:34 puppet puppet-master[27735]: Could not configure routes
from /etc/puppet/routes.yaml: Could not find
I did `yum update` on my puppet server about a week ago. Up to that point I
had puppet and puppetdb running on the same machine. Since the update
puppetdb doesn't appear to be listening on port 8081 anymore.
When I run `puppet agent --test` on a client I get this error:
err: Could not
I responded to this in ask, but I'll answer here also.
In the file /etc/puppetdb/conf.d/jetty.ini, the settings ssl-host and
ssl-port must be set to listen on the SSL port (8081). However, if
your ssl certs aren't yet configured this may fail for you. Usually
puppetdb-ssl-setup is a good way to
I used 'puppetdb-ssl-setup' (after removing the ssl folder) to no avail.
(sorry about cross posting - I thought I had removed the 'ask' entry)
On Thursday, December 5, 2013 12:25:24 PM UTC-8, Ken Barber wrote:
I responded to this in ask, but I'll answer here also.
In the file
Can you show your jetty.ini? And the results of running
puppetdb-ssl-setup ... the more information the better in these kinds
of cases.
Also - is PuppetDB listening to port 8080?
On Thu, Dec 5, 2013 at 9:15 PM, Jon Yeargers ethrbu...@gmail.com wrote:
I used 'puppetdb-ssl-setup' (after removing
Hello,
I have a puppetmaster/agent setup. Puppet master is Ubuntu 12.04 and puppet
agent is ubuntu 12.04
When I do puppet agent --test, I get some error message like below. I have
checked and fog and ruby are the same versions on both boxes. In fact
though, I dont have any requirement for
Setting the 'ssl_host=' param to 0.0.0.0 turned the trick (so to speak). I
kept trying variations on what the ssl cert was created for.
Thank you for clearing this up for me.
On Thursday, December 5, 2013 1:17:51 PM UTC-8, Ken Barber wrote:
Can you show your jetty.ini? And the results of
I was going over a related post in puppet developers (unfortunately seems
to wrong place for my questions )and my questions are pasted on the top of
the chain.
Hi Chris,
I exactly have the same problem.
(This is actually two questions):
Running 'puppet agent --test' on a 1Ghz ARM based (Debian 6) fanless PC.
It's pretty common to see the 'catalog run' take 120-300 seconds. Is this
typical?
Second (and possibly related): when I do a 'puppet agent --test (--noop)' I
get this set of messages:
Dan,
Thanks for the detailed question. What version of Puppet agent do you have
installed?
On Thu, Dec 5, 2013 at 9:29 AM, d...@n-cube.org wrote:
I am mostly using Puppet for Linux nodes, but I have started deploying it
on a handful of Windows nodes, but seem to run into SSL problems every
On Wed, Dec 4, 2013 at 9:04 PM, Jeff Bachtel
jbach...@bericotechnologies.com wrote:
Is there a way that I'm not seeing to make scheduled_task create a task
that runs on Windows startup?
I don't believe this is an option with the current provider for
scheduled_task.
Unrelated (but too
I use NagiosXI and Puppet and have had some success in developing some
interoperability without sacrificing the controls of the gui. My
environment consists of linux hosts running puppet and a myriad of windows
and netowrking devices which were all configured in NagiosXI via the gui.
After I got puppetdb working I was looking about at the various bits of
data available. Looking at the 'nodes' option I was suprised to see this:
report_timestamp : null
for every node. They all have this for their puppet.conf:
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
Well, I can execute this with for individual module via *puppet apply
--binder true ...* I haven't been able to do this successfully on my
vagrant box. I found out that vagrant use --detailed-exitcode option with
puppet apply, which interfere with *--binder true* option. I have to set*
binder
https://projects.puppetlabs.com/issues/14368#change-101086
Summary:
(We dont need to improve our public documentation, because people can go
BUY documentation for puppet)
I can understand changing it to low priority or something.
But *Rejecting* this issue?
For a supposedly free, open source
On 2013-06-12 1:30, chengkai liang wrote:
Well, I can execute this with for individual module via *puppet apply
--binder true ...* I haven't been able to do this successfully on my
vagrant box. I found out that vagrant use --detailed-exitcode option
with puppet apply, which interfere with
Seems to me more like:
After a year we still haven't found time for this. Let's keep our bug
database manageable but only keeping the stuff we can do within a
reasonable time or the bug reports that contain some troubleshooting effort
we don't want to redo.
Quite a reasonable approach I'd say.
32 matches
Mail list logo
