> - --runinterval
>
> See http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference.
Thanks a lot!
--
Best regards, Pavel
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to t
Hello,
im trying to create a class that creates a cronjob that is run ever 15
minutes on 2 Servers.
These jobs should run at 15 and 45 on one server and on 0 and 30 on
the other server.
When i set a variable to '0,30' puppet complains that its not a valid
minute.
Is there a different approach in p
I'm adding tables to the storeconfigs database, to support my
storereports plugin, and would like some guidance on handling the
schema version.
First prize would see my database extensions applied as migrations.
But then ActiveRecord would want to bump the schema version.
Any ideas on how to han
Sorry folks, I'm replying to myself but here is what I found out. For
some reason running with shorter --runinterval gives me a warning on
the second and further update sessions with puppetmasterd:
"Other end went away; restarting connection and retrying."
But puppetmasterd is running for sure..
--runinterval is an option to be used in daemon mode (place it in
puppet.conf)
If you trigger puppet via cron, you can decide the interval at cron
level.
I personally would never place a runinterval value lesser than 30
minutes (3 mins is really extreme, if you need to apply changes
immediately u
Hello,
is still get the same error:
err: Could not create notifyMissingVideo: Parameter minute failed: 15,45 is
not a valid minute at /etc/puppet/manifests/classes/cronjobs.pp:119
warning: Not using cache on failed catalog
warning: Configuration could not be instantiated: Parameter minute failed:
You can do something like this
cron {
"getBroadcast":
command => "/server/www-production/www.server.de/cli/
getBroadcastFromFtp.php",
user=> root,
weekday => 3,
minute => $hostname ? {
server-vm1
Hi
> is still get the same error:
>
> err: Could not create notifyMissingVideo: Parameter minute failed: 15,45 is
> not a valid minute at /etc/puppet/manifests/classes/cronjobs.pp:119
> warning: Not using cache on failed catalog
> warning: Configuration could not be instantiated: Parameter minute
Tim Galyean wrote:
> The company I work for is getting ready to deploy a large puppet
> configuration into an existing environment. The majority of the
> servers that this will be deployed on are web servers, however some of
> them are configured different from the rest.
>
> We have a set of defa
Paul Gear wrote:
> Hi,
>
> I'm trying to create a squid url_regex ACL source file for various
> different sites. Each site needs a slightly different configuration, so
> my plan was to create the a bunch of files on the server, then drag them
> down and concatenate them into a single file on the
Is there a way to see if variables are defined?
if(defined($var)) {
} else {
fail("var is not defined")
}
I am getting the error:
err: Could not retrieve catalog: interning empty string at
/etc/puppet/modules-dev/puppet/manifests/init.pp:14 on node
viepcldx-e10.eu.boehringer.com
--~--~--
Hi!
just wondering if anyone here is running puppet using nginx
+passenger?! If yes, show me please you nginx.conf?
Thanks,
Kirill
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to th
I opened up 8140/tcp from the clients to the puppetmaster and haven't
had any issues pushing configurations and filebucketing. The clients
shouldn't need anything specific opened; the usual 'established'
traffic - which will already be allowed.
On Jul 1, 9:50 am, Jason Amato wrote:
> I have a
Le jeudi 02 juillet 2009 à 13:35 +0200, Dan Bode a écrit :
> Is there a way to see if variables are defined?
I use this syntax :
if $var {
# blah
}
else
{
# bluh
}
requires a not-too-old puppet
Nico.
signature.asc
Description: Ceci est une partie de message numériquement signé
On Thu, Jul 2, 2009 at 6:57 AM, David Schmitt wrote:
>
> Tim Galyean wrote:
> > The company I work for is getting ready to deploy a large puppet
> > configuration into an existing environment. The majority of the
> > servers that this will be deployed on are web servers, however some of
> > them
Hi
>> Is there a way to see if variables are defined?
>
> I use this syntax :
>
> if $var {
> # blah
> }
> else
> {
> # bluh
> }
>
> requires a not-too-old puppet
which will #bluh if $var is set to false as well, however you can do:
if ($var != '') {
# blah
}
else
{
# blu
Hi all,
my pre-commit script (copied from
http://www.reductivelabs.com/trac/puppet/wiki/PuppetVersionControl)
fails with error:
$ svn ci -m "nodo td007 a prod"
Sendingmanifests/nodes.pp
Transmitting file data .svn: Commit failed (details follow):
svn: 'pre-commit' hook failed with erro
On Thu, Jul 2, 2009 at 7:32 AM, Arnau Bria wrote:
>
> Hi all,
>
> my pre-commit script (copied from
> http://www.reductivelabs.com/trac/puppet/wiki/PuppetVersionControl)
> fails with error:
>
>
> $ svn ci -m "nodo td007 a prod"
> Sending manifests/nodes.pp
> Transmitting file data .svn: Co
On Thu, 2 Jul 2009 07:54:44 -0700
Nigel Kersten wrote:
Hi Nigel,
[...]
> FWIW, it's also just been patched recently:
>
> http://projects.reductivelabs.com/issues/2369
Bug is about Puppet 0.25, I'm on puppet-server-0.24.8-1.el5.1 x86_64.
It stopped working when I migrate my server from 386 to
On Thu, Jul 2, 2009 at 8:13 AM, Arnau Bria wrote:
>
> On Thu, 2 Jul 2009 07:54:44 -0700
> Nigel Kersten wrote:
>
> Hi Nigel,
>
> [...]
>> FWIW, it's also just been patched recently:
>>
>> http://projects.reductivelabs.com/issues/2369
>
> Bug is about Puppet 0.25, I'm on puppet-server-0.24.8-1.el5.
On Thu, 2 Jul 2009 08:21:41 -0700
Nigel Kersten wrote:
Hi,
[...]
> I'm not sure how your distro change may have affected your PATH, but
> the same patch will apply cleanly to 0.24.x as well if you wish to
> implement it.
ok, thanks.
> The bug also applies to 0.24.x, it's just that we're suppos
I'm about to deal with the same issue. This certainly isn't a Mac only
issue.
The way I see it a "puppetca --clean needs to be
executed on the server.
I figure either a puppet admin has to do it, which it labor intensive,
or a script can do it. I haven't figured out a way for the script t
On Thu, 2 Jul 2009 08:21:41 -0700
Nigel Kersten wrote:
> I'm not sure how your distro change may have affected your PATH, but
> the same patch will apply cleanly to 0.24.x as well if you wish to
> implement it.
worked fine.
Many thanks,
Arnau
--~--~-~--~~~---~--~
Well, the suggestion to have the client do it via a SSH command is a good
one and is working for me. Thanks to Michael and Nigel for pointing me in
this direction. I just need to formalize the process in my environment.
However (there is always a however). I am still a little shaky on the whole
ce
It appears the ssh keys would have to be for the puppet user on the
puppetmasterd server. How can I be assured that the key is not used
for evil?
Would I need to write a bunch of fugly stuff in my sshd_config to
limit what the puppet user can do via the ssh command? any examples?
---
Thank
On Thu, Jul 2, 2009 at 12:21 PM, Allan Marcus wrote:
> Would I need to write a bunch of fugly stuff in my sshd_config to
> limit what the puppet user can do via the ssh command? any examples?
You put the client's key in /root/.ssh/authorized_keys. All you need
to do is prepend this to it:
comma
nice!
Would this directive also stop scp, sftp, or anything else I can't
think of?
---
Thanks,
Allan Marcus
505-667-5666
On Jul 2, 2009, at 10:24 AM, Michael Semcheski wrote:
>
> On Thu, Jul 2, 2009 at 12:21 PM, Allan Marcus wrote:
>> Would I need to write a bunch of fugly stuff in my ssh
What about just running a "puppetca --clean --all" every night? Not
pretty, but would it work?
-Allan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to pupp
why not just create a new schema and have 1 to 1 relationships with
tables (if you are extending tables).
---
Thanks,
Allan Marcus
505-667-5666
On Jul 2, 2009, at 2:08 AM, Sheldon Hearn wrote:
>
> I'm adding tables to the storeconfigs database, to support my
> storereports plugin, and woul
from what I can tell, this is almost a great idea, except that by
using the command="/usr/sbin/puppetca", we would be ignoring any
command passed to the ssh session. The best I can figure there would
be no way to restrict the ssh session to just the puppetca command and
pass the certname t
On Thu, Jul 2, 2009 at 1:29 PM, Allan Marcus wrote:
> from what I can tell, this is almost a great idea, except that by
> using the command="/usr/sbin/puppetca", we would be ignoring any
> command passed to the ssh session. The best I can figure there would
> be no way to restrict the ssh session
I can't figure how to do this cleanly, here's the story:
I have an rsyslog class with a template generating /etc/rsyslog.conf
I have some other classes (namely, ossec::server, does what it says)
that need to influence what's going on inside rsyslog.conf, in
particular I want local0.* not to be l
Can you create fact that determines your condition (if ossec server is
to be or is installed I take it)? You can then refer to the fact in
your rsyslog code.
---
Thanks,
Allan Marcus
505-667-5666
On Jul 2, 2009, at 3:03 PM, niczar wrote:
>
> I can't figure how to do this cleanly, here's
Other solution would be to create a rsyslog type and call it in the
ossec::server class.
I have a sendmail class that has this syslog type:
syslog { "/var/log/maillog":
selector => "mail.debug",
ensure => present,
owner => root,
Udo Waechter wrote:
> Feedback welcome. Have fun.
> udo.
Hi Udo,
You might want to look into virtual resources instead of using all the
`if defined(Resource[whatever])' statements.
http://reductivelabs.com/trac/puppet/wiki/VirtualResources
-scott
--~--~-~--~~~---~
David Schmitt wrote:
> ...
>> I'd rather not distribute the entire directory from the server, since it
>> contains custom content for each node. Is there a way i can do this
>> with templates that include other files? (Or templates that are plain
>> text rather than .erb?) I'd really like to fi
36 matches
Mail list logo