[Puppet Users] Puppet on Openelec

2014-07-02 Thread Ellick Johnson 
Anyone ever tried to get puppet on the Openelec OS? I want to keep all my 
XBMC configs updated.

Open Embedded Linux Entertainment Center (OpenELEC) is a small Linux 
distribution built from scratch as a platform to turn your computer into an 
XBMC  media center.

-Ellick

-- 
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/48061eeb-1c64-4beb-98e6-a553e7eff36a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Windows warning about source permissions

2014-07-02 Thread Rob Reynolds 
On Tue, Jul 1, 2014 at 9:53 PM, Michael Legleux  wrote:

> This warning is haunting me:
>
> Copying owner/mode/group from the source file on Windows is deprecated;
> use source_permissions => ignore.
>
> It is referenced here:
> http://docs.puppetlabs.com/windows/writing.html#managing-file-permissions
>
> I am not copying ANY files or anything yet, the site.pp is otherwise
> blank. What files are PUPPET copying?
> This folder is empty:
> so I put this in site.pp
> if $osfamily == 'windows' {
> File { source_permissions => ignore } }
> to no avail.
>
> Must I just live with this warning? What gives?
> Immediately after the warning it says
> Debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts.d]: Copying owner
> from the source file on Windows is deprecated; user source_permissions =>
> ignore.
> Debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts.d]: Copying mode
> from the source file on Windows is deprecated; user source_permissions =>
> ignore.
> Debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts.d]: Copying group
> from the source file on Windows is deprecated; user source_permissions =>
> ignore.
>
> C:/ProgramData/PuppetLabs/puppet/var/facts.d is empty!
>

Does the directory already exist? Perhaps the permissions are not set
correctly and something is attempting to create that.

What version of Puppet on the master? What version on the agent?


>
>  --
> 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/eb59f831-4eb6-491f-9a5d-c73f25f37b1c%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2014 , September
20-24 in San Francisco*
*Register by July 31st to take advantage of the Early Bird discount
 **--**save $249!*

-- 
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/CAMJiBK4v1dhy47TY5ywd0EU4tAT%3DajhH036-GFht_0%3DzGZoufA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Forge doesn't work reliably for me

2014-07-02 Thread Jesse Scott 
This appears to be a bug with how we report that you already have the 
latest available version for modules that only have a single release. I've 
opened a ticket in our bug tracker which you can follow here:

https://tickets.puppetlabs.com/browse/PUP-2882

If you have any additional information you would like to share related to 
this issue, you can do so on that ticket.


Thanks for the report!

-Jesse


On Tuesday, July 1, 2014 8:04:20 PM UTC-7, Michael Legleux wrote:
>
> I'm also seeing this on:
> https://forge.puppetlabs.com/rismoney/windowsnetwork
>
> On Monday, June 30, 2014 5:24:17 AM UTC-7, Jonathan Gazeley wrote:
>>
>> Recently I have been unable to upgrade some modules (or check for 
>> upgrades) from Puppet Forge using the module tool. 
>>
>> All of my modules were originally installed from the Forge. This problem 
>> only occurs with some modules but it always occurs. 
>>
>> [jg4461@puppet-prod ~]$ sudo puppet module upgrade ghoneycutt-sysklogd 
>> Notice: Preparing to upgrade 'ghoneycutt-sysklogd' ... 
>> Notice: Found 'ghoneycutt-sysklogd' (v1.0.0) in /etc/puppet/modules ... 
>> Notice: Downloading from https://forgeapi.puppetlabs.com ... 
>> Error: Could not upgrade 'ghoneycutt-sysklogd' (v1.0.0 -> latest) 
>>No releases are available from https://forgeapi.puppetlabs.com 
>>  Does 'ghoneycutt-sysklogd' have at least one published release? 
>>
>> Besides ghoneycutt-sysklogd, other modules I am unable to update are 
>> crayfishx-hiera_mysql and mkrakowitzer-stash. 
>>
>> I heard that this problem may be caused by an incorrect Modulefile but 
>> these look OK to me. All three modules exist on the Forge and with the 
>> same name, so I'm not sure what to check next. Any ideas? 
>>
>> Cheers, 
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/22637edb-6810-437e-a648-f2bc29d704ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PuppetDB: Problems with PID file missing

2014-07-02 Thread Ken Barber 
This is probably a long shot ... but we have this ticket here for PuppetDB:

https://tickets.puppetlabs.com/browse/PDB-675

It describes a scenario where when the PID file is missing, the
service script is unable to stop the running process. Now our solution
is simple, we have a fallback to kill any java process owned by
puppetdb if the PID file is missing, so easily worked around really
... however ...

The issue I wanted to talk about though, is why this is happening.

I'm looking for people who perhaps felt this kind of 'restart' pain
during upgrade. I had heaps of people mentioning this to me on the IRC
#puppet channel a few weeks ago, but it seems to have dried up. I was
foolish not to confirm the issue there and then, as I thought it was
easily replicable but its proven more elusive.

Has someone ran into the missing PID issue? Can you help me try to
track down the issue? The only information I have is that it was
during an upgrade, and only on Debian based boxes.

Thanks.

ken.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAE4bNTk6eFgUpGotu8DNCErOrjJ%2B2870R7kF0iW41ryOufR8mQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Reduce Duplicated File Attributes failure

2014-07-02 Thread Martin Alfke 
Hi,

you want to use file resource defaults for code de-deplucation.
resource defaults are references and the resource type starts with a capital 
letter.

You want:

File {
   ensure => 'file',
   owner => ,
   ...
}

Please always use ensure => file and not ensure => present.
The first one is more clear.

hth,

Martin


On 02 Jul 2014, at 17:05, Paolo Supino  wrote:

