date:20120731

Hi group, 

I am managing an NFS mount with puppet. And it does not work, and seriously 
I really don't see how this can work out nicely. First I make sure with a 
file {} class that the directory I want to mount exists. Cause it is used 
by the webserver it should belong to the wwwrun/www group on the system. No 
prob. 

Then I mount the NFS share on the dir. No prob. 

On the 2nd run of puppet though ... Error! The NFS mount point is "changed" 
over to root:root with 775 permissions (or 777? I don't remember). Puppet 
of course now wants to set the user:group of the dir ... and naturally 
fails. 

So is there a way to keep this error from happening?


Thanks in advance & greetings, 
Axel.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/tw1oa58dRhoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] "Could not find dependency Package" even the package already theres.

2012-07-31 Thread Jakov Sosic


On 07/31/2012 10:58 AM, heriyanto wrote:

asterisk package already installed. I don't plan installation for this package 
managed by puppet.
just want manage the file configuration.


You cannot depend on an item that is not defined somewhere else in the 
manifest, or in a node configuration.


You would have to remove dependency from your class (line that says: 
require => Package["asterisk"],), because dependency searches through 
compiled puppet configuration for package {"asterisk": } definition.


I would recommend that you write another resource that checks for some 
file that package itself bring along, and depend on that resource.




--
Jakov Sosic
www.srce.unizg.hr

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Possible to push changes to nodes?

2012-07-31 Thread Jakov Sosic


On 07/31/2012 11:08 AM, Sandra Schlichting wrote:

Note that getting puppet kick working is a multi-step process:

- Gotta change all agents' puppet.conf to have listen = true in
either [main] or [agent].
- Gotta open port 8139 to incoming connections on every agent node's
firewall.
- Gotta add the following stanza somewhere near the top of each
agent node's auth.conf file:

path /run
auth yes
allow puppet.example.com 


That is very interesting!

I have now tried this with Puppet 3.0rc3, and on the node side I get

Error: Could not find indirection 'run'

so I have filed a bug report

http://projects.puppetlabs.com/issues/15717

Do you think it could be a bug, or am I doing something wrong?

My setup is explained in the bug report =)


Could you post your whole auth.conf once more? And maybe try to put this:

[puppetrunner]
   allow *

to your client's /etc/puppet/namespace.auth?

Also check if your DNS is working ok.


--
Jakov Sosic
www.srce.unizg.hr

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Long processing time using Augeas

2012-07-31 Thread Alexander Holte-Davidsen

Hi!

I using Augeas to handle dump and passno for certain mount points in
/etc/fstab. Each mount point is defined as it's own augeas block:

augeas { 'homeLV':
context =>
'/files/etc/fstab',
changes => [
'set *[file =
"/home"]/dump 0',
'set *[file =
"/home"]/passno 0',
],
onlyif => 'match *[file =
"/home"] size > 0',
}
augeas { 'optLV':
context =>
'/files/etc/fstab',
changes => [
'set *[file =
"/opt"]/dump 0',
'set *[file =
"/opt"]/passno 0',
],
onlyif => 'match *[file =
"/opt"] size > 0',
}

This code is taking a very long to to process, about 10 seconds for six
mount points. When running a debug run, I can see that /etc/fstab is opened
 for each augeas code block, also when no change is needed.
debug: Augeas[varLV](provider=augeas): Opening augeas with root /home, lens
path , flags 0
debug: Augeas[varLV](provider=augeas): Augeas version 0.10.0 is installed
debug: Augeas[varLV](provider=augeas): Will attempt to save and only run if
files changed
debug: Augeas[varLV](provider=augeas): sending command 'set' with params
["/files/etc/fstab/*[file = \"/home\"]/dump", "0"]
debug: Augeas[varLV](provider=augeas): sending command 'set' with params
["/files/etc/fstab/*[file = \"/home\"]/passno", "0"]
debug: Augeas[varLV](provider=augeas): Skipping because no files were
changed
debug: Augeas[varLV](provider=augeas): Closed the augeas connection
debug: Augeas[srvLV](provider=augeas): Opening augeas with root /opt, lens
path , flags 0
debug: Augeas[srvLV](provider=augeas): Augeas version 0.10.0 is installed
debug: Augeas[srvLV](provider=augeas): Will attempt to save and only run if
files changed
debug: Augeas[srvLV](provider=augeas): sending command 'set' with params
["/files/etc/fstab/*[file = \"/opt\"]/dump", "0"]
debug: Augeas[srvLV](provider=augeas): sending command 'set' with params
["/files/etc/fstab/*[file = \"/opt\"]/passno", "0"]
debug: Augeas[srvLV](provider=augeas): Skipping because no files were
changed
debug: Augeas[srvLV](provider=augeas): Closed the augeas connection


Are there any obvious ways to speed this up? For example better checking
before the code is executed? Putting all the mount point changes in one
augeas block would probably speed things up a bit, but then I would not be
able to use the onlyif-statement per mount point?

Regards,
Alexander

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Long processing time using Augeas

2012-07-31 Thread Alexander Holte-Davidsen

After some more debugging, it looks like it takes about one second to
process each augeas block, so putting all the statements in one block
speeds things up a lot.

Are there any other ways to do this? I want to be able to check if the
mount point exists before I try change...

Regards,
Alexander

On Tue, Jul 31, 2012 at 1:56 PM, Alexander Holte-Davidsen <
alexander.david...@gmail.com> wrote:

> Hi!
>
> I using Augeas to handle dump and passno for certain mount points in
> /etc/fstab. Each mount point is defined as it's own augeas block:
>
> augeas { 'homeLV':
> context =>
> '/files/etc/fstab',
> changes => [
> 'set *[file =
> "/home"]/dump 0',
> 'set *[file =
> "/home"]/passno 0',
> ],
> onlyif => 'match *[file =
> "/home"] size > 0',
> }
> augeas { 'optLV':
> context =>
> '/files/etc/fstab',
> changes => [
> 'set *[file =
> "/opt"]/dump 0',
> 'set *[file =
> "/opt"]/passno 0',
> ],
> onlyif => 'match *[file =
> "/opt"] size > 0',
> }
>
> This code is taking a very long to to process, about 10 seconds for six
> mount points. When running a debug run, I can see that /etc/fstab is opened
>  for each augeas code block, also when no change is needed.
> debug: Augeas[varLV](provider=augeas): Opening augeas with root /home,
> lens path , flags 0
> debug: Augeas[varLV](provider=augeas): Augeas version 0.10.0 is installed
> debug: Augeas[varLV](provider=augeas): Will attempt to save and only run
> if files changed
> debug: Augeas[varLV](provider=augeas): sending command 'set' with params
> ["/files/etc/fstab/*[file = \"/home\"]/dump", "0"]
> debug: Augeas[varLV](provider=augeas): sending command 'set' with params
> ["/files/etc/fstab/*[file = \"/home\"]/passno", "0"]
> debug: Augeas[varLV](provider=augeas): Skipping because no files were
> changed
> debug: Augeas[varLV](provider=augeas): Closed the augeas connection
> debug: Augeas[srvLV](provider=augeas): Opening augeas with root /opt, lens
> path , flags 0
> debug: Augeas[srvLV](provider=augeas): Augeas version 0.10.0 is installed
> debug: Augeas[srvLV](provider=augeas): Will attempt to save and only run
> if files changed
> debug: Augeas[srvLV](provider=augeas): sending command 'set' with params
> ["/files/etc/fstab/*[file = \"/opt\"]/dump", "0"]
> debug: Augeas[srvLV](provider=augeas): sending command 'set' with params
> ["/files/etc/fstab/*[file = \"/opt\"]/passno", "0"]
> debug: Augeas[srvLV](provider=augeas): Skipping because no files were
> changed
> debug: Augeas[srvLV](provider=augeas): Closed the augeas connection
>
>
> Are there any obvious ways to speed this up? For example better checking
> before the code is executed? Putting all the mount point changes in one
> augeas block would probably speed things up a bit, but then I would not be
> able to use the onlyif-statement per mount point?
>
> Regards,
> Alexander
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] trouble with puppetlabs-mysql module; ignores db and user creation

2012-07-31 Thread tom s

There's been at least one other report of something like this, but that was 
a little while ago and changes to the module have been made recently.

Basically I can create a database, set the root password, but not do 
anything else:

node 'puppetclient.tomtest.com' {
class { 'mysql::server':
service_name => 'mysql',
config_hash => { 'root_password' => 'mymysqlrootpass', },
package_name => 'MySQL-server',
}
mysql::db { 'testdb':
user=> 'testdb',
password=> 'testdb',
host=> 'localhost',
grant   => ['ALL'],
}
}

Installs mysql, correctly sets the root password then stops.  The DB is 
never created and no errors are issued.

Can anyone help me debug this issue?, I've not gone down the custom 
resources route myself yet, so I'm not sure how I go about working out 
where the problem is.

Cheers,

Tom.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/O-N6g5jMiRgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] High CPU load / queued passenger requests

2012-07-31 Thread Luke Baker

After restarting our puppetmaster host, we are seeing high CPU load and a 
ton of queued passenger requests. I would suspect that our puppetmaster is 
falling victim to the thundering herd of puppet agents, but we have 
deployed most of our agents using a randomized cron job. The others are 
using 'splay = true' if they are running puppet agent. 

Some info:
Puppetmaster is RHEL6 x86_64 (VM)
4 vCPU 8GB memory
Apache 2.2
Passenger 3.0.7

The vhost for our puppetmaster includes these passenger options:
PassengerHighPerformance on
PassengerUseGlobalQueue on
PassengerPoolIdleTime 1500
PassengerMaxPoolSize 24
PassengerMaxRequests 4000
PassengerStatThrottleRate 120
PassengerSpawnMethod smart
RackAutoDetect Off
RailsAutoDetect Off


Look at all of these queued requests!

Passenger-status:
--- General information ---
max  = 24
count= 24
active   = 22
inactive = 2
Waiting on global queue: 234

