I did some test indeed but it was nog clear whatever both exec were executed
i have named.conf and in some case it need a reload and other cases a
restart
if it changes ...
but all good. thanks
On Fri, Sep 24, 2010 at 4:57 PM, Silviu Paragina wrote:
> notify and subscribe are somewhat the sam
notify and subscribe are somewhat the same thing, but specified in
different parts of the dependency.
The file resource should notify both execs and/or services, if it
doesn't it should be considered a bug and reported. ;)
You should try it just to be sure, it's usually faster than waiting for
Hello
simple question ... if 2 or more EXEC subcribes to a file and that file is
changed would
then all the EXECs be run ? or does it depend whatever the FILE notifies the
EXEC?
please bare in mind. I'm a 'new' puppet user, thanks
--
-ls
--
You received this message because you are subscribe
On Fri, Sep 24, 2010 at 12:34 PM, Nan Liu wrote:
> On Fri, Sep 24, 2010 at 11:20 AM, Nigel Kersten wrote:
>> eg the proposal is that if you don't specify the protocol, server
>> address, modules prefix, module name, it is assumed you are referring
>> to a file path relative to the 'files' subdire
On Fri, Sep 24, 2010 at 11:20 AM, Nigel Kersten wrote:
> eg the proposal is that if you don't specify the protocol, server
> address, modules prefix, module name, it is assumed you are referring
> to a file path relative to the 'files' subdirectory of the current
> module.
>
> If you wish to fully
It looks like adding the line "logoutput => true" in the exec definition
ends up sending this stdout to the centralized yaml log in the "message:"
field along a separate log with the standard "executed successfully"
summary.
--- !ruby/object:Puppet::Transaction::Report
host: puppetdclient.exampl
debugging your exec's for one. The exec may return something that is
functionally correct, but not what was intended.
Granted, I am brand new to puppet within the last month or so.
Conceptually, I'm sure that I don't have a very good handle on the "puppet
way" of doing things yet so I may not be
On Fri, Sep 24, 2010 at 11:29 AM, Tim Lank wrote:
> It would be great to have it configurable, so that it could be off by
> default for those that don't want it.
>
> I may be in the minority here, but having a surety of exactly what was
> executed and a knowledge of the output would be a good thin
It would be great to have it configurable, so that it could be off by
default for those that don't want it.
I may be in the minority here, but having a surety of exactly what was
executed and a knowledge of the output would be a good thing to me. Seems
that the ability to turn this on would be a
[cross-posting as I'd like to know whether my intuition about this
being the most common case is correct]
class foo {
file { "/etc/foo.conf":
source => "puppet:///modules/foo/foo.conf",
}
}
For me, every single one of my source specifications refers to a file
inside the current module.
On Fri, Sep 24, 2010 at 10:08 AM, Tim Lank wrote:
> Thanks. Can you elaborate on the puppet's reports? All I see are here:
> http://docs.puppetlabs.com/references/latest/report.html
>
> Is there one that reports on the stdout&stderr of the tasks the client
> performs? (and not in YAML)
I believ
On Fri, Sep 24, 2010 at 6:44 PM, Patrick wrote:
> Any chance you ran out of RAM? This happened to me and the swapping killed
> my performance. Webrick only runs one instance and you're now running 10
> instances which will use up much more RAM.
>
No, not a RAM related problem:
$ free -m
On Sep 24, 2010, at 10:08 AM, Tim Lank wrote:
> Thanks. Can you elaborate on the puppet's reports? All I see are here:
> http://docs.puppetlabs.com/references/latest/report.html
>
> Is there one that reports on the stdout&stderr of the tasks the client
> performs? (and not in YAML)
I'm almo
A sample report that is sent back in yaml format to the puppetmaster in
$vardir/puppet/reports/ looks like this:
--- !ruby/object:Puppet::Transaction::Report
host: puppetdclient.example.org
logs:
- !ruby/object:Puppet::Util::Log
file: /etc/puppet/manifests/templates.pp
level: !
By default, puppet looks for the hostname "puppet" for the server. You can
change that in puppet.conf, but it's usually better to just use DNS to always
point the the right box.
On Sep 24, 2010, at 10:04 AM, Kikanny wrote:
> Holy crap! That fixed it! Thank you so much for your help!
>
> On Se
Thanks for the lead. I remember this coming up around the same time as
3399 and have been able to avoid it entirely by simply not using
ensure. That said, this feels like a different issue.
On Sep 24, 1:22 pm, Bryan Horstmann-Allen
wrote:
>
> You may be running into this too:
>
--
You receive
+--
| On 2010-09-24 10:06:10, windowsrefund wrote:
|
| I'm running 0.25.4 patched with Martin's iptype (3399) fix. The zone
| type appears to be unable to create zones on Opensolaris nv_134. I'm
| thinking this is related
Thanks. Can you elaborate on the puppet's reports? All I see are here:
http://docs.puppetlabs.com/references/latest/report.html
Is there one that reports on the stdout&stderr of the tasks the client
performs? (and not in YAML)
The remote syslog would take some coding to cull together in a coher
I'm running 0.25.4 patched with Martin's iptype (3399) fix. The zone
type appears to be unable to create zones on Opensolaris nv_134. I'm
thinking this is related to the fact that nv_134 dropped support for
sparse zones. During my testing, I've tried to work around this by not
using the inherit att
Got this fixed with Patrick's help. I had to add puppet as an alias in
the /etc/hosts file. For more info:
http://groups.google.com/group/puppet-users/browse_thread/thread/61a66d600c16b6a6/e65f73003e5ec489#e65f73003e5ec489
On Sep 24, 11:08 am, Kikanny wrote:
> Hi. I'm using puppet 2.6.1 on ubuntu
Holy crap! That fixed it! Thank you so much for your help!
On Sep 24, 12:55 pm, Patrick wrote:
> Try putting puppet as an alias to your server in /etc/hosts (DNS is a better
> long term solution, but /etc/hosts is usually easier). The test it again.
> If that doesn't work, test it with ping t
On Sep 24, 2010, at 3:52 AM, Tim Lank wrote:
> puppet-users:
>
> I'm trying to find a way to obtain the stdout (and stderr) output from
> individual puppet client configuration runs. I'd like a central storage of
> this information if possible.
>
> In short, I'd like to know what the clien
Try putting puppet as an alias to your server in /etc/hosts (DNS is a better
long term solution, but /etc/hosts is usually easier). The test it again. If
that doesn't work, test it with ping to make sure "ping puppet" works.
On Sep 24, 2010, at 9:45 AM, Kikanny wrote:
> Yup. I get the follo
Yup. I get the following when I say ping puppet
ping: unknown host puppet
So I haven't defined puppet as a hostname somewhere or something?
On Sep 24, 12:38 pm, Patrick wrote:
> On Sep 24, 2010, at 5:34 AM, Kikanny wrote:
>
> > Thanks guys! I upgraded puppet from 0.25.4 to 2.6.1. Now when I try
On Sep 24, 2010, at 5:03 AM, jtournier wrote:
> Hi,
>
> i'm actually using puppet+mongrel for 630 servers. Performances are
> correct, but we need to reboot the puppetmaster every 3 hours because
> of memory problems :-(
>
> I decided to migrate to a configuration puppet+apache2+passanger on a
On Sep 24, 2010, at 5:34 AM, Kikanny wrote:
> Thanks guys! I upgraded puppet from 0.25.4 to 2.6.1. Now when I try to
> run puppetd on the same machine as puppemasterd, I get the following
> error message:
>
> err: Could not retrieve catalog from remote server: getaddrinfo: Name
> or service not
It can be turned off in the file resource itself. That means you can do it for
all files if you default that value (assuming you don't override if in a
resource).
Just put this in your site.pp. This code might have typos in it, but gets the
point across:
File {
filebucket => none,
}
We're not using a puppetmaster, so we're collecting info on runs via
syslog and puppet -v:
puppet -v /path/to/manifest.pp | logger -t puppet
And then we're using a splunk-alike to run ad-hon reports on the
logs.
* Tim Lank [2010/09/24 06:52]:
> I'm trying to find a way to obtain the stdout (a
Hi,
i'm actually using puppet+mongrel for 630 servers. Performances are
correct, but we need to reboot the puppetmaster every 3 hours because
of memory problems :-(
I decided to migrate to a configuration puppet+apache2+passanger on a
Ubuntu 10.04 system.
During my tests, everything was working
I accomplish this with a Environment variable. First you define
environments like PROD/PRE and then for each machine in an environment you
simply define that one variable (which for me is gather from an app
definition).
Than I setup a template for each environment.
-
puppet-users:
I'm trying to find a way to obtain the stdout (and stderr) output from
individual puppet client configuration runs. I'd like a central storage of
this information if possible.
In short, I'd like to know what the client exactly did with the
configuration that it was sent. Ideally
Hi group
I have the following definition:
package { 'samba-system-config':
ensure => absent,
before => Package['samba'],
}
package { 'samba-config-samba':
ensure => absent,
before => Package['samba'],
}
package
Thanks guys! I upgraded puppet from 0.25.4 to 2.6.1. Now when I try to
run puppetd on the same machine as puppemasterd, I get the following
error message:
err: Could not retrieve catalog from remote server: getaddrinfo: Name
or service not known
err: Could not retrieve catalog; skipping run
I'm n
Hi. I'm using puppet 2.6.1 on ubuntu lucid. I'm running puppetd and
puppetmasterd on the same machine. When I try to run the puppet agent,
I get the following error:
err: Could not retrieve catalog from remote server: getaddrinfo: Name
or service not known
err: Could not retrieve catalog; skipping
> Nexenta is using SMF like Solaris, not init.d like Linux.
You can modify the SMF service manifest to include the path. For
example:
See http://www.cuddletech.com/blog/pivot/entry.php?id=182
You can also do it with svccfg:
svccfg -s puppetma
On 09/23/2010 09:31 PM, R.I.Pienaar wrote:
I have two sites with a small number of machines at each. Each site is
functionally identical. I would like to set up a bunch of templates
for the various services at each site, with a handful of variables that
indicate which site the service is confi
devzero2000,
Thanks for your comment. Unless I am misunderstanding you are
suggesting the package statement is failing because the file does not
exist since the push fails... the push is working without any
problems. I can confirm the file exists in the required location.
Any other suggestions a
How does one turn of the file bucket feature for puppetd. I simply
don't want backup copies of the files. I deal with things like that in a
different way. I cannot see how to turn it off.
Marc
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
On 09/24/2010 02:57 PM, James Cammarata wrote:
That's the good thing about the way we do it - there's only one level of
scope: basezone. Every variable we define in all the classes along the way
is visible at that level, so we don't have to remember class names of all
the stuff in the middle.
Hello Chris,
For me it was just the path to the pid file from puppet's init
script. If I was you, I'd check the location of the lock file, and
the executable as well. Otherwise, you should try Jeff's suggestion.
Hope it helps.
Cheers,
Henry
On Sep 24, 3:32 am, Christian
wrote:
> Hi Henr
On Thu, Sep 23, 2010 at 12:34 PM, Ohad Levy
mailto:ohadl...@gmail.com>> wrote:
I can also recommend using frozen repos, with a testing cycle every time you
update them...
I a while ago I wrote a small web app[1] to collect all versions of all
packages across all of your hosts, you might find it
> This works exactly as it appears, and is a reasonable approach, though
> in my example scenario the scope is limited ; i would harbour concerns
> about tracking this though many levels of scope (as you have) without
> proper internal documentation. :)
That's the good thing about the way we
On 09/23/2010 09:06 PM, James Cammarata wrote:
Here's the way we do it, and it works very well for us, while avoiding
"globals" and the associated issues.
First, we have a "basezone" class, which is empty and really is just a
place holder (you'll see what this is for in a minute):
Thanks for
Hi,
You can use stuff like cobbler with puppet. The cobbler server has
all the repositories configured via its Web interface and the client
nodes will have the repositories that is present on the cobbler
server. You then only one system (cobbler server) that manages the
repository. The client ma
On 09/23/2010 08:40 PM, Mark Glossop wrote:
Er, unless I'm missing something folks, the OP wasn't asking about managing
/etc/resolv.conf - AFAICT /etc/resolv.conf was only used by the OP as an
example. How to manage that file in a one-off case it wasn't the objective.
So rehashing [paraphrasi
Hi Henry,
what was exactly wrong with your PID file? It seems i have a very
similar problem with the init.d puppetd stop start service. I checked
the PIDFILE path and the file was written correctly there. Also a
process id is written in that file.
Christian
On 23 Sep., 22:28, CraftyTech wrote:
46 matches
Mail list logo