> Hi 
> 
> I'm trying to follow the process described in the link: 
> http://www.puppetcookbook.com/posts/remove-duplicated-file-resource-attributes.html
>  in a Puppet 2.7.x (x == 23 or 25) to try and reduce carpal tunnel 
> syndrome... ;-) 
> 
> but when I run puppet I get the following error: "err: Could not parse for 
> environment production: All resource specifications require names; expected 
> '%s' at init.pp:13" ...
> 
> Line 13 is the closing curly brace for the block (numbers on the left are the 
> line numbers as they appear in the editor): 
> 
>   8   file {
>   9 ensure  => 'present',
>  10 owner   => 'jboss',
>  11 group   => 'jboss',
>  12 mode=> '0775',
>  13   }
> 
> Can this be done with Puppet 2.7.x (I don't know for what version puppet 
> cookbook was written (the original one)
> 
> 
> 
> 
> 
> 
> 
> 
> TIA,
> Paolo 
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/CA%2BB25By4_KvX5s61N8G%3D3qLsH_3ZApYGSgbpkKP3f5qD2qe9ag%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/429F03C9-9F64-48B3-A308-74718C27%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: postrun command in windows

2014-07-02 Thread Rakesh Kathpal 
Yes.. it works perfectly from commandline..
On 2 Jul 2014 19:33, "Brahim Dagher"  wrote:

> Do you have success running 'puppet facts upload' from the command line?
>
> On Tuesday, July 1, 2014 7:38:40 AM UTC-4, Rakesh K wrote:
>>
>> Hi,
>>
>> My puppet.conf on windows looks like the following
>>
>> [main]
>> server="mypuppetmaster.com"
>> pluginsync=true
>> autoflush=true
>> environment=production
>> certname ="mypuppetagent.com"
>> report=true
>> postrun_command='puppet facts upload'
>>
>> When I am trying the puppet run, I am getting the error below
>>
>> *Error: Could not run command from postrun_command: CreateProcess()
>> failed: The system cannot find the file specified.*
>>
>> I even tried using the complete path but still same issue...
>>
>> I am using puppet 3.4.2., please let me know if there is any resolution
>> for this issue..
>>
>> Thanks,
>>
>> Rakesh K.
>>
>  --
> 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/b8935d03-9dd1-48e4-9efe-c26877624003%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAEJrXMW_hshroTEyathLMM%3DiL7kPgn0zZzn5hMfU4zMJ3XDa8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] rpm exits 0 on scriptlet failure

2014-07-02 Thread Christopher Wood 
This is where my mileage varies from yours; I would have the rpm install files 
and leave the data munging to an exec or type/provider where the error will 
show through to puppet. I don't see a puppet issue here, in the same manner 
that a bug in an init script is not a puppet service (type) issue.

I've never been on board the do-complicated-things-in-rpms train and your 
experience is why.

On Wed, Jul 02, 2014 at 07:51:10AM -0700, Raul Macian wrote:
>I have a problem that starts to make me think that puppet is not usable to
>install packages. I will explain:
>There is a common situation when you put some code on the %post when
>creating rpm. In my case I am executing some db migrations after the
>installation has been performed. The problems rises when something goes
>wrong in the scriptlet because the yum command will ignore the failure end
>exits with a succesful code. To add more complexity the yum provider
>performs a yum -q command, that means no output on your logs. So you don't
>know if the installation has ended ok or not.
>Here explains some things exposed
>https://bugzilla.redhat.com/show_bug.cgi?id=569930
> 
>--
>You received this message because you are subscribed to the Google Groups
>"Puppet Users" group.
>To unsubscribe from this group and stop receiving emails from it, send an
>email to [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/341271db-3ac7-4330-ba23-4dd6a1f51952%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/341271db-3ac7-4330-ba23-4dd6a1f51952%40googlegroups.com?utm_medium=email&utm_source=footer
>3. https://groups.google.com/d/optout

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/20140702172128.GA3865%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Do modules need to be installed on agents?

2014-07-02 Thread zerozerounouno 
Il giorno martedì 1 luglio 2014 04:25:23 UTC+2, Garrett Honeycutt ha 
scritto:
 

> I agree with Rich. The issue you are likely facing with the selinux 
> module is that the directory is 'spiette-selinux' instead of 'selinux' 
>

The path was right, but thank you very much (to both of you) for the 
answers and the interesting pointers.

In the meantime I did a global software upgrade (puppet master, puppet 
agent, foreman...) and things started working as expected, but I'll give a 
read to those interesting docs anyway.

Marco.

-- 
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/9cca90d8-d1ca-4221-b5a8-34f7c052a8b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Hiera variables working only with explicit mode

2014-07-02 Thread Louis Coilliot 
Hello,

with a puppet master version 3.5, I only get hiera override if I set the
variables if I used the explicit syntax.

Example : $myvar=hiera('mymod::myvar,'failback')

What did I miss to enable implicit override ?

On other platform I set, this is working fine implicitly.

The puppet master is linked to a Foreman, maybe this is related.

Thanks in advance.

Louis Coilliot

-- 
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/CAE9jN30q0_7Hk382gH2D2O2Awi%2BQ3rG6C6j4tC6%2BFzAH3c9-yA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Reduce Duplicated File Attributes failure

2014-07-02 Thread Matthew Hyclak 
You need to tell puppet what file you would like those attributes set.
Probably

file {
  '/etc/jboss.conf':
ensure => 'present',
owner  => 'jboss',
group   => 'jboss',
mode   => '0755'.
}

which would create a blank file at /etc/jboss.conf.

If you need to control the contents of the file, you would need a source or
content parameter.

Matt


On Wed, Jul 2, 2014 at 11:05 AM, Paolo Supino 
wrote:

> Hi
>
> I'm trying to follow the process described in the link:
> http://www.puppetcookbook.com/posts/remove-duplicated-file-resource-attributes.html
> in a Puppet 2.7.x (x == 23 or 25) to try and reduce carpal tunnel
> syndrome... ;-)
>
> but when I run puppet I get the following error: "err: Could not parse for
> environment production: All resource specifications require names; expected
> '%s' at init.pp:13" ...
>
> Line 13 is the closing curly brace for the block (numbers on the left are
> the line numbers as they appear in the editor):
>
>   8   file {
>   9 ensure  => 'present',
>  10 owner   => 'jboss',
>  11 group   => 'jboss',
>  12 mode=> '0775',
>  13   }
>
> Can this be done with Puppet 2.7.x (I don't know for what version puppet
> cookbook was written (the original one)
>
>
>
>
>
>
>
>
> TIA,
> Paolo
>
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CA%2BB25By4_KvX5s61N8G%3D3qLsH_3ZApYGSgbpkKP3f5qD2qe9ag%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAO7w0s6Q5iH11Orf6FNDGgqdc2KzUL-YKmz31FT5AcpH-ZS_tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Reduce Duplicated File Attributes failure

2014-07-02 Thread Paolo Supino 
Hi

I'm trying to follow the process described in the link:
http://www.puppetcookbook.com/posts/remove-duplicated-file-resource-attributes.html
in a Puppet 2.7.x (x == 23 or 25) to try and reduce carpal tunnel
syndrome... ;-)

but when I run puppet I get the following error: "err: Could not parse for
environment production: All resource specifications require names; expected
'%s' at init.pp:13" ...

Line 13 is the closing curly brace for the block (numbers on the left are
the line numbers as they appear in the editor):

  8   file {
  9 ensure  => 'present',
 10 owner   => 'jboss',
 11 group   => 'jboss',
 12 mode=> '0775',
 13   }

Can this be done with Puppet 2.7.x (I don't know for what version puppet
cookbook was written (the original one)








TIA,
Paolo

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BB25By4_KvX5s61N8G%3D3qLsH_3ZApYGSgbpkKP3f5qD2qe9ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] rpm exits 0 on scriptlet failure

2014-07-02 Thread Raul Macian 
I have a problem that starts to make me think that puppet is not usable to 
install packages. I will explain:

There is a common situation when you put some code on the %post when 
creating rpm. In my case I am executing some db migrations after the 
installation has been performed. The problems rises when something goes 
wrong in the scriptlet because the yum command will ignore the failure end 
exits with a succesful code. To add more complexity the yum provider 
performs a yum -q command, that means no output on your logs. So you don't 
know if the installation has ended ok or not.

Here explains some things exposed

https://bugzilla.redhat.com/show_bug.cgi?id=569930

-- 
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/341271db-3ac7-4330-ba23-4dd6a1f51952%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] augeas error with erwbgy/system module