--- Application groups ---
/etc/puppet/rack:
  App root: /etc/puppet/rack
  * PID: 24840   Sessions: 1Processed: 528 Uptime: 9h 41m 19s
  * PID: 24703   Sessions: 1Processed: 513 Uptime: 9h 42m 17s
  * PID: 24642   Sessions: 1Processed: 567 Uptime: 9h 42m 29s
  * PID: 24827   Sessions: 1Processed: 572 Uptime: 9h 41m 28s
  * PID: 24869   Sessions: 1Processed: 530 Uptime: 9h 41m 4s
  * PID: 24586   Sessions: 1Processed: 572 Uptime: 9h 42m 32s
  * PID: 24715   Sessions: 1Processed: 539 Uptime: 9h 42m 17s
  * PID: 29046   Sessions: 1Processed: 487 Uptime: 8h 52m 35s
  * PID: 24609   Sessions: 1Processed: 575 Uptime: 9h 42m 30s
  * PID: 24605   Sessions: 1Processed: 488 Uptime: 9h 42m 30s
  * PID: 24831   Sessions: 1Processed: 555 Uptime: 9h 41m 27s
  * PID: 29036   Sessions: 1Processed: 549 Uptime: 8h 52m 35s
  * PID: 24583   Sessions: 1Processed: 565 Uptime: 9h 42m 32s
  * PID: 24768   Sessions: 1Processed: 521 Uptime: 9h 41m 56s
  * PID: 24850   Sessions: 1Processed: 579 Uptime: 9h 41m 16s
  * PID: 29050   Sessions: 1Processed: 497 Uptime: 8h 52m 35s
  * PID: 24567   Sessions: 1Processed: 536 Uptime: 9h 42m 37s
  * PID: 24761   Sessions: 1Processed: 570 Uptime: 9h 42m 5s
  * PID: 24709   Sessions: 1Processed: 575 Uptime: 9h 42m 17s
  * PID: 29042   Sessions: 1Processed: 488 Uptime: 8h 52m 35s
  * PID: 24865   Sessions: 1Processed: 559 Uptime: 9h 41m 5s
  * PID: 29039   Sessions: 1Processed: 506 Uptime: 8h 52m 35s

/usr/share/foreman:
  App root: /usr/share/foreman
  * PID: 24724   Sessions: 0Processed: 5743Uptime: 9h 42m 16s
  * PID: 24717   Sessions: 0Processed: 5099Uptime: 9h 42m 17s

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/p1uXXzKJhCcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Using file{} with array parameter fails

Hello readers, 

I am wondering - I intend to create a few directory trees with the file{ 
[array] } pattern, but unfortunately Puppet complains. It says  "File[] is 
already declared in file ..." - which kind of looks like as if Puppet takes 
a file object with an array as parameter as a single, unnamed File object. 
I would assume this would be equivalent to 

File{ array[0] : ... }
File{ array[1] : ... }
File{ array[2] : ... }

... etc. Unfortunately the directories should have different owners and 
permissions, so I cannot merge those into a single file{} statement. Any 
advice how I can achieve what I want without breaking this up into - right 
now - six different file{} delarations? 

Thanks in advance & greetings, 
Axel.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Sowc-6bIiOgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] trouble with puppetlabs-mysql module; ignores db and user creation

2012-07-31 Thread Walter Heck

In these cases you would start by checking a run of puppetd -t -d -v
to see if it shows up there. If not, then look carefully if the
resource is really included on that node. If it is, there should be a
hint on what is happening..

On Tue, Jul 31, 2012 at 9:19 PM, tom s  wrote:
> There's been at least one other report of something like this, but that was
> a little while ago and changes to the module have been made recently.
>
> Basically I can create a database, set the root password, but not do
> anything else:
>
> node 'puppetclient.tomtest.com' {
> class { 'mysql::server':
> service_name => 'mysql',
> config_hash => { 'root_password' => 'mymysqlrootpass', },
> package_name => 'MySQL-server',
> }
> mysql::db { 'testdb':
> user=> 'testdb',
> password=> 'testdb',
> host=> 'localhost',
> grant   => ['ALL'],
> }
> }
>
> Installs mysql, correctly sets the root password then stops.  The DB is
> never created and no errors are issued.
>
> Can anyone help me debug this issue?, I've not gone down the custom
> resources route myself yet, so I'm not sure how I go about working out where
> the problem is.
>
> Cheers,
>
> Tom.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/O-N6g5jMiRgJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.



-- 
Walter Heck

--
Check out my startup: Puppet training and consulting @ http://www.olindata.com
Follow @olindata on Twitter and/or 'Like' our Facebook page at
http://www.facebook.com/olindata

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Using file{} with array parameter fails

2012-07-31 Thread David Schmitt


Hi Axel,

On 31.07.2012 15:59, Axel Bock wrote:

Hello readers,

I am wondering - I intend to create a few directory trees with the file{
[array] } pattern, but unfortunately Puppet complains. It says "File[]
is already declared in file ..."- which kind of looks like as if Puppet
takes a file object with an array as parameter as a single, unnamed File
object. I would assume this would be equivalent to

File{ array[0] : ... }
File{ array[1] : ... }
File{ array[2] : ... }

... etc. Unfortunately the directories should have different owners and
permissions, so I cannot merge those into a single file{} statement. Any
advice how I can achieve what I want without breaking this up into -
right now - six different file{} delarations?


You're description is not totally clear to me, but here's an example how 
arrays should work:



  $filesA = ["/tmp/A1", "/tmp/A2", "/tmp/A3" ]
  $filesB = ["/tmp/B1", "/tmp/B2", "/tmp/B3" ]

  file {
$filesA:
  ensure => present,
  mode => 0644, owner => root;
$filesB:
  ensure => present,
  mode => 0755, owner => "www-data";
  }

If you're looking for something different you might want to look into 
setting recurse=>true. Read the Type Reference for more info.


Best Regards, David

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] File diff in log

2012-07-31 Thread Antidot SAS

Hi everyone,


Just a quick question since lately, when puppet runs in verbose mode I do
see anymore the diff from the current file and the file from the puppet
master (version 2.7.18) is this normal, we only the the md5 signature? Is
there an option to display the diff?


Regards,
JM

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

RE: [Puppet Users] File diff in log

2012-07-31 Thread Kinzel, David

>From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On 
>Behalf Of Antidot SAS
>Hi everyone,

>Just a quick question since lately, when puppet runs in verbose mode I do see 
>anymore the diff from the current file and the file from the puppet master 
>(version 2.7.18) is this normal, we only the the md5 signature? Is there an 
>option to display the diff?

--show_diff should do it on the command line. And yes, this was changed from 
what it used to be in 2.6



This email communication and any files transmitted with it may contain
confidential and or proprietary information and is provided for the use of the
intended recipient only. Any review, retransmission or dissemination of this
information by anyone other than the intended recipient is prohibited. If you
receive this email in error, please contact the sender and delete this
communication and any copies immediately. Thank you.

http://www.encana.com

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] trouble with puppetlabs-mysql module; ignores db and user creation

2012-07-31 Thread tom s

hmmm, it shows up, but doesn't seem to do anything about it:

debug: 
/Stage[main]//Node[puppetclient.tomtest.com]/Mysql::Db[testdb]/Database_grant[testdb@localhost/testdb]/require:
 
requires Database_user[testdb@localhost]
debug: /Stage[main]/Mysql::Server/Service[mysqld]/require: requires 
Package[mysql-server]
debug: /Stage[main]/Mysql::Config/File[/etc/mysql]/notify: subscribes to 
Exec[mysqld-restart]
debug: /Stage[main]/Mysql::Config/File[/etc/mysql/conf.d]/notify: 
subscribes to Exec[mysqld-restart]
debug: /Stage[main]/Mysql::Config/File[/etc/my.cnf]/notify: subscribes to 
Exec[mysqld-restart]
debug: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/require: requires 
File[/etc/mysql/conf.d]
debug: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/notify: subscribes 
to Exec[mysqld-restart]
debug: /Stage[main]/Mysql::Config/File[/root/.my.cnf]/require: requires 
Exec[set_mysql_rootpw]
debug: /Stage[main]/Mysql::Config/File[/root/.my.cnf]/notify: subscribes to 
Exec[mysqld-restart]
debug: 
/Stage[main]//Node[puppetclient.tomtest.com]/Mysql::Db[testdb]/Database[testdb]/require:
 
requires Class[Mysql::Server]
debug: /Stage[main]/Mysql::Server/before: requires Class[Mysql::Config]
debug: 
/Stage[main]//Node[puppetclient.tomtest.com]/Mysql::Db[testdb]/Database_user[testdb@localhost]/require:
 
requires Database[testdb]
debug: /Stage[main]/Mysql::Config/File[/etc/mysql/conf.d]: Autorequiring 
File[/etc/mysql]
debug: Service[mysqld](provider=redhat): Executing 'ps -ef'
debug: Service[mysqld](provider=redhat): PID is 6770
debug: Puppet::Type::Service::ProviderRedhat: Executing '/sbin/chkconfig 
mysql'
debug: Exec[set_mysql_rootpw](provider=posix): Executing check 'mysqladmin 
-u root -pmymysqlrootpass status > /dev/null'
debug: Executing 'mysqladmin -u root -pmymysqlrootpass status > /dev/null'


On Tuesday, 31 July 2012 14:59:53 UTC+1, Walter Heck wrote:
>
> In these cases you would start by checking a run of puppetd -t -d -v 
> to see if it shows up there. If not, then look carefully if the 
> resource is really included on that node. If it is, there should be a 
> hint on what is happening.. 
>
> On Tue, Jul 31, 2012 at 9:19 PM, tom s <> wrote: 
> > There's been at least one other report of something like this, but that 
> was 
> > a little while ago and changes to the module have been made recently. 
> > 
> > Basically I can create a database, set the root password, but not do 
> > anything else: 
> > 
> > node 'puppetclient.tomtest.com' { 
> > class { 'mysql::server': 
> > service_name => 'mysql', 
> > config_hash => { 'root_password' => 'mymysqlrootpass', }, 
> > package_name => 'MySQL-server', 
> > } 
> > mysql::db { 'testdb': 
> > user=> 'testdb', 
> > password=> 'testdb', 
> > host=> 'localhost', 
> > grant   => ['ALL'], 
> > } 
> > } 
> > 
> > Installs mysql, correctly sets the root password then stops.  The DB is 
> > never created and no errors are issued. 
> > 
> > Can anyone help me debug this issue?, I've not gone down the custom 
> > resources route myself yet, so I'm not sure how I go about working out 
> where 
> > the problem is. 
> > 
> > Cheers, 
> > 
> > Tom. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Puppet Users" group. 
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msg/puppet-users/-/O-N6g5jMiRgJ. 
> > To post to this group, send email to puppet-users@googlegroups.com. 
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com. 
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en. 
>
>
>
> -- 
> Walter Heck 
>
> -- 
> Check out my startup: Puppet training and consulting @ 
> http://www.olindata.com 
> Follow @olindata on Twitter and/or 'Like' our Facebook page at 
> http://www.facebook.com/olindata 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/ou9dzjMZbV0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Possible to push changes to nodes?

