On Wed, Apr 21, 2010 at 8:42 PM, Sukh Khehra wrote:
> Forgot to mention that I am running version puppet-0.25.4-1 on both
> sides on centos 5.4.
>
> -Original Message-
> From: Sukh Khehra
> Sent: Wednesday, April 21, 2010 8:39 PM
> To: 'puppet-users@googlegroups.com'
> Subject: variable i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/04/10 1:37 PM, Jeremy Hansen wrote:
> We're seeing this periodically from client machines:
>
> Apr 21 16:31:09 blumfrub puppetd[31154]: (/File[/var/lib/puppet/lib])
> Failed to generate additional resources using 'eval_generate': Error 400
> on
We're seeing this periodically from client machines:
Apr 21 16:31:09 blumfrub puppetd[31154]: (/File[/var/lib/puppet/lib]) Failed to
generate additional resources using 'eval_generate': Error 400 on SERVER:
undefined method `collect' for nil:NilClass
http://projects.reductivelabs.com/issues/286
On Apr 21, 2010, at 7:34 PM, Ohad Levy wrote:
> Brian,
>
> Login to your second puppetmaster and try the following:
> backup your /var/lib/puppet and /etc/puppet dirs
> stop your puppetmaster and puppetd processes
> rm -rf /var/lib/puppet/ssl
> edit your /etc/puppet.conf
> under the [main] secti
Forgot to mention that I am running version puppet-0.25.4-1 on both
sides on centos 5.4.
-Original Message-
From: Sukh Khehra
Sent: Wednesday, April 21, 2010 8:39 PM
To: 'puppet-users@googlegroups.com'
Subject: variable interpolation weirdness
Can someone please explain what's happening
Can someone please explain what's happening here? Let me know if you
need more info. Thanks in advance for your time.
I have a module called abc. This is the init.pp for that module.
###
$ cat modules/production/abc/manifests/init.pp
# Puppet Module: abc
#
class abc {
packag
puppet will re-parse its config file if it is changing, so usually no need
to restart the daemon.
saying that, imho, its much better to run puppet via a cron.
Ohad
On Thu, Apr 22, 2010 at 3:48 AM, Patrick wrote:
>
> On Apr 21, 2010, at 12:01 PM, Kim Gert Nielsen wrote:
>
> >
> > On Apr 21, 2010
Brian,
Login to your second puppetmaster and try the following:
- backup your /var/lib/puppet and /etc/puppet dirs
- stop your puppetmaster and puppetd processes
- rm -rf /var/lib/puppet/ssl
- edit your /etc/puppet.conf
- under the [main] section add:
ca = false
ca_server =
-
I wonder if there is any way to hack to turn off ssl because I need to
really get this to work. We are running puppet w/i our internal
network so I can give up security / ssl to get it to work. Maybe I
need to modify puppetmaster client / server to just pass a "true" at
this pt.
On Apr 21, 7:07
On Apr 21, 2010, at 3:59 PM, Brian Lam wrote:
> I apologized ahead of time if this post shouldn't go here but I having
> been knocking my heading for the last two days trying to get over the
> following error while trying to "clone" my primary puppetmasterd
> because we have outgrown one puppetmas
I apologized ahead of time if this post shouldn't go here but I having
been knocking my heading for the last two days trying to get over the
following error while trying to "clone" my primary puppetmasterd
because we have outgrown one puppetmasterd setup.
I have basically set up a 2nd instance of
Seph, Ken,
Thanks for your patches on this module ! I love the --comment idea. I
will definitely pull this asap.
> You shouldn't need the 'before' in the 'iptables' resource. Not quite
> sure why its not executing, but how about this ...
I do know why it's not executing: unfortunately this ipta
Hi Ken,
Were those 200GB populated with 50GB+ of data?
Yes it can be mounted with the same options on the command line fine. Also
if the EBS vol is already mounted it still hangs when it gets to it (remount
thingy). iostat shows high I/O on the volume when this happens, so I
thought it was due
I'm using the resolv.conf pattern described here:
http://projects.puppetlabs.com/projects/puppet/wiki/Resolv_Conf_Patterns
In my node templates I have a "base" class that does all of the
housekeeping chores to set up a basic server (install preferred
editors, subversion, etc.). I added a call to
Hehehe - cool bananas. Happy to merge - just one small problem.
I'm guessing that syntax is how you persist rules in Ubuntu? I run
Ubuntu at work now but I'm a newb:
/sbin/iptables-save > /etc/iptables.rules
Using that will break fedora - so we need a facter if/then. Do you
have the time to add
I Bliss:
On Wednesday 21 April 2010 20:33:26 Bill Weiss wrote:
> All,
>
> I'm just getting started with puppet, so excuse any lack of vocabulary
> in this email.
>
> I've got a server (CentOS 5.4) running with a little more than the
> example puppet configuration. Importantly, I'm using the suppl
Ken writes:
> What scope did you define that code in? Try it in your /etc/puppet/
> manifests/site.pp file.
I tried it in both the iptables module and the site.pp file. But, I like
your module more.
> http://github.com/kbarber/puppet-iptables
>
> Its a mod to the camptocamp code. It persists ip
All,
I'm just getting started with puppet, so excuse any lack of vocabulary
in this email.
I've got a server (CentOS 5.4) running with a little more than the
example puppet configuration. Importantly, I'm using the supplied
auth.conf, and the relevant portion looks like this:
path ~ ^/catalo
On Apr 21, 2010, at 12:01 PM, Kim Gert Nielsen wrote:
>
> On Apr 21, 2010, at 8:50 PM, Patrick wrote:
>
>>
>> Is restarting puppet using itself supported? I had always assumed it wasn't.
>>
>
> I got the example long time ago from example42 and they just added a service
> for it. It has wo
On Apr 21, 2010, at 5:51 AM, Ken wrote:
> More data is needed I think.
>
> Can you run puppetd --no-daemonize --debug in 'screen' or by piping
> the output somewhere? It may give you a better clue.
First, it think your saying that the client is crashing or hanging.
My advice would be to do th
On Apr 21, 2010, at 8:50 PM, Patrick wrote:
>
> Is restarting puppet using itself supported? I had always assumed it wasn't.
>
I got the example long time ago from example42 and they just added a service
for it. It has worked before but if its unsupported then it might be the
problem I have
That was it... I kept forgetting the client. So stupid. I kept
thinking it was based on the server. My bad.
THANK YOU FOR THE QUICK RESPONSE!
I am back in operation again... Yay!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this
On Apr 21, 2010, at 11:43 AM, Kim Gert Nielsen wrote:
>
> On Apr 21, 2010, at 2:51 PM, Ken wrote:
>
>> More data is needed I think.
>>
>> Can you run puppetd --no-daemonize --debug in 'screen' or by piping
>> the output somewhere? It may give you a better clue.
>>
>
> debug: Service[puppet](
nevermind .. someone actually made a change so it restartet just as it should
leavning my screen killed
/Kim
On Apr 21, 2010, at 8:43 PM, Kim Gert Nielsen wrote:
>
> info: Filebucket[/var/lib/puppet/clientbucket]: Adding
> /etc/puppet/puppet.conf(f855be601e533a86b2c86a1e48e40281)
> info: //pu
On Wed, 21 Apr 2010, Jewels wrote:
> puppetca --revoke hostname
> puppetca --clean hostname
You added the old cert's serial number to a revocation list, and
then removed the cert from puppetca. The cert might or might not
still exist on the client.
> On client re-issue puppetd --server puppet --
On Apr 21, 2010, at 11:30 AM, Jewels wrote:
> I have a problem I can't figure out. I was having cert problems with a
> host - it seemed to have multiple host names (mot likely from dns
> changes in the past) and all the certs were valid. Although it was
> giving an error about a cert I could not
On Apr 21, 2010, at 2:51 PM, Ken wrote:
> More data is needed I think.
>
> Can you run puppetd --no-daemonize --debug in 'screen' or by piping
> the output somewhere? It may give you a better clue.
>
Well I partly got something
info: Filebucket[/var/lib/puppet/clientbucket]: Adding
/etc/pupp
I have a problem I can't figure out. I was having cert problems with a
host - it seemed to have multiple host names (mot likely from dns
changes in the past) and all the certs were valid. Although it was
giving an error about a cert I could not identify. So I tried:
puppetca --revoke hostname
pupp
No except, that I see the problem as well:
http://projects.reductivelabs.com/issues/2888
http://projects.reductivelabs.com/issues/2661
Well I can see that these 2 problems actually logs .. mine just gives nothing
.. I have been running puppetd in screens but so far nothing.
/Kim
--
You rec
Hi folks,
See a recent post on our blog that we're pretty excited about:
http://www.puppetlabs.com/blog/zenoss-and-puppet-labs-partner-to-deliver-integrated-it-monitoring-and-automation-for-next-generation-datacenters/
If you're interested in using Zenoss and Puppet together, we can now
more eas
I didn't seen this myself Matt. I was using 200g EBS volumes. Can you
see the mount command in action while its blocking and try to
replicate manually it with all command line options etc.
I found the provided and community Centos images where a bit poor -
and rolled my own from scratch because I
> My main problem is defining in puppet the name of the EBS volume to
> attach, and having the puppet client on the EC2 instance actually
> *attach* the volume after it has "spun-up".
Is this because you want to be able to convert the EBS id to a /dev/
sdX device? So the EBS volume id is what you
I recently upgraded puppet on my client machine to 0.25.4 (using the
package from EPEL). However I'm not getting this error:
debug: Finishing transaction 23575711646920 with 0 changes
debug: Using cached certificate for ca, good until Sun Feb 01 09:38:22
UTC 2015
debug: Using cached certificate fo
Having the ebs vol id as a parameter in the node manifest works for us
$ebsvol = "xxx"
Then use the Mount type with that variable in your manifest file.
We've observed an issue when mounting EBS volumes in EC2 on our CentOS 5 AMI
though - puppetd seems to hang when executing the mount command.
More data is needed I think.
Can you run puppetd --no-daemonize --debug in 'screen' or by piping
the output somewhere? It may give you a better clue.
On Apr 21, 12:39 pm, Kim Gert Nielsen wrote:
> Hi all,
>
> The last 2 weeks we have been having problems with puppetd just randomly
> stopping. T
Thanks for the reply. I think the mounting part should be straight
forward.
My main problem is defining in puppet the name of the EBS volume to
attach, and having the puppet client on the EC2 instance actually
*attach* the volume after it has "spun-up".
On Apr 21, 1:07 pm, Ken wrote:
> > Is it p
> Is it possible, using puppet, to configure an EC2 instance so that
> when it boots it attaches & mounts an EBS volume? If so, what steps
> would one take to achieve this?
The mounting should normally be done by your os - ie. put the entry
in /etc/fstab.
However - puppet can manage the /etc/fsta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Our suspicion comes down to its a problem with a timeout since
> usually it stops after a high catalog run time.
>
> So ... Any idea on how to track this down ? _any_ input is welcome
No except, that I see the problem as well:
http://projects.redu
Hi all,
The last 2 weeks we have been having problems with puppetd just randomly
stopping. The only thing the log shows is:
Apr 21 12:14:59 relay puppetd[1376]: Finished catalog run in 4.78 seconds
Apr 21 12:30:07 relay puppetd[1376]: Finished catalog run in 4.76 seconds
Apr 21 12:45:20 relay p
Hi all:
El Miércoles, 21 de Abril de 2010 06:55:29, Daniel Pittman escribió:
> donavan writes:
[...]
> > When I made up my sites broadcast fact I solved it in a manner like
> > interfaces.rb. Essentially there are multiple "broadcast_$interface"
> > facts, and while creating these the interface
Is it possible, using puppet, to configure an EC2 instance so that
when it boots it attaches & mounts an EBS volume? If so, what steps
would one take to achieve this?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send em
Meanwhile I have made a little progress when I removed authlogic-2.1.2
from vendor/gems.
But came not too far...
Can someone please point me into the right direction?
Many Thanks in advance
Lutz
Now I get:
bash-3.00# rake install --trace
(in /opt/reductivelabs-puppet-dashboard-v1.0.0rc2-0-gd5918
42 matches
Mail list logo