2014-07-02 Thread Dominic Cleal 
On 01/07/14 21:38, Arpin Dominique (Nter) wrote:
> Hi,
> 
> I install the erwbgy/system module, I have those errors :
> 
> Debug: Augeas[ntp-servers](provider=augeas): Opening augeas with root /, lens 
> path , flags 64
> Debug: Augeas[ntp-servers](provider=augeas): Augeas version 1.2.0 is installed
> Warning: Augeas[ntp-servers](provider=augeas): Loading failed for one or more 
> files, see debug for /augeas//error output
> Debug: Augeas[ntp-servers](provider=augeas): /augeas/files/etc/ntp.conf/error 
> = parse_failed
> Debug: Augeas[ntp-servers](provider=augeas): 
> /augeas/files/etc/ntp.conf/error/pos = 163
> Debug: Augeas[ntp-servers](provider=augeas): 
> /augeas/files/etc/ntp.conf/error/line = 8
> Debug: Augeas[ntp-servers](provider=augeas): 
> /augeas/files/etc/ntp.conf/error/char = 0
> Debug: Augeas[ntp-servers](provider=augeas): 
> /augeas/files/etc/ntp.conf/error/lens = 
> /usr/share/augeas/lenses/dist/ntp.aug:126.14-129.45:
> Debug: Augeas[ntp-servers](provider=augeas): 
> /augeas/files/etc/ntp.conf/error/message = Iterated lens matched less than it 
> should
> Debug: Augeas[ntp-servers](provider=augeas): Will attempt to save and only 
> run if files changed
> Debug: Augeas[ntp-servers](provider=augeas): Closed the augeas connection
> Error: /Stage[main]/Ntp::Config/Augeas[ntp-servers]: Could not evaluate: 
> Unknown command
> 
> I'm using Puppet 3.6.2 with RHEL 5 32bits clients...
> 
> Someone had this error?

It's a problem parsing ntp.conf on line 8.  Please open a ticket at
https://github.com/hercules-team/augeas/issues and include a copy of
ntp.conf so we can see the issue.

Cheers,

-- 
Dominic Cleal
Red Hat Engineering

-- 
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/53B41781.8080001%40redhat.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: postrun command in windows

2014-07-02 Thread Brahim Dagher 
Do you have success running 'puppet facts upload' from the command line?

On Tuesday, July 1, 2014 7:38:40 AM UTC-4, Rakesh K wrote:
>
> Hi,
>
> My puppet.conf on windows looks like the following
>
> [main]
> server="mypuppetmaster.com"
> pluginsync=true
> autoflush=true
> environment=production
> certname ="mypuppetagent.com"
> report=true
> postrun_command='puppet facts upload'
>
> When I am trying the puppet run, I am getting the error below
>
> *Error: Could not run command from postrun_command: CreateProcess() 
> failed: The system cannot find the file specified.*
>
> I even tried using the complete path but still same issue...
>
> I am using puppet 3.4.2., please let me know if there is any resolution 
> for this issue..
>
> Thanks,
>
> Rakesh K.
>

