date:20160530

Re: [Puppet Users] Puppet and SVN

2016-05-30 Thread Alex Samad

Hi


Finally got some time to look at this


On 24 May 2016 at 11:22, Rob Nelson  wrote:
> I wrote some articles on using Git with puppet and r10k. It's a little out
> of date in the referenced versions of puppet and r10k, so check to make sure
> you're using the modern file locations, but otherwise remains accurate.
> https://rnelson0.com/2014/05/19/puppet-and-git-201-r10k-setup-installation/
>
> There's a link to a Git 100 series I wrote if you need assistance with Git
> itself.


I notice in the previous installs of puppet every thing was under
/etc/puppet  and you recommended putting that under git.


I see with the latest version of puppet I have

/etc/puppetlabs
should I place that under git

The only thing of concern there would be the ssl directory.

or do i just add
code/
puppet/
puppetserver/


THanks
Alex

-- 
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/CAJ%2BQ1PUs%3Dr6a74VPQ9K0z40Uu_bHXAdfeJEYMph4JCJ%3DRcFLQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Diagnose error with simple tutorial in "Learning Puppet 4"?

2016-05-30 Thread David M. Karr

On 05/30/2016 07:41 PM, Patrick Ryll wrote:
This solution worked for me, thanks. Is there any chance someone
could put this on the Puppet 4 Errata page and/or inform Jo Rhett of
this issue? It doesn't seem to be included as of yet (May 30th, 2016)
in the O'Reilly errata. Thanks...I'll be happy to do it myself, but
since I didn't really figure this out...anyway, very helpful thanks.

I sent it indirectly to Jo a while ago (to the O'Reilly booktech email
address). I didn't submit it directly to errata because I wasn't
confident that was exactly the correct solution. He will eventually see it.

On Tuesday, May 17, 2016 at 3:38:36 PM UTC-4, David Karr wrote:

I'm stepping through "Learning Puppet 4". I'm on the chapter that
builds a simple custom module. I've followed the instructions as
far as I can tell, but when I try to apply the module, I get the
following:

|
[vagrant@client modules]$ puppet apply --environment test
../manifests/
Error:EvaluationError:Errorwhileevaluating a
Methodcall,Couldnotfind class::puppet::agent forclient.example.com
at /etc/puppetlabs/code/environments/test/manifests/site.pp:6:43on
node client.example.com
|

I'm sure I've done something wrong, but I can't see it.

Here's the "site.pp" file being referenced:
|
notify {'UsingTest':
message =>"Processing catalog from the Test environment.",
}

# lookup all classes defined in hiera and other data sources
lookup('classes',Array[String],'unique').include
|

And here's the modules "init.pp" manifest (although I get the same
error when I comment out the entire body of the class definition):
|
classpuppet {
# install puppet-agent
package{'puppet-agent':
ensure=>'latest',
notify =>Service['puppet'],
}

# manage the puppet service
service {'puppet':
ensure=>'running',
enable =>true,
subscribe =>Package['puppet-agent'],
}
}
|

What else could I do to get more information?

--
You received this message because you are subscribed to a topic in the
Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/NRgYyd7FV8U/unsubscribe.
To unsubscribe from this group and all its topics, 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/3b430fa8-5386-4999-84bd-b26a687ddea3%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/574D167E.8040504%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Diagnose error with simple tutorial in "Learning Puppet 4"?

2016-05-30 Thread Patrick Ryll

This solution worked for me, thanks.  Is there any chance someone could put 
this on the Puppet 4 Errata page and/or inform Jo Rhett of this issue?  It 
doesn't seem to be included as of yet (May 30th, 2016) in the O'Reilly 
errata.  Thanks...I'll be happy to do it myself, but since I didn't really 
figure this out...anyway, very helpful thanks.

On Tuesday, May 17, 2016 at 3:38:36 PM UTC-4, David Karr wrote:
>
> I'm stepping through "Learning Puppet 4".  I'm on the chapter that builds 
> a simple custom module.  I've followed the instructions as far as I can 
> tell, but when I try to apply the module, I get the following:
>
> [vagrant@client modules]$ puppet apply --environment test ../manifests/
> Error: Evaluation Error: Error while evaluating a Method call, Could not 
> find class ::puppet::agent for client.example.com at /etc/puppetlabs/code/
> environments/test/manifests/site.pp:6:43 on node client.example.com
>
> I'm sure I've done something wrong, but I can't see it.
>
> Here's the "site.pp" file being referenced:
> notify { 'UsingTest':
> message => "Processing catalog from the Test environment.",
> }
>
> # lookup all classes defined in hiera and other data sources
> lookup('classes', Array[String], 'unique').include
>
> And here's the modules "init.pp" manifest (although I get the same error 
> when I comment out the entire body of the class definition):
> class puppet {
>   # install puppet-agent
>   package { 'puppet-agent':
> ensure => 'latest',
> notify => Service['puppet'],
>   }
>
>   # manage the puppet service
>   service { 'puppet':
> ensure => 'running',
> enable => true,
> subscribe => Package['puppet-agent'],
>   }
> }
>
> What else could I do to get more information?
>

