On 05/25/2014 05:38 AM, Tim Dunphy wrote:
Hey all,
I'm trying to write a puppet module to deploy the cassandra database
automatically. I'm using puppet templates to provide the IP address to
the listen_address parameter of the cassandra.yaml file like so:
listen_address: <%= ipaddress %>
So fa
On 05/24/2014 07:54 AM, Bad Tux wrote:
Am I missing a configuration option in the manual to somehow disable SSL
certificate validation? Does everybody add a cron job to their puppet
master to stop the puppetmaster daemon and blow away its SSL directory
then restart it at exactly 12:00AM every da
I've been using the default (which if I read correctly is 5s?); seems
likely that a good answer here for me would be to push it out to
$something_long and use restart.txt or somesuch to uptake changes. I may
try that this week.
My MaxRequests was already 10k. I'm guessing that 5 seconds of cache w
On 05/24/2014 04:01 AM, Matt Wise wrote:
When you have hundreds of hosts and run Puppet every 30 mins (splayed
across the hour), it seems that you end up running into various 'dpkg'
locks fairly randomly and at a surprisingly high occurrence (once or
twice a day at least). This happens if you do
>
> Generate the number of tokens that's the maximum number of nodes you
> expect in your cassandra clusters (for example 15), put them into array,
> and let the module use them, for example:
> $tokens = [ '-9223372036854775808', '-6148914691236517206',
> '-3074457345618258604', '-2' , '30744573456
I am new to puppet and decided to really get my feet wet by writing a
duplicity module (https://github.com/JCotton1123/puppet-duplicity.git). I
am struggling to deal with the fact that variables are immutable and cannot
be reassigned (within the same scope). This has become a real issue while
t
No problem, the error messages as exceptions are - somewhat not helpful.
The trick for a user to reading JVM stack traces is to ignore the stack
trace, and focus on the errors only - its the noise that makes it hard.
Just thank your stars you aren't forced to read an erlang stack trace
*wink*.
ke
Hi ,
After installing the script and while starting the service i obtain the
error message bellow
/etc/init.d/puppet-dashboard start
[] Starting Puppet Dashboard:/usr/bin/ruby: No such file or directory
-- /usr/share/puppet-dashboard/script/server (LoadError)
[FAIL] Puppet Dashboard is not
I've always found that when creating modules I'd focus on creating class
parameters out of the most important configuration options of whatever I'm
managing. After that I'd add a similar approach as yours for "everything
else". This is a good approach because your module becomes usable for all
