Hi Milind,
The critical difference here is that subscribe =>
File[$old_launch_agent_path] does NOT tell Puppet to watch for changes in
that file on disk.
Instead it will run that exec if Puppet itself is managing that resource
and makes changes to that resource. In other words,
File[$old_launch_a
*Background*
Puppet Newbie, trying to maintain some old puppet version on a box. The aim
is to unload an old program using it's old plist file and start new one.
*Problem*
I have following code in .pp file
$old_launch_agent_path =
"${home}/Library/LaunchAgents/com.company.program.plist"
Hi,
I've been struggling to debug this Puppet code for a couple of days now.
Perhaps it's something obvious but I just can't see it! Can anyone suggest
a debugging approach to get this working??
Why is it complaining every time that redis and Ruby are already at the
lastest versions?
More imp
All-
I'm using puppet (open source) 3.7.5 on our master (RHEL6.6, x86_64) and
all clients (RHEL 5.x, RHEL 6.x, RHEL 7.x).
I'm refreshing the hardware on our puppet master, and wanted to take the
opportunity to switch the master to RHEL 7 (and therefore new Ruby and
some ruby libraries). I'm st
Hello
I'm using Puppet Master 3.7 thru Apache/Passenger and I am facing this
compilation issue:
[1;31mError: Could not retrieve catalog from remote server: Error 400 on
SERVER: assert_type(): Expected type String[1, default] does not match actual:
Float on node (...)[0m
I have been looking
When I'm installing some package using puppet, let's say
package { "xxx":
ensure => present,
}
How do I include if it is running yum install, or apt-get when I'm pushing
this module on os level?
I want to have output like,
using yum install xx or something like that if it is
Hah, indeed. 3.5.0 has introduced some fun changes ;-) Thanks for your help!
On Tuesday, May 20, 2014 4:42:04 PM UTC-4, Christopher Wood wrote:
>
> Sorry, I've stayed at 3.4.3 so that the exciting things can happen to
> other people for a while.
>
> Were I debugging this, I'd check my data to ma
Sorry, I've stayed at 3.4.3 so that the exciting things can happen to other
people for a while.
Were I debugging this, I'd check my data to make sure that everything was the
same as from 3.4.2 and then try to reproduce using the simplest pp file I could
(then maybe file a bug).
On Tue, May 20,
Thanks for the tip, worked like a charm. Turns out I had some variables
with an uppercase first letter.
Got past that, but now I'm also dealing with something else unexpected.
Info: Retrieving pluginfacts
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 400 on
If you run your puppetmaster in the foreground with debug enabled it might tell
you more. (You'll have to stop the usual daemon first, and run it as the usual
user not root.)
puppet master --debug --no-daemonize 2>&1 | tee /var/tmp/pm1.log
Also use --config in there if you need it, of course.
Hey team,
Testing the waters with the new Future Parser functionality.
I've enabled it in [main] and [master] with parser = future, in my
puppet.conf, and am running puppet v3.5.1. Earlier versions of puppet
(namely, 3.4.2) worked fine with this setting enabled and the exact same
modules. I k
I am getting this error with a manifest run in puppet:
Feb 26 12:05:46 cwt1 puppet-master[30680]: Hiera eyaml backend: Unable to
decrypt hiera data. Do the keys match and are they the same as those used to
encrypt?
Unfortunately I get that same line with no additional details with "puppet
mast
I was wondering is there is a way to see what puppet things a node resource
is, such as classes it includes. Somehow in our environment it is picking
up a class that we did not specify.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To uns
I'm using the vcsrepo module to clone a git repo as a particular user, and
I'm getting a puzzling error:
Debug: Executing '/usr/bin/su myuser -c "/usr/local/bin/git clone
g...@git.myhostname.com:repos/myrepo.git /home/myuser/myrepo"'
Error: Execution of '/usr/bin/su myuser -c "/usr/local/bin/git
Debug output is sent to Apache error log, because of missing permissions to
write to the defined logdest.
So - bottom line - thanks for your reply, "--logdest" is necessary. Without
it debug output is (per default) not sent to /var/log/messages.
Am Mittwoch, 24. Juli 2013 09:59:40 UTC+2 schrieb
Did what you posted.
Strange thing happened: nothing appears in the specified logdest. Instead:
the (wanted) debug output it now sent to apache's error log!
I have no idea what's going on - but at least I have the output I was
looking for :-/
Thanks,
Christian
Am Mittwoch, 24. Juli 2013 09:42:
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"
wrote:
> Hi,
> I'm currently tryin
Hi,
I'm currently trying to debug a performance issue I'm having. Therefore I
would need "DEBUG" output. When using one puppetmaster process, this is
fairly easy by starting it like this:
> puppet master --no-daemonize --debug
Now I need to see this debug output when running puppetmaster th
Hello,
for the last couple of hours I've been trying to wrap my head around a
problem writing a custom facter plugin and I'm not getting it.
I'm trying to export LLDP neighbors as facter variables. I've already
found https://gist.github.com/1424959 and I'm quite happy with it, so
the issue is not
Pienaar is a seasoned puppet master I am sure he can help?
http://www.devco.net/archives/2009/08/19/tips_and_tricks_for_puppet_debugging.php
On Wed, Aug 29, 2012 at 10:10 PM, Douglas Garstang
wrote:
> So... how can I debug ruby code for custom functions? Putting a 'puts'
> in the ruby script does
So... how can I debug ruby code for custom functions? Putting a 'puts'
in the ruby script doesn't actually cause anything to go anywhere.
Doug
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@goo
On Thursday, August 23, 2012 12:07:18 PM UTC-5, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "ZJE" >
> > To: puppet...@googlegroups.com
> > Sent: Thursday, August 23, 2012 6:04:22 PM
> > Subject: [Puppet Users] debugg
- Original Message -
> From: "ZJE"
> To: puppet-users@googlegroups.com
> Sent: Thursday, August 23, 2012 6:04:22 PM
> Subject: [Puppet Users] debugging hiera
>
> Is there a way to check which data file(s) hiera is attempting to
> parse? I tried "pup
Is there a way to check which data file(s) hiera is attempting to parse? I
tried "puppet -d" with no luck. I'm wanting to select the variable
"dnsservers" based on a custom fact.
---
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find data item dnsservers
Hello All,
I'm trying to get LDAP Nodes working but it's failing on my puppet
master with "err: Could not find default node or by name with
'node.example.com, node.example, node,' on node node.example.com", the
client of course error's with "Could not retrieve catalog from remote
server:". A revie
But to answer your question, vncservers file is a little different . . .
there are two type of lines:
1. contains a space-separated list of port and usernames separated by
colons, e.g.:
VNCSERVERS="92:gmatz 44:wsmith"
2. contains arguments to be supplied to vncserver, with port number acting
as a
Stefan, thanks again for your reply. I'm just trying to get something
working, even if it doesn't actually do anything yet . . .
On Mon, Sep 19, 2011 at 1:48 PM, Stefan Schulte <
stefan.schu...@taunusstein.net> wrote:
> On Thu, Sep 15, 2011 at 04:22:45PM -0400, Guy Matz wrote:
> > hi! Does anyo
On Thu, Sep 15, 2011 at 04:22:45PM -0400, Guy Matz wrote:
> hi! Does anyone have any advice on debugging a new custom type?
>
> Any thoughts would be greatly appreciated . . .
>
> BTW, I'm getting the error:
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Could not r
With respect to this recent error, I'm guessing that the path to the pid
file doesn't exist. With the issue you've been having on the type/provider
itself, I believe that I found that the parsedfile provider generally has
name hard coded as the namevar. This may be a bit far fetched, but see if
cha
ok, i found out what pastebin is. All on my own!! :-) But puppet agent
--trace doesn't give me very much output. Only:
[root@gmatzpupnode ~]# puppet agent --trace
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/daemon.rb:47:in `create_pidfile'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/util.rb:38:in `
Scott,
Thanks for the reply!! Can you tell me what you mean by "just a
definition"? or point me to a doc?
Thanks a lot!
Guy
On Thu, Sep 15, 2011 at 8:46 PM, Scott Smith wrote:
> Hm, doesn't address your issue but you could probably do thus with just a
> definition instead of writing a new typ
Adrien,
Thanks for the reply. can you tell me what a pastebin is?
Thanks,
Guy
On Thu, Sep 15, 2011 at 6:50 PM, Adrien Thebo wrote:
> Could you provide the output of puppet agent --trace in a pastebin to
> accompany this?
>
> On Thu, Sep 15, 2011 at 1:22 PM, Guy Matz wrote:
>
>> hi! Does anyo
Hm, doesn't address your issue but you could probably do thus with just a
definition instead of writing a new type.
On Sep 15, 2011 1:22 PM, "Guy Matz" wrote:
> hi! Does anyone have any advice on debugging a new custom type?
>
> Any thoughts would be greatly appreciated . . .
>
> BTW, I'm getting
Could you provide the output of puppet agent --trace in a pastebin to
accompany this?
On Thu, Sep 15, 2011 at 1:22 PM, Guy Matz wrote:
> hi! Does anyone have any advice on debugging a new custom type?
>
> Any thoughts would be greatly appreciated . . .
>
> BTW, I'm getting the error:
> err: Cou
hi! Does anyone have any advice on debugging a new custom type?
Any thoughts would be greatly appreciated . . .
BTW, I'm getting the error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not render to pson: undefined method `merge' for []:Array
with some very rou
On Sat, Aug 21, 2010 at 4:19 PM, Jeff McCune wrote:
> On Sat, Aug 21, 2010 at 3:59 PM, Douglas Garstang
> wrote:
>> My site.pp:
>>
>> node default {
>> }
>
> Your empty node classification is entirely consistent with the terse
> agent output you pasted.
That's not what is happening. It is findin
On Sat, Aug 21, 2010 at 3:59 PM, Douglas Garstang
wrote:
> My site.pp:
>
> node default {
> }
Your empty node classification is entirely consistent with the terse
agent output you pasted.
On Fri, Aug 20, 2010 at 5:06 PM, Douglas Garstang
wrote:
> Aug 21 00:04:09 app01 puppet-agent[5975]: Starti
My site.pp:
# /etc/puppet/manifests/site.pp
import "definitions/*.pp"
import "modules/*.pp"
import "nodes/pax/*.pp"
#import "nodes/den/*.pp"
# The filebucket option allows for file backups to the server
filebucket { main: server => 'puppet' }
# Set global defaults - including backing up all fil
On Aug 20, 2010, at 5:06 PM, Douglas Garstang wrote:
>
> When I create a default node, the client logs:
>
> Aug 21 00:04:09 app01 puppet-agent[5975]: Starting Puppet client version 2.6.0
> Aug 21 00:04:10 app01 puppet-agent[5975]: Finished catalog run in 0.01 seconds
>
> which doesn't really
On Fri, Aug 20, 2010 at 4:09 PM, Christopher Johnston
wrote:
> Do you have a defaut node in nodes.pp?
>
> Sent from my iPhone
>
> On Aug 20, 2010, at 5:18 PM, Douglas Garstang wrote:
>
>> How do I debug errors with external nodes? When my client connects,
>> the following appears on the puppetmas
Do you have a defaut node in nodes.pp?
Sent from my iPhone
On Aug 20, 2010, at 5:18 PM, Douglas Garstang wrote:
> How do I debug errors with external nodes? When my client connects,
> the following appears on the puppetmaster when running in debug mode.
> It's not feasible to always be runnin
How do I debug errors with external nodes? When my client connects,
the following appears on the puppetmaster when running in debug mode.
It's not feasible to always be running the pupeptmaster in debug mode.
debug: importing '/etc/puppet/modules/yum/manifests/client.pp' in
environment production
Hello,
Alright, my puppetmaster configuration works without external nodes,
but I really need my external node script to work.
In my /etc/puppet/puppet.conf I have the following:
[main]
...
node_terminus = exec
external_nodes = /etc/puppet/tools/external_nodes.py
When running puppetm
Hi all,
How can I debug external node script errors? I cant seem to figure out what
is wrong with my script. It appears to work from the command line, but not
from puppet.
thanks,
Dan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
Puppet's been super for our installation of ~800 hosts, but I'm trying
to figure out why puppetrun isn't working for our us. Nodes work fine
as clients, but when I try to use puppetrun, everything looks fine on
the client side:
puppetd -d -v --no-daemonize gives:
...
notice: Finished catalog ru
Here is what I'd like to do:
I'd like to run puppet and see exactly what it would do, or what it
tried to do.
Do i need to run puppet or puppetd to get that to happen? I've been
trying the --verbose --parseonly options, but they have not been
working as I would expect...
--~--~-~--~
so I've found myself with a few reasons to need to debug
puppetd/puppetmasterd lately since we upgraded to 0.24.5
I've been doing this by basically throwing Puppet.notice/warning statements
into the code, which feels rather primitive...
How are people doing debugging? I've poked around a bit and
47 matches
Mail list logo