-- 
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/3b430fa8-5386-4999-84bd-b26a687ddea3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Reset Admin password

2016-05-30 Thread James Pryor

https://puppet.com/blog/puppet-enterprise-console-password-reset
I hope this helps.

James

On Mon, May 30, 2016 at 9:39 PM, warron.french 
wrote:

> I have root access to the server, which has a monolithic installation of
> PE installed.
>
>
> Can someone please provide me with the correct method to alter the *admin
> *password, since I already have it *written *down but it is not working.
>
>
> Thanks in advance,
>
> --
> Warron French
>
> --
> 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/CAJdJdQ%3DSCZinjNpTBEijdK8-As8%3Dog4kmuAg9unBa%2BgQTDiXOw%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/CAOsPUciLAsz%3DZTah%3DZ%3DSAz%2Bdw1Nm3muOa_tq0hu3UVc9isZNnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Reset Admin password

2016-05-30 Thread warron.french

I have root access to the server, which has a monolithic installation of PE
installed.


Can someone please provide me with the correct method to alter the
*admin *password,
since I already have it *written *down but it is not working.


Thanks in advance,

--
Warron French

-- 
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/CAJdJdQ%3DSCZinjNpTBEijdK8-As8%3Dog4kmuAg9unBa%2BgQTDiXOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Multiple resource bodies?

2016-05-30 Thread dkoleary

Hey;

Thank you all for the information.  That was definitely the issue.  I'm not 
overly worried about '/' so I just took it out - primarily had it in there 
for completeness.  In nigh on 30 years of admin, I think I've had someone 
change the ownership of root maybe twice.  Those other directories - that 
tends to happen more often.  

Any rate, thanks again.  I appreciate it.

Doug O'Leary

-- 
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/9ef583ff-cf25-4032-94d2-4fe42c479188%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Could not receive all responses, mcollective

2016-05-30 Thread cbtshare



Hello All, 

I have 2 client hosts and one puppet masters, I have installed activemq and 
mcollective  and mcollective-puppet-agent on the client machines, machine 1 
is working fine, but machine 2 is not:

 mco ping

client1   time=248.11 ms
puppetmaster   time=273.24 ms
client2 time=273.90 ms

*my server.cfg on both *

main_collective = mcollective
collectives = mcollective
libdir = /usr/libexec/mcollective
logfile = /var/log/mcollective.log
loglevel = info
daemonize = 1

# Plugins
securityprovider = psk
plugin.psk = unset

classesfile = /var/lib/puppet/classes.txt

connector = activemq
plugin.activemq.pool.size = 1
#plugin.activemq.pool.1.host = stomp1
plugin.activemq.pool.1.host = puppetmaster
plugin.activemq.pool.1.port = 61613
plugin.activemq.pool.1.user = ad**
plugin.activemq.pool.1.password = ad**


plugin.puppet.command = puppet agent
plugin.puppet.splay = true
plugin.puppet.splaylimit = 30
plugin.puppet.config = /etc/puppet/puppet.conf
plugin.puppet.signal_daemon = true

# Facts
factsource = yaml
plugin.yaml = /etc/mcollective/facts.yaml

