date:20130722

[Puppet Users] look for puppet users in the Tucson area

2013-07-22 Thread Joshua Hoblitt


Hello,

I'm interested in organizing a PUG in the Tucson area with regular 
meetings on the University of Arizona campus.  However, I'm not actually 
aware of any users in the area external to $day_job.  If you are in the 
Tucson area or know someone who is, I'd be interested in meeting you 
even if your not interested in attending PUG meetings.


Cheers,

-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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet modules calling yum or repo's

2013-07-22 Thread Brendan O'Bra

The files are pulled from the agents - i.e. "yum install foo" or "svn up"
are run on the agent (and not the master).


On Mon, Jul 22, 2013 at 12:54 PM, Worker Bee  wrote:

> Hi Everyone;
>
> I am sorry if this sounds like a dumb question but, I am trying to
> troubleshoot an issue and want to make sure it is not my ignorance that is
> the issue.
>
> When using files from svn or yum repos in manifests, does the puppetmaster
> check out the files and then push them to the host?  So, does only the
> puupetmaster required access to the repo or does each target need access?
>
> Thank you
> Bee
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
GVoice: 707.410.0371
LinkedIn: http://www.linkedin.com/in/brendanobra

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Nagios resources

2013-07-22 Thread Pete Brown

On 23 July 2013 02:47, Matthew Nicholson  wrote:
> Jonathan,
>
> You would want to do it on the client level, when its exporting its host
> definition, like:
>
> @@nagios_host { $hostname:
>   ensure => present,
>   alias => $hostname,
>   address => $ipaddress,
>   use => $template,
>   hostgroups => $hostgroups,
>   notes => "$manufacturer $productname",
>   target => "/etc/nagios/conf.d/puppet/$hostname.cfg",
> }

I find it best to not use a target for the nagios resources.
The provider is only able to delete them if you use the default locations.

>
> etc.
>
>
> On Mon, Jul 22, 2013 at 10:08 AM, Jonathan Gazeley
>  wrote:
>>
>> Hi all,
>>
>> We've been using Puppet to write out our Nagios configs for ages. I think
>> I understand it pretty well. Recently we've had reason to set 'target' on
>> all Nagios resources, based on the fqdn of the monitored host. However I
>> don't want to have to set 'target' by hand on all Nagios resources (nor
>> remember to set it on all future ones).
>>
>> So my question is: what's the easiest way to bulk-set the 'target'
>> parameter according to the fqdn?
>>
>> So far I tried setting it on the Nagios server, which didn't work because
>> $::fqdn is always the name of the Nagios server, not the monitored host
>>
>>   Nagios_host <<| |>> {
>> notify => Service['nagios'],
>> target => "/etc/nagios/conf.d/${::fqdn}.cfg",
>>   }
>>
>> I also tried including this on the monitored host, which didn't work
>> because it attempts to realise all Nagios_host resources on the monitored
>> host, not the Nagios server.
>>
>> Nagios_host <<| |>> { target => "/etc/nagios/conf.d/${::fqdn}.cfg", }
>>
>> Is there an easy way to easily making all nagios_* resources have a
>> fqdn-specific target?
>>
>> Thanks,
>> Jonathan
>>
>> --
>> 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 post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>
>
>
> --
> Matthew Nicholson
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] How do I set global noop?

2013-07-22 Thread Sam Morrison

I'm trying to set a global noop but it doesn't seem possible,

There are 2 bugs open about this which to me look pretty serious as the 
expected behaviour isn't the case.

http://projects.puppetlabs.com/issues/21286
http://projects.puppetlabs.com/issues/6549

If anyone has a work around (that doesn't include modifying puppet.conf 
file) I would be very interested.

Cheers,
Sam


-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

2013-07-22 Thread Forrie

Adding --debug to the config.ru didn't provide any real info -- not sure 
why, but the client continued to connect and I see this in the log:

10.101.0.10 - - [22/Jul/2013:15:11:15 -0400] "GET 
/production/certificate/machine.ourdomain.com? HTTP/1.1" 404 62 "-" "-"

and nothing is returned.

I'm wondering if there is a permissions problem.  I can't imagine, as I've 
never touched it.

If I remove all the client SSL certs (backing them up), I presume I would 
really need to start over again -- that would require going to each client 
and removing the /var/lib/puppet directory and going through the setup 
process again.  

I'm willing to do that, at this point, since I'm not really getting 
anywhere figuring out what the problem is here.  I just want to make sure I 
do this properly.


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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

2013-07-22 Thread Forrie

I don't have selinux enabled on this system.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] chocolatey, windows, powershell and fault bucket

2013-07-22 Thread Francesco Sacchi

Hi,
I configured puppet open source with the  chocolatey module and one windows 
client.
When the puppet agent run as a service (not the interactive version) I can 
see in the windows event log some errors like

Fault bucket  1734820220, type 5
Event name: PowerShell

Fault bucket , type 0
Event name: PowerShell

I tried to google it but I did not find anything relevant apart from some 
discussions about running powershell in a thread or something similar..

Any hint on how to fix this?

Thanks

f.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Installing MSI failed with errror: The network name cannot be found.

2013-07-22 Thread Rob Reynolds

Can you send the manifest and output from puppet apply --debug --trace?

Also do you have the agent already installed?

--
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*


On Mon, Jul 22, 2013 at 5:34 AM, tinu  wrote:

> puppet apply --debug scomagent.pp:
>
>
> info: Loading facts in
> C:/ProgramData/PuppetLabs/puppet/var/lib/facter/defaultgateway.rb
>
> info: Loading facts in
> C:/ProgramData/PuppetLabs/puppet/var/lib/facter/networkadapters.rb
> warning: Deprecation notice:  Resource references should now be
> capitalized on line 22 in file
> //puppetmaster/puppet/development/modules/services/manifests/scomagent.pp
> warning: Deprecation notice:  Resource references should now be
> capitalized on line 27 in file
> //puppetmaster/puppet/development/modules/services/manifests/scomagent.pp
> debug: Creating default schedules
> debug: Failed to load library 'selinux' for feature 'selinux'
> debug: Puppet::Type::File::ProviderPosix: feature posix is missing
> debug: Failed to load library 'ldap' for feature 'ldap'
> debug: Failed to load library 'shadow' for feature 'libshadow'
> debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/ca.pem]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]
> debug:
> /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/server.domain.com.pem]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
> debug:
> /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys/server.domain.com.pem]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state]: Autorequiring
> File[C:/ProgramData/PuppetLabs/puppet/var]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/log]: Autorequiring
> File[C:/ProgramData/PuppetLabs/puppet/var]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/crl.pem]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/client_yaml]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/lib]: Autorequiring
> File[C:/ProgramData/PuppetLabs/puppet/var]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
> debug:
> /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys/server.domain.com.pem]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/resources.txt]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
> debug:
> /File[C:/ProgramData/PuppetLabs/puppet/var/state/last_run_summary.yaml]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts]: Autorequiring
> File[C:/ProgramData/PuppetLabs/puppet/var]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/graphs]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
> debug:
> /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certificate_requests]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/state.yaml]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/clientbucket]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/classes.txt]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
> debug:
> /File[C:/ProgramData/PuppetLabs/puppet/var/state/last_run_report.yaml]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]: Autorequiring
> File[C:/ProgramData/PuppetLabs/puppet/etc]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/client_data]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/var/run]: Autorequiring
> File[C:/ProgramData/PuppetLabs/puppet/var]
> debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]:
> Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
> debug:
> /File[C:/ProgramData/PuppetLabs/puppet/var/state/last_run_summary.yaml]/mode:
> mode changed '2000644' to '0644'
> debug: Finishing transaction 40182696
> debug: Loaded state in 0.00 seconds
> debug: Loaded state in 0.02 seconds
> info: Applying configuration version '1374223809'
> debug: /Schedule[daily]: Skipping device resources because running on a
> host
> debug: /Schedule[mon

Re: [Puppet Users] Pruning policy required ?

2013-07-22 Thread Ramin K


On 7/22/2013 11:53 AM, Reginald Choudari wrote:

I'm seeing on my puppetmasters that after a while, their
/var/lib/puppet/reports folder eventually hogs up all available disk
space. I'm just wondering how other people face this problem; is there
some puppet configuration that will take care of this. Otherwise, I can
implement a simple cron task.


There isn't an configuration that I'm aware of and I use the following cron.

# Puppet Name: puppet delete reports
43 * * * * find /var/lib/puppet/reports/ -mmin +300 -type f -print0 | 
xargs -0 -r rm > /dev/null 2>&1


300 minutes might be too quick depending on how you use reports or how 
much you care about them. Modify as needed.


Ramin

--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

2013-07-22 Thread Yaniv Kaul

I'd also disable or move to permissive selinux.
Y.

On Monday, July 22, 2013 10:19:35 PM UTC+3, Forrie wrote:
>
> Adding --debug to the config.ru didn't provide any real info -- not sure 
> why, but the client continued to connect and I see this in the log:
>
> 10.101.0.10 - - [22/Jul/2013:15:11:15 -0400] "GET /production/certificate/
> machine.ourdomain.com? HTTP/1.1" 404 62 "-" "-"
>
> and nothing is returned.
>
> I'm wondering if there is a permissions problem.  I can't imagine, as I've 
> never touched it.
>
> If I remove all the client SSL certs (backing them up), I presume I would 
> really need to start over again -- that would require going to each client 
> and removing the /var/lib/puppet directory and going through the setup 
> process again.  
>
> I'm willing to do that, at this point, since I'm not really getting 
> anywhere figuring out what the problem is here.  I just want to make sure I 
> do this properly.
>
>
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet modules calling yum or repo's

2013-07-22 Thread Worker Bee

Ok,

So, I am correct, each agent will need to be able to access the repo

Thanks for clarifying!

Bee


On Mon, Jul 22, 2013 at 4:01 PM, Brendan O'Bra wrote:

> The files are pulled from the agents - i.e. "yum install foo" or "svn up"
> are run on the agent (and not the master).
>
>
> On Mon, Jul 22, 2013 at 12:54 PM, Worker Bee wrote:
>
>> Hi Everyone;
>>
>> I am sorry if this sounds like a dumb question but, I am trying to
>> troubleshoot an issue and want to make sure it is not my ignorance that is
>> the issue.
>>
>> When using files from svn or yum repos in manifests, does the
>> puppetmaster check out the files and then push them to the host?  So, does
>> only the puupetmaster required access to the repo or does each target need
>> access?
>>
>> Thank you
>> Bee
>>
>> --
>> 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 post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
>
> --
> GVoice: 707.410.0371
> LinkedIn: http://www.linkedin.com/in/brendanobra
>
>  --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] AIX mcollective errors

2013-07-22 Thread Jonathan Reed

Each run of the mcollective is spitting out errors about being unable to 
connect to my virtual ethernet devices.

root@hostname# /opt/puppet/sbin/refresh-mcollective-metadata   
entstat: 0909-003 Unable to connect to device vi0, errno = 19
entstat: 0909-003 Unable to connect to device vi1, errno = 19
entstat: 0909-003 Unable to connect to device vi2, errno = 19
entstat: 0909-003 Unable to connect to device vi3, errno = 19
entstat: 0909-003 Unable to connect to device vi4, errno = 19
entstat: 0909-003 Unable to connect to device vi5, errno = 19
entstat: 0909-003 Unable to connect to device vi6, errno = 19

As a workaround I redirected stderr to dev/null, but has anyone else had 
this trouble on AIX?

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Pruning policy required ?

2013-07-22 Thread Dan White