2012-07-31 Thread Sandra Schlichting


>
>
> Could you post your whole auth.conf once more?


Sure =) I haven't touched anything besides adding your lines towards the 
bottom

auth.conf
http://pastebin.com/1Vv0y2tc

debug output from node
http://pastebin.com/h5cTHxUS

namespace.auth
http://pastebin.com/6Qut6MSJ

puppet.conf
http://pastebin.com/54Q1hyVS
 

> And maybe try to put this: 
>
> [puppetrunner] 
> allow * 
>
> to your client's /etc/puppet/namespace.auth? 
>

I didn't had such file before, but even with, I get the same error. The 
debug log is with this file in place.
 

> Also check if your DNS is working ok. 
>

Just tested. They work both ways.


 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/qFd3CRxo38EJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Bad exit code?

2012-07-31 Thread Stephanie Jackson

Hi all,

I'm running puppet agent as a onetime process.  I would expect, if it can't 
create the pid file, that it would exit non-zero.  However, it seems to exit 
zero.  Is there any way to change this?  I'd like to know if it couldn't run, 
and it seems that this is an error.

[root@db1r1 ~]# puppet agent --onetime --detailed-exitcodes
[root@db1r1 ~]# puppet agent --onetime --detailed-exitcodes
Could not prepare for execution: Could not create PID file: 
/var/run/puppet/agent.pid
[root@db1r1 ~]# echo $?
0

Any thoughts?
-Stephanie

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] File diff in log

2012-07-31 Thread Antidot SAS

Thx the '--show_diff ' helped


Regards,
JM

On Tue, Jul 31, 2012 at 4:25 PM, Kinzel, David wrote:

> >From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com]
> On Behalf Of Antidot SAS
> >Hi everyone,
>
> >Just a quick question since lately, when puppet runs in verbose mode I do
> see anymore the diff from the current file and the file from the puppet
> master (version 2.7.18) is this normal, we only the the md5 signature? Is
> there an option to display the diff?
>
> --show_diff should do it on the command line. And yes, this was changed
> from what it used to be in 2.6
>
>
>
> This email communication and any files transmitted with it may contain
> confidential and or proprietary information and is provided for the use of
> the
> intended recipient only. Any review, retransmission or dissemination of
> this
> information by anyone other than the intended recipient is prohibited. If
> you
> receive this email in error, please contact the sender and delete this
> communication and any copies immediately. Thank you.
>
> http://www.encana.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Managing /etc/ssh/shosts.equiv

2012-07-31 Thread banjer

Hi, does anyone have any elegant solutions for managing shosts.equiv?  In 
my puppet ssh module, host keys for /etc/ssh/ssh_known_hosts are 
automatically managed with:

@@sshkey { $hostname:
ensure => present,
type => "rsa",
key  => $sshrsakey,
}

Sshkey <<| |>>


Is there a similar construct for shosts.equiv?  Its just a list of 
hostnames, so I'm hoping there is an easy way to dump all the puppet agent 
hostnames to a file so I don't have to manually add new hosts as they come 
up.  Thanks for any ideas.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/FaB92_bBLjMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] $concat_basedir not defined

Hey folks,

I am using puppet for some OpenStack deployments and on a new node things 
look pretty good right until after the successful reception of a cert from 
the puppet master.  I get this error: 

err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
$concat_basedir not defined. Try running again with pluginsync enabled at 
/usr/share/puppet/modules/concat/manifests/setup.pp:25 on node 
controller-1.example.com
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

Things seem to be as they should in the setup.pp file it refers to.  I have 
searched for similar issues and cannot seem to find much on this issue.  It 
happens every time I build a node.

Below is the setup.pp file for your reference.

# Sets up the concat system.
#
# $concatdir is where the fragments live and is set on the fact 
concat_basedir.
# Since puppet should always manage files in $concatdir and they should
# not be deleted ever, /tmp is not an option.
#
# $puppetversion should be either 24 or 25 to enable a 24 compatible
# mode, in 24 mode you might see phantom notifies this is a side effect
# of the method we use to clear the fragments directory.
#
# The regular expression below will try to figure out your puppet version
# but this code will only work in 0.24.8 and newer.
#
# It also copies out the concatfragments.sh file to ${concatdir}/bin
class concat::setup {
  $id = $::id
  $root_group = $id ? {
root=> 0,
default => $id
  }

  if $::concat_basedir {
$concatdir = $::concat_basedir
  } else {
fail ("\$concat_basedir not defined. Try running again with pluginsync 
enabled")
  }

  $majorversion = regsubst($::puppetversion, 
'^[0-9]+[.]([0-9]+)[.][0-9]+$', '\1')

  file{"${concatdir}/bin/concatfragments.sh":
owner  => $id,
group  => $root_group,
mode   => '0755',
source => $majorversion ? {
  24  => 'puppet:///concat/concatfragments.sh',
  default => 'puppet:///modules/concat/concatfragments.sh'
};

  [ $concatdir, "${concatdir}/bin" ]:
ensure => directory,
owner  => $id,
group  => $root_group,
mode   => '0750';

  ## Old versions of this module used a different path.
  '/usr/local/bin/concatfragments.sh':
ensure => absent;
  }
}

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/HJw_dn5BW_EJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined



- Original Message -
> From: "Shannon McFarland" 
> To: puppet-users@googlegroups.com
> Sent: Tuesday, July 31, 2012 9:06:04 AM
> Subject: [Puppet Users] $concat_basedir not defined
> 
> Hey folks,
> 
> 
> I am using puppet for some OpenStack deployments and on a new node
> things look pretty good right until after the successful reception
> of a cert from the puppet master. I get this error:
> 
> 
> 
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: $concat_basedir not defined. Try running again with pluginsync 
> enabled at

pretty much as it says here, try enabling pluginsync in your 
puppet.conf on the node using pluginsync=true

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined

That is the issue.  It is already enabled.
[main]
logdir=/var/log/puppet
server=
pluginsync=true


On Tuesday, July 31, 2012 10:27:04 AM UTC-6, R.I. Pienaar wrote:
>
>
>
> - Original Message - 
> > From: "Shannon McFarland"  
> > To: puppet-users@googlegroups.com 
> > Sent: Tuesday, July 31, 2012 9:06:04 AM 
> > Subject: [Puppet Users] $concat_basedir not defined 
> > 
> > Hey folks, 
> > 
> > 
> > I am using puppet for some OpenStack deployments and on a new node 
> > things look pretty good right until after the successful reception 
> > of a cert from the puppet master. I get this error: 
> > 
> > 
> > 
> > err: Could not retrieve catalog from remote server: Error 400 on 
> > SERVER: $concat_basedir not defined. Try running again with pluginsync 
> enabled at 
>
> pretty much as it says here, try enabling pluginsync in your 
> puppet.conf on the node using pluginsync=true 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/DLVbAUrlT9UJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined



- Original Message -
> From: "Shannon McFarland" 
> To: puppet-users@googlegroups.com
> Sent: Tuesday, July 31, 2012 9:30:35 AM
> Subject: Re: [Puppet Users] $concat_basedir not defined
> 
> That is the issue. It is already enabled.
> 
> [main]
> logdir=/var/log/puppet
> server=
> pluginsync=true

Best to show the full output then from "puppet agent --test"

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined

localadmin@controller-1:/$ puppet agent --test
err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
$concat_basedir not defined. Try running again with pluginsync enabled at 
/usr/share/puppet/modules/concat/manifests/setup.pp:25 on node 
controller-1.example.com
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
localadmin@controller-1:/$

Also, just so you have it:
localadmin@controller-1:/$ puppet agent -td
debug: Failed to load library 'rubygems' for feature 'rubygems'
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/home/localadmin/.puppet/ssl/private]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: /File[/home/localadmin/.puppet/ssl/private_keys]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: /File[/home/localadmin/.puppet/ssl/public_keys]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: /File[/home/localadmin/.puppet/var/state/graphs]: Autorequiring 
File[/home/localadmin/.puppet/var/state]
debug: /File[/home/localadmin/.puppet/var/client_yaml]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/var/client_data]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/var/run]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/var/log]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/ssl/certs]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: /File[/home/localadmin/.puppet/var/state]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/ssl]: Autorequiring 
File[/home/localadmin/.puppet]
debug: /File[/home/localadmin/.puppet/var/lib]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/var/state/last_run_report.yaml]: 
Autorequiring File[/home/localadmin/.puppet/var/state]
debug: 
/File[/home/localadmin/.puppet/ssl/certs/controller-1.example.com.pem]: 
Autorequiring File[/home/localadmin/.puppet/ssl/certs]
debug: /File[/home/localadmin/.puppet/ssl/crl.pem]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: /File[/home/localadmin/.puppet/var/clientbucket]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/var]: Autorequiring 
File[/home/localadmin/.puppet]
debug: /File[/home/localadmin/.puppet/ssl/certs/ca.pem]: Autorequiring 
File[/home/localadmin/.puppet/ssl/certs]
debug: /File[/home/localadmin/.puppet/var/facts]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/var/state/last_run_summary.yaml]: 
Autorequiring File[/home/localadmin/.puppet/var/state]
debug: 
/File[/home/localadmin/.puppet/ssl/public_keys/controller-1.example.com.pem]: 
Autorequiring File[/home/localadmin/.puppet/ssl/public_keys]
debug: /File[/home/localadmin/.puppet/ssl/certificate_requests]: 
Autorequiring File[/home/localadmin/.puppet/ssl]
debug: 
/File[/home/localadmin/.puppet/ssl/private_keys/controller-1.example.com.pem]: 
Autorequiring File[/home/localadmin/.puppet/ssl/private_keys]
debug: Finishing transaction 70190598951000
debug: /File[/home/localadmin/.puppet/ssl/certs/ca.pem]: Autorequiring 
File[/home/localadmin/.puppet/ssl/certs]
debug: /File[/home/localadmin/.puppet/ssl/crl.pem]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: /File[/home/localadmin/.puppet/ssl/private]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: /File[/home/localadmin/.puppet/var/log]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: 
/File[/home/localadmin/.puppet/ssl/private_keys/controller-1.example.com.pem]: 
Autorequiring File[/home/localadmin/.puppet/ssl/private_keys]
debug: /File[/home/localadmin/.puppet/ssl/private_keys]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: /File[/home/localadmin/.puppet/ssl/public_keys]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: 
/File[/home/localadmin/.puppet/ssl/public_keys/controller-1.example.com.pem]: 
Autorequiring File[/home/localadmin/.puppet/ssl/public_keys]
debug: /File[/home/localadmin/.puppet/var/facts]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/var/lib]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug: /File[/home/localadmin/.puppet/ssl/certs]: Autorequiring 
File[/home/localadmin/.puppet/ssl]
debug: /File[/home/localadmin/.puppet/ssl/certificate_requests]: 
Autorequiring File[/home/localadmin/.puppet/ssl]
debug: 
/File[/home/localadmin/.puppet/ssl/certs/controller-1.example.com.pem]: 
Autorequiring File[/home/localadmin/.puppet/ssl/certs]
debug: /File[/home/localadmin/.puppet/var]: Autorequiring 
File[/home/localadmin/.puppet]
debug: /File[/home/localadmin/.puppet/ssl]: Autorequiring 
File[/home/localadmin/.puppet]
debug: /File[/home/localadmin/.puppet/var/run]: Autorequiring 
File[/home/localadmin/.puppet/var]
debug:

Re: [Puppet Users] Possible to push changes to nodes?

2012-07-31 Thread Eric Sorenson

We saw this too, and I don't think it's intentional. 

On Tuesday, July 31, 2012 2:08:53 AM UTC-7, Sandra Schlichting wrote:
>
> Note that getting puppet kick working is a multi-step process:
>>
>> - Gotta change all agents' puppet.conf to have listen = true in either 
>> [main] or [agent].
>> - Gotta open port 8139 to incoming connections on every agent node's 
>> firewall.  
>> - Gotta add the following stanza somewhere near the top of each agent 
>> node's auth.conf file:
>>
>> path /run
>> auth yes
>> allow puppet.example.com
>>
>
> That is very interesting!
>
> I have now tried this with Puppet 3.0rc3, and on the node side I get
>
> Error: Could not find indirection 'run'
>
> so I have filed a bug report
>
> http://projects.puppetlabs.com/issues/15717
>
> Do you think it could be a bug, or am I doing something wrong?
>
> My setup is explained in the bug report =)
>
>
>
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/TTYrth0atrIJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined



- Original Message -
> From: "Shannon McFarland" 
> To: puppet-users@googlegroups.com
> Sent: Tuesday, July 31, 2012 9:35:54 AM
> Subject: Re: [Puppet Users] $concat_basedir not defined
> 
> 
> localadmin@controller-1:/$ puppet agent --test
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: $concat_basedir not defined. Try running again with
> pluginsync enabled at
> /usr/share/puppet/modules/concat/manifests/setup.pp:25 on node
> controller-1.example.com
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
> localadmin@controller-1:/$

Looks like you're not running it as root, this probably affects
what config is being used.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined

OK. I am rebuilding the node again to check something.  I will manually run 
it as root but this is not a solution other than this test as we won't be 
having our nodes come up running as root accounts.

On Tuesday, July 31, 2012 11:07:45 AM UTC-6, R.I. Pienaar wrote:
>
>
>
> - Original Message - 
> > From: "Shannon McFarland"  
> > To: puppet-users@googlegroups.com 
> > Sent: Tuesday, July 31, 2012 9:35:54 AM 
> > Subject: Re: [Puppet Users] $concat_basedir not defined 
> > 
> > 
> > localadmin@controller-1:/$ puppet agent --test 
> > err: Could not retrieve catalog from remote server: Error 400 on 
> > SERVER: $concat_basedir not defined. Try running again with 
> > pluginsync enabled at 
> > /usr/share/puppet/modules/concat/manifests/setup.pp:25 on node 
> > controller-1.example.com 
> > warning: Not using cache on failed catalog 
> > err: Could not retrieve catalog; skipping run 
> > localadmin@controller-1:/$ 
>
> Looks like you're not running it as root, this probably affects 
> what config is being used. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/QXtZ0oLQApMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined

Yeah, I ran it with 'sudo' and it pulled the plugin and kicked off.  So, 
how can I point to the correct configuration without running as root or 
sudo in my preseed?

On Tuesday, July 31, 2012 11:26:11 AM UTC-6, Shannon McFarland wrote:
>
> OK. I am rebuilding the node again to check something.  I will manually 
> run it as root but this is not a solution other than this test as we won't 
> be having our nodes come up running as root accounts.
>
> On Tuesday, July 31, 2012 11:07:45 AM UTC-6, R.I. Pienaar wrote:
>>
>>
>>
>> - Original Message - 
>> > From: "Shannon McFarland"  
>> > To: puppet-users@googlegroups.com 
>> > Sent: Tuesday, July 31, 2012 9:35:54 AM 
>> > Subject: Re: [Puppet Users] $concat_basedir not defined 
>> > 
>> > 
>> > localadmin@controller-1:/$ puppet agent --test 
>> > err: Could not retrieve catalog from remote server: Error 400 on 
>> > SERVER: $concat_basedir not defined. Try running again with 
>> > pluginsync enabled at 
>> > /usr/share/puppet/modules/concat/manifests/setup.pp:25 on node 
>> > controller-1.example.com 
>> > warning: Not using cache on failed catalog 
>> > err: Could not retrieve catalog; skipping run 
>> > localadmin@controller-1:/$ 
>>
>> Looks like you're not running it as root, this probably affects 
>> what config is being used. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/9wmGhWSDYZYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] exec in master transfer files to the node

2012-07-31 Thread Nikolaos Hatzopoulos

exec { "sshkeygen":
path=> "/usr/bin:/usr/sbin:/bin",
creates => [ "puppet:///myuser/files/$username/id_rsa" ,
"puppet:///myuser/files/$username/id_rsa.pub" ],
command =>
generate("/bin/bash","/etc/puppet/manifests/myusers/sshkeygen.bash" )
}


this command does not work!! why?

err: Could not retrieve catalog from remote server: wrong header line format
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

--Nikos

On Tue, Jul 31, 2012 at 12:07 AM, David Schmitt  wrote:

> On 30.07.2012 19:21, Nikolaos Hatzopoulos wrote:
>
>> How you exec something in the master produce a file and
>> this files you transfer it to your node?
>>
>
> take a look at the template(), inline_template() and generate() function:
>
> http://docs.puppetlabs.com/**references/stable/function.**html
>
>
> Best Regards, David
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users+unsubscribe@**
> googlegroups.com .
> For more options, visit this group at http://groups.google.com/**
> group/puppet-users?hl=en
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Long processing time using Augeas

2012-07-31 Thread Jake - USPS

Try something like the following instead (added 'incl' and 'lens' and 
removed context as its default based on incl is what you had) :

augeas { 'homeLV':
  incl => '/etc/fstab',
  lens => 'Fstab.lns',
  changes => [
'set *[file = "/home"]/dump 0',
'set *[file = "/home"]/passno 0',
  ],
  onlyif => 'match *[file = "/home"] size > 0',
}

I think this helps augeas not autoload everything it can possibly edit and 
narrows it in on just one file.

Regards,
Jake

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/CiA2fUipMl8J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] puppet doc questions

2012-07-31 Thread llow...@oreillyauto.com

Does puppet doc require a specific version of any gems (such as rdoc or 
rake) to operate?

I'm getting some errors when I try to generate my rdoc now.

# puppet doc --output /var/www/test --modulepath 
/etc/puppet/environments/test/modules -m rdoc
RDoc::RDocError is deprecated and will be removed in RDoc 4
Could not generate documentation: uninitialized constant 
RDoc::RDoc::Generator


I am on puppet 2.7.17, Ubuntu 12.04 (32bit, server).

# gem list

*** LOCAL GEMS ***

abstract (1.0.0)
actionmailer (3.0.15)
actionpack (3.0.15)
activemodel (3.0.15)
activerecord (3.0.15)
activeresource (3.0.15)
activesupport (3.0.15)
ancestry (1.2.5)
arel (2.0.10)
audited (3.0.0.rc1)
audited-activerecord (3.0.0.rc1)
builder (2.1.2)
diff-lcs (1.1.3)
erubis (2.6.6)
has_many_polymorphs (3.0.0.beta1)
hiera (0.3.0)
i18n (0.5.0)
jquery-rails (1.0.19)
json (1.7.3)
mail (2.2.19)
metaclass (0.0.1)
mime-types (1.19)
mocha (0.12.1)
mysql (2.8.1)
net-ldap (0.3.1)
polyglot (0.3.3)
puppetlabs_spec_helper (0.2.0)
rack (1.2.5, 1.1.0)
rack-mount (0.6.14)
rack-test (0.5.7)
rails (3.0.15)
railties (3.0.15)
rake (0.9.2.2)
rdoc (3.12)
rdoc-data (3.12)
rest-client (1.6.7)
rspec (2.11.0)
rspec-core (2.11.1)
rspec-expectations (2.11.2)
rspec-mocks (2.11.1)
rspec-puppet (0.1.3)
ruby2ruby (1.3.1)
ruby_parser (2.3.1)
safemode (1.0.1)
scoped_search (2.3.7)
sexp_processor (3.2.0)
thor (0.14.6)
treetop (1.4.10)
tzinfo (0.3.33)
uuidtools (2.1.3, 2.1.2)
will_paginate (3.0.3)

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/w8-dWeL-oHAJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] puppet agent --test

2012-07-31 Thread Stuart Cracraft