*mcollective logs on client 2 which is not working*
I, [2016-05-30T09:50:39.005585 #17972]  INFO -- : activemq.rb:114:in 
`on_connecting' TCP Connection attempt 0 to 
stomp://ad...@puppetmaster.intranet.mundomedia.com:61613
I, [2016-05-30T09:50:39.073301 #17972]  INFO -- : activemq.rb:119:in 
`on_connected' Connected to 
stomp://ad...@puppetmaster.intranet.mundomedia.com:61613
I, [2016-05-30T09:56:55.506081 #17972]  INFO -- : runner.rb:104:in `rescue 
in block in main_loop' Exiting after signal: SIGTERM
I, [2016-05-30T09:56:55.740564 #19536]  INFO -- : config.rb:167:in 
`loadconfig' The Marionette Collective version 2.8.4 started by 
/usr/sbin/mcollectived using config file /etc/mcollective/server.cfg
I, [2016-05-30T09:56:55.740717 #19536]  INFO -- : mcollectived:64:in 
`' The Marionette Collective 2.8.4 started logging at info level
I, [2016-05-30T09:56:55.740928 #19536]  INFO -- : activemq.rb:211:in 
`initialize' ActiveMQ connector initialized.  Using stomp-gem 1.3.2
I, [2016-05-30T09:56:55.741505 #19536]  INFO -- : activemq.rb:313:in 
`connection_headers' Connecting without STOMP 1.1 heartbeats, if you are 
using ActiveMQ 5.8 or newer consider setting 
plugin.activemq.heartbeat_interval
I, [2016-05-30T09:56:55.741934 #19536]  INFO -- : activemq.rb:114:in 
`on_connecting' TCP Connection attempt 0 to 
stomp://ad...@puppetmaster.intranet.mundomedia.com:61613
I, [2016-05-30T09:56:55.811740 #19536]  INFO -- : activemq.rb:119:in 
`on_connected' Connected to 
stomp://ad...@puppetmaster.intranet.mundomedia.com:61613


*Ports are open, no iptables, permissions are correct, I just cant 
understand why it wont work from puppet master*

 /usr/bin/mco puppet runonce -I client2

 | [ > ] 0 / 
1warn 2016/05/30 09:56:21: client.rb:251:in `start_receiver' Could not 
receive all responses. Expected : 1. Received : 0





Finished processing 0 / 1 hosts in 22137.92 ms


No response from:

client2



-- 
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/43b5f181-d67e-4274-981d-ad1d170501fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Multiple resource bodies?

2016-05-30 Thread Henrik Lindberg


On 30/05/16 19:45, Rob Nelson wrote:

I would be willing to bet '/' is somewhat special and may be the
problem. I've never actually tried to manage the root of the FS directly
and I think the need to may indicate some more significant issues than
puppet should be handling.



Yes, known problem.
See https://tickets.puppetlabs.com/browse/PUP-1796


You could also look at pl_training/dirtree, which lets you manage a
single directory and it will create intermediate directories as needed
with the same owner/group/mode.



That may work around the problem in PUP-1796.

- henrik


--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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/b6013b60-a3b6-c46b-58b3-384a0c194532%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 3.8.5 Master with 3.7.2 Agents

2016-05-30 Thread Henrik Lindberg

On 27/05/16 12:59, Rob Nelson wrote:

IME you definitely won't have issues with 3.7.2 agents talking to a
3.8.5 master.

When you are ready to move to puppet 4, however, the upgrade docs
say that the agents should all hit 3.8 before you upgrade the master to
4.latest. However, I skipped that step in my upgrade and 3.7.x agents
talked fine with 4.3.x (latest when I did this). I can't say if the docs
are over protective, or if I just missed all the cases where that breaks
something.

I think it depends on the version on the server side. IIRC early 4.x
versions did not support the older version of the communication
protocol. I believe this was added for easier upgrade, but I am not 100%
sure.

- henrik

On Friday, May 27, 2016, christg76 > wrote:

Hi, background here is that I want to use both Master and agents
from the Debian repo. The Master runs on Jessie (3.8.5 from the
backports), and some agents still on wheezy (3.7.2 from the backports).
This is not a new install, but rather an intermediate upgrade to the
last Puppet 3 version, before moving on to 4 and Puppet Server.
Is anybody aware of issues with 3.8.5 Master and 3.7.2 Agents? Is
there any reason why I should not be running this setup for a while?
Cant see anything pressing from the release notes..

Many Thanks,
Chris

.
To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/a19fc9f0-8636-489e-bf8a-aaeec46040ab%40googlegroups.com

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

Rob Nelson
rnels...@gmail.com

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

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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/965f65dc-826f-179f-31eb-728ff8c77af0%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Multiple resource bodies?

2016-05-30 Thread Rob Nelson

I would be willing to bet '/' is somewhat special and may be the problem.
I've never actually tried to manage the root of the FS directly and I think
the need to may indicate some more significant issues than puppet should be
handling.

You could also look at pl_training/dirtree, which lets you manage a single
directory and it will create intermediate directories as needed with the
same owner/group/mode.

On Monday, May 30, 2016, Arpin Dominique (Nter) <
dominique.ar...@casino.qc.ca> wrote:

> Hi,
>
>
>
> Maybe you can regroup each item with the same configuration, like this:
>
>
>
> $file_system_list = [‘/’,’/home’,’/opt’]
>
>
>
> $file_system_list.each | String $file_system| {
>
>   file {“$file_system”:
>
> ensure => ‘directory’,
>
> owner => ‘root’,
>
> group => ‘root’
>
>   }
>
> }
>
>
>
>
>
>
>
> *Dominique Arpin*
>
> Tél. Interne: 140-4156
>
> Tél. 514 285.2929 Poste: 140-4156
>
>
> *De :* puppet-users@googlegroups.com
>  [mailto:
> puppet-users@googlegroups.com
> ] *De la
> part de* dkoleary
> *Envoyé :* 30 mai, 2016 13:09
> *À :* Puppet Users
> *Objet :* [Puppet Users] Multiple resource bodies?
>
>
>
> Hey;
>
>
>
> According to the puppet language resource guide at
> https://docs.puppet.com/puppet/latest/reference/lang_resources_advanced.html
> :
>
> If a resource expression includes more than one resource body, the
> expression will declare multiple resources of that resource type. (A
> resource body is a title and a set of attributes; each body must be
> separated from the next one with a semicolon.)
>
> With that, can someone take a peek and tell me what I'm messing up with
> this manifest?
>
>
>
> file {
>   default:
> ensure   => 'directory',
> owner=> 'root',
> group=> 'root',
>   ;
>
>
>   '/': mode  => '0755' ;
>   '/home': mode  => '0755' ;
>   '/opt' : mode  => '0755' ;
>   '/usr' : mode  => '0755' ;
>   '/var' : mode  => '0755' ;
>   '/tmp' : mode  => '1777' ;
>   '/var/tmp' : mode  => '1777' ;
>
>
>   '/etc/passwd':
> ensure   => 'file',
> mode => '0644',
>   ;
>   '/etc/group':
> ensure   => 'file',
> mode => '0644',
>   ;
>
>
>   '/etc/shadow':
> ensure   => 'file',
> mode => '',
>   ;
>
>
>   '/etc/rc.d/init.d':
> mode => '0755',
> recurse  => true,
>   ;
> }
>
>
>
>
>
> I'm not seeing the error; but, when I try to apply it, I get:
>
> $ sudo puppet apply ./file.pp
>
> Notice: Compiled catalog for node1.olearycomputers.com in environment
> production in 0.04 seconds
>
> Error: Parameter path failed on File[/]: File paths must be fully
> qualified, not '' at
> /ignite/dkoleary/mpi_git/puppet/modules/mpicommon/manifests/file.pp:1
>
>
>
> Any pointers, greatly appreciated.
>
>
>
> Doug O'Leary
>
>
>
> --
> 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/f284439e-d1d8-49f0-a77e-d0c07ce61239%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> Mise en garde concernant la confidentialité : Le présent message,
> comprenant tout fichier qui y est joint, est envoyé à l'intention exclusive
> de son destinataire; il est de nature confidentielle et peut constituer une
> information protégée par le secret professionnel. Si vous n'êtes pas le
> destinataire, nous vous avisons que toute impression, copie, distribution
> ou autre utilisation de ce message est strictement interdite. Si vous avez
> reçu ce courriel par erreur, veuillez en aviser immédiatement l'expéditeur
> par retour de courriel et supprimer le courriel. Merci!
>
> Confidentiality Warning: This message, including any attachment, is sent
> only for the use of the intended recipient; it is confidential and may
> constitute privileged information. If you are not the intended recipient,
> you are hereby notified that any printing, copying, distribution or other
> use of this message is strictly prohibited. If you have received this email
> in error, please notify the sender immediately by return email, and delete
> it. Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com
> 
> .
> To view this discussion on the web

Re: [Puppet Users] Multiple resource bodies?

2016-05-30 Thread Henrik Lindberg


On 30/05/16 19:09, dkoleary wrote:

Hey;

According to the puppet language resource guide
at https://docs.puppet.com/puppet/latest/reference/lang_resources_advanced.html:

If a resource expression includes more than one resource body, the
expression will declare multiple resources of that resource type. (A
resource body is a title and a set of attributes; each body must be
separated from the next one with a semicolon.)

With that, can someone take a peek and tell me what I'm messing up with
this manifest?

|
file {
  default:
ensure  =>'directory',
owner=>'root',
group   =>'root',
  ;


  '/'   :mode  =>'0755';
  '/home'   :mode  =>'0755';
  '/opt':mode  =>'0755';
  '/usr':mode  =>'0755';
  '/var':mode  =>'0755';
  '/tmp':mode  =>'1777';
  '/var/tmp':mode  =>'1777';


  '/etc/passwd':
ensure  =>'file',
mode =>'0644',
  ;
  '/etc/group':
ensure  =>'file',
mode =>'0644',
  ;


  '/etc/shadow':
ensure  =>'file',
mode =>'',
  ;


  '/etc/rc.d/init.d':
mode =>'0755',
recurse  =>true,
  ;
}
|


I'm not seeing the error; but, when I try to apply it, I get:

$ sudo puppet apply ./file.pp
Notice: Compiled catalog for node1.olearycomputers.com in environment
production in 0.04 seconds
Error: Parameter path failed on File[/]: File paths must be fully
qualified, not '' at
/ignite/dkoleary/mpi_git/puppet/modules/mpicommon/manifests/file.pp:1

Any pointers, greatly appreciated.



From what I can tell by reading through that, your manifest looks ok in 
terms of multiple bodies and use of defaults.


The problem is known. See https://tickets.puppetlabs.com/browse/PUP-1796
which has a work around using '/.' (which may or may not work according 
to the comments on that ticket).


- henrik


Doug O'Leary

--
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/f284439e-d1d8-49f0-a77e-d0c07ce61239%40googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.





--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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/e8fe22be-eaf7-39e1-ef5c-4cdd5848ec94%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Multiple resource bodies?

2016-05-30 Thread dkoleary

Hey;

Thanks for the response.  I'm trying to work my way into iteration a bit 
slower than my fourth manifest :)  If all else fails, I'm pretty sure I can 
set up separate file resource declarations; but, this multiple resource 
bodies, in this case, seems like this is cleaner.

Thanks

Doug O'Leary

-- 
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/ef2dfc24-053b-4e73-aa76-eb857b8db0fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [Puppet Users] Multiple resource bodies?

2016-05-30 Thread Arpin Dominique (Nter)

Hi,

Maybe you can regroup each item with the same configuration, like this:

$file_system_list = [‘/’,’/home’,’/opt’]

$file_system_list.each | String $file_system| {
  file {“$file_system”:
ensure => ‘directory’,
owner => ‘root’,
group => ‘root’
  }
}



Dominique Arpin
Tél. Interne: 140-4156
Tél. 514 285.2929 Poste: 140-4156


De : puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] De la 
part de dkoleary
Envoyé : 30 mai, 2016 13:09
À : Puppet Users
Objet : [Puppet Users] Multiple resource bodies?

Hey;

According to the puppet language resource guide at 
https://docs.puppet.com/puppet/latest/reference/lang_resources_advanced.html:

If a resource expression includes more than one resource body, the expression 
will declare multiple resources of that resource type. (A resource body is a 
title and a set of attributes; each body must be separated from the next one 
with a semicolon.)
With that, can someone take a peek and tell me what I'm messing up with this 
manifest?

file {
  default:
ensure   => 'directory',
owner=> 'root',
group=> 'root',
  ;


  '/': mode  => '0755' ;
  '/home': mode  => '0755' ;
  '/opt' : mode  => '0755' ;
  '/usr' : mode  => '0755' ;
  '/var' : mode  => '0755' ;
  '/tmp' : mode  => '1777' ;
  '/var/tmp' : mode  => '1777' ;


  '/etc/passwd':
ensure   => 'file',
mode => '0644',
  ;
  '/etc/group':
ensure   => 'file',
mode => '0644',
  ;


  '/etc/shadow':
ensure   => 'file',
mode => '',
  ;


  '/etc/rc.d/init.d':
mode => '0755',
recurse  => true,
  ;
}


I'm not seeing the error; but, when I try to apply it, I get:
$ sudo puppet apply ./file.pp
Notice: Compiled catalog for node1.olearycomputers.com in environment 
production in 0.04 seconds
Error: Parameter path failed on File[/]: File paths must be fully qualified, 
not '' at /ignite/dkoleary/mpi_git/puppet/modules/mpicommon/manifests/file.pp:1

Any pointers, greatly appreciated.

Doug O'Leary

--
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/f284439e-d1d8-49f0-a77e-d0c07ce61239%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mise en garde concernant la confidentialité : Le présent message, comprenant 
tout fichier qui y est joint, est envoyé à l'intention exclusive de son 
destinataire; il est de nature confidentielle et peut constituer une 
information protégée par le secret professionnel. Si vous n'êtes pas le 
destinataire, nous vous avisons que toute impression, copie, distribution ou 
autre utilisation de ce message est strictement interdite. Si vous avez reçu ce 
courriel par erreur, veuillez en aviser immédiatement l'expéditeur par retour 
de courriel et supprimer le courriel. Merci!

Confidentiality Warning: This message, including any attachment, is sent only 
for the use of the intended recipient; it is confidential and may constitute 
privileged information. If you are not the intended recipient, you are hereby 
notified that any printing, copying, distribution or other use of this message 
is strictly prohibited. If you have received this email in error, please notify 
the sender immediately by return email, and delete it. Thank you!

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

[Puppet Users] Multiple resource bodies?

2016-05-30 Thread dkoleary

Hey;

According to the puppet language resource guide 
at https://docs.puppet.com/puppet/latest/reference/lang_resources_advanced.html:

If a resource expression includes more than one resource body, the 
expression will declare multiple resources of that resource type. (A 
resource body is a title and a set of attributes; each body must be 
separated from the next one with a semicolon.)

With that, can someone take a peek and tell me what I'm messing up with 
this manifest?

file {
  default:
ensure   => 'directory',
owner=> 'root',
group=> 'root',
  ;


  '/': mode  => '0755' ;
  '/home': mode  => '0755' ;
  '/opt' : mode  => '0755' ;
  '/usr' : mode  => '0755' ;
  '/var' : mode  => '0755' ;
  '/tmp' : mode  => '1777' ;
  '/var/tmp' : mode  => '1777' ;


  '/etc/passwd':
ensure   => 'file',
mode => '0644',
  ;
  '/etc/group':
ensure   => 'file',
mode => '0644',
  ;


  '/etc/shadow':
ensure   => 'file',
mode => '',
  ;


  '/etc/rc.d/init.d':
mode => '0755',
recurse  => true,
  ;
}


I'm not seeing the error; but, when I try to apply it, I get:

$ sudo puppet apply ./file.pp
Notice: Compiled catalog for node1.olearycomputers.com in environment 
production in 0.04 seconds
Error: Parameter path failed on File[/]: File paths must be fully 
qualified, not '' at 
/ignite/dkoleary/mpi_git/puppet/modules/mpicommon/manifests/file.pp:1

Any pointers, greatly appreciated.

Doug O'Leary

-- 
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/f284439e-d1d8-49f0-a77e-d0c07ce61239%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Outofmemory error for puppetserver process

2016-05-30 Thread Matthaus Owens

Jim,

The 'XX:OnOutOfMemoryError=kill -9 %p' in the process list doesn't indicate
that puppet server is out of memory, it is a Java flag that tells Java what
to do if puppet server hits an outofmemory error. The output you have
pasted looks totally normal to me.

HTH

On Monday, May 30, 2016, Jim  wrote:

> Hi Matthaus,
>
> My hostname is misleading. I upgraded at the time of posting to Ubuntu
> 15.10. Now I have upgraded to 16.04.
>
> I ran the command you suggested instead of service puppetserver start and
> I don't see OutOfMemory errors process.
>
> root@jim-Ubuntu1504:~# ps -aef|grep -i puppet|grep -v grep
> root  1116 1  0 19:34 ?00:00:02
> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent
> --no-daemonize
> root  1719 1  0 19:38 ?00:00:08
> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived
> --config=/etc/puppetlabs/mcollective/server.cfg
> --pidfile=/var/run/puppetlabs/mcollective.pid --daemonize
> root  2644  1544  0 22:35 pts/000:00:00 bash
> /opt/puppetlabs/server/apps/puppetserver/cli/apps/foreground
> root  2650  2644  0 22:35 pts/000:00:00 runuser puppet -s
> /bin/bash -c /usr/bin/java -Xms512m -Xmx512m -XX:MaxPermSize=512m
> -Dlogappender=STDOUT  -cp
> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar
>  clojure.main -m puppetlabs.trapperkeeper.main  --config
> /etc/puppetlabs/puppetserver/conf.d --bootstrap-config
> /etc/puppetlabs/puppetserver/bootstrap.cfg
> puppet2651  2650 55 22:35 ?00:00:42 /usr/bin/java -Xms512m
> -Xmx512m -XX:MaxPermSize=512m -Dlogappender=STDOUT -cp
> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar
> clojure.main -m puppetlabs.trapperkeeper.main --config
> /etc/puppetlabs/puppetserver/conf.d --bootstrap-config
> /etc/puppetlabs/puppetserver/bootstrap.cfg
> root@jim-Ubuntu1504:~#
>
>
> Also when I do see that error as like below when I do Ctrl + C and execute
> service puppetserver start I get the OutOfMemory error like below.
>
> root@jim-Ubuntu1504:~# ps -aef|grep -i puppet|grep -v grep
> root  1116 1  0 19:34 ?00:00:02
> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent
> --no-daemonize
> root  1719 1  0 19:38 ?00:00:08
> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived
> --config=/etc/puppetlabs/mcollective/server.cfg
> --pidfile=/var/run/puppetlabs/mcollective.pid --daemonize
> puppet3386 1 66 22:41 ?00:00:45 /usr/bin/java
> -XX:OnOutOfMemoryError=kill -9 %p -Djava.security.egd=/dev/urandom -Xms512m
> -Xmx512m -XX:MaxPermSize=512m -cp
> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar
> clojure.main -m puppetlabs.trapperkeeper.main --config
> /etc/puppetlabs/puppetserver/conf.d -b
> /etc/puppetlabs/puppetserver/bootstrap.cfg
> root@jim-Ubuntu1504:~#
>
> I wonder if I am doing start-up incorrectly ? Either even in this state
> where it sayOutOfMemoryError my puppetserver still serves all of its
> agents. The reason I say so is I changed motd file on all agents +
> installed vim package on agents.
>
> I am not sure which is the right method to start the server ? Also instead
> of running in foreground can I run it in background using nohup ?
>
> Regards,
> Jim
>
>
> On Friday, 27 May 2016 02:46:14 UTC+10, Matthaus Litteken wrote:
>>
>> Jim,
>> For debugging failures on ubuntu 15.04, I would recommend trying
>> `/opt/puppetlabs/bin/puppetserver foreground`, it may show you the errors
>> that are causing the service to shutdown. Ubuntu 15.04 is a bit difficult
>> to debug on, because while it has systemd support, the puppetserver
>> packages for that platform still ship sysv init scripts. In my experience,
>> the sysv-systemd integration seems to swallow some startup errors and
>> messages that would usually go to journalctl on a systemd platform. We
>> started shipping systemd service files for puppetserver starting in Ubuntu
>> 16.04.
>>
>> HTH
>>
>> On Thu, May 26, 2016 at 6:56 AM, Jim  wrote:
>>
>>> Hi Trevor,
>>>
>>> No luck.
>>>
>>> 2016-05-26 23:46:26,745 INFO  [Thread-1] [p.t.internal] Shutting down
>>> due to JVM shutdown hook.
>>> 2016-05-26 23:46:26,747 INFO  [Thread-1] [p.t.internal] Beginning
>>> shutdown sequence
>>> 2016-05-26 23:46:26,761 INFO  [clojure-agent-send-pool-1]
>>> [p.s.j.jruby-puppet-agents] Flush request received; creating new JRuby pool.
>>> 2016-05-26 23:46:26,765 INFO  [clojure-agent-send-pool-1]
>>> [p.s.j.jruby-puppet-agents] Replacing old JRuby pool with new instance.
>>> 2016-05-26 23:46:26,765 INFO  [clojure-agent-send-pool-1]
>>> [p.s.j.jruby-puppet-agents] Swapped JRuby pools, beginning cleanup of old
>>> pool.
>>> 2016-05-26 23:46:26,770 INFO  [clojure-agent-send-pool-1]
>>> [p.s.j.jruby-puppet-internal] Cleaned up old JRuby instance with id 1.
>>> 2016-05-26 23:46:26,772 INFO  [Thread-1] [p.t.s.w.jetty9-service]
>>>

Re: [Puppet Users] Outofmemory error for puppetserver process

2016-05-30 Thread Jim

Hi Matthaus,

My hostname is misleading. I upgraded at the time of posting to Ubuntu 
15.10. Now I have upgraded to 16.04.

I ran the command you suggested instead of service puppetserver start and I 
don't see OutOfMemory errors process.

root@jim-Ubuntu1504:~# ps -aef|grep -i puppet|grep -v grep
root  1116 1  0 19:34 ?00:00:02 
/opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent 
--no-daemonize
root  1719 1  0 19:38 ?00:00:08 
/opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived 
--config=/etc/puppetlabs/mcollective/server.cfg 
--pidfile=/var/run/puppetlabs/mcollective.pid --daemonize
root  2644  1544  0 22:35 pts/000:00:00 bash 
/opt/puppetlabs/server/apps/puppetserver/cli/apps/foreground
root  2650  2644  0 22:35 pts/000:00:00 runuser puppet -s /bin/bash 
-c /usr/bin/java -Xms512m -Xmx512m -XX:MaxPermSize=512m 
-Dlogappender=STDOUT  -cp 
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar 
 clojure.main -m puppetlabs.trapperkeeper.main  --config 
/etc/puppetlabs/puppetserver/conf.d --bootstrap-config 
/etc/puppetlabs/puppetserver/bootstrap.cfg  
puppet2651  2650 55 22:35 ?00:00:42 /usr/bin/java -Xms512m 
-Xmx512m -XX:MaxPermSize=512m -Dlogappender=STDOUT -cp 
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar 
clojure.main -m puppetlabs.trapperkeeper.main --config 
/etc/puppetlabs/puppetserver/conf.d --bootstrap-config 
/etc/puppetlabs/puppetserver/bootstrap.cfg
root@jim-Ubuntu1504:~# 


Also when I do see that error as like below when I do Ctrl + C and execute 
service puppetserver start I get the OutOfMemory error like below.

root@jim-Ubuntu1504:~# ps -aef|grep -i puppet|grep -v grep
root  1116 1  0 19:34 ?00:00:02 
/opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent 
--no-daemonize
root  1719 1  0 19:38 ?00:00:08 
/opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived 
--config=/etc/puppetlabs/mcollective/server.cfg 
--pidfile=/var/run/puppetlabs/mcollective.pid --daemonize
puppet3386 1 66 22:41 ?00:00:45 /usr/bin/java 
-XX:OnOutOfMemoryError=kill -9 %p -Djava.security.egd=/dev/urandom -Xms512m 
-Xmx512m -XX:MaxPermSize=512m -cp 
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar 
clojure.main -m puppetlabs.trapperkeeper.main --config 
/etc/puppetlabs/puppetserver/conf.d -b 
/etc/puppetlabs/puppetserver/bootstrap.cfg
root@jim-Ubuntu1504:~# 

I wonder if I am doing start-up incorrectly ? Either even in this state 
where it sayOutOfMemoryError my puppetserver still serves all of its 
agents. The reason I say so is I changed motd file on all agents + 
installed vim package on agents.

I am not sure which is the right method to start the server ? Also instead 
of running in foreground can I run it in background using nohup ?

Regards,
Jim


On Friday, 27 May 2016 02:46:14 UTC+10, Matthaus Litteken wrote:
>
> Jim,
> For debugging failures on ubuntu 15.04, I would recommend trying 
> `/opt/puppetlabs/bin/puppetserver foreground`, it may show you the errors 
> that are causing the service to shutdown. Ubuntu 15.04 is a bit difficult 
> to debug on, because while it has systemd support, the puppetserver 
> packages for that platform still ship sysv init scripts. In my experience, 
> the sysv-systemd integration seems to swallow some startup errors and 
> messages that would usually go to journalctl on a systemd platform. We 
> started shipping systemd service files for puppetserver starting in Ubuntu 
> 16.04.
>
> HTH
>
> On Thu, May 26, 2016 at 6:56 AM, Jim  
> wrote:
>
>> Hi Trevor,
>>
>> No luck.
>>
>> 2016-05-26 23:46:26,745 INFO  [Thread-1] [p.t.internal] Shutting down due 
>> to JVM shutdown hook.
>> 2016-05-26 23:46:26,747 INFO  [Thread-1] [p.t.internal] Beginning 
>> shutdown sequence
>> 2016-05-26 23:46:26,761 INFO  [clojure-agent-send-pool-1] 
>> [p.s.j.jruby-puppet-agents] Flush request received; creating new JRuby pool.
>> 2016-05-26 23:46:26,765 INFO  [clojure-agent-send-pool-1] 
>> [p.s.j.jruby-puppet-agents] Replacing old JRuby pool with new instance.
>> 2016-05-26 23:46:26,765 INFO  [clojure-agent-send-pool-1] 
>> [p.s.j.jruby-puppet-agents] Swapped JRuby pools, beginning cleanup of old 
>> pool.
>> 2016-05-26 23:46:26,770 INFO  [clojure-agent-send-pool-1] 
>> [p.s.j.jruby-puppet-internal] Cleaned up old JRuby instance with id 1.
>> 2016-05-26 23:46:26,772 INFO  [Thread-1] [p.t.s.w.jetty9-service] 
>> Shutting down web server(s).
>> 2016-05-26 23:46:26,781 INFO  [Thread-1] [p.t.s.w.jetty9-core] Shutting 
>> down web server.
>> 2016-05-26 23:46:26,824 INFO  [Thread-1] [o.e.j.s.ServerConnector] 
>> Stopped ServerConnector@79303966{SSL-HTTP/1.1}{0.0.0.0:8140}
>> 2016-05-26 23:46:26,824 INFO  [Thread-1] [o.e.j.s.h.ContextHandler] 
>> Stopped o.e.j.s.h.ContextHandler@2b87522b{/,null,UNAVAILABLE}
>> 2016-05-26

Re: [Puppet Users] 3.8.5 Master with 3.7.2 Agents

2016-05-30 Thread christg76

Thats what i thought.. many thanks for the info Rob!

-- 
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/1649c0a5-17b9-4c20-a6d4-0d3c144b097f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet and SVN

Re: [Puppet Users] Re: Diagnose error with simple tutorial in "Learning Puppet 4"?

[Puppet Users] Re: Diagnose error with simple tutorial in "Learning Puppet 4"?

Re: [Puppet Users] Reset Admin password

[Puppet Users] Reset Admin password

Re: [Puppet Users] Multiple resource bodies?

[Puppet Users] Could not receive all responses, mcollective

Re: [Puppet Users] Multiple resource bodies?

Re: [Puppet Users] 3.8.5 Master with 3.7.2 Agents

Re: [Puppet Users] Multiple resource bodies?

Re: [Puppet Users] Multiple resource bodies?

Re: [Puppet Users] Multiple resource bodies?

RE: [Puppet Users] Multiple resource bodies?

[Puppet Users] Multiple resource bodies?

Re: [Puppet Users] Outofmemory error for puppetserver process

Re: [Puppet Users] Outofmemory error for puppetserver process

Re: [Puppet Users] 3.8.5 Master with 3.7.2 Agents

17 matches

Site Navigation

Mail list logo

Footer information