We would also be interested in an alternative server to rsync from.
Best regards,
Andreas Paul
On Monday, April 24, 2017 at 2:46:24 PM UTC+2, Chris Kuehl wrote:
>
> Is there an alternative server we can rsync from? We've been using ftpsync
> (the recommended tool <https://www.
Hi,
shameless self-plug: you could try out my r10k fork
https://github.com/xorpaul/g10k
It does the almost all operations in parallel which can speed up your
environment deployment dramatically.
Already compiled binary blobs can be found here:
https://github.com/xorpaul/g10k/releases
On Tue
Found a Puppet Server bug which sounds to me like the source of my problem:
https://tickets.puppetlabs.com/browse/SERVER-346
On Thursday, July 2, 2015 at 6:36:52 PM UTC+2, Andreas Paul wrote:
>
> Hello there,
>
> I'm trying to bootstrap my new Puppet 4 environment with
Hello there,
I'm trying to bootstrap my new Puppet 4 environment with an external CA as
described here:
https://docs.puppetlabs.com/puppet/latest/reference/config_ssl_external_ca.html#option-2-single-intermediate-ca
Here is the important part of the config:
webserver.conf:
> ...
> ssl-cert : /
[pool-3-thread-1] [cli.services] Finished
database garbage collection
On Friday, January 2, 2015 6:19:06 PM UTC+1, Andreas Paul wrote:
>
> Hi Wyatt,
>
> - Have you recently upgraded PuppetDB, or changed any other part of your
> Puppet/PuppetDB installation?
> No, we haven
>
> That should help get the ball rolling -- to my knowledge we haven't seen
> this before.
>
> Thanks,
> Wyatt
>
>
> On 01/02/2015 06:44 AM, Andreas Paul wrote:
> > Hi there,
> >
> > the PuppetDB garbage collection fails sometimes after 5 minutes
Hi there,
the PuppetDB garbage collection fails sometimes after 5 minutes and
sometimes after 2-3 hours with the following error message:
2014-12-29 12:12:57,312 INFO [pool-3-thread-1] [cli.services] Starting
database garbage collection
2014-12-29 16:31:39,106 ERROR [pool-3-thread-1] [cli.serv
I have the same problem, but the other way around :)
My puppet client only uses the node definitions in the environment specific
site.pp
Anyway you can debug the master with:
puppet master --verbose --no-daemonize --debug
On Wednesday, September 26, 2012 9:55:21 AM UTC+2, Axel Bock wrote:
>
>
Basically what John said, either the tomcat module doesn't offer a class
"tomcat" or you installed the module outside of your puppetmaster
modulepath.
You can look up where your puppetmaster will look for modules by running:
# puppet config print modulepath
/etc/puppet/modules:/usr/share/puppet/
ok up 'RedHat.yaml' first, since
> 'operatingsystem' is listed first in the hierarchy.
>
> The hiera gems are installed:
> [root@puppet-dev specifications]# gem list hiera
>
> *** LOCAL GEMS ***
>
> hiera (0.3.0)
> hiera-puppet (0.3.0)
>
>
>
:29 PM UTC+2, Luke Baker wrote:
>
> Hmm, I moved the config file to /etc/puppet/ but my client is still giving
> me grief.
>
> On Tuesday, July 10, 2012 9:15:49 AM UTC-5, Andreas Paul wrote:
>>
>> AFAIK hiera-puppet looks for
>> */etc/puppet/hiera.yaml*
>> wh
Of course the file you want to deploy with puppet must be readable by the
puppetmaster.
Do you use Apache Passenger, Nginx or webbrick?
If you use Apache Passenger:
The file /etc/puppet/files/server_file must be readable by the user, who
owns the /etc/puppet/rack/config.ru file.
On Tuesday, Ju
AFAIK hiera-puppet looks for
*/etc/puppet/hiera.yaml*
whereas the hiera CLI looks for
*/etc/hiera.yaml*
You can still use the CLI by specifying the config file
hiera -c /etc/puppet/hiera.yaml sshpackages environment=development
or just symlink it :)
On Tuesday, July 10, 2012 3:31:43 PM UTC+2, Lu
Did you generate the necessary certs to access the puppetmaster facts with
the dashboard?
http://docs.puppetlabs.com/dashboard/manual/1.2/configuring.html#generating-certs-and-connecting-to-the-puppet-master
On Thursday, July 5, 2012 3:52:15 AM UTC+2, Dennis Jacobfeuerborn wrote:
>
> Hi,
> I've
I'm not sure if he wants to monitor the puppet runs on the clients.
Maybe he wants to monitor if the the puppetmaster is available or not, so
/usr/lib/nagios/plugins/check_tcp -H YOURPUPPETMASTER -p 8140
TCP OK - 0.000 second response time on port
8140|time=0.000464s;;;0.00;10.00
or
/usr/
Ah, exactly what I needed!
Thanks!
On Monday, April 30, 2012 5:32:26 PM UTC+2, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "Andreas Paul"
> > To: puppet-users@googlegroups.com
> > Sent: Monday, April 30, 2012 2:52:00 PM
> &g
Hello there,
I need to access the following hiera data in a script:
$ hiera -c /etc/puppet/hiera.yaml tomcats environment=development
line=intra3
["tc7_test1", "tc7_test8"]
or
$ hiera -c /etc/puppet/hiera.yaml apache_port environment=development
line=intra3 name=tc7_test1
81
The example on http
My previous understanding on what hiera is trying to accomplish was simply
wrong.
I moved all data to hiera and am now a happy camper :)
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.go
I need to create a XML file for our Nagios server.
This XML file needs to contain all Tomcats on this server, which are
created with a parameterized puppet ressource.
What I need is something like this:
test1
test2
from these ressources
example::ressource { "test1": }
example::ressource {
The problem was that I thought github.com/puppetlabs/hiera was the hiera
puppet module.
It worked after I copied the correct puppet module
github.com/puppetlabs/hiera-puppet to the modules folder.
On Wednesday, April 4, 2012 5:26:45 PM UTC+2, Andreas Paul wrote:
>
> Hi there,
>
&
Hi there,
for some reason I can't use hiera functions in my manifests.
Here are the relevant config files:
cat /etc/puppet/hiera.yaml
:hierarchy:
- %{environment}
- common
:backends:
- yaml
- puppet
:yaml:
:datadir: '/etc/puppet/environments/%{environment}/hieradata'
:puppet:
he worker list. I thought there was a better/simpler way to do this.
On Friday, March 23, 2012 2:05:51 PM UTC+1, jcbollinger wrote:
>
>
>
> On Mar 22, 10:15 am, Andreas Paul wrote:
> > Is there a way to look up which nodes share that specific module or
> class?
>
&g
kWorkerProperty worker.<%= name %>.host=<%= ipA %>
JkWorkerProperty worker.<%= name %>.host=<%= ipB %>
Which is just wrong, I know.
Maybe there is another even simpler way to do it.
Best regards,
Andreas Paul
--
You received this message because you are subscribed to
I don't know if there is a warning tag in puppet by default, but I would
try using the specific error tag in your tagmail.conf
err: m...@email.tld
You could also try setting
all: m...@email.tld
to test if your puppetmaster can send report emails at all.
P.S. I had to restart my puppetmaster (ap
Hi there,
I currently get my puppet run reports via email, can I somehow get the
actual diff of the changed files in those emails?
I'd like to get the exact same output as if I'm running puppetd -t on the
client.
Is that possible?
Best regards,
Andreas Paul
--
You received th
Hi there,
I think that the customer case studies make excellent propaganda material:
http://puppetlabs.com/customers/case-studies/
Take a look at them, but maybe puppetlabs employees have some powerpoint
presentations you need and are willing to share. :)
--
You received this message because y
Hi,
we are currently managing our puppet modules with one SVN workspace for each
admin.
The post commit hook script updates /etc/puppet/ directory and triggers the
puppet kick of the correct server.
The problem we have with this solution is that sometimes there are many
small checkins to one c
After a very serious discussion with myself :)
I found a solution/workaround which my colleagues are satisfied with.
Because we want to use puppet in push only mode, every admin has to login to
the puppetmaster anyway.
So instead of trying to get a post commit hook working from our subversion
s
Do you suggest calling that rsync in the post commit hook?
That is not possible as the svn hook script is run by a httpd user without
any permissions and granting him any permission just for that hook script
would be hard to justify.
--
You received this message because you are subscribed to th
That would, in the worst case, delay the visibility of the changes for 5
minutes.
Even running that cronjob every minute would dictate the admin to wait 1
minute before kicking the puppet clients. Otherwise we can't be sure if the
client would use the latest config.
--
You received this messag
Hello there,
I'm trying to get SVN working with puppet, but what I need to do is a remote
svn update on the puppetmaster server, so that puppet uses the latest
configuration.
The puppetlabs wiki page uses a simple svn update /etc/puppet in the
post-commit hook script, but that implies that the
Hello there,
I'm trying to replace our current sed and rsync configuration
management solution and we are used to have static and dynamic
configuration files in the same folder.
After creating a prototype with puppet I defined the static files as
modules and the dynamic files as templates.
What
ON file in the Puppet Dashboard
> directory. At the very least, you should be able to go into the Puppet
> Dashboard directory, confirm that it's v1.0.4, and then run
> `./script/server -e production` to get it running again until you
> figure out what's going on with your w
Disregard my question, for some reason I already had an old version of
puppet and facter on my new SLES11 machines.
After removing the old version it worked flawlessly.
On Oct 21, 3:29 pm, Andreas Paul wrote:
> I installed the 2.6.2 puppet and facter 1.5.8 gems and tried to run
> puppet,
I installed the 2.6.2 puppet and facter 1.5.8 gems and tried to run
puppet, but it failed with the following message:
err: Could not run Puppet configuration client: Could not retrieve
local facts: uninitialized constant Facter::IPAddress
Then I tried running facter alone:
# facter
/usr/lib64/rub
I get the following error:
Database isn't the current migration version: expected 20100726070117,
got 20100916183948 You must either run 'rake db:migrate' or set
environmental variable NO_MIGRATION_CHECK
I upgraded from 1.0.4rc2 and did run 'rake RAILS_ENV=production
db:migrate' before restarting
36 matches
Mail list logo