My times are synced between the two boxes yet this certificate error is being
generated on the puppet.

How can I remove all certs on both master and agent and force them both to 
completely renew?

Or alternatively, what is the "tweak" for:

[root@rhel03 puppet-enterprise-2.5.2-el-6-x86_64]# puppet agent --test
info: Retrieving plugin
err: /File[/var/opt/lib/pe-puppet/lib]: Failed to generate additional resources 
using 'eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server 
certificate B: certificate verify failed.  This is often because the time is 
out of sync on the server or client
err: /File[/var/opt/lib/pe-puppet/lib]: Could not evaluate: SSL_connect 
returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify 
failed.  This is often because the time is out of sync on the server or client 
Could not retrieve file metadata for puppet://puppet/plugins: SSL_connect 
returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify 
failed.  This is often because the time is out of sync on the server or client
err: Could not retrieve catalog from remote server: SSL_connect returned=1 
errno=0 state=SSLv3 read server certificate B: certificate verify failed.  This 
is often because the time is out of sync on the server or client
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
err: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read 
server certificate B: certificate verify failed.  This is often because the 
time is out of sync on the server or client
[root@rhel03 puppet-enterprise-2.5.2-el-6-x86_64]#

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: puppet doc questions

2012-07-31 Thread llow...@oreillyauto.com

As an update, I did find http://projects.puppetlabs.com/issues/11786 which 
indicates that rdoc 1.x is needed, and that rdoc 2.x and 3.x will not work.

However, the oldest gem available is 2.0...

Any recommendations?

On Tuesday, July 31, 2012 1:57:12 PM UTC-5, llo...@oreillyauto.com wrote:
>
> Does puppet doc require a specific version of any gems (such as rdoc or 
> rake) to operate?
>
> I'm getting some errors when I try to generate my rdoc now.
>
> # puppet doc --output /var/www/test --modulepath 
> /etc/puppet/environments/test/modules -m rdoc
> RDoc::RDocError is deprecated and will be removed in RDoc 4
> Could not generate documentation: uninitialized constant 
> RDoc::RDoc::Generator
>
>
> I am on puppet 2.7.17, Ubuntu 12.04 (32bit, server).
>
> # gem list
>
> *** LOCAL GEMS ***
>
> abstract (1.0.0)
> actionmailer (3.0.15)
> actionpack (3.0.15)
> activemodel (3.0.15)
> activerecord (3.0.15)
> activeresource (3.0.15)
> activesupport (3.0.15)
> ancestry (1.2.5)
> arel (2.0.10)
> audited (3.0.0.rc1)
> audited-activerecord (3.0.0.rc1)
> builder (2.1.2)
> diff-lcs (1.1.3)
> erubis (2.6.6)
> has_many_polymorphs (3.0.0.beta1)
> hiera (0.3.0)
> i18n (0.5.0)
> jquery-rails (1.0.19)
> json (1.7.3)
> mail (2.2.19)
> metaclass (0.0.1)
> mime-types (1.19)
> mocha (0.12.1)
> mysql (2.8.1)
> net-ldap (0.3.1)
> polyglot (0.3.3)
> puppetlabs_spec_helper (0.2.0)
> rack (1.2.5, 1.1.0)
> rack-mount (0.6.14)
> rack-test (0.5.7)
> rails (3.0.15)
> railties (3.0.15)
> rake (0.9.2.2)
> rdoc (3.12)
> rdoc-data (3.12)
> rest-client (1.6.7)
> rspec (2.11.0)
> rspec-core (2.11.1)
> rspec-expectations (2.11.2)
> rspec-mocks (2.11.1)
> rspec-puppet (0.1.3)
> ruby2ruby (1.3.1)
> ruby_parser (2.3.1)
> safemode (1.0.1)
> scoped_search (2.3.7)
> sexp_processor (3.2.0)
> thor (0.14.6)
> treetop (1.4.10)
> tzinfo (0.3.33)
> uuidtools (2.1.3, 2.1.2)
> will_paginate (3.0.3)
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/AUpLN9701qoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined



- Original Message -
> From: "Shannon McFarland" 
> To: puppet-users@googlegroups.com
> Sent: Tuesday, July 31, 2012 10:46:37 AM
> Subject: Re: [Puppet Users] $concat_basedir not defined
> 
> Yeah, I ran it with 'sudo' and it pulled the plugin and kicked off.
> So, how can I point to the correct configuration without running as
> root or sudo in my preseed?

then you should edit whatever "puppet agent --configprint config"
reports as the right config file for the user else run puppet with
a specific --config=/etc/puppet/puppet.conf or similar

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [pe-users] [Puppet Users] puppet enterprise

2012-07-31 Thread Stuart Cracraft

Completed and master/agent restarted.

On Jul 31, 2012, at 11:41 AM, Shabir Ahmed  wrote:

> ### edit auth.conf  ###
> 
> #
> # Allow puppet kick access
> path /run
> method save
> auth any
> allow *
> 
>  
> 
> 
> ### edit  puppet.conf on agent under agent section:
> 
> listen = true
> 
> 
> 
> 
> 
> 
> 
> 
> On Mon, Jul 30, 2012 at 9:19 PM, Stuart Cracraft  wrote:
> 
> Here is the log from the puppet master after /etc/init.d/pe-puppet restart:
> 
> # puppet kick --trace --host rhel.oc.cox.net --debug
> Jul 30 21:03:25 rhel01 puppet-master[4266]: Starting Puppet master version 
> 2.7.12 (Puppet Enterprise 2.5.2)
> Jul 30 21:03:25 rhel01 puppet-master[4266]: Denying access: Forbidden 
> request: rhel01.oc.cox.net(10.0.1.6) access to /facts/rhel03.oc.cox.net 
> [save] authenticated  at line 53
> Jul 30 21:03:25 rhel01 puppet-master[4266]: Forbidden request: 
> rhel01.oc.cox.net(10.0.1.6) access to /facts/rhel03.oc.cox.net [save] 
> authenticated  at line 53
> Jul 30 21:03:25 rhel01 puppet-master[4212]: Error 403 on SERVER: Forbidden 
> request: rhel01.oc.cox.net(10.0.1.6) access to /facts/rhel03.oc.cox.net 
> [save] authenticated  at line 53
> Jul 30 21:03:25 rhel01 puppet-master[4266]: Report processor failed: 
> Connection refused - connect(2)
> 
> On Jul 30, 2012, at 8:42 PM, Stuart Cracraft  wrote:
> 
>> Unknown.
>> 
>> And a "kick" from the master to the agent returns with "connection refused - 
>> connect(2)"
>> despite the ports being set (8140, 61613) open on the puppet master firewall 
>> / iptables,
>> and ssh/ping both operational bi-directionally.
>> 
>> Any ideas puppeteers?
>> 
>> --Stuart
>> 
>> On Jul 30, 2012, at 3:17 PM, Gary Larizza  wrote:
>> 
>>> 
>>> 
>>> On Mon, Jul 30, 2012 at 3:10 PM, Stuart Cracraft  wrote:
>>> 
>>> On Jul 30, 2012, at 12:53 PM, Gary Larizza  wrote:
>>> 
 Hey Stuart,
 
 You might want to check out the pe-users list for Enterprise-specific 
 questions (people here can/will answer too, but you might bet better 
 results from the PE users on that list  --> 
 http://puppetlabs.com/services/customer-support/ and see the section on 
 Joining the Puppet Enterprise Users list). 
 
>>> ++ Thanks - I've applied for membership.
>>> 
 Are you sure you're targeting the PE Master and not the original Open 
 Source master?  
 Does the output of `puppet agent --configprint server` match your Puppet 
 Enterprise server address?  
>>> 
>>> It doesn't.
>>> 
>>> ++ The master is reporting one fully qualified name, its own, but not its 
>>> alias puppet.
>>> ++ The agent is reporting a different name, puppet. 
>>> ++ There is a skew. What is the best fix?
>>> 
>>> Ahh, great.  So, check out /etc/puppetlabs/puppet/puppet.conf and edit the 
>>> 'server' parameter to point to your Enterprise Master server's address.  By 
>>> default the value set is 'puppet', but you can pass a different value to 
>>> the installer to change this value - I believe the 'q_puppetagent_server=' 
>>> question (if you generate an installer answers file).   Does this help?
>>> 
>>>  
>>> 
 Did you make any changes to /etc/puppetlabs/puppet/auth.conf on the PE 
 Master?
>>> 
>>> 
>>> ++ No. It is unchanged.
>>> 
 
 
 
 On Sun, Jul 29, 2012 at 11:04 PM, Stuart Cracraft  
 wrote:
 No problem installing open puppet and using it. patterns run aok.
 
 when trying to use the installer for pe, on the puppetmaster, installs ok.
 
 when trying to use the installer for pe, on the puppet agent, installs ok
 but no cert sent as shown by puppet cert list on puppetmaster.
 
 also
 
   puppet agent --test
 
 on puppet agent shows
 
 err: could not retrieve catalog from remote server:
 error 400 on SERVER: Error 403 on SERVER:
 forbidden request puppemasters-fully-qualified-name.com access to /facts/ 
 agent [save] authenticated at line 53
 warning: not using cache on failed catalog
 error: could not retrieve catalog: skipping run
 
 Anyone knows what causes the above or how to proceed?
 
 
 --
 You received this message because you are subscribed to the Google Groups 
 "Puppet Users" group.
 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to 
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/puppet-users?hl=en.
 
 
 
 
 -- 
 
 Gary Larizza
 Professional Services Engineer
 Puppet Labs
 
 Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
 Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12 
  
 
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 "Puppet Users" group.
 To post to this group, send email to puppet-users@googlegroups.com.
 T

[Puppet Users] Calling a Custom Function?

2012-07-31 Thread bbloke


Hello all,

I'm trying to find the syntax for calling a custom function from another 
module.  I'm trying to use this custom function to test if a file exists on 
the Puppet master -

http://puppetmaster.blog.com/2010/11/09/file-exists/

I want to put this function in a module called "custom" and then use it 
from multiple other modules.  I just don't know what the syntax for doing 
that is, can anyone help?

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/-Yy4R79A68UJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Modify Facter Value

2012-07-31 Thread rjl