-- 
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/b8935d03-9dd1-48e4-9efe-c26877624003%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: How to handle java home in module?

2014-07-02 Thread Gavin Williams 
John

Cheers for the response... 

It's quite possibly i'm over-thinking the possible permeations on the Java 
side, and probably need to strip it back to as simple as possible. 
In that vein, I've gone with your suggestion of asserting what the 
JAVA_HOME *will be* once the relevant package has been installed by this 
module. 

Will get the latest changes pushed shortly for comment.

Cheers
Gavin 

On Wednesday, 2 July 2014 14:09:50 UTC+1, jcbollinger wrote:
>
>
>
> On Wednesday, July 2, 2014 5:06:46 AM UTC-5, Gavin Williams wrote:
>>
>> Morning all
>>
>> I'm currently working on a module[1] to support installation and 
>> configuration of Apache Karaf[2], a Java OSGi container... 
>>
>> I've got most of the installation piece sorted, and am starting to work 
>> on the configuration side of things. 
>> Unfortunately I've hit a bit of a blocker which I'm not sure of the best 
>> way to work-around. 
>>
>> As part of the service installation process, a Java wrapper config file 
>> is created. 
>> This config file needs to be modified to specify the 'JAVA_HOME' value. 
>> However I'm not sure of the best way to calculate this JAVA_HOME value, due 
>> to the variable nature of both Java variants (Java 6 vs 7, Oracle vs 
>> OpenJDK, release version) and the fact that Java might not be installed at 
>> the start of the Puppet run. 
>> The intention is to use a template for the config file, so it's 
>> modifiable by Puppet. 
>>
>> Options I can think of: 
>>
>>1. Use a fact to provide JAVA_HOME. This fails if Java isn't 
>>installed at the start of the agent run, which is a valid scenario if 
>> this 
>>module is also installing Java... 
>>2. Hard code the value based on a pre-determined file path based on 
>>chosen Java distro and version. Not very clean/configurable...
>>3. Update wrapper config file to pull in system env for JAVA_HOME. 
>>However this fails if the system version isn't the one that the app 
>> should 
>>use... 
>>
>> Am I missing a trick somewhere along the lines, or is hoping to achieve 
>> all this - Install Java, Install Karaf, configure Karaf service - in one 
>> run asking too much? 
>>
>
> Your criticisms of those options present an inconsistent view of your 
> requirements.  If the app needs to use a specific Java version that may be 
> different from the system's default (per remarks about #3) then it's going 
> to be pretty tricky to get the correct value from a fact, too (alternative 
> #1).  That seems to say that knowing the requisite Java version in advance 
> (#2) is one of your requirements, so whether that's clean or configurable 
> is irrelevant.
>  
>
>> Thoughts/ideas welcome. 
>>
>
> Since you are managing the Java package, in principle you can know what 
> JAVA_HOME you will need based on which package you are ensuring installed.  
> That is, you can know what the appropriate JAVA_HOME *will be* once 
> Puppet is done because it is (or can be) part of what you are managing, 
> albeit indirectly.
>
> If you want to be a little less prescriptive and a little more adaptive, 
> at the risk of possibly needing two runs to reach a stable configuration, 
> then you could try a combination of your alternatives 1 and 2: use a custom 
> fact to try to choose JAVA_HOME from among those of the runtimes available 
> before the run, and if there isn't any (or if none is suitable) then use a 
> prediction based on knowledge of what you are about to install.  Honestly, 
> though, this seems harder and messier than my previous alternative.
>
>
> 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/368007c0-f334-4105-8245-17b593b7c5aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Service start and stop

2014-07-02 Thread Satish Katuru 

Hi,

Please see my init.pp file.

First I am stopping the Jboss server and then deleting few folders,copying 
files and then trying to start the service.

When I place file copy statements it is not working. With out file copy 
statements I am able to stop the service and start the service.

I am not sure why it is happening like that.

Can any one give us suggestions?


I am using below command for the execution:

*sudo puppet agent -t --waitforcert=60 (with debug)*


Service stop and folder deletion was successfull.But When I Included the 
file copy statements like below Service is not getting started.
( 

file 

{

"/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/deploy/RulesService-1.0.esb":

ensure => "present",

mode => "0644",

owner => "katusa02",

group => "katusa02",

source => "puppet://$puppetserver/modules/httpd/RulesService-1.0.esb",

 

}
)


*Init.pp*

class httpd
{


service{
"stopjavaservice.sh":
ensure =>"stopped",
}



file 

{

"/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/tmp":
ensure => "absent",
force => "true",
recurse => "true",
owner => "katusa02",

}


file 

{

"/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/work":
ensure => "absent",
force => "true",
recurse => "true",
owner => "katusa02",

}



file 

{

"/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/log":
ensure => "absent",
force => "true",
recurse => "true",
owner => "katusa02",

}

file 

{

"/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/data":
ensure => "absent",
force => "true",
recurse => "true",
owner => "katusa02",

}


file 

{

"/home/katusa02/JBossRuntime/log":
ensure => "absent",
force => "true",
recurse => "true",
owner => "katusa02",

}

file 

{

"/home/katusa02/JBossRuntime/data":
ensure => "absent",
force => "true",
recurse => "true",
owner => "katusa02",

}


file 

{

"/home/katusa02/JBossRuntime/server.log":
ensure => "absent",
force => "true",
recurse => "true",
owner => "katusa02",

}


service{
"startjavaservice.sh":
ensure =>"running",
}


}



Am i Missing any thing here? Do I need to wait for some amount of time for 
each run?

Regards,
Sathish.

-- 
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/36548962-43e4-4970-ad4d-a842aafaf713%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppetlabs Firewall

2014-07-02 Thread jcbollinger 


On Tuesday, July 1, 2014 9:30:57 AM UTC-5, Danny Roberts wrote:
>
> I am using the Puppetlabs firewall module to manage our firewall. All 
> servers get our core ruleset:
>
> *[...]*This worked perfectly when I spun up a server with no role (and 
> therefore no extra rules. However when I spun up servers with the 'puppet' 
> & 'database' roles (and therefore the extra rules) it hung at:
>
>
> *Notice: /Stage[main]/Mycompany/Firewall[9001 
> fe701ab7ca74bd49f13b9f0ab39f3254]/ensure: removed*
> My SSH session eventually disconnects with a broken pipe. The puppet 
> server I spun up yesterday was available when I got into the office this 
> morning so it seems they do eventually come back but it takes some time. Is 
> there any reason I am getting cut of like that and is there any way to 
> avoid it?
>


I'm a little confused.  What does your SSH session have to do with it?  I 
don't find it especially surprising that an existing SSH connection gets 
severed when the destination machine's firewall is manipulated by Puppet, 
if that's what you're describing.  I would not necessarily have predicted 
it, but in retrospect it seems reasonable.

I'm supposing that you were connected remotely via SSH to the machine on 
which the agent was running, following the progress of the run in real 
time.  In that case, are you certain that the run was in fact interrupted 
at all?  Maybe the output from the remote side was curtailed when your SSH 
connection was disrupted, but the run continued.  Or if you were running 
un-daemonized, then perhaps the run was interrupted when severing the SSH 
connection produced a forced logout from the controlling terminal.

Any way around, the fact that the subject systems eventually recover on 
their own makes me suspect that the problem lies in how you were monitoring 
the run, rather than in your manifests.  You could try running puppet in 
daemon mode, or otherwise disconnected from a terminal, and checking the 
log after the fact to make sure everything went as it should.


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/6f941798-d072-42c1-ad6a-147318ea89c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: How to handle java home in module?

2014-07-02 Thread jcbollinger 


On Wednesday, July 2, 2014 5:06:46 AM UTC-5, Gavin Williams wrote:
>
> Morning all
>
> I'm currently working on a module[1] to support installation and 
> configuration of Apache Karaf[2], a Java OSGi container... 
>
> I've got most of the installation piece sorted, and am starting to work on 
> the configuration side of things. 
> Unfortunately I've hit a bit of a blocker which I'm not sure of the best 
> way to work-around. 
>
> As part of the service installation process, a Java wrapper config file is 
> created. 
> This config file needs to be modified to specify the 'JAVA_HOME' value. 
> However I'm not sure of the best way to calculate this JAVA_HOME value, due 
> to the variable nature of both Java variants (Java 6 vs 7, Oracle vs 
> OpenJDK, release version) and the fact that Java might not be installed at 
> the start of the Puppet run. 
> The intention is to use a template for the config file, so it's modifiable 
> by Puppet. 
>
> Options I can think of: 
>
>1. Use a fact to provide JAVA_HOME. This fails if Java isn't installed 
>at the start of the agent run, which is a valid scenario if this module is 
>also installing Java... 
>2. Hard code the value based on a pre-determined file path based on 
>chosen Java distro and version. Not very clean/configurable...
>3. Update wrapper config file to pull in system env for JAVA_HOME. 
>However this fails if the system version isn't the one that the app should 
>use... 
>
> Am I missing a trick somewhere along the lines, or is hoping to achieve 
> all this - Install Java, Install Karaf, configure Karaf service - in one 
> run asking too much? 
>

Your criticisms of those options present an inconsistent view of your 
requirements.  If the app needs to use a specific Java version that may be 
different from the system's default (per remarks about #3) then it's going 
to be pretty tricky to get the correct value from a fact, too (alternative 
#1).  That seems to say that knowing the requisite Java version in advance 
(#2) is one of your requirements, so whether that's clean or configurable 
is irrelevant.
 

> Thoughts/ideas welcome. 
>

Since you are managing the Java package, in principle you can know what 
JAVA_HOME you will need based on which package you are ensuring installed.  
That is, you can know what the appropriate JAVA_HOME *will be* once Puppet 
is done because it is (or can be) part of what you are managing, albeit 
indirectly.

If you want to be a little less prescriptive and a little more adaptive, at 
the risk of possibly needing two runs to reach a stable configuration, then 
you could try a combination of your alternatives 1 and 2: use a custom fact 
to try to choose JAVA_HOME from among those of the runtimes available 
before the run, and if there isn't any (or if none is suitable) then use a 
prediction based on knowledge of what you are about to install.  Honestly, 
though, this seems harder and messier than my previous alternative.


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/131d4f3a-df97-4ed1-b29d-322e5903d673%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Stop and Start Services running on Puppet Master or Agent Machine

2014-07-02 Thread Satish Katuru 
Hi,

You were correct.We should put our source files under Files folder.

On Tuesday, July 1, 2014 6:50:02 PM UTC+5:30, jcbollinger wrote:
>
>
>
> On Tuesday, July 1, 2014 3:32:12 AM UTC-5, Satish Katuru wrote:
>>
>> Yes,the folder is present in the Agent machine.The thing is in the Master 
>> Server it is unable to locate the Source file itself.
>>
>
> Not necessarily.  The master is unable to *read* the file, but that does 
> not necessarily mean it cannot *locate* it.
>
> The master will be looking for this file:
>
>   /httpd/files/hello
>
> Note the "files/" segment of the filesystem path, which does not appear in 
> the URI.  Note also, again, that your source URI does not match the 
> destination file name in that the source has no ".txt" extension.  The 
> source URI doesn't need to match the destination name (at all), but 
> typically it does.  The mismatch could be a sign that the URI does not 
> match the actual name of the source file (which it does need to do, of 
> course).
>
> Supposing that the source file exists, in the correct location, and with a 
> name matching the given source URI, the master still needs to be able to 
> read it.  Check the ownership and permissions of the source file, and if 
> SELinux is running in enforcing mode on the master then check that the 
> source file is labelled such that Puppet can read it.  Note here that the 
> master normally runs as an unprivileged user (often named "puppet").
>
>
> 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/843c90c1-c052-4604-b948-35a078dbeaa3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Explorer 1.0.0

2014-07-02 Thread Erik Dalén 
We would like to announce the first open source release of a web interface
for Puppet that we have created internally at Spotify.

Puppet Explorer is a web application for PuppetDB that lets you explore your
Puppet data.
It is made using AngularJS and CoffeeScript and runs entirely on the client
side, so the only backend that is needed is PuppetDB itself and a web
server to
share the static resources.

It has the same query language as the popular Puppet module
 dalen-puppetdbquery (https://forge.puppetlabs.com/dalen/puppetdbquery).
This lets you easily filter for a selection of nodes and show the events or
facts for only them. So you can handle hosts as groups without needing to
have
predefined groups, just make them up as you need and click on the pie
charts to
drill down further.

All views in the application are made to be able to link directly to them,
so
it is easy to share information you find with coworkers.

It has support for multiple PuppetDB servers.

It is using the V4 PuppetDB API, so therefore it needs PuppetDB 2.0. This is
currently marked as experimental, so PuppetDB 2.1 will likely break
compatibility but we should be able to create a fix for that quickly.

The source, more info and screenshots can be found at the Github page:
https://github.com/spotify/puppetexplorer

A built version of it ready for installation can be found here:
tar.gz:
http://dl.bintray.com/dalen/puppetexplorer/puppetexplorer-1.0.0.tar.gz
deb:
http://dl.bintray.com/dalen/puppetexplorer-apt/puppetexplorer_1.0.0-1_amd64.deb

A initial puppet module to manage it can be found here:
https://github.com/spotify/puppet-puppetexplorer

-- 
Erik Dalén
Systems Engineer, Site Reliability Engineering

-- 
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/CANn3uq1E3t4fQ0C8Ep%2B71jnMqixgPEmphPPHUevVfQe3vfxehg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: puppetlabs-firewall issue

2014-07-02 Thread Pablo Morales 
Cory Thank you very much!!! that was the issue...

target prot opt source   destination 
ACCEPT icmp --  0.0.0.0/00.0.0.0/0   /* 000 accept 
all icmp */ 
ACCEPT all  --  0.0.0.0/00.0.0.0/0   /* 001 accept 
all to lo interface */ 
ACCEPT all  --  0.0.0.0/00.0.0.0/0   /* 002 accept 
related established rules */ ctstate RELATED,ESTABLISHED 
ACCEPT tcp  --  0.0.0.0/00.0.0.0/0   multiport 
ports 80,443 /* 100 allow http and https access */ 
DROP   all  --  0.0.0.0/00.0.0.0/0   /* 999 drop 
all */ 


Thank for your time and support
Regards


El miércoles, 2 de julio de 2014 06:23:46 UTC-3, Cory Stoker escribió:
>
> Hmm... 
>
> Do you have plugin sync turned on in the agent config?  Should see 
> something like pluginsync = true in your puppet.conf.  The error 
> specified seems to be having an issue fining the type which is sync'ed 
> from the master to the agents through plugin sync. 
>
> On Tue, Jul 1, 2014 at 1:50 PM, Pablo Morales  > wrote: 
> > If it helps this is what I see when running in debug mode: 
> > 
> > debug: /Stage[main]/My_fw::Post/Firewall[999 drop all]/require: requires 
> > Class[My_fw::Pre] 
> > debug: /Stage[main]/My_fw::Pre/Firewall[001 accept all to lo 
> > interface]/before: requires Firewall[002 accept related established 
> rules] 
> > debug: /Stage[main]/Firewall::Linux::Redhat/require: requires 
> > Package[iptables] 
> > debug: /Stage[main]/My_fw::Pre/Firewall[000 accept all icmp]/before: 
> > requires Firewall[001 accept all to lo interface] 
> > debug: /Stage[main]/My_fw::Pre/Firewall[100 allow http and https 
> > access]/before: requires Class[My_fw::Post] 
> > debug: /Stage[main]/My_fw::Pre/Firewall[002 accept related established 
> > rules]/before: requires Class[My_fw::Post] 
> > debug: /Stage[main]/Users/User[pepe]: Autorequiring Group[shame] 
> > 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: Prefetching yum resources for package 
> > debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm 
> --version' 
> > debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -qa 
> > --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| 
> %{VERSION} 
> > %{RELEASE} %{ARCH} 
> > '' 
> > debug: Service[iptables](provider=redhat): Executing '/sbin/service 
> iptables 
> > status' 
> > debug: Puppet::Type::Service::ProviderRedhat: Executing '/sbin/chkconfig 
> > iptables' 
> > 
> > 
> > El martes, 1 de julio de 2014 16:17:30 UTC-3, Pablo Morales escribió: 
> >> 
> >> Hi there guys 
> >> I'm new to puppet I thinks it's a great tool and I'm trying to 
> configure 
> >> some task to perform automatically like users and some services which I 
> had 
> >> no 
> >> problems until now with iptables, this is what I'v got 
> >> 
> >> server and client: 
> >> CentOS release 6.5 (Final) 
> >> 
> >> On client: 
> >> puppet-2.7.25-2.el6.noarch 
> >> 
> >> On server: 
> >> puppet-server-3.6.2-1.el6.noarch 
> >> puppet-3.6.2-1.el6.noarch 
> >> 
> >> I'm following this: 
> >> https://forge.puppetlabs.com/puppetlabs/firewall 
> >> 
> >> My config on server: 
> >> /etc/puppet/modules/my_fw/manifests 
> >> post.pp 
> >> pre.pp 
> >> class my_fw::post { 
> >>   firewall { '999 drop all': 
> >> proto   => 'all', 
> >> action  => 'drop', 
> >> before  => undef, 
> >>   } 
> >> } 
> >> 
> >> class my_fw::pre { 
> >>   Firewall { 
> >> require => undef, 
> >>   } 
> >> 
> >>   # Default firewall rules 
> >>   firewall { '000 accept all icmp': 
> >> proto   => 'icmp', 
> >> action  => 'accept', 
> >>   }-> 
> >>   firewall { '001 accept all to lo interface': 
> >> proto   => 'all', 
> >> iniface => 'lo', 
> >> action  => 'accept', 
> >>   }-> 
> >>   firewall { '002 accept related established rules': 
> >> proto   => 'all', 
> >> ctstate => ['RELATED', 'ESTABLISHED'], 
> >> action  => 'accept', 
> >>   } 
> >> 
> >>   firewall { '100 allow http and https access': 
> >> port   => [80, 443], 
> >> proto  => tcp, 
> >> action => accept, 
> >>   } 
> >> 
> >> } 
> >> 
> >> /etc/puppet/manifests 
> >> site.pp 
> >> # tell puppet on which client to run the class 
> >> node slnxserver { 
> >> 
> >> include users 
> >> 
> >> #resources { "firewall": 
> >> #purge => true 
> >> #} 
> >> 
> >> Firewall { 
> >> before  => Class['my_fw::post'], 
> >> require => Class['my_fw::pre'], 
> >> } 
> >> 
> >> class { ['my_fw::pre', 'my_fw::post']: } 
> >> class { 'firewall': } 
> >> } 
> >> 
> >> On the client I see the f

[Puppet Users] How to handle java home in module?

2014-07-02 Thread Gavin Williams 
Morning all

I'm currently working on a module[1] to support installation and 
configuration of Apache Karaf[2], a Java OSGi container... 

I've got most of the installation piece sorted, and am starting to work on 
the configuration side of things. 
Unfortunately I've hit a bit of a blocker which I'm not sure of the best 
way to work-around. 

As part of the service installation process, a Java wrapper config file is 
created. 
This config file needs to be modified to specify the 'JAVA_HOME' value. 
However I'm not sure of the best way to calculate this JAVA_HOME value, due 
to the variable nature of both Java variants (Java 6 vs 7, Oracle vs 
OpenJDK, release version) and the fact that Java might not be installed at 
the start of the Puppet run. 
The intention is to use a template for the config file, so it's modifiable 
by Puppet. 

Options I can think of: 

   1. Use a fact to provide JAVA_HOME. This fails if Java isn't installed 
   at the start of the agent run, which is a valid scenario if this module is 
   also installing Java... 
   2. Hard code the value based on a pre-determined file path based on 
   chosen Java distro and version. Not very clean/configurable...
   3. Update wrapper config file to pull in system env for JAVA_HOME. 
   However this fails if the system version isn't the one that the app should 
   use... 
   
Am I missing a trick somewhere along the lines, or is hoping to achieve all 
this - Install Java, Install Karaf, configure Karaf service - in one run 
asking too much? 

Thoughts/ideas welcome. 

Cheers
Gavin

[1] https://github.com/fatmcgav/fatmcgav-karaf/tree/develop
[2] http://karaf.apache.org/index.html

-- 
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/7a7de688-a945-4db3-8d0e-6c4bceec5799%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet.conf documentation ammendment

2014-07-02 Thread Johan De Wit 

The best way is to file a ticket against the documentation.

Here is an example of one I did some time ago : 
https://tickets.puppetlabs.com/browse/DOCUMENT-97


Grts

Jo

On 02/07/14 11:26, James Green wrote:
Could someone kindly add a notice bar to the puppet.conf web 
documentation stating that:


/Changes to puppet.conf are picked up automatically by the puppet 
agent. You can observe this by making a change and tailing syslog for 
a few moments./


There are a few google results teaching us how to declare puppet as a 
service with a subscription to puppet.conf, which appears unnecessary 
given the above :)


Thanks,

James

--
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/CAMH6%2Bax9T5BKt%2BCwuCWeG8tzcEDOX17YRStdDMrocyWzhN5GPQ%40mail.gmail.com 
.

For more options, visit https://groups.google.com/d/optout.



--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer  (805008667232363)
Puppet Certified Professional 2013/2014 (PCP006)
_
 
Open-Future Phone +32 (0)2/255 70 70

Zavelstraat 72  Fax   +32 (0)2/255 70 71
3071 KORTENBERG Mobile+32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_
 



Next Events:
Linux Training | https://www.open-future.be/linux-training-8-till-12th-september
Puppet Introduction Course | 
https://www.open-future.be/puppet-introduction-course-15th-september
Puppet Fundamentals Training | https://www.open-future.be/puppet-fundamentals-training-16-till-18th-september 
Zabbix Certified Specialist | https://www.open-future.be/zabbix-certified-specialisttraining-22-till-24th-september

Zabbix Certified Professional | 
https://www.open-future.be/zabbix-certified-professional-training-25-till-26th-september
Subscribe to our newsletter | http://eepurl.com/BUG8H

--
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/53B3D47D.1080605%40open-future.be.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet.conf documentation ammendment

2014-07-02 Thread James Green 
Could someone kindly add a notice bar to the puppet.conf web documentation
stating that:

*Changes to puppet.conf are picked up automatically by the puppet agent.
You can observe this by making a change and tailing syslog for a few
moments.*

There are a few google results teaching us how to declare puppet as a
service with a subscription to puppet.conf, which appears unnecessary given
the above :)

Thanks,

James

-- 
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/CAMH6%2Bax9T5BKt%2BCwuCWeG8tzcEDOX17YRStdDMrocyWzhN5GPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: puppetlabs-firewall issue

2014-07-02 Thread Cory Stoker 
Hmm...

Do you have plugin sync turned on in the agent config?  Should see
something like pluginsync = true in your puppet.conf.  The error
specified seems to be having an issue fining the type which is sync'ed
from the master to the agents through plugin sync.

On Tue, Jul 1, 2014 at 1:50 PM, Pablo Morales  wrote:
> If it helps this is what I see when running in debug mode:
>
> debug: /Stage[main]/My_fw::Post/Firewall[999 drop all]/require: requires
> Class[My_fw::Pre]
> debug: /Stage[main]/My_fw::Pre/Firewall[001 accept all to lo
> interface]/before: requires Firewall[002 accept related established rules]
> debug: /Stage[main]/Firewall::Linux::Redhat/require: requires
> Package[iptables]
> debug: /Stage[main]/My_fw::Pre/Firewall[000 accept all icmp]/before:
> requires Firewall[001 accept all to lo interface]
> debug: /Stage[main]/My_fw::Pre/Firewall[100 allow http and https
> access]/before: requires Class[My_fw::Post]
> debug: /Stage[main]/My_fw::Pre/Firewall[002 accept related established
> rules]/before: requires Class[My_fw::Post]
> debug: /Stage[main]/Users/User[pepe]: Autorequiring Group[shame]
> 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: Prefetching yum resources for package
> debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm --version'
> debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -qa
> --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION}
> %{RELEASE} %{ARCH}
> ''
> debug: Service[iptables](provider=redhat): Executing '/sbin/service iptables
> status'
> debug: Puppet::Type::Service::ProviderRedhat: Executing '/sbin/chkconfig
> iptables'
>
>
> El martes, 1 de julio de 2014 16:17:30 UTC-3, Pablo Morales escribió:
>>
>> Hi there guys
>> I'm new to puppet I thinks it's a great tool and I'm trying to configure
>> some task to perform automatically like users and some services which I had
>> no
>> problems until now with iptables, this is what I'v got
>>
>> server and client:
>> CentOS release 6.5 (Final)
>>
>> On client:
>> puppet-2.7.25-2.el6.noarch
>>
>> On server:
>> puppet-server-3.6.2-1.el6.noarch
>> puppet-3.6.2-1.el6.noarch
>>
>> I'm following this:
>> https://forge.puppetlabs.com/puppetlabs/firewall
>>
>> My config on server:
>> /etc/puppet/modules/my_fw/manifests
>> post.pp
>> pre.pp
>> class my_fw::post {
>>   firewall { '999 drop all':
>> proto   => 'all',
>> action  => 'drop',
>> before  => undef,
>>   }
>> }
>>
>> class my_fw::pre {
>>   Firewall {
>> require => undef,
>>   }
>>
>>   # Default firewall rules
>>   firewall { '000 accept all icmp':
>> proto   => 'icmp',
>> action  => 'accept',
>>   }->
>>   firewall { '001 accept all to lo interface':
>> proto   => 'all',
>> iniface => 'lo',
>> action  => 'accept',
>>   }->
>>   firewall { '002 accept related established rules':
>> proto   => 'all',
>> ctstate => ['RELATED', 'ESTABLISHED'],
>> action  => 'accept',
>>   }
>>
>>   firewall { '100 allow http and https access':
>> port   => [80, 443],
>> proto  => tcp,
>> action => accept,
>>   }
>>
>> }
>>
>> /etc/puppet/manifests
>> site.pp
>> # tell puppet on which client to run the class
>> node slnxserver {
>>
>> include users
>>
>> #resources { "firewall":
>> #purge => true
>> #}
>>
>> Firewall {
>> before  => Class['my_fw::post'],
>> require => Class['my_fw::pre'],
>> }
>>
>> class { ['my_fw::pre', 'my_fw::post']: }
>> class { 'firewall': }
>> }
>>
>> On the client I see the following:
>> tail -f /var/log/messages
>> Jul  1 16:01:09 slnxserver puppet-agent[16431]: Finished catalog run in
>> 0.35 seconds
>> Jul  1 16:02:41 slnxserver puppet-agent[16431]: Finished catalog run in
>> 0.33 seconds
>> Jul  1 16:04:13 slnxserver puppet-agent[16431]: Finished catalog run in
>> 0.30 seconds
>> Jul  1 16:05:45 slnxserver puppet-agent[16431]: Finished catalog run in
>> 0.28 seconds
>> Jul  1 16:07:17 slnxserver puppet-agent[16431]: Finished catalog run in
>> 0.29 seconds
>>
>> No problems reported, but it seems the iptables rules are not applied, am
>> I missing somthing else?
>>
>> The 80:443 ports is not applied:
>>
>> iptables -nL
>> Chain INPUT (policy ACCEPT)
>> target prot opt source   destination
>>
>> Chain FORWARD (policy ACCEPT)
>> target prot opt source   destination
>>
>> Chain OUTPUT (policy ACCEPT)
>> target prot opt source   destination
>>
>> If I uncomment the resource statement above I get:
>> puppet-agent[16431]: Failed to apply catalog: Parameter name failed on
>> Resources[firewall]: Could not find resource type 'firewall' at
>> /etc/puppet/manifests/si