On Tuesday, August 12, 2014 3:22:04 AM UTC-7, Jim Ficarra wrote:
>
> If you mean installing a windows package (such as an MSI or EXE) – you
> should review the package resource type documentation
>
>
> https://docs.puppetlabs.com/puppet/latest/reference/resources_package_windows.html
>
> h
On Monday, August 18, 2014 10:51:35 AM UTC-5, Rob Reynolds wrote:
>
> This works great as long as the registry key is of type REG_EXPAND_SZ[1]
> value, but the key for Path[2] is set to REG_SZ.
>
Interesting; all the systems I looked at were REG_EXPAND_SZ. It looks like
if you insert a %variabl
Thanks Flamarion for the reply, my issue is resolved now.
Regards,
Vikas
On Tuesday, 19 August 2014 07:35:05 UTC+10, Flamarion Jorge wrote:
>
> Did you setup route.yml ?
>
> Flamarion Jorge
> Sent from my mobile
> Em 18/08/2014 02:05, "Vikas Kumar" >
> escreveu:
>
>> Hello everyone,
>>
>> I have
I do want the first part of If to run every time if the file exists, as the
unless and onlyif that are part of the exec commands are safety checks to
make sure to not overwrite the volume.
I wanted to use the if else condition to determine between creating a new
volume vs unecrypting an existing
The unless and onlyif that are part of the exec commands are safety checks
to make sure to not overwrite the volume.
I wanted to use the if else condition to determine between creating a new
volume vs unecrypting an existing one and mounting it.
On Monday, August 18, 2014 3:06:55 PM UTC-7, Elli
There are some parameters to the exec type that you could use, such as
creates, onlyif and unless. However, the pseudocode you have above has the
execs in your initial if block being run every time puppet runs, it seems.
Is that really what you want?
On Monday, August 18, 2014 2:45:23 PM UTC-7,
I am trying to figure out a way to use a if statement to run multiple sets
of commands depending if one file exists, but I am unable to find any good
documented ways of doing this.
Basic rough layout of what i would like to achieve is this:
Any help on getting the correct syntax for the if st
On Mon, Aug 18, 2014 at 01:48:55PM -0700, Wil Cooley wrote:
>On Mon, Aug 18, 2014 at 10:01 AM, Christopher Wood
><[1]christopher_w...@pobox.com> wrote:
>
> This is generally the reason that you need something like puppet, that
> you want to enforce a configuration.
>
> If y
File { " /etc/puppet/test":
ensure => "directory",
unless => 'test -d /etc/puppet/test'
}
Flamarion Jorge
Sent from my mobile
Em 18/08/2014 09:05, "Satish Katuru" escreveu:
Hi ,
I wanted to find out whether the directory exists or not in the machine.How
can I do it?
if I do it as below it will
Did you setup route.yml ?
Flamarion Jorge
Sent from my mobile
Em 18/08/2014 02:05, "Vikas Kumar" escreveu:
> Hello everyone,
>
> I have a puppetmaster v3.6.2-1 installed on Ubuntu 14.04 x86_64 server. I
> am using passenger (apache2) instead of Webrick.
>
> root@puppet:~# /etc/init.d/puppetmaste
Hi, I am trying to create a module with smart class parameter. Actually,
the simple one like
user { "$users":
ensure => "present",
uid => "$uid",
gid => "$gid",
}
I want to edit these functions via gui before pushing it out. What can be
the solution? or can anyone g
On Mon, Aug 18, 2014 at 10:01 AM, Christopher Wood <
christopher_w...@pobox.com> wrote:
> This is generally the reason that you need something like puppet, that you
> want to enforce a configuration.
>
> If you need to detect things about a server, there are a number of things
> you can do:
>
> a)
Hi Team,
I have just started learning puppet. Have downloaded VM and started working.
Following as mentioned
in: http://downloads.puppetlabs.com/docs/learningpuppet.pdf
I am able to login as root to the node but not able to
1) ssh root@
2) https:// - Live Management console not working
Can anyo
I have two remote locations and my puppetmaster is behind a firewall and I
want to allow access to it through stunnel so I tunneled the port to a
client machine and aliased the puppetmasters name to localhost. I can
connect to the puppetmaster and my external node classifier can identify
the
On Wed, Aug 13, 2014 at 8:22 AM, randal cobb wrote:
> from this manifest entry:
> augeas { 'apache2':
> context => "/files/etc/sysconfig/apache2",
> lens=> "sysconfig.lns",
> incl=> '/usr/share/augeas/lenses/dist/',
> changes =>
> 'set A
This is generally the reason that you need something like puppet, that you want
to enforce a configuration.
If you need to detect things about a server, there are a number of things you
can do:
a) monitoring (snmp?) check invoking a custom script, script detects the dir
b) use something like mc
On Fri, Aug 15, 2014 at 7:43 AM, badgerious wrote:
> Hi Jeff,
>
> You can reference other variables directly from within the PATH variable,
> like so:
>
> PATH=C:\other\stuff;%JAVA_HOME%;C:\more\other\stuff
>
> That way you can maintain just the JAVA_HOME variable and path will be
> updated autom
On Wed, Aug 13, 2014 at 12:55 PM, aaronm wrote:
> I am getting similar logs every day, but I am not using any scheduled
> tasks in my manifests...
>
> (**this is on PE 3.3 installed a week or two ago**)
> trigger changed '{'every' => '1', 'schedule' => 'daily', 'start_date' =>
> '2014-8-12', 'sta
On Monday, 18 August 2014 14:56:59 UTC+1, Ken Barber wrote:
Can you share the pertinent part of the diffs so we can see exactly
> what differences you mean? I'm not sure I am aware of the
> servername/serverip cases you mention in any core modules or core
> resources, perhaps these are being
> Using multiple Puppet masters behind SRV records is working well although I
> suspect the low duplication rates I am seeing is down to the fact the load
> balancing is split between the nodes and the servername/serverip being
> recorded is different when hitting the other Puppet master in the poo
Hello,
Using multiple Puppet masters behind SRV records is working well although I
suspect the low duplication rates I am seeing is down to the fact the load
balancing is split between the nodes and the servername/serverip being
recorded is different when hitting the other Puppet master in the
On Saturday, August 16, 2014 2:22:40 AM UTC-5, Malintha Adikari wrote:
>
> Hi,
>
> I am using following puppet class
>
>
>
>
>
>
>
>
>
> *class myclass{ $foo = [{"id" => "bar", "ip" => "1.1.1.1"}, {"id" =>
> "baz", "ip" => "2.2.2.2"}] map {$foo:} define map () { notify
> {$name['i
I just installed the puppetdbquery module from forge, and ran the below
commands. I think I am good :)
root@puppet:~# puppet query nodes '(architecture=amd64)'
box30.test.com
puppet.test.com
root@puppet:~#
root@puppet:~# curl -s 'http://puppet.test.com:8080/v3/nodes' | jq -r
'.[].name'
box30.te
Hi,
Check again your config as puppetlabs-puppetdb should install the
binary and then configure it.
Best Regards
--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257
Hi ,
I wanted to find out whether the directory exists or not in the machine.How
can I do it?
if I do it as below it will create a directory:
File { " /etc/puppet/test":
ensure => "directory",
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" gr
Hi Juan,
Thanks a ton, it did the magic. I was under an impression that puppetdb
forge module will install puppetdb too.
Now, *puppet agent --test* command is working fine. But, I need to ensure
that is working as desired. I am new to puppetdb, will google out something
or write a small class
Hi,
I am using puppetlabs-puppetdb module too.
Can you install puppetdb manually using your os package tool (apt/yum)?
Regards
--
Juan Sierra Pons j...@elsotanillo.net
Linux User R
Hi Juan,
Thanks for your help but I don't have these files. May be because I am
using modules instead of binaries.
Regards,
Vikas
On Monday, 18 August 2014 19:42:25 UTC+10, Juan Sierra Pons wrote:
>
> Hi
>
> Try removing (make a backup first just in case)
> /etc/puppet/routes.yaml and /etc/pu
Hi
Try removing (make a backup first just in case)
/etc/puppet/routes.yaml and /etc/puppet/puppetdb.conf and try again.
I had a similar problem time ago and starting from scratch fixed it
Best Regards
--
Juan Sie
Hi Atom,
I tried that but its not working out.
Below is the output of the command.
root@puppet:~# puppet agent --test
Info: Retrieving pluginfacts
Info: Retrieving plugin
...
...
Notice: Failed to connect to puppetdb within timeout window of 120 seconds;
giving up.
Error: Unable to connect to p
30 matches
Mail list logo