"tidy" (http://docs.puppetlabs.com/references/latest/type.html#tidy) has been 
suggested. 

I have not had good luck with it. I tried use it to clean files off of an FTP 
server that were 7 days old. It would not remove directories. 
I used a cron job instead . Two find commands: 

/usr/bin/find  -depth -mindepth 2 ! -type d -ctime +7 -exec rm 
-v {} \; 
/usr/bin/find  -depth -mindepth 2 -type d -empty -exec rmdir -v 
{} \; 

The first one cleans out files older than 7 days. 
The second one cleans out empty directories. 


“Sometimes I think the surest sign that intelligent life exists elsewhere in 
the universe is that none of it has tried to contact us.” 
Bill Waterson (Calvin & Hobbes) 

- Original Message -
From: "Reginald Choudari"  
To: puppet-users@googlegroups.com 
Sent: Monday, July 22, 2013 2:53:48 PM 
Subject: [Puppet Users] Pruning policy required ? 

I'm seeing on my puppetmasters that after a while, their 
/var/lib/puppet/reports folder eventually hogs up all available disk space. I'm 
just wondering how other people face this problem; is there some puppet 
configuration that will take care of this. Otherwise, I can implement a simple 
cron task. 

THanks, 
Reginald 


-- 
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 post to this group, send email to puppet-users@googlegroups.com. 
Visit this group at http://groups.google.com/group/puppet-users . 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet modules calling yum or repo's

2013-07-22 Thread Worker Bee

Hi Everyone;

I am sorry if this sounds like a dumb question but, I am trying to
troubleshoot an issue and want to make sure it is not my ignorance that is
the issue.

When using files from svn or yum repos in manifests, does the puppetmaster
check out the files and then push them to the host?  So, does only the
puupetmaster required access to the repo or does each target need access?

Thank you
Bee

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Pruning policy required ?

2013-07-22 Thread Reginald Choudari

I'm seeing on my puppetmasters that after a while, their 
/var/lib/puppet/reports folder eventually hogs up all available disk space. 
I'm just wondering how other people face this problem; is there some puppet 
configuration that will take care of this. Otherwise, I can implement a 
simple cron task.

THanks,
Reginald

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

2013-07-22 Thread Rob Reynolds

What account are you running the service under?

--
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*


On Mon, Jul 22, 2013 at 9:51 AM, Francesco Sacchi  wrote:

> Hi,
> I configured puppet open source with the  chocolatey module and one
> windows client.
> When the puppet agent run as a service (not the interactive version) I can
> see in the windows event log some errors like
>
> Fault bucket  1734820220, type 5
> Event name: PowerShell
>
> Fault bucket , type 0
> Event name: PowerShell
>
> I tried to google it but I did not find anything relevant apart from some
> discussions about running powershell in a thread or something similar..
>
> Any hint on how to fix this?
>
> Thanks
>
> f.
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Stage is a metaparam warning

2013-07-22 Thread Jakov Sosic

# puppet master --compile web01.example.com > /dev/null
Warning: stage is a metaparam; this value will inherit to all contained
resources in the yum::repo::base definition
Warning: stage is a metaparam; this value will inherit to all contained
resources in the yum::repo::epel definition
Warning: stage is a metaparam; this value will inherit to all contained
resources in the yum::repo::atomic definition
Warning: stage is a metaparam; this value will inherit to all contained
resources in the yum::repo::rpmforge definition
Warning: stage is a metaparam; this value will inherit to all contained
resources in the yum::repo::srce definition
Warning: stage is a metaparam; this value will inherit to all contained
resources in the yum::repo::srce::intern definition
Warning: stage is a metaparam; this value will inherit to all contained
resources in the yum::repo::puppetlabs definition
Warning: stage is a metaparam; this value will inherit to all contained
resources in the yum::repo::ius definition
Warning: stage is a metaparam; this value will inherit to all contained
resources in the yum::repo::pgdg92 definition



This is example of one of the classes (yum::repo::pgdg92):

class yum::repo::pgdg92 (
  $stage   = 'yumsetup',
  $exclude  = [],
){
  require yum::repo::base

  file { '/etc/yum.repos.d/pgdg-92-centos.repo' :
ensure  => file,
mode=> '0644',
owner   => root,
group   => root,
source  =>
"puppet:///modules/yum/${::operatingsystem}/${::operatingsystemrelease}/pgdg-92-centos.repo",
require => Package['pgdg-centos92'],
  }

  # install package depending on major version
  case $::operatingsystemrelease {
default: {}
/^5.*/: {
  package { 'pgdg-centos92' :
ensure   => '9.2-6',
provider => 'rpm',
source   =>
'http://yum.postgresql.org/9.2/redhat/rhel-5-i386/pgdg-centos92-9.2-6.noarch.rpm',
}
}
/^6.*/: {
  package { 'pgdg-centos92' :
ensure   => '9.2-6',
provider => 'rpm',
source   =>
'http://yum.postgresql.org/9.2/redhat/rhel-6-i386/pgdg-centos92-9.2-6.noarch.rpm',
}
}
  }
}


So, what should I do with this warning?! Move stage (meta)parameter from
class to resources (file/package)? Or simply ignore it?

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Master and Puppet Dashboard Server Fails to Send Report to itself

2013-07-22 Thread phundisk

Anyone have any idea on debugging methods I could apply?  I have already 
tried the --debug method to the client run but I was not able to get any 
more information from that.

On Wednesday, July 10, 2013 4:44:06 PM UTC-4, phundisk wrote:
>
> I have a puppet master who cannot send its puppet report to the puppet 
> dashboard server, which is located on itself.  All the clients are 
> successfully sending the reports every time.  I have tried multiple options 
> on the puppet master but I have yet to figure out as to why this is not 
> sending correctly.  I have also put some of my puppet.conf configurations 
> below.  If anyone has any suggestions as to a better way to troubleshoot or 
> solve this, it would be greatly appreciated.
>
> I am seeing the following error on every run.
>
> err: Could not send report: Error 400 on SERVER: Could not intern from yaml:
> syntax error on line 74821, col 14: `!binary ?
> "RmlsZVsvdmFyL3d3dy9odG1sL2tpY2tzdGFydC9jZW50b3M1NC9DZW50T1Mv\ndC1ub2RlcHMtMS42LjUtMmpwcC4yLng4Nl82NC5ycG0kJO8kOCQsJCMkYW50\nLXNjcmlwdHMtMS42LjUtMmpwcC4yLng4Nl82NC5ycG0k7iQ4JCwkISRhbnQt\nc3dpbmctMV0=\n"'
>
>
>
> Puppet Master Puppet.conf  ( I have tried multiple values for serialization 
> such as yaml, b64_zlib_yaml, leaving blank, etc)
>
> [main]
> vardir = /var/lib/puppet
> report = true
> preferred_serialization_format = yaml
> logdir = /var/log/puppet
> rundir = /var/run/puppet
> ssldir = $vardir/ssl
>
> [puppetd]
>
>
>
> [agent]
>   environment = office
>   classfile = $vardir/classes.txt
>   pluginsync = true
>   libdir = $vardir/agent_lib
>   localconfig = $vardir/localconfig
>   report = true
>   reportfrom = currenseepup...@currensee.com
>   preferred_serialization_format = yaml
>
>
> [master]
> modulepath = $confdir/env/$environment/modules:$confdir/modules
> autosign = /etc/puppet/autosign.conf
> reports = tagmail,store,http
> reporturl = http://ops3.local.domain.com:3000/reports/upload
> tagmap = /etc/puppet/tagmail.conf
> ssl_client_header = SSL_CLIENT_S_DN
> ssl_client_verify_header = SSL_CLIENT_VERIFY
> storeconfigs = true
> thin_storeconfigs = true
> dbadapter = mysql
> dbuser=xxx
> dbpassword=xx
> dbserver=localhost
> preferred_serialization_format = yaml
>
>
>
> Puppet.conf on clients
>
> [main]
> vardir = /var/lib/puppet
> report = true
> logdir = /var/log/puppet
> rundir = /var/run/puppet
> ssldir = $vardir/ssl
>
> [puppetd]
>  environment = office
>
>
> [agent]
>   environment = office
>   classfile = $vardir/classes.txt
>   localconfig = $vardir/localconfig
>   report = true
>
>
> _
> This email and any files transmitted with it are confidential and intended 
> solely for the addressee.  If you received this email in error, please do 
> not disclose the contents to anyone; kindly notify the sender by return 
> email and delete this email and any attachments from your system.
>
> © 2011 Currensee Inc. is a member of the National Futures Association 
> (NFA) Member ID 0403251 | Over the counter retail foreign currency (Forex) 
> trading may involve significant risk of loss. It is not suitable for all 
> investors and you should make sure you understand the risks involved before 
> trading and seek independent advice if necessary. Performance, strategies 
> and charts shown are not necessarily predictive of any particular result 
> and past performance is no indication of future results. Investor returns 
> may vary from Trade Leader returns based on slippage, fees, broker spreads, 
> volatility or other market conditions.
>
> Currensee Inc | 54 Canal St 4th Floor | Boston, MA 02114 | +1.617.624.3824
>

-- 
_
This email and any files transmitted with it are confidential and intended 
solely for the addressee.  If you received this email in error, please do 
not disclose the contents to anyone; kindly notify the sender by return 
email and delete this email and any attachments from your system.

© 2011 Currensee Inc. is a member of the National Futures Association (NFA) 
Member ID 0403251 | Over the counter retail foreign currency (Forex) 
trading may involve significant risk of loss. It is not suitable for all 
investors and you should make sure you understand the risks involved before 
trading and seek independent advice if necessary. Performance, strategies 
and charts shown are not necessarily predictive of any particular result 
and past performance is no indication of future results. Investor returns 
may vary from Trade Leader returns based on slippage, fees, broker spreads, 
volatility or other market conditions.

Currensee Inc | 54 Canal St 4th Floor | Boston, MA 02114 | +1.617.624.3824

-- 
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 e

[Puppet Users] puppet ignoring dependencies

2013-07-22 Thread cko

hi everyone,

my *site.pp* looks like this:


node "server.my.fqdn" { 
   class { "puppet_agent": } 
   class {"base_config:
 require=>Class["puppet_agent"]
 }
}

im trying to achieve that the "puppet_agent" module is applied before the 
"base config" modules. 

however, the puppet_agent module gets installed LAST.

any ideas?

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

2013-07-22 Thread Francesco Sacchi

I have powershell 2.0 and .net framework 4.0 installed.
and if I run puppet_interactive everything works...

Il giorno lunedì 22 luglio 2013 17:16:28 UTC+2, Rob Reynolds ha scritto:
>
> Let's validate your settings. You should have powershell 2.0+ and .net 
> framework 4.0 installed. 
>
> On the box you can quickly validate powershell by opening a command shell 
> and typing powershell.
>
>
>
> --
> Rob Reynolds
> Developer, Puppet Labs
>
> *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
> http://bit.ly/pupconf13*
> **Register now and take advantage of the Final Countdown discount - save 
> 15%!*
>
>
> On Mon, Jul 22, 2013 at 10:09 AM, Francesco Sacchi 
> 
> > wrote:
>
>> I tried both with my own account (which is domain administrator) and with 
>> another (local) administrator..
>>
>> Il giorno lunedì 22 luglio 2013 17:02:32 UTC+2, Rob Reynolds ha scritto:
>>>
>>> What account are you running the service under?
>>>
>>> --
>>> Rob Reynolds
>>> Developer, Puppet Labs
>>>  
>>> *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
>>> http://bit.ly/pupconf13*
>>> **Register now and take advantage of the Final Countdown discount - 
>>> save 15%!*
>>>
>>>
>>> On Mon, Jul 22, 2013 at 9:51 AM, Francesco Sacchi wrote:
>>>
  Hi,
 I configured puppet open source with the  chocolatey module and one 
 windows client.
 When the puppet agent run as a service (not the interactive version) I 
 can see in the windows event log some errors like

 Fault bucket  1734820220, type 5
 Event name: PowerShell

 Fault bucket , type 0
 Event name: PowerShell

 I tried to google it but I did not find anything relevant apart from 
 some discussions about running powershell in a thread or something 
 similar..

 Any hint on how to fix this?

 Thanks

 f.

 -- 
 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.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group/puppet-users
 .
 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...@googlegroups.com .
>> To post to this group, send email to puppet...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/puppet-users.
>> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Nagios resources

2013-07-22 Thread Matthew Nicholson

Jonathan,

You would want to do it on the client level, when its exporting its host
definition, like:

@@nagios_host { $hostname:
  ensure => present,
  alias => $hostname,
  address => $ipaddress,
  use => $template,
  hostgroups => $hostgroups,
  notes => "$manufacturer $productname",
  target => "/etc/nagios/conf.d/puppet/$hostname.cfg",
}

etc.


On Mon, Jul 22, 2013 at 10:08 AM, Jonathan Gazeley <
jonathan.gaze...@bristol.ac.uk> wrote:

> Hi all,
>
> We've been using Puppet to write out our Nagios configs for ages. I think
> I understand it pretty well. Recently we've had reason to set 'target' on
> all Nagios resources, based on the fqdn of the monitored host. However I
> don't want to have to set 'target' by hand on all Nagios resources (nor
> remember to set it on all future ones).
>
> So my question is: what's the easiest way to bulk-set the 'target'
> parameter according to the fqdn?
>
> So far I tried setting it on the Nagios server, which didn't work because
> $::fqdn is always the name of the Nagios server, not the monitored host
>
>   Nagios_host <<| |>> {
> notify => Service['nagios'],
> target => "/etc/nagios/conf.d/${::fqdn}.**cfg",
>   }
>
> I also tried including this on the monitored host, which didn't work
> because it attempts to realise all Nagios_host resources on the monitored
> host, not the Nagios server.
>
> Nagios_host <<| |>> { target => "/etc/nagios/conf.d/${::fqdn}.**cfg", }
>
> Is there an easy way to easily making all nagios_* resources have a
> fqdn-specific target?
>
> Thanks,
> Jonathan
>
> --
> 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+unsubscribe@**googlegroups.com
> .
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at 
> http://groups.google.com/**group/puppet-users
> .
> For more options, visit 
> https://groups.google.com/**groups/opt_out
> .
>
>
>


-- 
Matthew Nicholson

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Nagios resources

2013-07-22 Thread Jonathan Gazeley


Hi all,

We've been using Puppet to write out our Nagios configs for ages. I 
think I understand it pretty well. Recently we've had reason to set 
'target' on all Nagios resources, based on the fqdn of the monitored 
host. However I don't want to have to set 'target' by hand on all Nagios 
resources (nor remember to set it on all future ones).


So my question is: what's the easiest way to bulk-set the 'target' 
parameter according to the fqdn?


So far I tried setting it on the Nagios server, which didn't work 
because $::fqdn is always the name of the Nagios server, not the 
monitored host


  Nagios_host <<| |>> {
notify => Service['nagios'],
target => "/etc/nagios/conf.d/${::fqdn}.cfg",
  }

I also tried including this on the monitored host, which didn't work 
because it attempts to realise all Nagios_host resources on the 
monitored host, not the Nagios server.


Nagios_host <<| |>> { target => "/etc/nagios/conf.d/${::fqdn}.cfg", }

Is there an easy way to easily making all nagios_* resources have a 
fqdn-specific target?


Thanks,
Jonathan

--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Module team update: 2013-07-15 - 2013-07-19

2013-07-22 Thread Ashley Penney

My apologizes to all the readers for not getting this out on Friday.  It
was 100F in my basement and it felt like I was melting, I completely forgot
in my rush to escape the house and survive until today.

Three weeks into working on modules and we're making steady progress.
 Things have slowed down a little from my side as I work against the
rabbitmq module and with the community to try and make some firm decisions
on design patterns, but hunner has flown ahead and kept our contributions
moving.  As a result we made the following releases last week:

http://forge.puppetlabs.com/puppetlabs/apache/0.8.0 - mostly bugfixes.
http://forge.puppetlabs.com/puppetlabs/ruby/0.0.2 - development work
http://forge.puppetlabs.com/puppetlabs/mysql/0.9.0 - backup features,
bugfixes
http://forge.puppetlabs.com/puppetlabs/postgresql/2.4.0 - features

We also moved two modules into our namespace (we're working on the
transition for these, we've never done this formally before):

http://forge.puppetlabs.com/puppetlabs/inifile/1.0.0
http://forge.puppetlabs.com/puppetlabs/pe_upgrade/1.0.0

And nothing to do with us, but while checking releases I found that
puppetdb was updated last week:

http://forge.puppetlabs.com/puppetlabs/puppetdb/1.5.0

Of all the above work I'd say postgresql is the most important set of
changes as hunner merged in and wrote some new features so these add some
significant capabilities to this module.

Thanks everyone if you hung in and read all of this, I hope your week is
full of temperate weather and productive puppeting.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

2013-07-22 Thread Rob Reynolds

So let's set the service to run under your user name. Once you've done
that, restart the service.

Also, do you have chocolatey already installed? or are you installing it
with puppet?

--
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*


On Mon, Jul 22, 2013 at 10:31 AM, Francesco Sacchi  wrote:

> I have powershell 2.0 and .net framework 4.0 installed.
> and if I run puppet_interactive everything works...
>
> Il giorno lunedì 22 luglio 2013 17:16:28 UTC+2, Rob Reynolds ha scritto:
>>
>> Let's validate your settings. You should have powershell 2.0+ and .net
>> framework 4.0 installed.
>>
>> On the box you can quickly validate powershell by opening a command shell
>> and typing powershell.
>>
>>
>>
>> --
>> Rob Reynolds
>> Developer, Puppet Labs
>>
>> *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
>> http://bit.ly/pupconf13*
>> **Register now and take advantage of the Final Countdown discount - save
>> 15%!*
>>
>>
>> On Mon, Jul 22, 2013 at 10:09 AM, Francesco Sacchi wrote:
>>
>>> I tried both with my own account (which is domain administrator) and
>>> with another (local) administrator..
>>>
>>> Il giorno lunedì 22 luglio 2013 17:02:32 UTC+2, Rob Reynolds ha scritto:

 What account are you running the service under?

 --
 Rob Reynolds
 Developer, Puppet Labs

 *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
 http://bit.ly/pupconf13*
 **Register now and take advantage of the Final Countdown discount -
 save 15%!*


 On Mon, Jul 22, 2013 at 9:51 AM, Francesco Sacchi wrote:

>  Hi,
> I configured puppet open source with the  chocolatey module and one
> windows client.
> When the puppet agent run as a service (not the interactive version) I
> can see in the windows event log some errors like
>
> Fault bucket  1734820220, type 5
> Event name: PowerShell
>
> Fault bucket , type 0
> Event name: PowerShell
>
> I tried to google it but I did not find anything relevant apart from
> some discussions about running powershell in a thread or something 
> similar..
>
> Any hint on how to fix this?
>
> Thanks
>
> f.
>
> --
> 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.
> To post to this group, send email to puppet...@googlegroups.com.
>
> Visit this group at 
> http://groups.google.com/**group**/puppet-users
> .
> For more options, visit 
> https://groups.google.com/**grou**ps/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...@**googlegroups.com.
>>> To post to this group, send email to puppet...@googlegroups.com.
>>> Visit this group at 
>>> http://groups.google.com/**group/puppet-users
>>> .
>>> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

2013-07-22 Thread Rob Reynolds

Let's validate your settings. You should have powershell 2.0+ and .net
framework 4.0 installed.

On the box you can quickly validate powershell by opening a command shell
and typing powershell.



--
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*


On Mon, Jul 22, 2013 at 10:09 AM, Francesco Sacchi  wrote:

> I tried both with my own account (which is domain administrator) and with
> another (local) administrator..
>
> Il giorno lunedì 22 luglio 2013 17:02:32 UTC+2, Rob Reynolds ha scritto:
>>
>> What account are you running the service under?
>>
>> --
>> Rob Reynolds
>> Developer, Puppet Labs
>>
>> *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
>> http://bit.ly/pupconf13*
>> **Register now and take advantage of the Final Countdown discount - save
>> 15%!*
>>
>>
>> On Mon, Jul 22, 2013 at 9:51 AM, Francesco Sacchi wrote:
>>
>>> Hi,
>>> I configured puppet open source with the  chocolatey module and one
>>> windows client.
>>> When the puppet agent run as a service (not the interactive version) I
>>> can see in the windows event log some errors like
>>>
>>> Fault bucket  1734820220, type 5
>>> Event name: PowerShell
>>>
>>> Fault bucket , type 0
>>> Event name: PowerShell
>>>
>>> I tried to google it but I did not find anything relevant apart from
>>> some discussions about running powershell in a thread or something similar..
>>>
>>> Any hint on how to fix this?
>>>
>>> Thanks
>>>
>>> f.
>>>
>>> --
>>> 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.
>>> To post to this group, send email to puppet...@googlegroups.com.
>>>
>>> Visit this group at 
>>> http://groups.google.com/**group/puppet-users
>>> .
>>> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

2013-07-22 Thread Francesco Sacchi

I tried both with my own account (which is domain administrator) and with 
another (local) administrator..

Il giorno lunedì 22 luglio 2013 17:02:32 UTC+2, Rob Reynolds ha scritto:
>
> What account are you running the service under?
>
> --
> Rob Reynolds
> Developer, Puppet Labs
>
> *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
> http://bit.ly/pupconf13*
> **Register now and take advantage of the Final Countdown discount - save 
> 15%!*
>
>
> On Mon, Jul 22, 2013 at 9:51 AM, Francesco Sacchi 
> 
> > wrote:
>
>> Hi,
>> I configured puppet open source with the  chocolatey module and one 
>> windows client.
>> When the puppet agent run as a service (not the interactive version) I 
>> can see in the windows event log some errors like
>>
>> Fault bucket  1734820220, type 5
>> Event name: PowerShell
>>
>> Fault bucket , type 0
>> Event name: PowerShell
>>
>> I tried to google it but I did not find anything relevant apart from some 
>> discussions about running powershell in a thread or something similar..
>>
>> Any hint on how to fix this?
>>
>> Thanks
>>
>> f.
>>
>> -- 
>> 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 .
>> To post to this group, send email to puppet...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/puppet-users.
>> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Report processor failed: Failed to update events: unknown DS name

2013-07-22 Thread WP Koh


can anyone help to advice on how should i troubleshoot this problem? It 
didn;t causing big issue but the message keep repeating in the message log.
I have checked there is no hostname as mentioned in manifest.

Report processor failed: Failed to update events: unknown DS name 'failure'

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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet resources and Nagios Contacts\Contactgroups

2013-07-22 Thread Jakov Sosic

On 02/11/2013 02:23 PM, JamieC wrote:

> And generating them with;
> 
> Nagios_contactgroup <<||>>
> Nagios_contact <<||>>
> 
> Is there a way to create a list such as ;
> name1:username1:emailaddress1
> name2:username2:emailaddress2
> 
> And "loop" the creation?

Puppet doesn't support loops in it's declarative language. You should
write a defined type, and pass it an array.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] How to check service status to write monit snippet.

2013-07-22 Thread Jakov Sosic

On 02/23/2013 06:33 PM, eduardo wrote:
>  Hi all.
>  I'm working on monit module. I have an array of services to configure
> monit via ENC.
>  I need a consistent module logic so services arriving as input
> parameter must running on node agent.
> 
>  I'm trying to find out if there is services running to configure monit
> snippets.
>  So, The snippet will be only written into /etc/monit/conf.d when
> service is running.
> 
>  Let's say an input parameter like :
> 
>   services => ['ntp','ssh']
> 
>  But ntp service is not running. In that case I need the snippet for
> 'ntp' service not be written on conf.d
> 
>  Is there simple way to do it ?.

Either you write your own facts that state if the service is running, or
use exported resources from modules that manage services.

First method isn't bullet proof, because if services are not running and
they are supposed to, monit checks won't be activated in the first place.

Second method forces other modules to add support to your specific monit
module implementation, so module won't be reusable. But I would go the
latter path.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Installing MSI failed with errror: The network name cannot be found.

2013-07-22 Thread tinu

 puppet apply --debug scomagent.pp:

info: Loading facts in 
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/defaultgateway.rb
info: Loading facts in 
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/networkadapters.rb
warning: Deprecation notice:  Resource references should now be capitalized 
on line 22 in file 
//puppetmaster/puppet/development/modules/services/manifests/scomagent.pp
warning: Deprecation notice:  Resource references should now be capitalized 
on line 27 in file 
//puppetmaster/puppet/development/modules/services/manifests/scomagent.pp
debug: Creating default schedules
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::File::ProviderPosix: feature posix is missing
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Failed to load library 'shadow' for feature 'libshadow'
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/ca.pem]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/server.domain.com.pem]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys/server.domain.com.pem]:
 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/log]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/crl.pem]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/client_yaml]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/lib]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys/server.domain.com.pem]:
 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/resources.txt]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/var/state/last_run_summary.yaml]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/graphs]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certificate_requests]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/state.yaml]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/clientbucket]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/classes.txt]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/var/state/last_run_report.yaml]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/etc]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/client_data]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/run]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/var/state/last_run_summary.yaml]/mode: 
mode changed '2000644' to '0644'
debug: Finishing transaction 40182696
debug: Loaded state in 0.00 seconds
debug: Loaded state in 0.02 seconds
info: Applying configuration version '1374223809'
debug: /Schedule[daily]: Skipping device resources because running on a host
debug: /Schedule[monthly]: Skipping device resources because running on a 
host
debug: /Schedule[hourly]: Skipping device resources because running on a 
host
debug: /Schedule[never]: Skipping device resources because running on a host
debug: /Schedule[weekly]: Skipping device resources because running on a 
host
debug: /Schedule[puppet]: Skipping device resources because running on a 
host
debug: Finishing transaction 40928160
debug: Storing state
debug: Stored state in 0.05 seconds
notice: Finished catalog run in 0.

[Puppet Users] Puppet kick exists with 0 even when puppet run has failures

2013-07-22 Thread MrTeleBird

Hello,

when applying this patch to my 
/usr/lib/ruby/site_ruby/1.8/puppet/application/kick.rb  file:
http://projects.puppetlabs.com/issues/6255


I get this error message:

 *undefined method `logs' for nil:NilClass*

anyone knows what am i missing??

thanks!!
Cesar

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: puppet master and fileserver separate problem

2013-07-22 Thread Aviar

thank you for reply, i change: ensure => present,
but still not work

在 2013年7月21日星期日UTC+8下午10时01分00秒，Sneha More写道：
>
> Hi Aviar,
>  I think you should try this once.
>
> class test {
> notify { "hello world": }
>
> file { '/home/puppet/hello':
> owner => "root",
> group => "root",
> mode => 644,
> ensure => present,
> source => 
> "puppet:///fileserver.uc.local/extra_files/hello",
> }
> }
>
> Regards, 
> Sneha,
> NTT DATA GTS. (OSS Centre)
>
>
> On Friday, July 19, 2013 4:11:24 PM UTC+5:30, Aviar wrote:
>>
>> my environment：
>>
>> 192.168.0.13puppet.uc.local
>> 192.168.0.14puppetca.uc.local
>> 192.168.0.15report.uc.local
>> 192.168.0.16fileserver.uc.local
>> 192.168.0.17agent01.uc.local
>>
>>
>> i want run a master as fileserver (fileserver.uc.local)
>> the puppet.uc.local and fileserver.uc.local use one ca.pem
>>
>> on puppet.uc.local, i wrote a class for test
>>
>> class test {
>> notify { "hello world": }
>>
>> file { '/home/puppet/hello':
>> owner => "root",
>> group => "root",
>> mode => 644,
>> ensure => "file",
>> source => 
>> "puppet://fileserver.uc.local/extra_files/hello",
>> }
>> }
>>
>> but i found that, the agent fetch file_metadata from fileserver.uc.local 
>> and fetch file_content from puppet.uc.local
>>
>> puppet.uc.local:
>> 
>> [2013-07-19 18:25:07] DEBUG accept: 192.168.0.17:43547
>> [2013-07-19 18:25:07] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked.
>> [2013-07-19 18:25:07] 192.168.0.17 - - [19/Jul/2013:18:25:07 CST] "GET 
>> /production/node/agent01.uc.local? HTTP/1.1" 200 4032
>> [2013-07-19 18:25:07] - -> /production/node/agent01.uc.local?
>> [2013-07-19 18:25:07] DEBUG close: 192.168.0.17:43547
>> [2013-07-19 18:25:07] DEBUG accept: 192.168.0.17:43549
>> [2013-07-19 18:25:07] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked.
>> [2013-07-19 18:25:07] 192.168.0.17 - - [19/Jul/2013:18:25:07 CST] "POST 
>> /production/catalog/agent01.uc.local HTTP/1.1" 200 1560
>> [2013-07-19 18:25:07] - -> /production/catalog/agent01.uc.local
>> [2013-07-19 18:25:07] DEBUG close: 192.168.0.17:43549
>> [2013-07-19 18:25:07] DEBUG accept: 192.168.0.17:43551
>> [2013-07-19 18:25:07] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked.
>> [2013-07-19 18:25:07] 192.168.0.17 - - [19/Jul/2013:18:25:07 CST] "GET 
>> /production/file_content/extra_files/hello HTTP/1.1" 200 1300
>> [2013-07-19 18:25:07] - -> /production/file_content/extra_files/hello
>> [2013-07-19 18:25:07] DEBUG close: 192.168.0.17:43551
>> [2013-07-19 18:25:07] DEBUG accept: 192.168.0.17:43552
>> [2013-07-19 18:25:07] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked.
>> [2013-07-19 18:25:07] 192.168.0.17 - - [19/Jul/2013:18:25:07 CST] "GET 
>> /production/file_content/extra_files/hello HTTP/1.1" 200 1300
>> [2013-07-19 18:25:07] - -> /production/file_content/extra_files/hello
>> [2013-07-19 18:25:07] DEBUG close: 192.168.0.17:43552
>> 
>>
>>
>> fileserver.uc.local:
>> 
>> [2013-07-19 18:25:07] DEBUG accept: 192.168.0.17:44945
>> [2013-07-19 18:25:07] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked.
>> [2013-07-19 18:25:07] 192.168.0.17 - - [19/Jul/2013:18:25:07 CST] "GET 
>> /production/file_metadatas/plugins?links=manage&recurse=true&ignore=.svn&ignore=CVS&ignore=.git&checksum_type=md5
>>  
>> HTTP/1.1" 200 278
>> [2013-07-19 18:25:07] - -> 
>> /production/file_metadatas/plugins?links=manage&recurse=true&ignore=.svn&ignore=CVS&ignore=.git&checksum_type=md5
>> [2013-07-19 18:25:07] DEBUG close: 192.168.0.17:44945
>> [2013-07-19 18:25:07] DEBUG accept: 192.168.0.17:44947
>> [2013-07-19 18:25:07] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked.
>> [2013-07-19 18:25:07] 192.168.0.17 - - [19/Jul/2013:18:25:07 CST] "GET 
>> /production/file_metadata/extra_files/hello?links=manage HTTP/1.1" 200 279
>> [2013-07-19 18:25:07] - -> 
>> /production/file_metadata/extra_files/hello?links=manage
>> [2013-07-19 18:25:07] DEBUG close: 192.168.0.17:44947
>> 
>>
>> why? am i make a mistake
>> i wish you could understand, english is not my native language
>>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Installing Puppet on Windows: Error 1053

2013-07-22 Thread Иван Кадочников

Thanks for the information, I somehow managed to not notice your response 
for several days.

On Wednesday, July 17, 2013 6:52:43 PM UTC+2, Josh Cooper wrote:
>
>
>
> On Wednesday, July 17, 2013 9:27:05 AM UTC-7, Иван Кадочников wrote:
>>
>> Hi all,
>>
>> I have trouble installing puppet open source 3.2.3 from the msi package 
>> on Windows 7 Home Basic.
>> The error message is "Service 'Puppet Agent' (puppet) failed to start. 
>> Verify that you have sufficient privileges to start system services."
>>
>> I am pretty sure it's not a privileges problem.
>> If (without closing the installer, as that would roll back everything) I 
>> open Services and try to start Puppet Agent manually it fails to start with
>> "Error 1053: The service did not respond to the start or control request 
>> in a timely fashion."
>>
>> This may be a timeout problem (the hardware is a netbook), but I doubt it.
>>
>> 1) Is there a way to install Puppet without installing or auto-starting 
>> the service? A checkbox in the installer would be nice.
>>
>
> This is http://projects.puppetlabs.com/issues/18268
>
> 2) Is there a way to avoid rolling back the whole installation if the 
>> service failed to start? A yes/no dialog would be nice. "Yes, I will start 
>> the service later manually, after I figure out what's wrong, thank you"
>>
>
> We're using WiX to build our MSI. I'm not sure if there is an option to do 
> this?
>
A search lead me to the ServiceInstall component parameter Vital, which 
controls if failing to start the service fails the whole install. On the 
other hand, changing this would surprise people doing automated setup. And 
now that I know there's a reason for the service not working I don't care 
about preventing rollback that much...

 
>
>> 3) What could be causing this, what can I do to work around this?
>> I have tried adding registry key 
>> \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout = 
>> 12 (googling error 1053 led me to believe it might help, but it did not)
>>
>> Then I tried to run Puppet directly (still without closing the installer):
>>
>> C:\Program Files\Puppet Labs\Puppet\bin>puppet.bat
>> C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-dir-
>> 0.3.7/lib/win32/dir.rb:54:in `strip': invalid byte sequence in US-ASCII 
>> (Argumen
>> tError)
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
>> ms/win32-dir-0.3.7/lib/win32/dir.rb:54:in `block in '
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
>> ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `each'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
>> ms/win32-dir-0.3.7/lib/win32/dir.rb:36:in `'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/ge
>> ms/win32-dir-0.3.7/lib/win32/dir.rb:13:in `'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:60:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:60:in `rescue in require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:35:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/facter/lib/facter/util/config.r
>> b:44:in `'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:36:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:36:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/facter/lib/facter/util/resoluti
>> on.rb:7:in `'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:36:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:36:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/facter/lib/facter/util/fact.rb:
>> 2:in `'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:36:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:36:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/facter/lib/facter.rb:23:in `> dule:Facter>'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/facter/lib/facter.rb:19:in `> p (required)>'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:36:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9
>> .1/rubygems/custom_require.rb:36:in `require'
>> from C:/Program Files/Puppet 
>> Labs/Puppet/puppet/lib/pu

Re: [Puppet Users] Re: Perform action when exported resources change

2013-07-22 Thread George Brown

Hi Sneha,

This is for a GPFS (IBM parallel file system) cluster. When a new client is
added it needs to be added by an node that is already part of the cluster.
I'm trying to automate this through puppet

E.g. node80 has just been provisioned

After installing the client packages I need to add the node from a server
already in the cluster by running the following two commands

mmaddnode -N node80
mmchlicense client --accept -N node80

Obviously I only want to have this exec run when a new host is added but I
also only want it to execute for the newly added host (I don’t want it to
run though nodes01-79 also).

Unfortunately I have to run the above commands as it appears GPFS does not
perform this config through plain text files.

Many thanks,
George




George Brown


On 19 July 2013 20:35, Sneha More  wrote:

> Hi George,
>   You can directly use the fact hostname as $hostname in your
> manifest.
>   So though the hostname changes, puppet will take the updated value
> of $hostname.
>   Will you please elaborate about the scenario for new node? Do you
> want to use this hostname for certification signing or in manifest?
>
> Regards,
> Sneha.
> NTT DATA GTS. Pune.
>
>
>
> On Thursday, July 18, 2013 8:04:10 PM UTC+5:30, George Brown wrote:
>>
>> Hello,
>>
>> I am trying to work out how to have one server perform an action when a
>> new host is added.
>>
>> Specifically it needs to execute a command containing the hostname of the
>> new node in order to accept a license. My questions are as follows
>>
>> 1) As I hostname is available as a fact is there a easy way to export
>> this rather than having an exec perform /bin/hostname?
>>
>> 2) When the resource is updated is their a way to show only the updated
>> contents?
>>
>> Please let me know if I'm going the wrong way and if there's a better way
>> to do this
>>
>> Many thanks
>> George
>>
>  --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] look for puppet users in the Tucson area

Re: [Puppet Users] Puppet modules calling yum or repo's

Re: [Puppet Users] Puppet Nagios resources

[Puppet Users] How do I set global noop?

Re: [Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

Re: [Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

[Puppet Users] chocolatey, windows, powershell and fault bucket

Re: [Puppet Users] Re: Installing MSI failed with errror: The network name cannot be found.

Re: [Puppet Users] Pruning policy required ?

Re: [Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

Re: [Puppet Users] Puppet modules calling yum or repo's

[Puppet Users] AIX mcollective errors

Re: [Puppet Users] Pruning policy required ?

[Puppet Users] Puppet modules calling yum or repo's

[Puppet Users] Pruning policy required ?

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

[Puppet Users] Stage is a metaparam warning

[Puppet Users] Re: Puppet Master and Puppet Dashboard Server Fails to Send Report to itself

[Puppet Users] puppet ignoring dependencies

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

Re: [Puppet Users] Puppet Nagios resources

[Puppet Users] Puppet Nagios resources

[Puppet Users] Module team update: 2013-07-15 - 2013-07-19

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

Re: [Puppet Users] chocolatey, windows, powershell and fault bucket

[Puppet Users] Report processor failed: Failed to update events: unknown DS name

Re: [Puppet Users] Puppet resources and Nagios Contacts\Contactgroups

Re: [Puppet Users] How to check service status to write monit snippet.

[Puppet Users] Re: Installing MSI failed with errror: The network name cannot be found.

[Puppet Users] Puppet kick exists with 0 even when puppet run has failures

[Puppet Users] Re: puppet master and fileserver separate problem

[Puppet Users] Re: Installing Puppet on Windows: Error 1053

Re: [Puppet Users] Re: Perform action when exported resources change

34 matches

Site Navigation

Mail list logo

Footer information