Hi all,
I have a custom facts script that is distributed to all of my puppet 
clients. This first thing this script does is read a file on the client to 
determine the 'type' of server that it is. Later in the script, I would 
like to change the value based on some additional information. I don't seem 
to be able to modify the value of a fact once it has been set. For example

Facter.add("server_type") do
  setcode do
 "apache_web_server"
  end
end

# Later I may want to change the value.

if Facter.value("http_server") = "false"
   # Change value of "server_type" here. I have tried many different 
approaches but none work.
end

Any advice would be greatly appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/AXcBrQsr4YsJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] What data to restore an existing Puppet Master?

2012-07-31 Thread Mitchell Hashimoto

I'm planning some disaster scenarios for our Puppet master, and was curious
what data needs to be restored if I need to rebuild a Puppet master from
scratch? i.e. what needs to be backed up?

Are all necessary certs in `/var/lib/puppet/ssl`. Should that whole
directory get backed up? Or only certain files in there?

Is there any other data I need to back up?

Best,
Mitchell

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Modify Facter Value

2012-07-31 Thread rjl

Of course should be == and not =

if Facter.value("http_server") == "false"
   # Change value of "server_type" here. I have tried many different 
approaches but none work.
end

On Tuesday, July 31, 2012 2:38:15 PM UTC-6, rjl wrote:
>
> Hi all,
> I have a custom facts script that is distributed to all of my puppet 
> clients. This first thing this script does is read a file on the client to 
> determine the 'type' of server that it is. Later in the script, I would 
> like to change the value based on some additional information. I don't seem 
> to be able to modify the value of a fact once it has been set. For example
>
> Facter.add("server_type") do
>   setcode do
>  "apache_web_server"
>   end
> end
>
> # Later I may want to change the value.
>
> if Facter.value("http_server") = "false"
># Change value of "server_type" here. I have tried many different 
> approaches but none work.
> end
>
> Any advice would be greatly appreciated.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/ZAR3EpUQvYUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Modify Facter Value

It may be best to hold your value in a temporary variable and just have the 
setcode run at the end. I can't remember where I read it, but I don't think 
ruby custom facts can override other ruby custom facts once they are set 
(thought I believe the FACTER_ environment variables can override ruby 
custom facts).

On Tuesday, July 31, 2012 3:38:15 PM UTC-5, rjl wrote:
>
> Hi all,
> I have a custom facts script that is distributed to all of my puppet 
> clients. This first thing this script does is read a file on the client to 
> determine the 'type' of server that it is. Later in the script, I would 
> like to change the value based on some additional information. I don't seem 
> to be able to modify the value of a fact once it has been set. For example
>
> Facter.add("server_type") do
>   setcode do
>  "apache_web_server"
>   end
> end
>
> # Later I may want to change the value.
>
> if Facter.value("http_server") = "false"
># Change value of "server_type" here. I have tried many different 
> approaches but none work.
> end
>
> Any advice would be greatly appreciated.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/QQFBsSymMs8J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Possible to push changes to nodes?

2012-07-31 Thread Nick Fagerlund



On Tuesday, July 31, 2012 6:03:37 AM UTC-7, Jakov Sosic wrote:
>
>
> ... And maybe try to put this: 
>
> [puppetrunner] 
> allow * 
>
> to your client's /etc/puppet/namespace.auth? 
>
>
>
Don't use namespaceauth.conf; it's vestigial code and does nothing. Patrick 
and I proved last week that it's fully inert in at least Puppet 2.7 and 
later, so it'll have no effect on what you're seeing. (Although there was a 
bug during the 2.6 series where we required the file to be PRESENT even 
though we never consulted it. That was pretty cool.)

And yes, Sandra's experience sounds like a bug! Thank you for reporting.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/bJUIeW2aGW4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Access @resouce in custom type

Is it possible to access @resource variables inside a type?

I would like to make some decisions on parameters based on other parameters 
that may have already been set.

For example,
---
  newparam(:param1) do
Puppet.debug "Found drivesperarray parameter"
desc "parameter 1"
validate do |value|
  if resource[:otherparam] then
#dosomething
  else
resource[:param1] = 0
  end
end
Puppet.debug "Parameter 1 is: #{@resource[:param1]}"
  end
---

But I keep getting messages like "undefined method `[]' for nil:NilClass" 

Anyone have experience with this? I've tried searching around for example 
without much luck...

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/GvvMAT2llvMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] "Could not find dependency Package" even the package already theres.

2012-07-31 Thread Calvin Walton

On Tue, 2012-07-31 at 15:58 +0700, heriyanto wrote:
> asterisk package already installed. I don't plan installation for this 
> package managed by puppet.
> just want manage the file configuration.

If the package is already installed, adding
package { 'asterisk': }
to your puppet config won't do anything to your system. Puppet will
simply notice that the 'asterisk' package is already there, mark the
resource as present, and continue on with all the dependencies
satisfied.

> it come up when i yum search.
> 
> actually how "require => Package" working? its checking to repos or into 
> system?

require => Package[] doesn't do anything by itself. All it does is make
sure that the corresponding package {} resource is checked before
whatever you added the 'require' to. It just sets the order.

The package {} resource itself will query the package management system
to see if the package is installed, and will install it if it is
missing.

-- 
Calvin Walton 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: High CPU load / queued passenger requests

2012-07-31 Thread Luke Baker

I ended up restart the mysql database on the storeconfigs server which 
helped this problem dramatically. But, I'm still open for more tuning 
options if they're out there : )

On Tuesday, July 31, 2012 8:34:45 AM UTC-5, Luke Baker wrote:
>
> After restarting our puppetmaster host, we are seeing high CPU load and a 
> ton of queued passenger requests. I would suspect that our puppetmaster is 
> falling victim to the thundering herd of puppet agents, but we have 
> deployed most of our agents using a randomized cron job. The others are 
> using 'splay = true' if they are running puppet agent. 
>
> Some info:
> Puppetmaster is RHEL6 x86_64 (VM)
> 4 vCPU 8GB memory
> Apache 2.2
> Passenger 3.0.7
>
> The vhost for our puppetmaster includes these passenger options:
> PassengerHighPerformance on
> PassengerUseGlobalQueue on
> PassengerPoolIdleTime 1500
> PassengerMaxPoolSize 24
> PassengerMaxRequests 4000
> PassengerStatThrottleRate 120
> PassengerSpawnMethod smart
> RackAutoDetect Off
> RailsAutoDetect Off
>
>
> Look at all of these queued requests!
>
> Passenger-status:
> --- General information ---
> max  = 24
> count= 24
> active   = 22
> inactive = 2
> Waiting on global queue: 234
>
> --- Application groups ---
> /etc/puppet/rack:
>   App root: /etc/puppet/rack
>   * PID: 24840   Sessions: 1Processed: 528 Uptime: 9h 41m 19s
>   * PID: 24703   Sessions: 1Processed: 513 Uptime: 9h 42m 17s
>   * PID: 24642   Sessions: 1Processed: 567 Uptime: 9h 42m 29s
>   * PID: 24827   Sessions: 1Processed: 572 Uptime: 9h 41m 28s
>   * PID: 24869   Sessions: 1Processed: 530 Uptime: 9h 41m 4s
>   * PID: 24586   Sessions: 1Processed: 572 Uptime: 9h 42m 32s
>   * PID: 24715   Sessions: 1Processed: 539 Uptime: 9h 42m 17s
>   * PID: 29046   Sessions: 1Processed: 487 Uptime: 8h 52m 35s
>   * PID: 24609   Sessions: 1Processed: 575 Uptime: 9h 42m 30s
>   * PID: 24605   Sessions: 1Processed: 488 Uptime: 9h 42m 30s
>   * PID: 24831   Sessions: 1Processed: 555 Uptime: 9h 41m 27s
>   * PID: 29036   Sessions: 1Processed: 549 Uptime: 8h 52m 35s
>   * PID: 24583   Sessions: 1Processed: 565 Uptime: 9h 42m 32s
>   * PID: 24768   Sessions: 1Processed: 521 Uptime: 9h 41m 56s
>   * PID: 24850   Sessions: 1Processed: 579 Uptime: 9h 41m 16s
>   * PID: 29050   Sessions: 1Processed: 497 Uptime: 8h 52m 35s
>   * PID: 24567   Sessions: 1Processed: 536 Uptime: 9h 42m 37s
>   * PID: 24761   Sessions: 1Processed: 570 Uptime: 9h 42m 5s
>   * PID: 24709   Sessions: 1Processed: 575 Uptime: 9h 42m 17s
>   * PID: 29042   Sessions: 1Processed: 488 Uptime: 8h 52m 35s
>   * PID: 24865   Sessions: 1Processed: 559 Uptime: 9h 41m 5s
>   * PID: 29039   Sessions: 1Processed: 506 Uptime: 8h 52m 35s
>
> /usr/share/foreman:
>   App root: /usr/share/foreman
>   * PID: 24724   Sessions: 0Processed: 5743Uptime: 9h 42m 16s
>   * PID: 24717   Sessions: 0Processed: 5099Uptime: 9h 42m 17s
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/hNtnLgeBLzYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Access @resouce in custom type

On Tuesday, July 31, 2012 4:05:28 PM UTC-5, ZJE wrote:
>
> Is it possible to access @resource variables inside a type?
>
> I would like to make some decisions on parameters based on other 
> parameters that may have already been set.
>
> For example,
> ---
>   newparam(:param1) do
> Puppet.debug "Found drivesperarray parameter"
> desc "parameter 1"
> validate do |value|
>   if resource[:otherparam] then
> #dosomething
>   else
> resource[:param1] = 0
>   end
> end
> Puppet.debug "Parameter 1 is: #{@resource[:param1]}"
>   end
> ---
>
> But I keep getting messages like "undefined method `[]' for nil:NilClass" 
>
> Anyone have experience with this? I've tried searching around for example 
> without much luck...
>
> Thanks!
>


Actually, it turns out that setting  "resource[:param1] = 0" invokes the 
validate loop and the whole thing blows up eventually throws "stack level 
too deep" (glad that it didn't let it keep going)

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/bPZFhA3wtNMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Foreman 1.0 released!

2012-07-31 Thread trey85stang

