Ok, I'll take a look at that. Thanks!
On Monday, August 11, 2014 1:03:50 PM UTC-7, R.I. Pienaar wrote:
>
>
>
> - Original Message -----
> > From: "Guy Knights" >
> > To: puppet...@googlegroups.com
> > Sent: Monday, August 11, 2014 9:00:53
seems very
possible if mco is waiting for stdin to close.
Do you have any suggestions for band-aid fixes to get around this issue
(from the mcollective side)?
Thanks,
Guy
On Monday, August 11, 2014 12:01:06 PM UTC-7, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > F
I'm trying to execute a custom mcollective RPC call via Atlassian Bamboo
and have run into a frustrating issue. I've posted this question to the
Bamboo community help page but figured I could try asking the same thing
here in case anyone's run into this problem as well, even though I suspect
it
kage status
> ' routinely to find out if all the systems are running the same
> version.
>
> On 16.05.2014 12:09, Guy Knights wrote:
> > Thanks Garrett - so can you confirm then that ensure => present will
> > never try to upgrade a package after the initial instal
Thanks Garrett - so can you confirm then that ensure => present will never
try to upgrade a package after the initial install?
On Thursday, May 15, 2014 11:39:02 AM UTC-7, Garrett Honeycutt wrote:
>
> On 5/15/14, 11:19 AM, Guy Knights wrote:
> > I'm looking at ways to bette
I'm looking at ways to better automate our build pipeline and I'm trying to
envision ways to get our latest code package onto servers, while also being
able to update this package at specific, later times.
The code will be served from a local yum repository, so I figure we can
install the late
. I was under the impression that the actual file, not the symlink,
had to have these permissions, but apparently the symlink does as well.
Anyway, it's working now but I've updated this thread in case anyone else
runs into the same problem.
On Thursday, 10 April 2014 16:02:18 UTC-7, G
As an experiment, I downgraded back to 3.3.2. However, after restarting
apache I still get the same permission errors I listed in my original post.
On Thursday, 10 April 2014 14:46:48 UTC-7, Guy Knights wrote:
>
> I just upgraded puppet on my master machine (Ubuntu 12.04, running
I just upgraded puppet on my master machine (Ubuntu 12.04, running under
Passenger/Apache) and it doesn't work properly any more. The upgrade was
from 3.3.2 to 3.4.3.
First of all, after the upgrade I found that the location of config.ru had
changed, from /usr/share/puppet/ext/rack/files/config.ru
I have a service set up with a custom status check, but when I run puppet
it ignores my custom status command and runs the standard upstart status
check.
My service definition is as follows:
service { "gamedeploy-${title}":
ensure => running,
provider => upstart,
start => "/sbin/
I'd like to use the same init script (via upstart) for multiple service
definitions, and I thought that if I gave them different titles but the
same name paramter (eg. script name) it should allow that. However, I get a
duplicated definition error.
eg.
* service { "gamedeploy-backend":*
*nam
Oops...never mind. I just realised that I forgot to point the puppet apply
command at a manifest file. I did that and the command works now. Still, it
would be nice if it gave an error message if you don't supply a manifest.
On Fri, Jan 17, 2014 at 11:11 AM, Guy Knights
wrote:
> I we
edev(136, 0), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f87e13ba000
read(0,
It just hangs there at the "read(0," line.
On Fri, Jan 17, 2014 at 11:04 AM, Guy Knights
wrote:
> I have a bunch of dev servers which have begun experiencing the s
I have a bunch of dev servers which have begun experiencing the same issue
when I run puppet apply. The full command I'm using is: sudo puppet apply
--modulepath=/opt/puppet-conf/development/modules
--environment=development.
I've never had a problem running this command before, but very recently,
Well, wouldn't you know it but I just discovered the hiera() lookup
function which does exactly what I want.
On Friday, 13 December 2013 11:39:27 UTC-8, Guy Knights wrote:
>
> Is it possible to reuse hiera variables within hiera itself? We have some
> cases where we have a value
Is it possible to reuse hiera variables within hiera itself? We have some
cases where we have a value that needs to be changed before we deploy some
code - it's not ideal, but for now it has to be done this way. The value is
used within a hash structure that is somewhat complex, and this value i
uried deep in the puppetdb documentation. In any case, I'll work with this
option and see how I go.
On Monday, 9 December 2013 14:26:32 UTC-8, Guy Knights wrote:
>
> I'm doing some testing with the puppetlabs/haproxy module on a vagrant box
> with puppet 3 set up. The module
I'm doing some testing with the puppetlabs/haproxy module on a vagrant box
with puppet 3 set up. The module we use requires exported resources to be
enabled in order to specify haproxy backends, but I don't have it
configured in puppet. I have our puppet repo checked out to the VM and am
using
>- role accounts and restricted ssh logins (“from” and “command”
>options in the ${role_account_home}/.ssh/authorized_keys file)
>- A way to keep the ssh keys out of the hiera-data to keep the files
>human readable
>
>
> This is my response to the "Unplea
We're working on implementing hiera with our puppet 3 setup, and I'm
curious if the following is achievable. Currently, we manage each user
account within a class that realises a defined resource that creates the
user, groups, etc (for the record, we use the torrancew/account module). We
then h
I've noticed from time to time, and with certain manifests, that sometimes
there are resources that won't be applied on first run. There's no errors
during the initial run to say that a dependency failed, the resource just
isn't applied. If I then run puppet again after the first run, the resour
getting with the other require.
On Thursday, 19 September 2013 22:12:34 UTC-7, Dan Bode wrote:
>
> I'm pretty sure the error is b/c the class names need to be capitalized.
>
>
> On Tue, Sep 17, 2013 at 10:05 AM, Guy Knights
>
> > wrote:
>
>> Can someone tell
Does anyone have any feedback on this? I found at least one example
(eg.
https://genuxation.com/wiki/index.php/RSpec_tests_for_puppet_modules#Specifying_parameters_used_within_the_class)
but it didn't work for me.
Thanks,
Guy
On Tuesday, 17 September 2013 10:05:26 UTC-7, Guy Knights
Can someone tell me the correct way to specify the following require
statement in an rspec-puppet test?
*require =>
[Class['ssl'],Class['pcre3'],Staging::Extract["nginx-${version}.tar.gz"]]*
I tried this: *'require' =>
"[Class['ssl'],Class['pcre3'],Staging::Extract['nginx-1.4.1.tar.gz']]"* but
> https://groups.google.com/d/topic/puppet-users/9kdUVvrsr18/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this g
way to get puppet agent to tell me what environment it's using
when it requests the catalogue from the master?
Thanks,
Guy
On Thu, Sep 12, 2013 at 10:48 AM, Guy Knights
wrote:
> Thanks for the reply John. Here's my hiera.yaml file:
>
> ---
> :backends:
> - yaml
classes in roles/couchbase
[{"couchbase"=>nil}]
Testing for fact esg_role on the agent node:
$ facter esg_role
couchbase
For the record, my puppet version is 3.2.4, hiera is 1.2.1.
Hope this helps.
Regards,
Guy
On Thu, Sep 12, 2013 at 10:02 AM, jcbollinger wrote:
>
>
> O
I'm not sure at all what's going on here, but I've spent a lot of time
reading over the puppet hiera docs and setting everything up, but when I
run puppet agent it just seems to ignore the hiera setup completely.
Both the puppet master and agent nodes have exactly the same versions of
puppet an
I just worked this out shortly after my original post. The syntax I found
that works is
*'require' => 'Class[Couchbase::Server::Install]'*
On Monday, 2 September 2013 11:46:34 UTC-7, Guy Knights wrote:
>
> I'm writing a test for a module which declares a serv
I'm writing a test for a module which declares a service resource that has
a require parameter. However, when I run the test it throws an error on
this require as it seems that I have the syntax wrong. I've tried a few
different combinations but nothing seems to work. The error is below:
*/usr/
Ok, I found the solution - it was a simple case of adding the path to the
rspec bin directory to my PATH. Rake is using the -S switch, which uses
PATH to find the rspec binary.
Thanks,
Guy
On Fri, Aug 30, 2013 at 4:23 PM, Guy Knights wrote:
> Do I need to replace the entire contents
en you can just 'rake spec' and see if that works out better for you.
>
>
> On Fri, Aug 30, 2013 at 6:58 PM, Guy Knights
> wrote:
>
>> I'm trying to get rspec-puppet working and have run into a problem. I
>> have a VM running ubuntu lucid, have installed ruby
I'm trying to get rspec-puppet working and have run into a problem. I have
a VM running ubuntu lucid, have installed rubygems 1.3.5 from the apt
package and have install rspec-puppet (and other required gems), and rake,
using gem install.
I've run rspec-puppet-init in the module I want to test,
Hi,
What is the best way to ensure that when a node inherits another node, that
the inherited node's manifest runs first? Is there was a to ensure this
happens?
Thanks,
Guy
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discuss
Oh ok, thanks Dominic. I'll give that a go.
Regards,
Guy
On Wed, Jun 20, 2012 at 1:37 AM, Dominic Cleal wrote:
> On 19/06/12 22:02, Guy Knights wrote:
> > I can now confirm that Dominic was correct. I'm upgraded to puppet
> > 2.7.16 now and the augeas resources are
UTC-7, Dominic Cleal wrote:
>
> On 15/06/12 22:42, Guy Knights wrote:
> > Ok, thanks for your help Alan. BTW, I forgot include our puppet version
> > - it's 2.7.0.
>
> Which version of Augeas are you using? There's a bug if you're using
> Augeas 0.10.
7, Dominic Cleal wrote:
>>
>> On 15/06/12 22:42, Guy Knights wrote:
>> > Ok, thanks for your help Alan. BTW, I forgot include our puppet version
>> > - it's 2.7.0.
>>
>> Which version of Augeas are you using? There's a bug if you're using
Sorry, never mind this. I discovered that the source version of puppet was
install in /usr/local/libs/site_ruby while the repository version appears
to have been installed in /usr/lib/ruby1.8.
On Tue, Jun 19, 2012 at 12:41 PM, Guy Knights
wrote:
> Hi again,
>
> I attempted to upgra
That looks like the issue then. We're using augeas 0.10 (default with
ubuntu 10.04) and puppet 2.7.3. I'll look at upgrading puppet and see how
that goes.
Thanks all,
Guy
On Saturday, June 16, 2012 12:45:54 AM UTC-7, Dominic Cleal wrote:
>
> On 15/06/12 22:42, Guy Knight
oment...
>
> Lets see if someone else chimes in on this one and I'll give it a bit
> more thought.
>
> Regards,
> -ALan
>
> On Fri, Jun 15, 2012 at 5:27 PM, Guy Knights
> wrote:
> > Ok, thanks for the info. Are you implying that the puppet augeas resource
&g
rrorlog':
> notify=> Service['php5-fpm'],
> require => Package['php5-fpm'],
> changes => [
>"set /files/etc/php5/fpm/php.ini/PHP/error_log /var/log/php/php.log",
> ],
> }
>
> -Alan
>
> On Fri, Jun 15, 2012 a
',
>context => '/files/etc/php5/fpm/php.ini',
> changes => [
> "set /PHP/error_log /var/log/php/php.log",
> ],
> }
>
> Some relevant links.
> http://projects.puppetlabs.com/projects/1/wiki/Puppet_Augeas
> http://augeas.net/docs/referenc
I've recently configured a couple of augeas resources, one for a php.ini
file and one for sudoers, however neither set of changes is being saved. I
have no idea why. The sudoers resource is here:
augeas { 'set_sudoers':
context=> '/files/etc/sudoers/spec[user="%sudo"]',
changes
u're trying to do with a regular
> regex match, if you need to. Use the built-in $clientcert variable,
> which contains the node's certname.
>
> (This assumes you're doing the default behavior of using the certname
> as the node name. Hint: you almost certainly are.)
&
I appears that backreferences when using regexes in node names doesn't
work. Can anyone confirm this? If I'm incorrect, how do I go about using a
backreference to the name regex within the node definition container?
Thanks,
Guy
--
You received this message because you are subscribed to the Go
45 matches
Mail list logo
