Re: [Puppet Users] Install puppetDB on already deployed environment
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 puppetdb server! (puppet.test.com:8081) Error: /Stage[main]/Puppetdb::Master::Config/Puppetdb_conn_validator[ puppetdb_conn]/ensure: change from absent to present failed: Unable to connect to puppetdb server! (puppet.test.com:8081) Notice: /Stage[main]/Puppetdb::Master::Storeconfigs/Ini_setting[puppet.conf/ master/storeconfigs]: Dependency Puppetdb_conn_validator[puppetdb_conn] has failures: true Warning: /Stage[main]/Puppetdb::Master::Storeconfigs/Ini_setting[puppet.conf /master/storeconfigs]: Skipping because of failed dependencies Notice: /Stage[main]/Puppetdb::Master::Storeconfigs/Ini_setting[puppet.conf/ master/storeconfigs_backend]: Dependency Puppetdb_conn_validator[ puppetdb_conn] has failures: true Warning: /Stage[main]/Puppetdb::Master::Storeconfigs/Ini_setting[puppet.conf /master/storeconfigs_backend]: Skipping because of failed dependencies Notice: /Stage[main]/Puppetdb::Master::Routes/File[/etc/puppet/routes.yaml]: Dependency Puppetdb_conn_validator[puppetdb_conn] has failures: true Warning: /Stage[main]/Puppetdb::Master::Routes/File[/etc/puppet/routes.yaml ]: Skipping because of failed dependencies Notice: /Stage[main]/Puppetdb::Master::Puppetdb_conf/Ini_setting[ puppetdbport]: Dependency Puppetdb_conn_validator[puppetdb_conn] has failures: true Warning: /Stage[main]/Puppetdb::Master::Puppetdb_conf/Ini_setting[ puppetdbport]: Skipping because of failed dependencies Notice: /Stage[main]/Puppetdb::Master::Puppetdb_conf/Ini_setting[ soft_write_failure]: Dependency Puppetdb_conn_validator[puppetdb_conn] has failures: true Warning: /Stage[main]/Puppetdb::Master::Puppetdb_conf/Ini_setting[ soft_write_failure]: Skipping because of failed dependencies Notice: /Stage[main]/Puppetdb::Master::Puppetdb_conf/Ini_setting[ puppetdbserver]: Dependency Puppetdb_conn_validator[puppetdb_conn] has failures: true Warning: /Stage[main]/Puppetdb::Master::Puppetdb_conf/Ini_setting[ puppetdbserver]: Skipping because of failed dependencies Notice: /Stage[main]/Puppetdb::Master::Config/Service[puppetmaster]: Dependency Puppetdb_conn_validator[puppetdb_conn] has failures: true Warning: /Stage[main]/Puppetdb::Master::Config/Service[puppetmaster]: Skipping because of failed dependencies Notice: Finished catalog run in 120.27 seconds root@puppet:~# Also, I do not have puppetdb binary since I have used puppetdb module. root@puppet:~# ls -lrth /etc/init.d/puppet* -rwxr-xr-x 1 root root 1.7K Jun 10 07:07 /etc/init.d/puppetqd -rwxr-xr-x 1 root root 3.8K Jun 10 07:07 /etc/init.d/puppetmaster root@puppet:~# Any other suggestions to tackle this ? Regards, Vikas On Monday, 18 August 2014 15:09:26 UTC+10, Atom Powers wrote: Don't cancel it. It will eventually timeout or start working. You may want to start puppetdb manually if it times-out; 'service puppetdb start' -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/96579854-43be-4c4b-8af6-07aa1076788e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Install puppetDB on already deployed environment
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 Sierra Pons j...@elsotanillo.net Linux User Registered: #257202 Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CABS%3Dy9vc7M0rO%3D-D%3DjQQwTD1V3j5cnhFzXY4cM2tAvGCTg4%3D-A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Install puppetDB on already deployed environment
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/puppet/puppetdb.conf and try again. I had a similar problem time ago and starting from scratch fixed it Best Regards -- Juan Sierra Pons ju...@elsotanillo.net javascript: Linux User Registered: #257202 Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d397e2f6-3cd9-4768-8a15-8a8be9723a8a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Install puppetDB on already deployed environment
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 Registered: #257202 Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CABS%3Dy9vM_F_%3DWt09BfQZOj_JDLu63g-rPkFfu1dTg4JHpYTcsQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Install puppetDB on already deployed environment
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 to confirm it is working fine. Regards, Vikas On Monday, 18 August 2014 20:40:22 UTC+10, Juan Sierra Pons wrote: Hi, I am using puppetlabs-puppetdb module too. Can you install puppetdb manually using your os package tool (apt/yum)? Regards -- Juan Sierra Pons ju...@elsotanillo.net javascript: Linux User Registered: #257202 Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/277b9eb6-3b58-4ac3-99d4-06b5097377c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] How can we find out the directory presence?
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 group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/6f8d03fb-8d97-4832-a3b7-70868132c451%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Install puppetDB on already deployed environment
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: #257202 Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CABS%3Dy9um2mWrenMbUx%2BF3oj-EwMfuJxrzAyc3siZi3MN3RgJUw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Install puppetDB on already deployed environment
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.test.com puppet.test.com root@puppet:~# Regards, Vikas On Monday, 18 August 2014 21:41:05 UTC+10, Vikas Kumar wrote: 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 to confirm it is working fine. Regards, Vikas On Monday, 18 August 2014 20:40:22 UTC+10, Juan Sierra Pons wrote: Hi, I am using puppetlabs-puppetdb module too. Can you install puppetdb manually using your os package tool (apt/yum)? Regards -- Juan Sierra Pons ju...@elsotanillo.net Linux User Registered: #257202 Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/612214c0-9b34-4131-9993-617e8df9e8c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Cannot parse arrat into defined type
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['id']: } }}*
But this gives me
*err: Could not retrieve catalog from remote server: Could not intern from
pson: Could not convert from pson: Could not find relationship target
Change_config::Map[ip1.1.1.1idbar]warning: Not using cache on failed
catalogerr: Could not retrieve catalog; skipping run*
What is the reason for this ?
The reason is that your code is broken. Resource names / titles are
*strings*. If you try to use a hash as a resource title (via a variable,
since a hash literal in that position won't even parse) then it is
stringified for use as the name. The ip1.1.1.1idbar resource title is
exactly such a stringified hash. If you want to feed a hash to your
defined type then do it via a parameter.
With respect to the details of your code, it looks like you might be
searching for the create_resources()
https://docs.puppetlabs.com/references/3.4.stable/function.html#createresources
function. Your data take a form similar (but not identical) to the one
consumed by create_resources.
In addition, I strongly recommend choosing a different name than map for
your defined type, as map is the name of a built-in function in the
future parser. In fact, the defined type's name in your example is really
myclass::map, which is basically ok as long as you refer to it by that
name, but that would be much clearer if you did not nest the type
definition inside your class. It is poor style to nest class or type
definitions inside (other) classes; instead, each should reside in its own
file.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/4824d378-d36a-4979-a3a6-77dd2ed6911e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] PuppetDB Catalog Duplication and Multiple Masters
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 pool ? I saw this by switching on the debug setting in PuppetDB and diffing the resulting JSON files. Would that be the case, or is it something else I am not seeing ? Any ideas on how to improve this ? Thanks Paul -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/34ce1895-d737-4c8e-a064-cc84f989f46e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] PuppetDB Catalog Duplication and Multiple Masters
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 pool ? I saw this by switching on the debug setting in PuppetDB and diffing the resulting JSON files. 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 introduced to a custom resource? Can you also share a picture of your dashboard, so we can see the duplication rate? Would that be the case, or is it something else I am not seeing ? Any ideas on how to improve this ? Perhaps, with more details. ken. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNTnWmUKiQfLFZQw2V9i5LCAHEvpdqexaTPcrGC-qmf%3DjQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] PuppetDB Catalog Duplication and Multiple Masters
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 introduced to a custom resource? Can you also share a picture of your dashboard, so we can see the duplication rate? Would that be the case, or is it something else I am not seeing ? Any ideas on how to improve this ? Perhaps, with more details. ken. Thanks Ken, your reply has prompted me to take a look at something and we have some inline templates that dump some variables. I will switch these off to see if it takes care of it - and I suspect it will. If not I will come back to you. Cheers Paul -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/42ca5385-6ba4-4599-99bf-a9caed44bf55%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: scheduled_task changes on every puppet run
On Wed, Aug 13, 2014 at 12:55 PM, aaronm publicmai...@gmail.com 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', 'start_time' = '13:00'}' to '[{'every' = '1', 'schedule' =
'daily', 'start_time' = '13:00'}]'
/Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger
/opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp
---
(**this is from a longrunning PE server running 3.2 installed many months
ago**)
trigger changed '{'every' = '1', 'schedule' = 'daily', 'start_date' =
'2014-8-12', 'start_time' = '13:00'}' to '[{'every' = '1', 'schedule' =
'daily', 'start_time' = '13:00'}]'
/Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger
/opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp
The PE catalog includes a scheduled task. Would you mind following up on
the pe-users group?
On Thursday, August 7, 2014 7:36:18 AM UTC-4, cko wrote:
Hi,
I'm using the following scheduled_task on one of my windows server 2008
r2 boxes:
scheduled_task { 'reboot':
command = 'C:\WINDOWS\System32\shutdown.exe',
arguments = -r -f -t 01,
user = 'SYSTEM',
trigger = {
schedule= weekly,
start_time = '06:00',
every = 1,
day_of_week = sun,
}
}
Puppet creates the task and works just fine.
However, on every single puppet run the trigger changes (even though I
didn't change the puppet code).
The report shows the following output:
*Notice: /Stage[main]/Main/Node[NODE]/Scheduled_task[reboot]/trigger:
trigger changed '{'every' = '1', 'on' = ['sun'], 'schedule' = 'weekly',
'start_date' = '2014-8-7', 'start_time' = '06:00'}' to '[{'day_of_week'
= ['sun'], ' every' = '1', 'schedule' = 'weekly', 'start_time' =
'06:00'}]' Notice: Finished catalog run in 6.55 seconds*
Is there anything I can do to achieve idempotence with this scheduled
task?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e7823a79-676c-4c6e-a985-378d264e91f0%40googlegroups.com
https://groups.google.com/d/msgid/puppet-users/e7823a79-676c-4c6e-a985-378d264e91f0%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
Rob Reynolds
Developer, Puppet Labs
*Join us at PuppetConf 2014 http://www.puppetconf.com/, September
20-24 in San Francisco*
*Register by September 8th to take advantage of the Final Countdown
https://www.eventbrite.com/e/puppetconf-2014-tickets-7666774529?discount=FinalCountdown
*
*--**save $149!*
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAMJiBK7Qhv3dfBCGi8Va9%2Bo07oC0s-EiJw-e_o%3DFvERAQtvWdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Remove java from path - Windows
On Fri, Aug 15, 2014 at 7:43 AM, badgerious badge...@hotmail.com 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 automatically when it changes. 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. That means it is up to the application to expand the environment variable. As long as the application wanting to use %JAVA_HOME% does the expansion of the environment variable, all is good. Typically this happens just fine, but wanted to make you aware of this in case you run into any edge cases. [1]http://msdn.microsoft.com/en-us/library/windows/desktop/ms724884.aspx [2]HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment Eric On Thursday, August 14, 2014 7:16:56 AM UTC-5, Jeff Sparrow wrote: We are having an issue with some modules. They are adding the correct path, but they do not remove the old path: C:\Windows\system32path PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\IBM\RationalSDLC\common;;C:\Program Files (x86)\NTP\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin;C:\Program Files\Java\jdk1.7.0_50\bin;C:\PROGRA~1\apache-maven\bin;C:\Program Files\Java\jdk1.7.0_55\bin You can see that it added the correct path at the end, but the original version jdk1.7_50\bin still exists. How can we make sure that it removes the old version every time it installs a newer version? Edit: More importantly what we need to do is have it search for the JAVA_HOME path variable, compare that against Path variable, delete any java directory that doesnt belong, and copy the JAVA_HOME to Path. Hope that makes sense. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ef140bb1-c61b-41f1-80c4-1f9bf017f838%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/ef140bb1-c61b-41f1-80c4-1f9bf017f838%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Rob Reynolds Developer, Puppet Labs *Join us at PuppetConf 2014 http://www.puppetconf.com/, September 20-24 in San Francisco* *Register by September 8th to take advantage of the Final Countdown https://www.eventbrite.com/e/puppetconf-2014-tickets-7666774529?discount=FinalCountdown * *--**save $149!* -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMJiBK59WXYRPRSAAd4jiZ31Hhj4o9hdOF-9JccPPput5SON9Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How can we find out the directory presence?
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 mcollective to check in real time whether the dir exists
c) ssh in and use ls
The usual point also, that you should stop asking your servers how they are and
tell them how they should be. Declare, don't inquire.
On Mon, Aug 18, 2014 at 05:05:43AM -0700, Satish Katuru wrote:
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 group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [1]puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[2]https://groups.google.com/d/msgid/puppet-users/6f8d03fb-8d97-4832-a3b7-70868132c451%40googlegroups.com.
For more options, visit [3]https://groups.google.com/d/optout.
References
Visible links
1. mailto:puppet-users+unsubscr...@googlegroups.com
2.
https://groups.google.com/d/msgid/puppet-users/6f8d03fb-8d97-4832-a3b7-70868132c451%40googlegroups.com?utm_medium=emailutm_source=footer
3. https://groups.google.com/d/optout
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/20140818170118.GA906%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Augeas hates me!!!
On Wed, Aug 13, 2014 at 8:22 AM, randal cobb rco...@gmail.com wrote:
from this manifest entry:
augeas { 'apache2':
context = /files/etc/sysconfig/apache2,
lens= sysconfig.lns,
incl= '/usr/share/augeas/lenses/dist/',
changes =
'set APACHE_MODULES \'actions alias auth_basic
authn_file authz_host authz_groupfile authz_user autoindex cgi dir env
expires include log_config mime negotiation setenvif ssl userdir reqtimeout
authn_core authz_core status asis auth_digest headers proxy proxy_http
rewrite vhost_alias authz_default proxy_balancer\'',
}
Try instead:
augeas { 'apache2':
incl= '/etc/sysconfig/apache2',
lens= 'Sysconfig.lns',
changes = ...
}
You probably don't *need* either the incl or lens parameters but my
experience is that agent performance is absymal without them; otherwise
Augeas will scan and load all of the files it knows about when it starts
up, which is slow -- and coupled with the fact the Puppet provider creates
a new Augeas instance for every resource (unless this bug has been fixed),
it's really slow.
You might find more help with the Augeas guide:
https://docs.puppetlabs.com/guides/augeas.html
As others have said, Augeas can be tough to get your head around, in part
because there are at least 4 or 5 different languages involved, some of
which are confusingly similar or bleed into each other:
- Lens schema language
- Path expressions (and the link to the path expression doc is buried in
the Tree page and 404 anyway; should be
https://github.com/hercules-team/augeas/wiki/Path-expressions)
- Tree structure magic control files under /augeas
- Tree manipulation and query commands which are similar but not wholly
isomorphic:
- augtool commands
- Puppet parameters for Augeas type
- Language bindings aka public API: C, Ruby
To effectively test and develop Puppet resources, you need everything
EXCEPT the lens schema language. Unfortunately, if you click the
Documentation link on augeas.net, only the first sub-items are NOT
related to lens schema development. And docs extracted under Stock Lenses
is a muddle of both.
Wil
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAMmm3r5511CS4cadWxMZ-A6wcxd6x5HZZLaMm3K6AJaOeFD9Pg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet over stunnel fileserver issues
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 server and assign it a class but I can't seen to get transfers from the fileserver. My guess is that its trying to use random ports like an ftp server would so I though I would throw this question to the group to see if anyone else has had any luck or what people are doing with remote locations and 1 puppetmaster. Jason -- IMPORTANT NOTICE: This message, including any attachments (hereinafter collectively referred to as Communication), is intended only for the addressee(s) named above. This Communication may include information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this Communication is not the intended recipient, or the employee or agent responsible for delivering this Communication to the intended recipient, you are notified that any dissemination, distribution or copying of this Communication is strictly prohibited. If you have received this Communication in error, please notify the sender immediately by phone or email and permanently delete this Communication from your computer without making a copy. Thank you. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5ab5db03-e1c8-4157-bfad-513314783b16%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet Live Management/Console not working
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@ipaddress 2) https://ipaddress - Live Management console not working Can anyone please help me if I need to set any other config changes -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f61964cc-eaef-419e-8c99-fb27de3b868a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How can we find out the directory presence?
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) monitoring (snmp?) check invoking a custom script, script detects the dir b) use something like mcollective to check in real time whether the dir exists c) ssh in and use ls d) Write a custom fact; external facts https://docs.puppetlabs.com/facter/latest/custom_facts.html#external-facts make it as easy as writing a small shell script: /etc/facter/facts.d/mydir.sh: #!/bin/sh test -d /foo/bar echo dir_foo_bar_exists=true The usual point also, that you should stop asking your servers how they are and tell them how they should be. Declare, don't inquire. That's great advice and a worthwhile long-term goal. But when you're just starting out or are increasing management coverage incrementally, you need to do these kinds of things. Wil -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMmm3r7XFyhLHy2ocT1JSydYuY1GvJW9H_4XgJVQCKwptWeWEw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Module with smart class parameter
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 give me link to the documentation on this one?
Thanks in advance
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/29b997d2-8acd-4dde-9faf-f25f3844aa2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Install puppetDB on already deployed environment
Did you setup route.yml ? Flamarion Jorge Sent from my mobile Em 18/08/2014 02:05, Vikas Kumar vikas...@gmail.com 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/puppetmaster status * master is not running root@puppet:~# root@puppet:~# /etc/init.d/apache2 status * apache2 is running root@puppet:~# I am trying to install puppetdb via a module https://docs.puppetlabs.com/puppetdb/2.1/install_via_module.html, but after installing the module I ran 'puppet agent -t' command and encountered below errors. root@puppet:~# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin ... ... Info: Caching catalog for puppet.test.com Info: Applying configuration version '1408337383' Notice: Unable to connect to puppetdb server (puppet.test.com:8081): Connection refused - connect(2) Notice: Failed to connect to puppetdb; sleeping 2 seconds before retry Notice: Unable to connect to puppetdb server (puppet.test.com:8081): Connection refused - connect(2) Notice: Failed to connect to puppetdb; sleeping 2 seconds before retry Notice: Unable to connect to puppetdb server (puppet.test.com:8081): Connection refused - connect(2) Notice: Failed to connect to puppetdb; sleeping 2 seconds before retry ^CNotice: Caught INT; calling stop root@puppet:~# I checked that port 8081 is not being used by any daemon. root@puppet:~# netstat -an | grep 8081 root@puppet:~# telnet 192.168.1.99 8081 Trying 192.168.1.99... telnet: Unable to connect to remote host: Connection refused root@puppet:~# Please help me out to troubleshoot this. Regards, Vikas -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0fb35b85-6b24-47d5-a8a3-c632c0869956%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/0fb35b85-6b24-47d5-a8a3-c632c0869956%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2Bx2bU17LE5YLKsyTK2fihRq46XW6MHx9OVQgM9wZtLimfm7eA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How can we find out the directory presence?
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 satishkat...@gmail.com 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 create a directory:
File { /etc/puppet/test:
ensure = directory,
}
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/6f8d03fb-8d97-4832-a3b7-70868132c451%40googlegroups.com
https://groups.google.com/d/msgid/puppet-users/6f8d03fb-8d97-4832-a3b7-70868132c451%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CA%2Bx2bU37jc8pkVaZTF%2BLux38%2BKB%3DeJ%2BV93XR5%3DV55w%2B2TNASxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How can we find out the directory presence?
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 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 mcollective to check in real time whether the dir exists c) ssh in and use ls d) Write a custom fact; [2]external facts make it as easy as writing a small shell script: /etc/facter/facts.d/mydir.sh: #!/bin/sh test -d /foo/bar echo dir_foo_bar_exists=true If you're using this in manifests and you really can't manage the directory, this is better. Of course, I'd say go for a custom fact rather than an external fact. That way you get pluginsync for free. https://docs.puppetlabs.com/facter/2.0/fact_overview.html That said, if you need your monitoring-of-this-directory to eventually alert a human if something goes wrong, you'll need to set up monitoring/ticketing/alerting. Dig around on forge.puppetlabs.com for strings like: nagios snmp monit The usual point also, that you should stop asking your servers how they are and tell them how they should be. Declare, don't inquire. That's great advice and a worthwhile long-term goal. But when you're just starting out or are increasing management coverage incrementally, you need to do these kinds of things. Wil That rather depends on your goals, albeit that I'm on my second set of production puppetized services. In short, based on prior horrible experiences, I'm going for know what you're doing. For the current set of puppetized hosts I went with: a) be able to bootstrap all puppet infrastructure from a CentOS minimal install and the puppet git tree (some chicken/egg here requiring manual intervention, I admit) b) any node should be automagically configurable from a CentOS minimal install to full production readiness with no manual intervention (The basics.) This makes knowing what components constitute the puppetized services a direct requirement of running their backend nodes. It took longer to get going, but now there's no puppet-vs-nonpuppet-bits tracking, no who made that change when, and no make sure all servers have this for the puppetized hosts. (Still the basics.) It has, of course, shown up a number of interesting cultural practices around configuration changes that are still sorting themselves out. If I had to sum up, I'd say that puppet's main value so far is to throw all this stuff into sharp relief. The automation is good, but knowing what it takes to run things is the real advantage. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to [3]puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit [4]https://groups.google.com/d/msgid/puppet-users/CAMmm3r7XFyhLHy2ocT1JSydYuY1GvJW9H_4XgJVQCKwptWeWEw%40mail.gmail.com. For more options, visit [5]https://groups.google.com/d/optout. References Visible links 1. mailto:christopher_w...@pobox.com 2. https://docs.puppetlabs.com/facter/latest/custom_facts.html#external-facts 3. mailto:puppet-users+unsubscr...@googlegroups.com 4. https://groups.google.com/d/msgid/puppet-users/CAMmm3r7XFyhLHy2ocT1JSydYuY1GvJW9H_4XgJVQCKwptWeWEw%40mail.gmail.com?utm_medium=emailutm_source=footer 5. https://groups.google.com/d/optout -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140818214134.GA2144%40iniquitous.heresiarch.ca. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] If else statement if file exists
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 statement would be
appreciated
if file /volumes/vol1 exists { *exec { generate_loopback_tor: command =
/sbin/losetup /dev/loop6 /volumes/tor, unless = /sbin/losetup -a|
/bin/grep \/volumes/tor\, } *
*exec { generate_encrypt_tor:command = /sbin/cryptsetup create tor
,unless = /usr/bin/test -e /dev/mapper/tor, }exec {
generate_mount_tor: command = /bin/mount /dev/mapper/tor /usr/local/tor,
unless = /bin/mount | /bin/grep \/usr/local/tor\, } }* else { exec {
generate_empty_file_tor: command = /bin/dd of=/volumes/tor bs=256M
count=0 seek=1, unless = /usr/bin/test -e /volumes/tor, } exec {
generate_loopback_tor: command = /sbin/losetup /dev/loop6 /volumes/tor,
unless = /sbin/losetup -a| /bin/grep \/volumes/tor\, } exec {
generate_encrypt_tor: command = /bin/echo \XX\ |
/sbin/cryptsetup create tor /dev/loop6 -, unless = /usr/bin/test -e
/dev/mapper/tor, } exec { generate_zero_tor: command = /bin/dd
if=/dev/zero of=/dev/mapper/tor count=512 bs=1024, unless = /sbin/fdisk
-lu | /bin/grep \/dev/mapper/tor\, } exec { generate_mkfs_tor: command
= /sbin/mke2fs -j -O dir_index /dev/mapper/tor , onlyif = /sbin/parted
-l | /bin/grep \Error: /dev/mapper/tor: unrecognised disk label\, } exec
{ generate_mount_tor: command = /bin/mount /dev/mapper/tor
/usr/local/tor, unless = /bin/mount | /bin/grep \/usr/local/tor\, }
}
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/3b5fdfab-5d3b-4e84-baca-a87b97e74911%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: If else statement if file exists
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, Eugene Sapozhnikov wrote:
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 statement would be
appreciated
if file /volumes/vol1 exists { *exec { generate_loopback_tor: command =
/sbin/losetup /dev/loop6 /volumes/tor, unless = /sbin/losetup -a|
/bin/grep \/volumes/tor\, } *
*exec { generate_encrypt_tor:command = /sbin/cryptsetup create tor
,unless = /usr/bin/test -e /dev/mapper/tor, }exec {
generate_mount_tor: command = /bin/mount /dev/mapper/tor /usr/local/tor,
unless = /bin/mount | /bin/grep \/usr/local/tor\, } }* else { exec {
generate_empty_file_tor: command = /bin/dd of=/volumes/tor bs=256M
count=0 seek=1, unless = /usr/bin/test -e /volumes/tor, } exec {
generate_loopback_tor: command = /sbin/losetup /dev/loop6 /volumes/tor,
unless = /sbin/losetup -a| /bin/grep \/volumes/tor\, } exec {
generate_encrypt_tor: command = /bin/echo \XX\ |
/sbin/cryptsetup create tor /dev/loop6 -, unless = /usr/bin/test -e
/dev/mapper/tor, } exec { generate_zero_tor: command = /bin/dd
if=/dev/zero of=/dev/mapper/tor count=512 bs=1024, unless = /sbin/fdisk
-lu | /bin/grep \/dev/mapper/tor\, } exec { generate_mkfs_tor: command
= /sbin/mke2fs -j -O dir_index /dev/mapper/tor , onlyif = /sbin/parted
-l | /bin/grep \Error: /dev/mapper/tor: unrecognised disk label\, } exec
{ generate_mount_tor: command = /bin/mount /dev/mapper/tor
/usr/local/tor, unless = /bin/mount | /bin/grep \/usr/local/tor\, }
}
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/9f468d9c-cf7d-4ea6-96bc-1e4c1b6ee155%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: If else statement if file exists
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, Ellison Marks wrote:
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, Eugene Sapozhnikov wrote:
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 statement would be
appreciated
if file /volumes/vol1 exists { *exec { generate_loopback_tor: command =
/sbin/losetup /dev/loop6 /volumes/tor, unless = /sbin/losetup -a|
/bin/grep \/volumes/tor\, } *
*exec { generate_encrypt_tor:command = /sbin/cryptsetup create tor
,unless = /usr/bin/test -e /dev/mapper/tor, }exec {
generate_mount_tor: command = /bin/mount /dev/mapper/tor /usr/local/tor,
unless = /bin/mount | /bin/grep \/usr/local/tor\, } }* else { exec
{ generate_empty_file_tor: command = /bin/dd of=/volumes/tor bs=256M
count=0 seek=1, unless = /usr/bin/test -e /volumes/tor, } exec {
generate_loopback_tor: command = /sbin/losetup /dev/loop6 /volumes/tor,
unless = /sbin/losetup -a| /bin/grep \/volumes/tor\, } exec {
generate_encrypt_tor: command = /bin/echo \XX\ |
/sbin/cryptsetup create tor /dev/loop6 -, unless = /usr/bin/test -e
/dev/mapper/tor, } exec { generate_zero_tor: command = /bin/dd
if=/dev/zero of=/dev/mapper/tor count=512 bs=1024, unless = /sbin/fdisk
-lu | /bin/grep \/dev/mapper/tor\, } exec { generate_mkfs_tor: command
= /sbin/mke2fs -j -O dir_index /dev/mapper/tor , onlyif = /sbin/parted
-l | /bin/grep \Error: /dev/mapper/tor: unrecognised disk label\, } exec
{ generate_mount_tor: command = /bin/mount /dev/mapper/tor
/usr/local/tor, unless = /bin/mount | /bin/grep \/usr/local/tor\, }
}
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/701cfd1e-d251-4408-b7d5-b3f8fc1d3fac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: If else statement if file exists
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 one and mounting it
On Monday, August 18, 2014 3:06:55 PM UTC-7, Ellison Marks wrote:
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, Eugene Sapozhnikov wrote:
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 statement would be
appreciated
if file /volumes/vol1 exists { *exec { generate_loopback_tor: command =
/sbin/losetup /dev/loop6 /volumes/tor, unless = /sbin/losetup -a|
/bin/grep \/volumes/tor\, } *
*exec { generate_encrypt_tor:command = /sbin/cryptsetup create tor
,unless = /usr/bin/test -e /dev/mapper/tor, }exec {
generate_mount_tor: command = /bin/mount /dev/mapper/tor /usr/local/tor,
unless = /bin/mount | /bin/grep \/usr/local/tor\, } }* else { exec
{ generate_empty_file_tor: command = /bin/dd of=/volumes/tor bs=256M
count=0 seek=1, unless = /usr/bin/test -e /volumes/tor, } exec {
generate_loopback_tor: command = /sbin/losetup /dev/loop6 /volumes/tor,
unless = /sbin/losetup -a| /bin/grep \/volumes/tor\, } exec {
generate_encrypt_tor: command = /bin/echo \XX\ |
/sbin/cryptsetup create tor /dev/loop6 -, unless = /usr/bin/test -e
/dev/mapper/tor, } exec { generate_zero_tor: command = /bin/dd
if=/dev/zero of=/dev/mapper/tor count=512 bs=1024, unless = /sbin/fdisk
-lu | /bin/grep \/dev/mapper/tor\, } exec { generate_mkfs_tor: command
= /sbin/mke2fs -j -O dir_index /dev/mapper/tor , onlyif = /sbin/parted
-l | /bin/grep \Error: /dev/mapper/tor: unrecognised disk label\, } exec
{ generate_mount_tor: command = /bin/mount /dev/mapper/tor
/usr/local/tor, unless = /bin/mount | /bin/grep \/usr/local/tor\, }
}
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/268b8251-99f2-4219-a9ec-2762b095c941%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Install puppetDB on already deployed environment
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 vika...@gmail.com javascript: 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/puppetmaster status * master is not running root@puppet:~# root@puppet:~# /etc/init.d/apache2 status * apache2 is running root@puppet:~# I am trying to install puppetdb via a module https://docs.puppetlabs.com/puppetdb/2.1/install_via_module.html, but after installing the module I ran 'puppet agent -t' command and encountered below errors. root@puppet:~# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin ... ... Info: Caching catalog for puppet.test.com Info: Applying configuration version '1408337383' Notice: Unable to connect to puppetdb server (puppet.test.com:8081): Connection refused - connect(2) Notice: Failed to connect to puppetdb; sleeping 2 seconds before retry Notice: Unable to connect to puppetdb server (puppet.test.com:8081): Connection refused - connect(2) Notice: Failed to connect to puppetdb; sleeping 2 seconds before retry Notice: Unable to connect to puppetdb server (puppet.test.com:8081): Connection refused - connect(2) Notice: Failed to connect to puppetdb; sleeping 2 seconds before retry ^CNotice: Caught INT; calling stop root@puppet:~# I checked that port 8081 is not being used by any daemon. root@puppet:~# netstat -an | grep 8081 root@puppet:~# telnet 192.168.1.99 8081 Trying 192.168.1.99... telnet: Unable to connect to remote host: Connection refused root@puppet:~# Please help me out to troubleshoot this. Regards, Vikas -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0fb35b85-6b24-47d5-a8a3-c632c0869956%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/0fb35b85-6b24-47d5-a8a3-c632c0869956%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/9339c2c6-adaa-4f9c-8d4c-e93f0f8ec2e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Remove java from path - Windows
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 %variable% via the GUI, Windows will change it from REG_SZ to REG_EXPAND_SZ for you (and back again if you remove all the %variables%). I wonder if the windows_env puppet module should do that? I've done the %variable% in path before without issue and did a quick test before posting, but some further curiosity fueling googling suggests there may be gotchas that I was not previously aware of. To the OP: I'd be interested to hear if you have any such issues. Eric -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/46ffe10b-d5f3-4d01-ab1f-86208de831ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] install windows package
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 https://docs.puppetlabs.com/references/latest/type.html#package This works really well out of the box if your installer displays information in Control Panel/Installed Programs. If your installer doesn’t, you should look at using Rob Reynold’s Chocolatey packaging tool in conjunction with Josh Cooper’s Chocolatey Provider for the package resource type. That'd be Rich Siegel's chocolatey provider: https://forge.puppetlabs.com/rismoney/chocolatey Josh -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7afd676c-2a72-4059-95c3-76a941c9c6de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