Very nice and polished release.  I upgraded perfectly with the rpms on 
centos 6.3.  I greatly appreciate the new texteditor for the provisioning 
templates/scripts.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/F5T_TKhUlUYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Custom Package Provider Issue

2012-07-31 Thread Matthew

I'm running into an issue using a custom package provider for PEAR. 
Currently I've been using the provider found 
here,
 
which seems to work fine when I manually copy it to a client running the 
puppet agent.

The problem I'm having occurs when I rely on Puppet's pluginsync feature to 
copy the config out. I've got the custom provider stored on the puppet 
master in /etc/puppet/modules/common/lib/provider/package/pear.rb, and the 
puppet.conf for the client contains pluginsync=true The custom provider is 
being synchronized out to the client fine; that's not the issue. The 
problem shows up when I try to use a class requiring the custom provider on 
the client PC: despite the presence of the pear.rb file in 
/var/lib/puppet/lib/provider/package/ after puppet initially synchronizes 
it, Puppet continues to throw an error that it cannot find the package 
provider, even after restarting Puppet. 
>
> puppet-agent[13581]: Failed to apply catalog: Parameter provider failed: 
> Invalid package provider 'pear' at 
> /etc/puppet/manifests/classes/rhel-web.pp:50
>

Now the weird thing that happens, is that if I modify the pear.rb provider 
file on the client running the Puppet agent, then restart Puppet, it 
notices the file has been modified, re-synchronizes it from the Puppet 
master, and then the class using the custom provider works and install the 
packages using the custom provider.

I've verified that the file being transmitted initially is indeed identical 
to the file that is re-sent after being modified.

This issue has been reproducible each time I've tried it. Currently the 
setup I'm using to test this uses Puppet 2.7.18 with 64-bit RHEL6 on the 
Puppet master and 32-bit RHEL6 on the client running the Puppet agent.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/9q04TOuljm4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Get extra error output when debugging custom types?

Is it possible to get extra output when running custom types? Right now, 
I'm getting an error message and I'm not sure where in the code it's being 
thrown from.
For example, I can see that I'm trying to iterate over a null object, but 
I'm not sure where in the code this happening when the message is this:
---
Error: /Stage[main]//Node[testnode0101]/TestType[testname]: Could not 
evaluate: undefined method `each' for nil:NilClass
---

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/xV6maUmMVagJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Modify Facter Value

2012-07-31 Thread rjl

Thanks ZJE. That is what I ended up doing. 

On Tuesday, July 31, 2012 2:50:44 PM UTC-6, ZJE wrote:
>
> It may be best to hold your value in a temporary variable and just have 
> the setcode run at the end. I can't remember where I read it, but I don't 
> think ruby custom facts can override other ruby custom facts once they are 
> set (thought I believe the FACTER_ environment variables can override ruby 
> custom facts).
>
> On Tuesday, July 31, 2012 3:38:15 PM UTC-5, rjl wrote:
>>
>> Hi all,
>> I have a custom facts script that is distributed to all of my puppet 
>> clients. This first thing this script does is read a file on the client to 
>> determine the 'type' of server that it is. Later in the script, I would 
>> like to change the value based on some additional information. I don't seem 
>> to be able to modify the value of a fact once it has been set. For example
>>
>> Facter.add("server_type") do
>>   setcode do
>>  "apache_web_server"
>>   end
>> end
>>
>> # Later I may want to change the value.
>>
>> if Facter.value("http_server") = "false"
>># Change value of "server_type" here. I have tried many different 
>> approaches but none work.
>> end
>>
>> Any advice would be greatly appreciated.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/1YHE2l76EAgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] NFS mounts with puppet creates error

2012-07-31 Thread Christopher Wood

(inline)

On Tue, Jul 31, 2012 at 05:23:00AM -0700, Axel Bock wrote:
>Hi group,
> 
>I am managing an NFS mount with puppet. And it does not work, and
>seriously I really don't see how this can work out nicely. First I make
>sure with a file {} class that the directory I want to mount exists. Cause
>it is used by the webserver it should belong to the wwwrun/www group on
>the system. No prob.

This is changing the directory inode on the nfs client.

>Then I mount the NFS share on the dir. No prob.

Now the inode that your nfs client sees is on the nfs server. It is not the 
same inode that you just managed with puppet.

(I say inode, but depending on the nfs server it may not be a unix filesystem 
behind it.)

>On the 2nd run of puppet though ... Error! The NFS mount point is
>"changed" over to root:root with 775 permissions (or 777? I don't
>remember). Puppet of course now wants to set the user:group of the dir ...
>and naturally fails.

This is dependent on your nfs server settings. You likely have root_squash set 
by default (see 'man exportfs'), so any activity as the root user on the nfs 
client is mapped to a "nobody" or "nfsnobody" (uid 65535 or similar) on the nfs 
server. Check /etc/exports on the nfs server.

>So is there a way to keep this error from happening?

You can set no_root_squash on the export and run 'exportfs -a' on the nfs 
server. Then you might have to remount on the client end.

The broader issue is whether you should manage file permissions on the nfs 
client or the nfs server. I haven't decided myself, but if you do it on the 
server you won't have to reduce security by running no_root_squash. The mount 
will also arrive with the correct permissions.

>Thanks in advance & greetings,
>Axel.
> 
>--
>You received this message because you are subscribed to the Google Groups
>"Puppet Users" group.
>To view this discussion on the web visit
>[1]https://groups.google.com/d/msg/puppet-users/-/tw1oa58dRhoJ.
>To post to this group, send email to puppet-users@googlegroups.com.
>To unsubscribe from this group, send email to
>puppet-users+unsubscr...@googlegroups.com.
>For more options, visit this group at
>http://groups.google.com/group/puppet-users?hl=en.
> 
> References
> 
>Visible links
>1. https://groups.google.com/d/msg/puppet-users/-/tw1oa58dRhoJ

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Custom Package Provider Issue

2012-07-31 Thread Matthew

I'm running into a weird issue with a custom package provider for PEAR. I'm 
using the provider I found 
hereand
 the provider itself works fine. I've got it stored on the Puppet master 
under /etc/puppet/modules/common/lib/provider/package/pear.rb and the 
puppet.conf has pluginsync = true enabled on it, however when I initially 
deploy a class with any packages utilizing the pear provider, Puppet throws 
an error that it can't find the package provider

Failed to apply catalog: Parameter provider failed: Invalid package 
> provider 'pear' at /etc/puppet/manifests/classes/rhel-web.pp:50
>

Puppet throws this error even though the file has been synchronized and is 
available on the computer running the puppet agent in 
/var/lib/puppet/lib/provider/package/pear.rb. 

The weird behavior occurs if I modify the pear provider (on the client, or 
on the puppet master) so that puppet recognizes the file has been changed 
and re-sync's it from the Puppet master. After the file has been re-sync'd, 
the class using the custom provider starts working.
I've done diff comparisons of the file that is initially sent to the client 
and the file that it receives after the client side file is modified, and 
the files are identical, so I'm not sure why Puppet is failing initially 
and then starts working after re-transmitting that file. I've tried 
restarting the Puppet agent on the client and even rebooting the client and 
Puppet still behaves this way each time. So far I've been able to reproduce 
the issue every time.


Currently I am using Puppet 2.7.18 on both the Puppet master and client, 
with 64-bit RHEL 6 on the master and 32-bit RHEL6 on the client. 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Tu9KjOOb9LwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Modify Facter Value

2012-07-31 Thread Adrien Thebo

You can have multiple resolutions for a single fact, and use fact
precedence to determine which ones should be used first.
http://docs.puppetlabs.com/guides/custom_facts.html#fact-precedence has the
details on this.

On Tue, Jul 31, 2012 at 3:24 PM, rjl  wrote:

> Thanks ZJE. That is what I ended up doing.
>
>
> On Tuesday, July 31, 2012 2:50:44 PM UTC-6, ZJE wrote:
>>
>> It may be best to hold your value in a temporary variable and just have
>> the setcode run at the end. I can't remember where I read it, but I don't
>> think ruby custom facts can override other ruby custom facts once they are
>> set (thought I believe the FACTER_ environment variables can override ruby
>> custom facts).
>>
>> On Tuesday, July 31, 2012 3:38:15 PM UTC-5, rjl wrote:
>>>
>>> Hi all,
>>> I have a custom facts script that is distributed to all of my puppet
>>> clients. This first thing this script does is read a file on the client to
>>> determine the 'type' of server that it is. Later in the script, I would
>>> like to change the value based on some additional information. I don't seem
>>> to be able to modify the value of a fact once it has been set. For example
>>>
>>> Facter.add("server_type") do
>>>   setcode do
>>>  "apache_web_server"
>>>   end
>>> end
>>>
>>> # Later I may want to change the value.
>>>
>>> if Facter.value("http_server") = "false"
>>># Change value of "server_type" here. I have tried many different
>>> approaches but none work.
>>> end
>>>
>>> Any advice would be greatly appreciated.
>>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/1YHE2l76EAgJ.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>



-- 
Adrien Thebo | Puppet Labs Operations

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Get extra error output when debugging custom types?

2012-07-31 Thread Stefan Schulte

On Tue, Jul 31, 2012 at 03:24:15PM -0700, ZJE wrote:
> Is it possible to get extra output when running custom types? Right now, 
> I'm getting an error message and I'm not sure where in the code it's being 
> thrown from.
> For example, I can see that I'm trying to iterate over a null object, but 
> I'm not sure where in the code this happening when the message is this:
> ---
> Error: /Stage[main]//Node[testnode0101]/TestType[testname]: Could not 
> evaluate: undefined method `each' for nil:NilClass
> ---
> 

Try to run puppet with the --trace option which will hopefully show a
stacktrace when the error is happening. Otherwise you can place a few
method call like

debug "inside validation block"

etc and run puppet with -d/--debug

-Stefan

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined

Here is the deal, we are trying to launch the puppet agent --test from the 
preseed file using this line:
d-i preseed/late_command string in-target puppet agent --test --waitforcert 
0 || true; 

I tried using 'puppet agent --config=/etc/puppet/puppet.conf --test 
--waitforcert 0' given your suggestion but I don't think that it is a valid 
flag for the puppet agent (--config).

During the late_command run it gets a cert from the master just fine but 
then dies:

Jul 31 23:13:08 puppet-agent[5244]: Caching certificate for 
controller-1.example.com
Jul 31 23:13:08 in-target: ^[[0;32minfo: Caching certificate for 
controller-1.example.com^[[0m
Jul 31 23:13:09 puppet-agent[5244]: Caching certificate_revocation_list for 
ca
Jul 31 23:13:09 in-target: ^[[0;32minfo: Caching 
certificate_revocation_list for ca^[[0m
Jul 31 23:13:11 puppet-agent[5244]: Could not retrieve catalog from remote 
server: Error 400 on
SERVER: $concat_basedir not defined. Try running again with pluginsync 
enabled at /usr/share/pup
pet/modules/concat/manifests/setup.pp:25 on node controller
Jul 31 23:13:11 in-target: ^[[1;35merr: Could not retrieve catalog from 
remote server: Error 400
 on SERVER: $concat_basedir not defined. Try running again with pluginsync 
enabled at /usr/share
/puppet/modules/concat/manifests/setup.pp:25 on node control
Jul 31 23:13:11 puppet-agent[5244]: Not using cache on failed catalog
Jul 31 23:13:11 in-target: ^[[0;33mwarning: Not using cache on failed 
catalog^[[0m
Jul 31 23:13:11 puppet-agent[5244]: Could not retrieve catalog; skipping run
Jul 31 23:13:11 in-target: ^[[1;35merr: Could not retrieve catalog; 
skipping run^[[0m

Does the 'puppet agent' command support a path to the correct puppet.conf?  

Shannon

On Tuesday, July 31, 2012 1:52:59 PM UTC-6, R.I. Pienaar wrote:
>
>
>
> - Original Message - 
> > From: "Shannon McFarland"  
> > To: puppet-users@googlegroups.com 
> > Sent: Tuesday, July 31, 2012 10:46:37 AM 
> > Subject: Re: [Puppet Users] $concat_basedir not defined 
> > 
> > Yeah, I ran it with 'sudo' and it pulled the plugin and kicked off. 
> > So, how can I point to the correct configuration without running as 
> > root or sudo in my preseed? 
>
> then you should edit whatever "puppet agent --configprint config" 
> reports as the right config file for the user else run puppet with 
> a specific --config=/etc/puppet/puppet.conf or similar 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/gJtyRr22APcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Access @resouce in custom type

2012-07-31 Thread Nick Lewis

On Tuesday, July 31, 2012 2:05:28 PM UTC-7, ZJE wrote:
>
> Is it possible to access @resource variables inside a type?
>
> I would like to make some decisions on parameters based on other 
> parameters that may have already been set.
>
> For example,
> ---
>   newparam(:param1) do
> Puppet.debug "Found drivesperarray parameter"
> desc "parameter 1"
> validate do |value|
>   if resource[:otherparam] then
> #dosomething
>   else
> resource[:param1] = 0
>   end
> end
> Puppet.debug "Parameter 1 is: #{@resource[:param1]}"
>   end
> ---
>
> But I keep getting messages like "undefined method `[]' for nil:NilClass" 
>
> Anyone have experience with this? I've tried searching around for example 
> without much luck...
>
>
It sounds like what you actually want is a munge block, which is used to 
change the value of the parameter.

munge do |value|
  if resource[:otherparam] then
#dosomething
  else
0
  end
end

validate should be used only to raise an exception if the value is invalid. 
Puppet will call validate and then munge. Also, parameters are set in the 
order they're defined in the type/.rb file, and validated/munged 
before moving on to the next parameter. So a parameter can only depend on 
the values of parameters that come *before* it.
 

> Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/vNg7G08OxowJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] $concat_basedir not defined



- Original Message -
> From: "Shannon McFarland" 
> To: puppet-users@googlegroups.com
> Sent: Tuesday, July 31, 2012 4:22:31 PM
> Subject: Re: [Puppet Users] $concat_basedir not defined
> 
> Here is the deal, we are trying to launch the puppet agent --test
> from the preseed file using this line:
> d-i preseed/late_command string in-target puppet agent --test
> --waitforcert 0 || true;
> 
> 
> I tried using 'puppet agent --config=/etc/puppet/puppet.conf --test
> --waitforcert 0' given your suggestion but I don't think that it is
> a valid flag for the puppet agent (--config).
> 
> 
> During the late_command run it gets a cert from the master just fine
> but then dies:
> 
> 
> 
> Jul 31 23:13:08 puppet-agent[5244]: Caching certificate for
> controller-1.example.com
> Jul 31 23:13:08 in-target: ^[[0;32minfo: Caching certificate for
> controller-1.example.com^[[0m
> Jul 31 23:13:09 puppet-agent[5244]: Caching
> certificate_revocation_list for ca
> Jul 31 23:13:09 in-target: ^[[0;32minfo: Caching
> certificate_revocation_list for ca^[[0m
> Jul 31 23:13:11 puppet-agent[5244]: Could not retrieve catalog from
> remote server: Error 400 on
> SERVER: $concat_basedir not defined. Try running again with
> pluginsync enabled at /usr/share/pup
> pet/modules/concat/manifests/setup.pp:25 on node controller
> Jul 31 23:13:11 in-target: ^[[1;35merr: Could not retrieve catalog
> from remote server: Error 400
> on SERVER: $concat_basedir not defined. Try running again with
> pluginsync enabled at /usr/share
> /puppet/modules/concat/manifests/setup.pp:25 on node control
> Jul 31 23:13:11 puppet-agent[5244]: Not using cache on failed catalog
> Jul 31 23:13:11 in-target: ^[[0;33mwarning: Not using cache on failed
> catalog^[[0m
> Jul 31 23:13:11 puppet-agent[5244]: Could not retrieve catalog;
> skipping run
> Jul 31 23:13:11 in-target: ^[[1;35merr: Could not retrieve catalog;
> skipping run^[[0m
> 
> 
> Does the 'puppet agent' command support a path to the correct
> puppet.conf?

it does, are you certain it has pluginsync=true in the config 
file at that time? 

you can also just do --pluginsync on the command line

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: High CPU load / queued passenger requests

2012-07-31 Thread Ramin K

On 7/31/2012 2:17 PM, Luke Baker wrote:

I ended up restart the mysql database on the storeconfigs server which
helped this problem dramatically. But, I'm still open for more tuning
options if they're out there : )

Some info:
Puppetmaster is RHEL6 x86_64 (VM)
4 vCPU 8GB memory
Apache 2.2
Passenger 3.0.7

PassengerHighPerformance on
PassengerMaxPoolSize 8
PassengerMinInstances 1
PassengerMaxRequests 1
PassengerStatThrottleRate 120
PassengerPreStart https://puppet.mydomain.com:8140/

In Passenger 3.0.x GlobalQueue is on by default so you can drop that.

MinInstances is new in 3.0.x. Using it obviates the need for timeout
settings. Setting MinInstances beyond 1 unless done at the vhost level
for specific reasons is a bad idea because Passenger can balance
application instances better than you. Keep in mind that MinInstances
does not start applications when your http daemon starts for the first
time.

PassengerPreStart does start applications when the server restarts and
takes a URL as an argument which it uses in the host headers when it
connects to localhost. This should also be applied at the vhost level.

MaxRequests can be reasonably high with a mature app like Puppet.

MaxPoolSize is a little harder to size. A Puppet master is usually CPU
bound and I default to (cores * 2), but it depends on your apps. I'd aim
for 80% of CPU with all Rack processes in use and add or drop from the
poolsize to achieve it. Keep in mind that a Puppet Rack process will
weigh in around 150-200MB and you should have enough RAM to support the
max pool size.

Rails/Rack autodetect shouldn't be needed with a normal vhost for Puppet.

I would not touch the Passenger spawn method at all unless there is a
specific reason to modify it. There is not a reason to modify it with
Puppet in my opinion.

http://www.modrails.com/documentation/Users%20guide%20Apache.html#spawning_methods_explained

Ramin

--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] duplicate resources across defined types

2012-07-31 Thread Joe Topjian

Hello,

I am hoping that someone might be able to shed some light on the best way
to solve an issue.

https://github.com/puppetlabs/puppetlabs-apache/commit/c2c75a62b7dafced8a6120a14bacfc8be7539282

This commit introduced functionality into the vhost type to ensure that the
$docroot and $logroot exist. This is smart as Apache will throw a warning
if $docroot does not exist and error out if $logroot does not exist.

I believe the original intention of the author was to make the names of
these resources unique so that multiple vhosts can share the same docroot
and logroot (line 71-80). However, the path of the resources is not unique
across vhosts that use the same $docroot and $logroot and therefore puppet
will error out.

The first thing that came to my mind was to make the resources virtual and
then just realize a single directory. Unless something special needs done,
marking the two file resources as virtual (@file) still does not work.

The other option that has been discussed is to use a conditional if block:

https://github.com/puppetlabs/puppetlabs-apache/pull/37/files

Here, on all but one of the vhost entries, you mark ensure_dirs as false
and Puppet will not enforce the existence of the two directories. This
works, but it comes off as a workaround more than a proper solution.

Any ideas?

Thanks,
Joe

--
Joe Topjian
Systems Administrator
Cybera Inc.

www.cybera.ca

Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
of cyberinfrastructure.

--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Using file{} with array parameter fails

thanks for the reply, I actually made an error in my declaration. I used 
two variables which I had just moved out of scope, and so I declared two 
empty File[] objects - and puppet complained. 

When your solution didn't work either it hit me :) . 

thanks & greetings!
Axel.



Am Dienstag, 31. Juli 2012 16:10:23 UTC+2 schrieb David Schmitt:
>
> Hi Axel, 
>
>
>$filesA = ["/tmp/A1", "/tmp/A2", "/tmp/A3" ] 
>$filesB = ["/tmp/B1", "/tmp/B2", "/tmp/B3" ] 
>
>file { 
>  $filesA: 
>ensure => present, 
>mode => 0644, owner => root; 
>  $filesB: 
>ensure => present, 
>mode => 0755, owner => "www-data"; 
>} 
>
> If you're looking for something different you might want to look into 
> setting recurse=>true. Read the Type Reference for more info. 
>
> Best Regards, David 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/hgdnKnvvHGcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] NFS mounts with puppet creates error