Re: [Puppet Users] Reg : Pushing files from Puppet Master to Agent node

[Jose Luis Ledesma]

In fact puppetmaster cannot force a push, but mcollective can force a puppet 
run. And that with a file resource would make the job.

Regards,

-- 
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/270f1025-cc3a-414e-b8cf-9717bf025819%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Reg : Pushing files from Puppet Master to Agent node

[Dirk Heinrichs]

Am 28.01.2014 08:09, schrieb krishna bhaskara rao:

> I have installed puppetmaster in ubuntu machine and i have installed
> puppet in all my clients using apt-get. I have joined all my puppet
> clients with puppet master. Is it possible to copy a file to all these
> puppet clients from puppet master instead of going into agent and
> issue the command to pull?

No. The master does not actively push stuff to the agents. However, you
also don't need to "go into agent and issue the command to pull". The
agent runs as a daemon and queries the master every 30 minutes, so all
you need to do is to provide a manifest containing a "file" resource
which puts your file in place.

For example, a simple approach to change the agents puppet.conf could
look like this:

/etc/puppet/modules/puppetconf/manifests/init.pp

class puppetconf {

  service { 'PuppetAgent':
name => 'puppet',
ensure => 'running',
enable => 'true',
subscribe => File['puppet.conf'],
  }

  file { 'puppet.conf':
path => '/etc/puppet/puppet.conf',
ensure => file,
source => 'puppet:///modules/puppetconf/puppet.conf',
  }
}

You would then put the puppet.conf file that should be copied to your
agents into /etc/puppet/modules/puppetconf/files.

HTH...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 



http://www.recommind.com

-- 
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/52E75A61.7080703%40recommind.com.
For more options, visit https://groups.google.com/groups/opt_out.
<>

RE: [Puppet Users] Reg : Pushing files from Puppet Master to Agent node

[SHARNINDER_KHERA]

Dell - Internal Use - Confidential
Read up about the built-in file resource type.

http://docs.puppetlabs.com/references/latest/type.html#file

--
Sharninder


From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On 
Behalf Of krishna bhaskara rao
Sent: Tuesday, January 28, 2014 12:39 PM
To: puppet-users@googlegroups.com
Subject: [Puppet Users] Reg : Pushing files from Puppet Master to Agent node

Hi,

I have installed puppetmaster in ubuntu machine and i have installed puppet in 
all my clients using apt-get. I have joined all my puppet clients with puppet 
master. Is it possible to copy a file to all these puppet clients from puppet 
master instead of going into agent and issue the command to pull?

Please any one can response as early as possible.

With Regards,
Krishna Bhaskar.


--
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/efa13350-1ff8-40c4-af3f-31e5a114d487%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
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/C78F9D4A46AFAF4584E9A0EB442B3FCA49691C%40NOIX10HMNOI03.AMER.DELL.COM.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Reg : Pushing files from Puppet Master to Agent node

[krishna bhaskara rao]

Hi,

I have installed puppetmaster in ubuntu machine and i have installed puppet 
in all my clients using apt-get. I have joined all my puppet clients with 
puppet master. Is it possible to copy a file to all these puppet clients 
from puppet master instead of going into agent and issue the command to 
pull?

Please any one can response as early as possible.

With Regards,
Krishna Bhaskar.


-- 
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/efa13350-1ff8-40c4-af3f-31e5a114d487%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] CA puppetmaster

[Vassiliy Vins]

Hi!

I have 2 puppetmasters with High availability configuration.

If first dead, second starts.

Could you tell me which file from  $ssl_dir of primary  should I copy to 
secondary  puppetmaster that clients recognize it as primary one?

Any amendments should I make inside files?

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/cf21db49-f71c-4c29-90b9-861c1cb63599%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

[Rob Reynolds]

You should be able to take ownership of the directory you cannot delete as
an administrator. Once you have done that you should be able to move
forward with deleting those. I think the prior install attempts might have
botched something and that directory is not removed.


On Mon, Jan 27, 2014 at 5:13 PM, Rob Reynolds  wrote:

> Can you blow away the C:/ProgramData/PuppetLabs directory and try the
> install again?
>
>
> On Mon, Jan 27, 2014 at 12:01 PM, Josh D  wrote:
>
>>
>>
>> On Monday, January 27, 2014 10:34:36 AM UTC-7, Rob Reynolds wrote:
>>>
>>> Josh,
>>>  Can you try something for me? With the install, can you add the
>>> following to it?
>>>
>>> msiexec /qn /i themsilocation.msi PUPPET_AGENT_STARTUP_MODE=Manual
>>>
>>> And tell me if it installs okay?
>>>
>>>
>> Yep, one step ahead of you.  We were able to install by changing the
>> startup mode to manual.  Attempting to start the service post install,
>> resulted in: Error 1053: The service did not respond to the start or
>> control request in a timely fashion.
>>
>> There wasn't anything helpful in event viewer so we moved on to starting
>> the agent manually.  The pertinent portion of the output from puppet agent
>> --test --debug --verbose is below:
>>
>> Error: Could not set 'directory' on ensure: Permission denied -
>> C:/ProgramData/P
>> uppetLabs/puppet/var/state/graphs
>> Error: Could not set 'directory' on ensure: Permission denied -
>> C:/ProgramData/P
>> uppetLabs/puppet/var/state/graphs
>> Wrapped exception:
>> Permission denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
>> Error: /File[C:/ProgramData/PuppetLabs/puppet/var/state/graphs]/ensure:
>> change f
>> rom absent to directory failed: Could not set 'directory' on ensure:
>> Permission
>> denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
>> [0;36mDebug: /File
>> [C:/ProgramData/PuppetLabs/puppet/var/state/graphs]: Nothing to manage:
>> no ensure and the resource doesn't exist [0m
>> [0;36mDebug: Finishing transaction 38297820 [0m
>> Error: Could not prepare for execution: Got 3 failure(s) while
>> initializing: Cou
>> ld not set 'directory' on ensure: Permission denied -
>> C:/ProgramData/PuppetLabs/
>> puppet/var/state/graphs; Could not set 'directory' on ensure: Permission
>> denied
>> - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
>> Wrapped exception:
>> Permission denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs;
>> change fr
>> om absent to directory failed: Could not set 'directory' on ensure:
>> Permission d
>> enied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
>>
>>
>> So I hopped into the PuppetLabs directory and started looking at
>> permissions.  Everything is good up to
>> C:/ProgramData/PuppetLabs/puppet/var.  Meaning the Administrators group has
>> full control and can make modifications.  That is required for running
>> puppet agent manually outside of the service.  Every directory under
>> C:/ProgramData/PuppetLabs/puppet/var is good *except* for
>> C:/ProgramData/PuppetLabs/puppet/var/state.  That directory appears to have
>> been created by the service (system account) and does not have any
>> permissions for "Administrators" set.   I attempted to alter the
>> permissions, but I just get access denied even with an admin account.
>>
>> So in summary, the service times out for reasons unknown.  Running puppet
>> agent manually fails because Administrators cannot modify anything under
>> C:/ProgramData/PuppetLabs/puppet/var/state
>>
>> --
>> 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/73b52441-e66d-4661-bf1b-fc3737ec4912%40googlegroups.com
>> .
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Rob Reynolds
> Developer, Puppet Labs
>
> Join us at PuppetConf 2014, September 23-24 in San Francisco -
> http://bit.ly/pupconf14
> Register now and save 40%! Offer expires January 31st.
>



-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save 40%! Offer expires January 31st.

-- 
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/CAMJiBK7qeRGug2DYoDvTZ%2Bi_K6mnVHryj0Z_2eRTn2bRc2Ra_A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

[Rob Reynolds]

Can you blow away the C:/ProgramData/PuppetLabs directory and try the
install again?


On Mon, Jan 27, 2014 at 12:01 PM, Josh D  wrote:

>
>
> On Monday, January 27, 2014 10:34:36 AM UTC-7, Rob Reynolds wrote:
>>
>> Josh,
>>  Can you try something for me? With the install, can you add the
>> following to it?
>>
>> msiexec /qn /i themsilocation.msi PUPPET_AGENT_STARTUP_MODE=Manual
>>
>> And tell me if it installs okay?
>>
>>
> Yep, one step ahead of you.  We were able to install by changing the
> startup mode to manual.  Attempting to start the service post install,
> resulted in: Error 1053: The service did not respond to the start or
> control request in a timely fashion.
>
> There wasn't anything helpful in event viewer so we moved on to starting
> the agent manually.  The pertinent portion of the output from puppet agent
> --test --debug --verbose is below:
>
> Error: Could not set 'directory' on ensure: Permission denied -
> C:/ProgramData/P
> uppetLabs/puppet/var/state/graphs
> Error: Could not set 'directory' on ensure: Permission denied -
> C:/ProgramData/P
> uppetLabs/puppet/var/state/graphs
> Wrapped exception:
> Permission denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
> Error: /File[C:/ProgramData/PuppetLabs/puppet/var/state/graphs]/ensure:
> change f
> rom absent to directory failed: Could not set 'directory' on ensure:
> Permission
> denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
> [0;36mDebug: /File
> [C:/ProgramData/PuppetLabs/puppet/var/state/graphs]: Nothing to manage: no
> ensure and the resource doesn't exist [0m
> [0;36mDebug: Finishing transaction 38297820 [0m
> Error: Could not prepare for execution: Got 3 failure(s) while
> initializing: Cou
> ld not set 'directory' on ensure: Permission denied -
> C:/ProgramData/PuppetLabs/
> puppet/var/state/graphs; Could not set 'directory' on ensure: Permission
> denied
> - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
> Wrapped exception:
> Permission denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs;
> change fr
> om absent to directory failed: Could not set 'directory' on ensure:
> Permission d
> enied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
>
>
> So I hopped into the PuppetLabs directory and started looking at
> permissions.  Everything is good up to
> C:/ProgramData/PuppetLabs/puppet/var.  Meaning the Administrators group has
> full control and can make modifications.  That is required for running
> puppet agent manually outside of the service.  Every directory under
> C:/ProgramData/PuppetLabs/puppet/var is good *except* for
> C:/ProgramData/PuppetLabs/puppet/var/state.  That directory appears to have
> been created by the service (system account) and does not have any
> permissions for "Administrators" set.   I attempted to alter the
> permissions, but I just get access denied even with an admin account.
>
> So in summary, the service times out for reasons unknown.  Running puppet
> agent manually fails because Administrators cannot modify anything under
> C:/ProgramData/PuppetLabs/puppet/var/state
>
> --
> 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/73b52441-e66d-4661-bf1b-fc3737ec4912%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save 40%! Offer expires January 31st.

-- 
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/CAMJiBK74a%3DxTm384UDrTRFHamnFCg%2B3qThKEjM5Bm4K_PBBH-A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] How to execute a target action before this one when this one triggers

[Bret Wortman]

I'm looking at the case of distributing /etc/cups/printers.conf.

When this file changes, I'd like to distribute it. But before placing the 
new file, cupsd needs to be shut down, and restarted again afterwards. This 
can be done easily enough using an Exec to shut it down and the existing 
Service entry to trigger a restart, but how can I tell my manifest that 
when the File triggers, first do the Exec, then the File, then the Service?

Is there a way to chain these together to produce the effect I'm looking 
for? To stop a service before deploying a new config file, then start it up 
again?

file { '/etc/cups/printers.conf':
require => Package['cups'],
source => 'puppet:///modules/cups/printers.conf',
notify => Service['cupsd'],
:
}

service { 'cupsd':
ensure => running,
enable => true,
}

exec { 'stop-cupsd':
command => 'service cupsd stop',
:
}

-- 
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/2878a401-5bd8-4ac5-996f-79c4dc289724%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] What is the convention used if I want to pull content from source-control for populating a manifest resource?

[Mark Jaffe]

Manifest for an app:

class my_app {
.
.
.

   file { '/etc/sysconfig/my_app/configs':
ensure =>  directory,
mode  =>   0755,
source => 
 'https://subversion.mycompany.com/repository/project/trunk/model-config',
}

How would I provide user auth?

-- 
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/c0af66b3-a4c4-4f50-bdcd-e04a80b24a7e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: How to find the time when a Puppet manifest is executed

[elliott]

The fix I found for this is to schedule the task using an XML template with 
the  parameter specified (you can edit these settings under 
Task Properties > Triggers > Edit > Advanced).  The task repeats every 
minute for 15 minutes after the start time.

The StartBoundary parameter is set to the time on the Puppet server (this 
is the compile time for the manifest, so anywhere from 1 to 10 minutes 
before the run completes).  In reality the task will start the next minute 
after the run finishes, which is fine for my purposes.

It's UGLY, but it works :)

-- 
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/e64f4898-011c-4180-b6c7-9b0ab630fdd9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] How to find the time when a Puppet manifest is executed

[elliott]

On Monday, January 27, 2014 9:17:18 AM UTC-8, Felix.Frank wrote:
>
> Ugh, that's too bad. 
>
>
Haha, indeed.
 

> Also FWIW, I did this on linux using "echo  | at now+3min", which 
> works out of the box as long as "atd" is running. 
> Perhaps a similar crutch can be created using the Windows Task Scheduler. 
>

Thanks for the idea, however I couldn't find an easy way to get the time 3 
minutes from now in the Windows CLI (note: I am NOT a Windows script 
expert, there may be a way).

I did end up finding a way that will work for me.  It's ugly, but I'll 
document it for reference.


> Regards, 
> Felix 
>
> On 01/27/2014 06:07 PM, elliott wrote: 
> > Any ideas? The clients are all Windows, FWIW. 
>

-- 
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/e0157fc5-4169-4ea1-b671-e266ebbfcd2f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] environment variable inside a template

[Jose Luis Ledesma]

Nevermind, it's solved

-- 
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/8093392a-44de-4e36-be90-a186d9348971%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

[Josh D]

On Monday, January 27, 2014 10:34:36 AM UTC-7, Rob Reynolds wrote:
>
> Josh,
>  Can you try something for me? With the install, can you add the following 
> to it? 
>
> msiexec /qn /i themsilocation.msi PUPPET_AGENT_STARTUP_MODE=Manual
>
> And tell me if it installs okay?
>
>
Yep, one step ahead of you.  We were able to install by changing the 
startup mode to manual.  Attempting to start the service post install, 
resulted in: Error 1053: The service did not respond to the start or 
control request in a timely fashion.

There wasn't anything helpful in event viewer so we moved on to starting 
the agent manually.  The pertinent portion of the output from puppet agent 
--test --debug --verbose is below:

Error: Could not set 'directory' on ensure: Permission denied - 
C:/ProgramData/P
uppetLabs/puppet/var/state/graphs
Error: Could not set 'directory' on ensure: Permission denied - 
C:/ProgramData/P
uppetLabs/puppet/var/state/graphs
Wrapped exception:
Permission denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
Error: /File[C:/ProgramData/PuppetLabs/puppet/var/state/graphs]/ensure: 
change f
rom absent to directory failed: Could not set 'directory' on ensure: 
Permission
denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
 [0;36mDebug: /File
[C:/ProgramData/PuppetLabs/puppet/var/state/graphs]: Nothing to manage: no 
ensure and the resource doesn't exist [0m
 [0;36mDebug: Finishing transaction 38297820 [0m
Error: Could not prepare for execution: Got 3 failure(s) while 
initializing: Cou
ld not set 'directory' on ensure: Permission denied - 
C:/ProgramData/PuppetLabs/
puppet/var/state/graphs; Could not set 'directory' on ensure: Permission 
denied
- C:/ProgramData/PuppetLabs/puppet/var/state/graphs
Wrapped exception:
Permission denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs; 
change fr
om absent to directory failed: Could not set 'directory' on ensure: 
Permission d
enied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs


So I hopped into the PuppetLabs directory and started looking at 
permissions.  Everything is good up to 
C:/ProgramData/PuppetLabs/puppet/var.  Meaning the Administrators group has 
full control and can make modifications.  That is required for running 
puppet agent manually outside of the service.  Every directory under 
C:/ProgramData/PuppetLabs/puppet/var is good *except* for 
C:/ProgramData/PuppetLabs/puppet/var/state.  That directory appears to have 
been created by the service (system account) and does not have any 
permissions for "Administrators" set.   I attempted to alter the 
permissions, but I just get access denied even with an admin account.

So in summary, the service times out for reasons unknown.  Running puppet 
agent manually fails because Administrators cannot modify anything under 
C:/ProgramData/PuppetLabs/puppet/var/state

-- 
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/73b52441-e66d-4661-bf1b-fc3737ec4912%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppetmaster + hearbeat + mon

[Vassiliy Vins]

Hi!

2 puppetmasters and 1 client installed on VMware. I'm using  puppetversion 
3.4.2 on all 3 hosts

2 pupetmasters, one as primary  (hostname =puppetserver.ops.ss) , second 
(hostname=puppetslave) as secondary, client (hostname=client.ops.ss). High 
availability and all other steps  -  exactly as described on this link 
http://projects.puppetlabs.com/projects/1/wiki/High_Availability_Patterns

2 puppetmasters + 1 client  in 192.168.1.x network

2 puppetmasters connected via 10.0.0.x network for heartbeat purposes. ( 
primary 10.0.0.1, secondary 10.0.0.2,  redundant IP 192.168.1.200)
heartbeat works

I moved ca_crl.pem to secondary puppetmaster according to link above.

primary puppetmaster
*/etc/hosts*
127.0.0.1 puppetserver
192.168.1.20 client
192.168.1.30 puppetslave

*puppet.conf*
all defaults , only added in
[main]
ca =true


secondary puppetmaster
*/etc/hosts*
127.0.0.1 puppetslave
192.168.1.20client
192.168.1.10puppetserver.ops.ss

*puppet.conf*
[main]
server = puppetserver.ops.ss
listen = true
ca = false
ca_server = puppetserver.ops.ss

client
*/etc/hosts*
127.0.0.1client
192.168.1.200 puppetserver.ops.ss

*puppet.conf*
[main]
server = puppetserver.ops.ss
listen = true

Client machine gets certificate and puppet works with primary puppetmaster 
-   no problem at all.

Now I stop primary puppetmaster,   wait for secondary takes 192.168.1.200  
redundant ipand trying on client machine:
#puppet agent --server puppetserver.ops.ss --waitforcert 45 --test --verbose
trying to get certificate from secondary puppetmaster for testing purposes.

And I got respond :
Could not retrieve catalog from remote  server: Server hostname 
'puppetserver.ops.ss' did not match server certificate; expected puppetslave

Could you help me with the problem? What's wrong?   

#openss x509 -text -noout -in /var/lib/puppet/ssl/certs/ca.pem   on 
secondary puppetmaster
gives CN=Puppet  CA:puppetserver.ops.ss

in my understanding secondary puppetmaster shoud send respond  as primary 
one ("puppetserver.ops.ss"), when first one is dead 
and actually it does,  why client does not accept it?

Thank you for your help

























-- 
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/8d59db1d-14b4-44f6-987d-960d45938d36%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] environment variable inside a template

[Jose Luis Ledesma]

Is it possible to use the environment variable inside a template?

I use a ENC, and I want to avoid the :
Warning: Local environment: "production" doesn't match server specified 
node environment "201401", switching agent to "201401".

So I decided to setup puppet.conf inside one of my classes:

file { 'puppet.conf':
path=> '/etc/puppet/puppet.conf',
owner   => 'root',
group   => 'root',
mode=> '0644',
content => template("puppetserver/puppet.conf.rb"),
  }

With a template to setup the right environemnt:

# cat puppet.conf.rb
[main]
# The Puppet log directory.
# The default value is '$vardir/log'.
logdir = /var/log/puppet

# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
rundir = /var/run/puppet

# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = $vardir/ssl
environment = <% @environment %>

[...]

But when I run puppet agent -t

Notice: /Stage[main]/Puppetserver/File[puppet.conf]/content:
--- /etc/puppet/puppet.conf 2014-01-24 13:57:38.936012378 +0100
+++ /tmp/puppet-file20140127-16572-37fj6g-0 2014-01-27 
17:42:06.854923849 +0100
@@ -10,6 +10,7 @@
 # Where SSL certificates are kept.
 # The default value is '$confdir/ssl'.
 ssldir = $vardir/ssl
+environment =


It seems it is not able to read the environment variable. Any ideas?

thanks,

-- 
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/7f4adb4f-23e5-42df-8d91-7372786eea05%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

[Rob Reynolds]

Josh,
 Can you try something for me? With the install, can you add the following
to it?

msiexec /qn /i themsilocation.msi PUPPET_AGENT_STARTUP_MODE=Manual

And tell me if it installs okay?


Then we'll move onto trying to start the service and see what errors crop
up.


On Mon, Jan 27, 2014 at 10:57 AM, Josh D  wrote:

> On Friday, January 24, 2014 1:02:59 PM UTC-7, Rob Reynolds wrote:
>
>> The supported way of making it work is to update to at least 3.3.1.
>>
>
> Just tried installing the 3.4.2 client and had the same problem; service
> fails to start and the installation is rolled back.  The log is *slightly*
> different.
>
> StartServices: Service: Puppet Agent
>
> Error 1920. Service 'Puppet Agent' (puppet) failed to start.  Verify that
> you have sufficient privileges to start system services.
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37672 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37536 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 29532 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37384 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 38872 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 34136 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 33292 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 1136 could not be cancelled.
> Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 33376 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 32688 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 31448 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 31128 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 33536 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 30684 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 27924 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 11324 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37092 could not be
> cancelled. Error: 1168
> MSI (s) (94:8C) [09:41:44:708]: I/O on thread 30248 could not be
> cancelled. Error: 1168
> MSI (s) (94:D8) [09:41:44:708]: Product: Puppet -- Error 1920. Service
> 'Puppet Agent' (puppet) failed to start.  Verify that you have sufficient
> privileges to start system services.
> Are you sure you want to cancel?
> Action ended 9:41:50: InstallFinalize. Return value 3.
>
>
> --
> 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/17b9a371-7aa5-4894-bf23-0e1fc5be7b9c%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save 40%! Offer expires January 31st.

-- 
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/CAMJiBK4sm3Kuc8TjdF3kTKBiLB7o7NvS2CdxnULfz4fcx_cvww%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] How to find the time when a Puppet manifest is executed

[Felix Frank]

Ugh, that's too bad.

Also FWIW, I did this on linux using "echo  | at now+3min", which
works out of the box as long as "atd" is running.
Perhaps a similar crutch can be created using the Windows Task Scheduler.

Regards,
Felix

On 01/27/2014 06:07 PM, elliott wrote:
> Any ideas? The clients are all Windows, FWIW.

-- 
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/52E6949E.607%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] How to find the time when a Puppet manifest is executed

[elliott]

I'm wondering if anyone knows a good way to get the date and time when a 
portion of code in a Puppet manifest is actually *executed*. Sometimes my 
manifests take a long time to run, and I need to schedule a task to occur 
soon after the end of the run, no matter when that occurs.

I have tried the time() function, setting a variable using generate() (using 
the date function on the Puppet master), and even creating a custom fact, 
but everything I've tried gets evaluated when the manifests are *parsed* on 
the server, rather than when they actually execute on the client.

Any ideas? The clients are all Windows, FWIW.

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/436ba1f1-b8a1-426e-97f7-0b2ff7a9b25e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

[Josh D]

On Friday, January 24, 2014 1:02:59 PM UTC-7, Rob Reynolds wrote:
>
> The supported way of making it work is to update to at least 3.3.1.
>

Just tried installing the 3.4.2 client and had the same problem; service 
fails to start and the installation is rolled back.  The log is *slightly* 
different.

StartServices: Service: Puppet Agent
Error 1920. Service 'Puppet Agent' (puppet) failed to start.  Verify that 
you have sufficient privileges to start system services.
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37672 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37536 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 29532 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37384 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 38872 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 34136 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 33292 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 1136 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 33376 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 32688 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 31448 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 31128 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 33536 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 30684 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 27924 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 11324 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37092 could not be cancelled. 
Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 30248 could not be cancelled. 
Error: 1168
MSI (s) (94:D8) [09:41:44:708]: Product: Puppet -- Error 1920. Service 
'Puppet Agent' (puppet) failed to start.  Verify that you have sufficient 
privileges to start system services.
Are you sure you want to cancel?
Action ended 9:41:50: InstallFinalize. Return value 3.
 

-- 
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/17b9a371-7aa5-4894-bf23-0e1fc5be7b9c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Listing Unresponsive nodes

[Deepak Giridharagopal]

On Mon, Jan 27, 2014 at 7:12 AM, kaustubh chaudhari wrote:

> HI Vaibhav,
>
> I use the below procedure. Hope this helps you!
>
> ==
> Use the below procedure to delete the nodes permanantly!
>
> On Puppet Master Server
>
> # puppet node clean 
> # puppet node deactivate 
>

It's worth mentioning that in addition to "puppet node deactivate", which
explicitly asks for the given node to be removed, there are some options
available that will automatically deactivate nodes after a period of
inactivity:

http://docs.puppetlabs.com/puppetdb/1.5/configure.html#node-ttl
http://docs.puppetlabs.com/puppetdb/1.5/configure.html#node-purge-ttl

deepak


>
> ON Dashboard server
> # cd /usr/share/puppet-dashboard
> # rake RAILS_ENV=production node:del name=node_certname
> ==
>
> -Kaustubh
>
>
> On Monday, January 27, 2014 8:44:10 AM UTC-5, vaibhav gupta wrote:
>>
>> Hi All,
>>
>> Is there a way to list unresponsive nodes using a RAKE Task?
>>
>> Just to give the background for the need of such task: In our
>> organization we are having multiple instances of puppet master to manage
>> different set of environments (like DEV, QA, UAT, PROD). Just to verify the
>> configurations, puppet users connect QA host (agent) to puppet master
>> configured to serve requests to DEV machines and eventually results in
>> uploading the reports to DEV master. Once the verification is completed,
>> those nodes gets listed on the Dashboard in Unresponsive Section.
>>
>> I am looking out for a way to delete nodes which are in unresponsive
>> state through a cron job and thus need to check for the status of Node
>> using some RAKE Task.
>>
>> Regards
>> Vaibhav Gupta
>>
>  --
> 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/a7d612fa-3dc5-4965-a56a-8024d349f3d1%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAOjOXY3D7BMOvw37rtYnXpB79gbKLdO9v_7ydKcy7eW8jr-LOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Hash and loops

[jcbollinger]

On Sunday, January 26, 2014 7:13:51 AM UTC-6, thbe wrote:
>
> Hi @all,
>
> I try to pass a hash to a module class like this:
>
> class { 'modulename':
>   filecontent => {
> name1 => 'value1',
> name2 => 'value2',
> ...
> namex => 'valuex',
>   }
> }
>
> ​The class should take the hash list, loop over the list and create i.e. 
> file resources with namex and content valuex. What is the best way to do 
> this and, even more important, is it possible to do something like this?
>
>

Yes.  You can do it in a general way (i.e. without the restrictions in form 
imposed by create_resources()) by relying on array-titled resources.  You 
also need a function to extract the keys of a hash into an array, such as 
the keys() function available in PuppetLabs "stdlib" add-in module.  Then 
you do something like this:

class modulename ($filecontent) {
  $filenames = keys($filecontent)
  modulename::file { $filenames: }
}

define modulename::file () {
  $mycontent = $modulename::filecontent[$title]
  # do something with my content
}


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/6882b84f-453d-427c-9b69-cca547e71085%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Module ordering in nodes.pp

[jcbollinger]

On Monday, January 27, 2014 1:05:16 AM UTC-6, Sam Rajagopal wrote:
>
> I have nodes.pp defined as follows
>  
> node "abc.x.com", "123.x.com" {
> include module1
> include module2
> include module3
> }
>  
> Very simple definition. No parameterization, no scoping etc
> When I run "puppet agent -t" on the agent, I see the execution jumping to 
> module 3 after module 1. 
> Not sure how I can do "before" or "after" to say - execute module 2 only 
> if module 1 is successful.
>  
>


The order in which Puppet applies resources between which there are is no 
relationships is not predictable.  As Jose says, you can express 
relationships between classes via the chaining arrows, just as if classes 
were resources.  For example,

Class['module1'] => Class['module2'] => Class['module3']

That gives you both ordering and dependency: if an earlier resource 
[/class] in such a chain fails, then the later ones will not be applied.  
And that's sensible, because if there is no dependency between two classes 
/ resources then there should be no need for controlling their relative 
order of application.

 

> Also, I get different results when I run the agent second time. Say, 
> something was owned by app user. Next time it becomes, root user. 
> appreciate any help.
>


There is no way we can guess what might be causing the different results 
without examining the relevant manifests.


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/26054a93-4083-4cd1-a614-badf45db1797%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Composite namevars for custom Type

[Len]

Eric,

Thanks that addressed it. I should have tried that. :} 

Thanks again
Len


On Sunday, January 26, 2014 10:34:46 AM UTC-5, badgerious wrote:
>
> Len,
>
> I tried out your code, and it looks good (the resource in the puppet 
> manifest doesn't conform to the title pattern format, which causes a 
> different error, but the title_patterns method itself is being recognized). 
> I'd try restarting the puppetmaster. I've found this to be necessary when 
> making changes to types. 
>
> Eric
>
> On Saturday, January 25, 2014 10:20:46 PM UTC-6, Len wrote:
>>
>> John,
>>
>> Thanks for the link. What I think is happening, is that I am not 
>> overloading the title_patterns function/method correctly. I've followed 
>> some other examples I came across, including the one in the link. But it 
>> does not seem to be picking up the def self.title_patterns from the custom 
>> type. And I'm still learning ruby and the inner workings of puppet.
>>
>> Len
>>  
>>
>> On Saturday, January 25, 2014 12:08:18 PM UTC-5, Len wrote:
>>>
>>>
>>> Jan 23
>>> To all,
>>>
>>> I am on puppet 2.7.3 and I'm working on a custom RabbitMQ type, that 
>>> will use composite namevar.  I did not see any work out there already for 
>>> managing rabbitMQ bindings so I've started on one and I'm running into 
>>> problems with the composite namevar. I have a very basic type ( below ) but 
>>> when I run the puppet as an agent I still get the error "Error 400 on 
>>> SERVER: Could not render to pson: you must specify title patterns when 
>>> there are two or more key attributes"
>>>
>>> Any help or pointers would be appreciated.
>>>
>>> #Puppet Manifest: 
>>>
>>>   rabbitmq_binding { 'testing':
>>>
>>> source  => "src",
>>>
>>> destination => "dest",
>>>
>>>   }
>>>
>>> # Puppet Type
>>>
>>> Puppet::Type.newtype(:rabbitmq_binding) do
>>>
>>>   desc 'rabbitmq_binding creates a puppet type for managing rabbitMQ 
>>> binding'
>>>
>>>   def self.title_patterns
>>>
>>> [ [
>>>
>>> /^(.*):(.*)$/,  # pattern to parse :
>>>
>>> [
>>>
>>>   [:source, lambda{|x| x} ],
>>>
>>>   [:destination, lambda{|x| x} ]
>>>
>>> ] ]
>>>
>>> ]
>>>
>>>   end
>>>
>>>   newparam( :source ) do  
>>>
>>> isnamevar
>>>
>>>   end
>>>
>>>   newparam( :destination ) do
>>>
>>> isnamevar
>>>
>>>   end
>>>
>>> end
>>>
>>

-- 
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/b8a82622-7064-48d2-9160-a0dbde46f206%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard Groups

[kaustubh chaudhari]

Hi,

I was looking for a way to group the servers dynamically. Eg: create a 
"Windows" Group and all the existing nodes and new nodes should be part of 
"Windows" group.
I edit a group and then add each server, but practically its not possible 
with 2k servers in all!!

Is there a way to do that?

-Kaustubh

-- 
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/f38e02be-61e8-4694-aeeb-f0201d16a694%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Listing Unresponsive nodes

[kaustubh chaudhari]

HI Vaibhav,

I use the below procedure. Hope this helps you!

==
Use the below procedure to delete the nodes permanantly!

On Puppet Master Server

# puppet node clean 
# puppet node deactivate 

ON Dashboard server
# cd /usr/share/puppet-dashboard
# rake RAILS_ENV=production node:del name=node_certname
==

-Kaustubh

On Monday, January 27, 2014 8:44:10 AM UTC-5, vaibhav gupta wrote:
>
> Hi All,
>
> Is there a way to list unresponsive nodes using a RAKE Task? 
>
> Just to give the background for the need of such task: In our organization 
> we are having multiple instances of puppet master to manage different set 
> of environments (like DEV, QA, UAT, PROD). Just to verify the 
> configurations, puppet users connect QA host (agent) to puppet master 
> configured to serve requests to DEV machines and eventually results in 
> uploading the reports to DEV master. Once the verification is completed, 
> those nodes gets listed on the Dashboard in Unresponsive Section.
>
> I am looking out for a way to delete nodes which are in unresponsive state 
> through a cron job and thus need to check for the status of Node using some 
> RAKE Task. 
>
> Regards
> Vaibhav Gupta 
>

-- 
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/a7d612fa-3dc5-4965-a56a-8024d349f3d1%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Listing Unresponsive nodes

[vaibhav gupta]

Hi All,

Is there a way to list unresponsive nodes using a RAKE Task? 

Just to give the background for the need of such task: In our organization 
we are having multiple instances of puppet master to manage different set 
of environments (like DEV, QA, UAT, PROD). Just to verify the 
configurations, puppet users connect QA host (agent) to puppet master 
configured to serve requests to DEV machines and eventually results in 
uploading the reports to DEV master. Once the verification is completed, 
those nodes gets listed on the Dashboard in Unresponsive Section.

I am looking out for a way to delete nodes which are in unresponsive state 
through a cron job and thus need to check for the status of Node using some 
RAKE Task. 

Regards
Vaibhav Gupta 

-- 
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/2f7c6bd3-971c-4410-b040-af531cfb5990%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: file resource to provide serveral files

[Andreas Dvorak]

Hi,

thank you now it is working.

Best regards,
Andreas

-- 
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/ba52661e-31c0-49b6-bbe0-8b784057bf8f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.