On 30 Jul 2013 18:57, Paul Pham m...@paulpham.net wrote:
Do most folks who use puppet not use yum? Or are most people okay with
letting puppet install dependencies automagically?
Puppet has different package providers and I use the appropriate one
depending on what I want it to do.
If I want
When having problems like this it is often a good idea to shut down the
Apache web server and run:
# puppet master --debug
from a console instead. If that works then your Puppet setup is okay and
you should look at your web server and passenger config.
- Keith
On 18 Jul 2013 20:21, Forrie
I believe the --debug in config.ru sends output to syslog so either look in
/var/log/messages (or similar) or specify a log destination filename like:
ARGV --logdest /var/log/puppet/puppet-master.log
- Keith
On 23 Jul 2013 09:15, Christian Flamm christian.le.fl...@gmail.com
wrote:
Hi,
Perhaps try removing the final trailing comma after enable = false. Some
Puppet versions have a problem with this.
- Keith
On 24 Jun 2013 01:11, Manoj Bhola mbhol...@gmail.com wrote:
Hi,
I hope someone can help.
I have created a custom class module which updates a configuration file.
http://docs.puppetlabs.com/puppet/2.7/reference/modules_publishing.html
Is there a toolkit generally used to develop/manage puppet modules?
I've been playing with the modules on puppetlabs and have a question about
the packaging used.
It appears many of the developers are using some tools /
This could be an issue with time on the host being inconsistent. Is it
configured to use NTP to sync against a time server?
- Keith
On 11 Jun 2013 05:06, Luke Vidler luke.vid...@gmail.com wrote:
Me Three, same versions and errors - Did you guys work out how to fix it
yet?
On Thursday,
!
On Tuesday, June 4, 2013 2:09:48 PM UTC-6, Keith Burdis wrote:
You could set a custom role fact on node1 and node2 with the value
webserver and then use the role fact in your Hiera hierarchy.
For example using facter.d on on node1 and node2:
# cd /etc/facter/facts.d
# echo 'role
You could set a custom role fact on node1 and node2 with the value
webserver and then use the role fact in your Hiera hierarchy.
For example using facter.d on on node1 and node2:
# cd /etc/facter/facts.d
# echo 'role: webserver' custom_facts.yaml
# facter -p role
role = webserver
and on the
Are you running into the Socket.gethostbyname(Socket.gethostname) issue
pointed out by Wil Cooley a few days ago?
https://groups.google.com/forum/?fromgroups#!topic/puppet-dev/z09Nkk18tREhttps://groups.google.com/forum/?fromgroups#!topic/puppet-dev/z09Nkk18tRE
If so there is potential
With PuppetDB 1.1 it is now possible to use exported resources when
running puppet apply [1], though of course this still means having a
central PuppetDB. This is not relevant for a single machine setup though,
as you say.
- Keith
[1]
Two options come to mind:
1) Install the JDK and Tomcat products from tarball into separate
directories for each version which is what I do with
erwbgy/sunjdkhttp://forge.puppetlabs.com/erwbgy/sunjdk
and erwbgy/tomcat http://forge.puppetlabs.com/erwbgy/tomcat
2) Create custom packages for each
This is often an issue with the underlying yum command being executed.
Try running:
# puppet apply --verbose --debug --execute 'package
{yum-plugin-versionlock: ensure = latest}'
to see what is happening.
On my host this shows that '/usr/bin/yum -d 0 -e 0 -y install
yum-plugin-versionlock' is
Perhaps try:
$ echo 'syntax on' ~/.vimrc
- Keith
On 16 May 2013 15:27, Balasubramaniam Natarajan bala150...@gmail.comwrote:
Hi
I am trying to install vim-puppet for syntax highlight of puppet manifest
file. I first installed vim-puppet and then vim. Then I ran
vim-addon-manager -w
'
notice: Finished catalog run in 3.42 seconds
On Thursday, May 16, 2013 10:12:33 AM UTC-4, Keith Burdis wrote:
This is often an issue with the underlying yum command being executed.
Try running:
# puppet apply --verbose --debug --execute 'package
{yum-plugin-versionlock: ensure = latest
Perhaps try:
# puppet apply --execute 'include manual'
- Keith
On 16 May 2013 21:40, Nev neva...@gmail.com wrote:
I need to be able to run a certain class ONLY when it is called
manually from the client.
I created a class named manual and can run it from the client like
this:
puppet
, Keith Burdis wrote:
Perhaps try:
# puppet apply --execute 'include manual'
- Keith
On 16 May 2013 21:40, Nev nev...@gmail.com wrote:
I need to be able to run a certain class ONLY when it is called
manually from the client.
I created a class named manual and can run it from the client
You should be able to cluster Tomcat without using multicast by having a
static members list with TCP pings to check the cluster nodes. You could of
course use exported resources to create the static members list.
Not sure about Glassfish but I'd expect it to be possible to do something
similar
I don't believe there is any existing Puppet functionality that does this
though the Capabilities
armaturehttps://github.com/puppetlabs/armatures/blob/master/arm-6.capabilities/capabilities.md
discusses
a potential future solution.
You might find
Is the time set correctly on these hosts? If not then I'd suggest
synchronising them with an NTP time server like those at pool.NTP.org.
- Keith
On 22 Apr 2013 17:54, Przemek p.slodkiew...@gmail.com wrote:
Hi,
I'm rookie puppet user and I trying to establish simple Server-Client
connection
Perhaps try using the str2bool function from puppetlabs-stdlib [1].
- Keith
[1] https://github.com/puppetlabs/puppetlabs-stdlib
On 17 Apr 2013 18:09, Matthias Saou matth...@saou.eu wrote:
Hi,
I'm trying to clean up some manifests by moving class parameters which
I change globally to Hiera
From that page: External facts are only available in Facter 1.7 and later.
I expect you need to either upgrade or install the stdlib module.
- Keith
On 13 Apr 2013 15:18, Larry Fast lfast1...@gmail.com wrote:
I'm trying to load custom facts via /etc/facter/facts.d/* according to
Try running:
# yum-config-manager --enable rhel-6-server-optional-rpms
- Keith
On 10 April 2013 10:04, Yusup Ashrap aph...@gmail.com wrote:
I have having the same problem with install puppet on redhat 6.2.
--
You received this message because you are subscribed to the Google Groups
The permissions of /tmp should be 1777 so that all users can create files
but the sticky bit is set. Setting the sticky bit ensures that files and
directories under /tmp can only be renamed or deleted by the user that owns
them.
- Keith
On 3 April 2013 00:41, Kubes
If you use hiera try Craig Dunn's
hiera-gpghttp://www.craigdunn.org/2011/10/secret-variables-in-puppet-with-hiera-and-gpg/
.
- Keith
On 3 April 2013 14:18, jim stra...@gmail.com wrote:
Hello all
I mainly use Puppet for managing windows hosts, and what to know they best
way to either
...@bravo5.org wrote:
On Mar 28, 2013, at 10:56 AM, Keith Burdis ke...@burdis.org wrote:
Today I started using Jordan Sissel's fpm [1] to build multiple rpms for
each tomcat instance with a different prefix - something like:
This seems like a good opportunity to use CATALINA_BASE for multiple
Yes, perhaps try:
# chown -R puppet:puppet /etc/puppet /var/lib/puppet
- Keith
On 28 Mar 2013 05:27, Nick Fagerlund nick.fagerl...@puppetlabs.com
wrote:
On Wednesday, March 27, 2013 6:22:05 PM UTC-7, Philip Brown wrote:
nope, nothing.
I tried your suggestion of explicitly setting it.
On 28 Mar 2013 01:22, Philip Brown p...@bolthole.com wrote:
On Wed, Mar 27, 2013 at 2:10 PM, Nick Fagerlund
nick.fagerl...@puppetlabs.com wrote:
...
to keith's suggestion, of
Also you can use the hiera command-line utility [1] to test - for
example:
# hiera --debug philcheck::value
I have been using the file, exec approach for my modules but transferring
big zip or tar files is a pain because they take up space, as you say, and
sometimes the transfer times out when the files are really big.
Today I started using Jordan Sissel's fpm [1] to build multiple rpms for
each tomcat
Perhaps try:
# ln -sf /etc/puppet/hiera.yaml /etc/hiera.yaml
Also you can use the hiera command-line utility [1] to test - for example:
# hiera --debug philcheck::value
- Keith
[1] http://docs.puppetlabs.com/hiera/1/command_line.html
On 27 March 2013 18:29, Philip Brown
You need to enable the optional repository.
On 27 Mar 2013 21:38, T.J. Yang tjyang2...@gmail.com wrote:
Hi,
I followed puppetlab procedure to install open source version of puppet
agent 3.x.
It works for CentOS 6.4 but not RHEL 6.4, anyone has pointer where I
missed ?
[root@mon04 ~]# yum
The agent only writes logs under /var/log/puppet if you run it as a service
- for example using:
$ service puppet once
(Note that due to buffering it may take a few seconds for entries to appear
in puppet.log.)
There are a number of existing issues that could be related to your problem
guide. Is there
a way to let puppetlabs know that there is a problem during the evaluation
period?
On Sat, Mar 23, 2013 at 4:18 AM, Keith Burdis ke...@burdis.org wrote:
Puppet runs fine on RHEL 6.2. It looks like your auth.conf is missing
some entries. Do you perhaps have
as per the PE 2.7 quickstart guide. Is there
a way to let puppetlabs know that there is a problem during the evaluation
period?
On Sat, Mar 23, 2013 at 4:18 AM, Keith Burdis ke...@burdis.org wrote:
Puppet runs fine on RHEL 6.2. It looks like your auth.conf is missing
some entries. Do you
Puppet runs fine on RHEL 6.2. It looks like your auth.conf is missing some
entries. Do you perhaps have an auth.conf.rpmnew you need to move into
place?
- Keith
Hi All,
I am trying to follow the documentation at this link:
http://docs.puppetlabs.com/pe/latest/quick_start.html
When I get to
Good news. I'd encourage people to file bug or feature requests on GitHub
if they run into problems or have ideas for improvements. Tutorial
documentation is coming Real Soon Now (TM) :-)
- Keith
On 22 March 2013 15:46, John Smith burnncrash...@gmail.com wrote:
thank you very much!!!
Try adding an entry for your hostname in /etc/hosts - for example:
127.0.0.1 server1
- Keith
On 22 Mar 2013 08:38, bibop554 bibop...@gmail.com wrote:
Hi,
I am using puppet 2.6.2-5 in debian 6.0.3.
I would like to execute puppet in standalone, with puppet apply, but
puppet does not
burnncrash...@gmail.com wrote:
On Friday, March 22, 2013 8:54:50 AM UTC-7, Keith Burdis wrote:
Good news. I'd encourage people to file bug or feature requests on
GitHub if they run into problems or have ideas for improvements. Tutorial
documentation is coming Real Soon Now (TM) :-)
- Keith
Hi Andy,
When trying to implement something like Craig Dunn's roles and profiles
pattern with hiera I ended up with:
:hierarchy:
- %{hostname}
- roles/%{role}
- profiles/%{software1}
- profiles/%{software2}
- profiles/%{software3}
- profiles/%{software4}
- profiles/%{software5}
-
The Puppet master runs as the puppet user so try:
# chown -R puppet:puppet /etc/puppet
- Keith
On 13 March 2013 19:42, Mike Canty cantyma...@yahoo.com wrote:
Successfully installed Puppet 3.1.1 under Centos 6. When trying to start
puppet as the root user, puppet generates the following
:25 AM, Keith Burdis wrote:
2) Adding refreshonly = true to the exec.
3) Remove the creates and subscribe from the exec.
The subscribe is actually fine, but yes - the 'creates' needs to go in
order to allow repeated execution.
Note that this can be considered unclean manifest design
The master runs as the puppet user not root so try:
# chown -R puppet:puppet /etc/puppet
- Keith
On 14 Mar 2013 15:09, Mike Canty cantyma...@yahoo.com wrote:
I am running Centos 6 and was able to install Puppet 3.1.1. However, when
trying to run puppet, as root, for the first time, I
Hi Byron,
Some suggestions:
1) Hiera comes with a handy command-line tool to query your config so try
using that first. What does running:
# hiera -h system::augeas
return? If it returns the ntp hash then your hiera config is good.
2) If not, are /etc/hiera.yaml and /etc/puppet/hiera.yaml
The great thing about Puppet is that it gives you lots of different ways to
manage your host data. Personally I am a big fan of hiera and its YAML
backend because it is simple for non-Puppet users to understand and allows
them to manage the config without having to write or modify Puppet
The Puppet agent tries to connect to the master using the hostname 'puppet'
by default so one solution may be to add an /etc/hosts entry for 'puppet'
with the correct IP for your Puppet master:
* # echo “your puppet master ip puppet” /etc/hosts*
*
*
For example:*
*
# echo 10.0.67.1 puppet
Perhaps try:
1) Adding a notify = Exec['unpack_archive'] to the file resource.
2) Adding refreshonly = true to the exec.
3) Remove the creates and subscribe from the exec.
That way the exec will only be called when the file changes.
- Keith
On 14 Mar 2013 07:56, dirk.heinri...@altum.de
There is no user type declared in the users class. Perhaps move the user
type call out of the adm_user define.
On 9 Mar 2013 17:57, mike miguelc...@gmail.com wrote:
Hi guys,
I need help with the class, i have created my class (users) but when i
apply from agent apers the next error:
I am running 3.1.0 and hiera booleans appear to be working fine.
- Keith
On 6 March 2013 09:15, Richard Clark rich...@fohnet.co.uk wrote:
On Wed, Mar 06, 2013 at 01:29:29PM +1000, Peter Brown wrote:
Getting booleans from hiera to puppet is not currently not functioning
like
you would
Perhaps Puppet is not using the puppet.conf file you think it is. Try
running:
# puppet agent --configprint confdir
- Keith
On 4 Mar 2013 20:49, JGonza1 jgonza1...@gmail.com wrote:
I also made the changes below in the puppet.conf file to tell puppet where
to look for the the modules and
Ok so Puppet is reading /etc/puppet/puppet.conf. The timestamp on this file
shows is hasn't been changed for a few days though.
Is the output of:
# puppet agent --configprint moduledir
# puppet agent --configprint manifestdir
on the master what you expect?
Perhaps you have a permissions /
What section of /etc/puppet/puppet.conf is your moduledir etc set in? This
should be in [main] or [master] - see the 'Config Blocks' section in the
docs.
Alternatively perhaps the master has not actually been restarted somehow
and is still using the old config.
- Keith
On 4 Mar 2013 21:54,
Have you looked at using hiera [1] for your configuration? It is very good
for cascading defaults with more specific config at the top of the
hierarchy and the least specific at the bottom. It is part of Puppet 3 and
an add on for 2.7.
- Keith
[1]
Since it would apply to more than just permissions perhaps
'source_attributes' would be better?
- Keith
On 9 Feb 2013 01:21, Jakov Sosic jso...@srce.hr wrote:
On 02/08/2013 06:46 PM, Josh Cooper wrote:
Hi John,
On Fri, Feb 8, 2013 at 9:22 AM, jcbollinger
john.bollin...@stjude.org wrote:
If you are running the master under mod_passenger then you can
set 'LogLevel debug'.
On 3 February 2013 04:29, Schofield dbschofi...@gmail.com wrote:
I would like to see the SSL handshake between the master and agent. How
do I enable this?
--
You received this message because you are
I can't check at the moment but shouldn't that be 'mco puppet runonce fqdn=
puppet.example.net' ?
- Keith
On 1 February 2013 11:23, snlsingha...@gmail.com wrote:
Hey i have installed mcollective server cleint and puppet master, agent
successfully. I have also installed puppet agent plugin.
Try running the Puppet agent manually with 'puppet agent --test --verbose'.
The output should indicate what is preventing it from starting.
- Keith
On 31 Jan 2013 09:44, Mamta Garg itsmamta.b...@gmail.com wrote:
Please find now.
On Wed, Jan 30, 2013 at 4:49 PM, Nikola Petrov
Run it where you were getting the error you posted.
- Keith
On 31 Jan 2013 09:59, Mamta Garg itsmamta.b...@gmail.com wrote:
So this command i should run it on master machine?
On Thu, Jan 31, 2013 at 4:53 AM, Keith Burdis ke...@burdis.org wrote:
Try running the Puppet agent manually
as in screeshot but All nodes are still showing
unresponsive.
On Thu, Jan 31, 2013 at 5:05 AM, Keith Burdis ke...@burdis.org wrote:
Run it where you were getting the error you posted.
- Keith
On 31 Jan 2013 09:59, Mamta Garg itsmamta.b...@gmail.com wrote:
So this command i should run
Perhaps 'puppet node' is what you're looking for?
$ sudo puppet node status $(facter fqdn)
[sudo] password for kburdis:
lnxmgt-01.domain
Currently active
Last catalog: 2013-01-31T14:57:22.518Z
Last facts: 2013-01-31T14:57:14.732Z
To get more info you'll can install PuppetDB and that's as simple
If you like the style guide the you'll like puppet-lint -
https://github.com/rodjek/puppet-lint
- Keith
On 31 January 2013 16:15, Kodiak Firesmith kfiresm...@gmail.com wrote:
I figured this out via taking another look at the style guide. This is
resolved.
Changed this to this:
class
-5, Keith Burdis wrote:
If you like the style guide the you'll like puppet-lint -
https://github.com/rodjek/**puppet-linthttps://github.com/rodjek/puppet-lint
- Keith
On 31 January 2013 16:15, Kodiak Firesmith kfire...@gmail.com wrote:
I figured this out via taking another look
Thank you both for sharing details of your Vagrant setups. This will
certainly save me some time.
- Keith
On 30 Jan 2013 07:01, Felipe Salum fsa...@gmail.com wrote:
I have done something similar, installing puppet master, puppetdb and a
few nodes for testing, everything via vagrant.
The puppet master runs as the puppet user so try 'chown -R puppet:puppet
/etc/puppet /var/log/puppet /var/lib/puppet'.
- Keith
On 30 Jan 2013 18:39, Raymond Regnier raymondregn...@gmail.com wrote:
Hey all, this is my first post. I did try and search the group first
before posting :)
I've
that.. so now its owned by puppet:puppet -rw-rw however it still
gives me the same errror
On Wednesday, January 30, 2013 1:49:36 PM UTC-5, Keith Burdis wrote:
The puppet master runs as the puppet user so try 'chown -R puppet:puppet
/etc/puppet /var/log/puppet /var/lib/puppet'.
- Keith
On 30
a service puppetmaster status
it states puppet dead but pid file exists. I manually delete the pid file
and it does the same thing
On Wednesday, January 30, 2013 2:00:27 PM UTC-5, Keith Burdis wrote:
Try 'service puppetmaster restart' and see if you get any logs under
/var/logs/puppet
Here's one way:
1) Install the erwbgy/system module:
# puppet module install erwbgy/system
2) Configure a custom fact using facter_dot_d for the default gateway:
include system::schedules
$config = {
'default_route' = {
'type' = 'script',
'value' = #!/bin/bash\nprintf
You can set the default values to undef and then the standard user type
will use its defaults (if any). It usually makes sense to default the
ensure parameter to 'present' though because if it is undef then nothing
will happen:
define site::user (
$ensure = 'present',
When you specify include sysctl then Puppet includes the sysctl class and
this class only ensures that the /etc/sysctl.conf file exists:
class sysctl {
file { /etc/sysctl.conf:
ensure = present,
owner = root,
group = root,
mode = 0644,
}
}
which it
67 matches
Mail list logo
