[Puppet Users] Re: Dashboard rhel5 problems

[Stefan Heijmans]

Which version of dashboard are you running, 1.2x?
I'm running puppet 2.6.6 (from EPEL5) and dashboard 1.1.1 with
passenger 3.0.8 on RHEL 5.6 with ruby 1.8.5.

You could try this ruby 1.8.7 package from 
http://rpm.aegisco.com/aegisco/rhel/5Server/x86_64/
They are Allowed Contributors to Chef


On Aug 15, 6:05 pm, Marek Dohojda  wrote:
> So I moved further.  The issue is ruby version.  Dashboard passenger ruby
> apparently wants to be above version 1.8.5, which is the default version for
> RHEL5.  This likely would not have been an issue if I haven't already
> upgrade puppet to 2.6.6 and thereby loaded new passenger.
> I will see if there is anything I can do without upgrading Ruby, since I
> prefer to stay consistent with the versions present due to further patching
> considerations.
>
>
>
>
>
>
>
> On Fri, Aug 12, 2011 at 3:07 PM, Craig White  wrote:
>
> > On Aug 12, 2011, at 1:13 PM, Marek Dohojda wrote:
>
> > > Hello
>
> > > I have a running puppet and passenger (2.6.8) running on RHEL5.  I
> > installed dashboard and configured it, and all that is working as well.
> >  However I don't want to run webrick I want to put dashboard under passenger
> > with apache.
>
> > > I have done the conf change to add virtual host, and changed it to run
> > under port 3000 (as default).
>
> > > Everything start correctly, but that's as far as I can get.  When I go to
> > the server port 3000 I get default apache web page (due to there not being
> > index.html nor any app running).  I followed another instructions which said
> > to add this for RHEL:
>
> > >     SetEnv RAILS_ENV production
> > >        RackBaseURI /
>
> > > This allowed me to get ruby error screen instead of default apache test
> > page.  However I go an error "file not found" config.ru.  I copied
> > config.ru to /usr/share/puppet-dashboard/ from (
> > > /usr/share/puppet-dashboard/vendor/rails/railties/dispatches/config.ru)
> > which was only place I found config.ru within dashboard.
> > > Now I am getting following:
> > >  Exception NoMethodError in PhusionPassenger::Rack::ApplicationSpawner
> > (undefined method `requirement' for #)
> > (process 24074):
>
> > > And at this point I am stuck.  I bet I am missing something probably
> > simple but I can't figure out what.
>
> > > I am including my conf for passanger below:
> > > PassengerHighPerformance on
> > > PassengerMaxPoolSize 12
> > > PassengerPoolIdleTime 1500
> > > # PassengerMaxRequests 1000
> > > PassengerStatThrottleRate 120
> > > RailsAutoDetect On
> > 
> > I've got the above lines inside my  declaration
>
> > I also have
> > PassengerUseGlobalQueue on
> > 
> > > Listen 3000
> > > 
> > >         ServerName 
> > >         DocumentRoot /usr/share/puppet-dashboard/public/
> > >         SetEnv RAILS_ENV production
> > >         RackBaseURI /
> > >         
> > >                 Options None
> > >                 AllowOverride AuthConfig
> > >                 Order allow,deny
> > >                 allow from all
> > 
> > I have
> > Options -Multiviews
> > here inside the  declaration
> > 
> > >         
> > >   ErrorLog /var/log/httpd/dashboard_error.log
> > >   LogLevel warn
> > >   CustomLog /var/log/httpd/dashboard_access.log combined
> > >   ServerSignature On
> > > 
>
> > > I hope someone can point me in the right direction.
> > > Thank you!
> > 
> > not sure but this may help
>
> > Craig
>
> > --
> > 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] dashboard 1.1.1 with filebucket doesn't show contents of the new file

[Stefan Heijmans]

Am using dashboard 1.1.1 with the use_file_bucket_diffs option.

When clicking on the links within a report it will show the old md5
file (on the left) but not the new md5 file (on the right)
like;
content content changed '{md5}26a3112822d01f2ce6b3f052bf2809de' to
'{md5}dd97364ab0559344d73231f517951595'

26a3112822d01f2ce6b3f052bf2809de ==> is displayed normally
dd97364ab0559344d73231f517951595 ==> We're sorry, but something went
wrong.

puppet-dashboard log shows;
Processing FilesController#show (for 192.168.20.20 at 2011-08-21
17:37:49) [GET]
  Parameters: {"action"=>"show", "controller"=>"files",
"file"=>"26a3112822d01f2ce6b3f052bf2809de"}
Completed in 22ms (View: 0, DB: 0) | 200 OK [http://192.168.20.100/
files/show?file=26a3112822d01f2ce6b3f052bf2809de]


Processing FilesController#show (for 192.168.20.20 at 2011-08-21
17:37:52) [GET]
  Parameters: {"action"=>"show", "controller"=>"files",
"file"=>"dd97364ab0559344d73231f517951595"}

Net::HTTPServerException (404 "Not Found"):
  /usr/lib/ruby/1.8/net/http.rb:2097:in `error!'
  lib/puppet_https.rb:34:in `get'
  app/controllers/files_controller.rb:23:in `show'
  haml (3.0.13) [v] rails/./lib/sass/plugin/rack.rb:41:in `call'
  passenger (3.0.8) lib/phusion_passenger/rack/request_handler.rb:
96:in `process_request'
  passenger (3.0.8) lib/phusion_passenger/abstract_request_handler.rb:
513:in `accept_and_process_next_request'
  passenger (3.0.8) lib/phusion_passenger/abstract_request_handler.rb:
274:in `main_loop'
  passenger (3.0.8) lib/phusion_passenger/classic_rails/
application_spawner.rb:321:in `start_request_handler'
  passenger (3.0.8) lib/phusion_passenger/classic_rails/
application_spawner.rb:275:in `send'
  passenger (3.0.8) lib/phusion_passenger/classic_rails/
application_spawner.rb:275:in `handle_spawn_application'
  passenger (3.0.8) lib/phusion_passenger/utils.rb:479:in `safe_fork'
  passenger (3.0.8) lib/phusion_passenger/classic_rails/
application_spawner.rb:270:in `handle_spawn_application'
  passenger (3.0.8) lib/phusion_passenger/abstract_server.rb:357:in
`__send__'
  passenger (3.0.8) lib/phusion_passenger/abstract_server.rb:357:in
`server_main_loop'
  passenger (3.0.8) lib/phusion_passenger/abstract_server.rb:206:in
`start_synchronously'
  passenger (3.0.8) lib/phusion_passenger/abstract_server.rb:180:in
`start'
  passenger (3.0.8) lib/phusion_passenger/classic_rails/
application_spawner.rb:149:in `start'
  passenger (3.0.8) lib/phusion_passenger/spawn_manager.rb:219:in
`spawn_rails_application'
  passenger (3.0.8) lib/phusion_passenger/
abstract_server_collection.rb:132:in `lookup_or_add'
  passenger (3.0.8) lib/phusion_passenger/spawn_manager.rb:214:in
`spawn_rails_application'
  passenger (3.0.8) lib/phusion_passenger/
abstract_server_collection.rb:82:in `synchronize'
  passenger (3.0.8) lib/phusion_passenger/
abstract_server_collection.rb:79:in `synchronize'
  passenger (3.0.8) lib/phusion_passenger/spawn_manager.rb:213:in
`spawn_rails_application'
  passenger (3.0.8) lib/phusion_passenger/spawn_manager.rb:132:in
`spawn_application'
  passenger (3.0.8) lib/phusion_passenger/spawn_manager.rb:275:in
`handle_spawn_application'
  passenger (3.0.8) lib/phusion_passenger/abstract_server.rb:357:in
`__send__'
  passenger (3.0.8) lib/phusion_passenger/abstract_server.rb:357:in
`server_main_loop'
  passenger (3.0.8) lib/phusion_passenger/abstract_server.rb:206:in
`start_synchronously'
  passenger (3.0.8) helper-scripts/passenger-spawn-server:99


Rendering /usr/share/puppet-dashboard/public/500.html (500 Internal
Server Error)


Is this because the new file is not in the filebucket yet?
any ideas anyone?

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.

[Puppet Users] Custom fact not set with mc-puppetd

[Stefan Heijmans]

Hello,

I've mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2
setup from 
http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML.

Now I've create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/
customer_status.rb.
On the client;
Running facter customer_status works.
Running 'puppet agent --test' works, customer_status is set in /etc/
mcollective/facts.yaml

On the server;
But running 'mc-puppetd --wi  runonce' doesn't set the
customer_status in /etc/mcollective/facts.yaml.

Anyone an idea why?

Thanks,
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.

[Puppet Users] Re: Custom fact not set with mc-puppetd

[Stefan Heijmans]

On Nov 1, 10:00 pm, "R.I.Pienaar"  wrote:
> - Original Message -
>
> you should be using pluginsync to copy out custom facts:
>
> http://docs.puppetlabs.com/guides/plugins_in_modules.html
>
Ok, enabled pluginsync, customer_status.rb is now copied to the client
in /var/lib/puppet/lib/facts.

> this could only really be down to some environment change, maybe its
> not picking up those fact or your custom fact only works based on
> some set of stuff in the environment etc?
>
Correct, customer_status.rb was picking up an environment variable set
from a file in /etc/profile.d/
I've changed customer_status.rb to get the value directly from this
file.

 'mc-puppetd --wi  runonce'  doens't work with
customer_status.rb in /var/lib/puppet/lib/facts
but it does work with customer_status.rb in /usr/lib/ruby/site_ruby/
1.8/facter.

-- 
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: ANNOUNCE: Puppet-Dashboard 1.2.3rc1 available

[Stefan Heijmans]

On 4 nov, 23:06, Matthaus Litteken  wrote:
> -- Fix #10270 dashboard-workers init script should check the right pid files

puppet-dashboard/ext/packaging/redhat/puppet-dashboard-workers.init
uses DASHBOARD_ROOT
this is not set in puppet-dashboard/ext/packaging/redhat/puppet-
dashboard.sysconfig, this uses DASHBOARD_HOME
so always defaulted at /usr/share/puppet-dashboard

puppet-dashboard/ext/packaging/redhat/puppet-dashboard.init does
DASHBOARD_HOME

fix;
1. add DASHBOARD_ROOT to puppet-dashboard/ext/packaging/redhat/puppet-
dashboard.sysconfig
2. preferred: replace DASHBOARD_ROOT with DASHBOARD_HOME in puppet-
dashboard/ext/packaging/redhat/puppet-dashboard-workers.ini

-- 
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] Puppet Dashboard 1.2.2; node report; change sort in log tab

[Stefan Heijmans]

The sorting in the log tab on a node report seems to be on the level
column, which is hard to read when multiple changes take place, as
notice and info of the actions are on the top and bottom of the log.
Can this be adjusted so its displayed as 'puppet agent --test' does
(sort on time and line column).

-- 
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 Dashboard 1.2.2; node report; change sort in log tab

[Stefan Heijmans]

Ok, will create a feature request for this.

On 11 nov, 18:58, Peter Meier  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/07/2011 08:55 PM, Stefan Heijmans wrote:
>
> > The sorting in the log tab on a node report seems to be on the
> > level column, which is hard to read when multiple changes take
> > place, as notice and info of the actions are on the top and bottom
> > of the log. Can this be adjusted so its displayed as 'puppet agent
> > --test' does (sort on time and line column).
>
> Sounds like a reasonable bug report/feature 
> request:http://projects.puppetlabs.com/projects/dashboard
>
> ~pete
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk69YkIACgkQbwltcAfKi3/RXgCfcIXrDJp32VnXVxK1UM7RYylV
> uesAoItxpdNGLAiqxq5RWSo04wLYvZ/s
> =Apya
> -END PGP SIGNATURE-

-- 
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] Puppet Dashboard; node.rake

[Stefan Heijmans]

Hello,
 
I've added an extra rake task (node:listfull) to node.rake which displays 
the nodes (all or by match) with defined groups & classes on it, like;
Nodename = 
Groups  = ,,
Classes = ,,
 
For groups I use;
NodeGroup.find(node.node_groups).each do |nodegroup|
and classes;
 
NodeClass.find(node.node_classes).each do |nodeclass|
But now I also want to display the parameters defined on a node, how would 
I do that, could not find it (yet) in any other rake task.
 
Stefan

-- 
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/-/Z6vcopoPWBwJ.
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 agent daemon does not load custom facts

[Stefan Heijmans]

Is the custom fact perhaps based on a environment variable?
 
I had something similar a while ago, check this post;
https://groups.google.com/d/msg/puppet-users/2gjjaWFJm4Q/uANKwM-xWQ4J
 
Stefan

-- 
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/-/9UXBvl1Xy7YJ.
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 Dashboard; node.rake

[Stefan Heijmans]

Finally found out how it worked, I've create a 2 new rake tasks (all or by 
match) to display a
fulllist of nodes with
Nodename : 
Params   : =,=
Groups   : ,,
Classes  : ,,

fulllist of groups with
Group   : 
Params  : =,=
Classes : ,,
Nodes   : ,,

Now I can easily search where what is used.
I've attached the rake file if people want to use it.

Stefan

-- 
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/-/0bl7zHa0ukgJ.
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.



fulllist.rake
Description: Binary data

[Puppet Users] Re: new user: need Conditional statement example within a file resource type

[Stefan Heijmans]

How about something like;


$hasfile = true
if $::hasfile {
   $fileensure = 'present'
}
else {
   $fileensure = 'absent'
}

file { "somefile" :

ensure => $::fileensure,
source => "puppet:///somefile",
owner => "root",
.
.
.
}

-- 
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/-/CWF3DekKQwAJ.
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: Puppet Dashboard; node.rake

[Stefan Heijmans]

Op zondag 11 december 2011 19:01:14 UTC+1 schreef Nigel Kersten het 
volgende:
>
> I've cc'd Dan and Kelsey, who have both been working on a Dashboard Puppet 
> Face for command-line control. Although the rake tasks are totally useful, 
> we'd like to be able to have all this functionality under a "puppet 
> dashboard ..." set of commands.
> -- 
> Nigel Kersten
> Product Manager, Puppet Labs
>

Hi Nigel,

we use rake at the moment as;
- we still run 2.6.12 in production 
- I don't get the Dashboard Puppet Face working on our test system with 
RHEL5.7 which has ruby 1.8.5
  gem install activerecord results in 
  *** buffer overflow detected ***: /usr/bin/ruby terminated
  /lib64/libc.so.6(__chk_fail+0x2f)[0x326bae807f]
  and activerecord 2.3.14 does install but doesn't seem to work.

Stefan
 

-- 
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/-/_gTltiX8x10J.
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: new user: need Conditional statement example within a file resource type

[Stefan Heijmans]

It's to be future proof, you can read about @
http://docs.puppetlabs.com/guides/scope_and_puppet.html
 
Stefan
 

-- 
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/-/ZZfr1sZfo7cJ.
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] Puppet Dashboard and Ruby 1.8.7 for EL5 systems HOWTO (draft)

[Stefan Heijmans]

Op vrijdag 6 januari 2012 01:53:31 UTC+1 schreef Michael Stanhke het 
volgende:
>
>
> One more thing to keep in mind is that EL5 only has about 2 years of
> life left on it.  It launched in 2007.
>
That's only for RHEL5 production phase 3 (31 March 2014), End of Extended 
Life Cycle is on 31 March 2017.

-- 
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/-/fzMr6PljNOgJ.
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: scaling projections for dashboard database?

[Stefan Heijmans]

Op maandag 9 januari 2012 19:40:00 UTC+1 schreef Jo het volgende:
>
> 2. Are there some database cleanup scripts which I have managed to 
> overlook that need to be run?
>
 
have you tried this?
Cleaning old 
reports http://docs.puppetlabs.com/dashboard/manual/1.2/maintaining.html

perhaps also give the 'optimize the database' as try.

Stefan

-- 
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/-/YVmoUlouvNcJ.
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] difficulty installing dashboard.

[Stefan Heijmans]

Op dinsdag 24 januari 2012 17:42:08 UTC+1 schreef Salty Old Cowdawg het 
volgende: 
>
> so... I gotta get 1.8.7 on the box?   EL6 is not an option at this point 
> as this is not a new box and does more than just puppet...
>
>  
There is a topic about this from Jo Rhett; 
https://groups.google.com/d/msg/puppet-users/CQTHj9nIYCw/b2Cr7-BxAwkJ
Or you can compile Ruby Enterprise Edition 1.8.7 yourself on that host.
 
So there are some options you could go for.
 
Stefan
 
 

-- 
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/-/tlUPyPIldowJ.
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: Upgrade 2.7.9 to 2.7.10; puppet client hangs

[Stefan Heijmans]

Tried the same puppet setup in my homelab, no problems after upgrading.
Looking at the diffs, one of them was a kernel difference;
- test environment RHEL57 2.6.18-274.12.1.el5
- homelabRHEL57 2.6.18-274.17.1.el5

Remembered this bug; http://projects.puppetlabs.com/issues/10418, it 
was updated with positive result on RHEL57 2.6.18-274.17.1.el5 kernel.
So the problem is now fixed with a new kernel in the test environment.

Stefan.

-- 
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/-/JJwRMD6U0nkJ.
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 no longer reading puppet.conf

[Stefan Heijmans]

Check http://projects.puppetlabs.com/issues/7270
puppet.conf doesn't support that face configuration options yet.

I use the command line option;
>>You can override database setting on the command line:
>>--adapter mysql --host 127.0.0.1 --database dashboard --username user 
--password password

>>the import worked last week 
I have no succes with importing yaml files, other functions work fine. Have 
send an email to Kelsey about this.

Stefan.

-- 
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/-/itZtv-JsZ2AJ.
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] Announce: Puppet 2.7.11 Available [security/maintenance update]

[Stefan Heijmans]

same is for RHEL5 (binary rpm), I see that the rpm on yum.puppetlabs.com is 
from 22-Feb-2012 and the http://projects.puppetlabs.com/issues/12572 is 
closed 17hours ago, thats later then the released rpm.
 
# rpm -q puppet puppet-server
puppet-2.7.11-1.el5
puppet-server-2.7.11-1.el5
#
#vim /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb
180   def save_last_run_summary(report)
181 last_run = Puppet.settings.setting(:lastrunfile)
182 last_run.create = true # force file creation
183
184 resource = last_run.to_resource
185 resource[:content] = YAML.dump(report.raw_summary)
186
187 catalog = Puppet::Resource::Catalog.new("last_run_file")
188 catalog.add_resource(resource)
189 ral = catalog.to_ral
190 ral.host_config = false
191 ral.apply
192   rescue => detail
193 puts detail.backtrace if Puppet[:trace]
194 Puppet.err "Could not save last run local report: #{detail}"
195   end

-- 
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/-/nnRYxWqYj24J.
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] Announce: Puppet 2.7.11 Available [security/maintenance update]

[Stefan Heijmans]

Matthaus, thanks for the new rpm's.

Small question; what is the difference between these versions;
.noarch.rpm
.el5.noarch.rpm

As the .noarch.rpm are not updated, they are still on 2.7.11-1.noarch.rpm.

-- 
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/-/S5rViizHBGwJ.
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] How to fully remove a node from Puppet Dashboard (v1.2.4)

[Stefan Heijmans]

Looks likes this bug at
http://projects.puppetlabs.com/issues/11210 

Op zaterdag 10 maart 2012 03:39:31 UTC+1 schreef Romeo Theriault het 
volgende:
>
> On Fri, Mar 9, 2012 at 12:05, Jeff McCune  wrote:
> > On Wed, Mar 7, 2012 at 8:22 PM, Romeo Theriault <
> romeo.theria...@maine.edu>
> > wrote:
> >>
> >> I can delete a node in dashboard fine, but when I do a search with the
> >> Inventory Search the node shows up again and also then shows up under
> >> "Unreported". Any way to get rid of all references to the node?
> >
> >
> > Hi Romeo,
> >
> > I think this is a bug.  Could you file a ticket describing what you'd 
> expect
> > to happen and what's actually happening when you delete a node at:
> >
> > http://projects.puppetlabs.com/projects/dashboard/issues/new
>
> Sure, I'll do this when I get back to work on Sunday. Thanks for the reply.
>
> -- 
> Romeo
>
>

-- 
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/-/fMQuM3IiCQAJ.
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] mcollective/puppetd & RHEL SELinux alert

[Stefan Heijmans]

Hello,
We are running Puppet 2.7.11-2 on RHEL57 x86_64 with MCollective (on client 
and server);
On the client;
# rpm -qa|grep -e puppet -e mcollective
mcollective-common-1.2.1-1.el5
puppet-2.7.11-2.el5
mcollective-1.2.1-1.el5
#
 
with kernel;
Linux  2.6.18-274.18.1.el5 #1 SMP Fri Jan 20 15:11:18 EST 2012 
x86_64 x86_64 x86_64 GNU/Linux
 
with SELinux enabled.
# facter|grep sel
selinux => true
selinux_config_mode => enforcing
selinux_config_policy => targeted
selinux_current_mode => enforcing
selinux_enforced => true
selinux_mode => targeted
selinux_policyversion => 21
#


In one of our manifest we set the password for some users. 
When we do a puppet-run from the puppetmaster with the mcollective plugin 
puppetd; 'mco puppetd --wi   runonce'
we get the following (reproducible) SELinux Alert.




Summary:

SELinux is preventing the nscd from using potentially mislabeled files
(/tmp/puppet.30676.0).

Detailed Description:

SELinux has denied nscd access to potentially mislabeled file(s)
(/tmp/puppet.30676.0). This means that SELinux will not allow nscd to use 
these
files. It is common for users to edit files in their home directory or tmp
directories and then move (mv) them to system directories. The problem is 
that
the files end up with the wrong file context which confined applications 
are not
allowed to access.

Allowing Access:

If you want nscd to access this files, you need to relabel them using 
restorecon
-v '/tmp/puppet.30676.0'. You might want to relabel the entire directory 
using
restorecon -R -v '/tmp'.

Additional Information:

Source Contextsystem_u:system_r:nscd_t
Target Contextsystem_u:object_r:initrc_tmp_t
Target Objects/tmp/puppet.30676.0 [ file ]
Sourcenscd
Source Path   /usr/sbin/nscd
Port  
Host  
Source RPM Packages   nscd-2.5-65.el5_7.1
Target RPM Packages
Policy RPMselinux-policy-2.4.6-316.el5_7.1
Selinux Enabled   True
Policy Type   targeted
MLS Enabled   True
Enforcing ModeEnforcing
Plugin Name   home_tmp_bad_labels
Host Name 
Platform  Linux 
  2.6.18-274.18.1.el5 #1 SMP Fri Jan 20 
15:11:18 EST
  2012 x86_64 x86_64
Alert Count   4
First SeenTue Mar 20 17:13:25 2012
Last Seen Tue Mar 20 17:13:25 2012
Local ID  fdec3437-c40e-407e-ab3c-f998cf0a49f5
Line Numbers  10078, 10079, 10080, 10082, 10083, 10084, 
10085,
  10086, 10087, 10089, 10090, 10091, 10092, 
10093,
  10094, 10096, 10097, 10098, 10099, 10100, 
10101,
  10103, 10104, 10105

Raw Audit Messages

type=AVC msg=audit(1332260005.415:16748): avc:  denied  { read write } for  
pid=31028 comm="nscd" path="/tmp/puppet.30676.0" dev=dm-3 ino=13 

scontext=system_u:system_r:nscd_t:s0 
tcontext=system_u:object_r:initrc_tmp_t:s0 tclass=file

type=AVC msg=audit(1332260005.415:16748): avc:  denied  { read write } for  
pid=31028 comm="nscd" path="/tmp/puppet.30676.0" dev=dm-3 ino=13 

scontext=system_u:system_r:nscd_t:s0 
tcontext=system_u:object_r:initrc_tmp_t:s0 tclass=file

type=SYSCALL msg=audit(1332260005.415:16748): arch=c03e syscall=59 
success=yes exit=0 a0=40e9de a1=7fff4f96d120 a2=7fff4f96d150 a3=0 items=2 

ppid=31024 pid=31028 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 
egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="nscd" 

exe="/usr/sbin/nscd" subj=system_u:system_r:nscd_t:s0 key="nscd_called-up"

type=CWD msg=audit(1332260005.415:16748): cwd="/"

type=PATH msg=audit(1332260005.415:16748): item=0 name="/usr/sbin/nscd" 
inode=721057 dev=fd:07 mode=0100755 ouid=0 ogid=0 rdev=00:00 

obj=system_u:object_r:nscd_exec_t:s0

type=PATH msg=audit(1332260005.415:16748): item=1 name=(null) inode=196612 
dev=fd:00 mode=0100755 ouid=0 ogid=0 rdev=00:00 

obj=system_u:object_r:ld_so_t:s0


The problem is that the temporary puppet file (/tmp/puppet.30676.0) gets a 
SELinux label initrc_tmp_t
which the nscd daemon is not allowed to access.
ncsd is default off;
# chkconfig --list nscd
nscd0:off   1:off   2:off   3:off   4:off   5:off   6:off
# service nscd status
nscd is stopped
#


When we run puppet locally with 'puppet agent -t' we don't get the SELinux 
alert, as the temporary puppet file is now written with the tmp_t 

SELinux label.

I've talked with Red Hat support about and they say in-the-end, the 
following about it;
>>As I had stated before, the 'puppet' software is not provided by Red Hat, 
and the SELinux rules required
>>for the curr

Re: [Puppet-dev] Re: [Puppet Users] Telly: Nagios types moving into Module

[Stefan Heijmans]

Hi,
>
> What will be the option(s) for Puppet users with no internet connection 
(not allowed), if things start to depend more on PMT and Puppet Forge?
Will we be able to make a local repo and do something like a 'puppet module 
localinstall' ?



-- 
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/-/mt4aK9XjSnYJ.
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] inventory service in Puppet-dashboard

[Stefan Heijmans]

Op vrijdag 15 juni 2012 14:30:03 UTC+2 schreef Sans het volgende: 
>
> Hi guys, 
>
> Just wondering, if any one can tell me it it's a "certificate" related 
> issue. Still can't find any thing obvious. Cheers!

 
did you check/follow this page?
http://docs.puppetlabs.com/dashboard/inventory_support.html
 
 

-- 
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/-/-edERuY9jaYJ.
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 dashboard not enabling inventory

[Stefan Heijmans]

>>I mean regardless of what settings are set shouldn't I at least be able 
to see the inventory tab if enable_inventory_service is set to true?
Yes if you mean the one on top of the screen
If you click on a node when it's not configured correctly it shows;
Inventory
Could not retrieve facts from inventory service: getaddrinfo: Name or 
service not known

>>Pointing to correct port for puppetdb and server in settings.yml
my inventory_server & inventory_port parameters points to  

>>Has anyone else successfully got the puppet dashboard working with 
dashboard version 1.2.17 with puppet 3?
Yes on rhel63 with
puppet 3.0.2
puppet dashboard 1.2.18
puppetdb 1.0.5

-- 
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/-/QPUP0oc6Gy0J.
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: Puppet dashboard not enabling inventory

[Stefan Heijmans]

on what OS are you, read that for instance debian uses a different location 
for config files

-- 
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/-/RRZ1lRxtVuIJ.
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: Puppet dashboard not enabling inventory

[Stefan Heijmans]

And if you create new settings.yml from settings.yml.example. Seems like like 
settings_reader.rb falls back to setings.yml.example if parameters are not 
correct in settings.yml. http://projects.puppetlabs.com/issues/14371
Or enable inventory in settings.yml.example?

-- 
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/-/Au384vAphAwJ.
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: Plan the manifests structure

[Stefan Heijmans]

This might help, watch/read this from Ken Barber; Modern Module Development
http://youtu.be/zNXSKv6987g
http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-cam

-- 
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/-/OeR5THb3zp0J.
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: Cobbler update

[Stefan Heijmans]

Hi, better try the Cobbler email list @ 
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Op donderdag 7 februari 2013 09:27:05 UTC+1 schreef kavitha...@gmail.com 
het volgende:

> Hello, 
>
>
> I have "cobbler 2.0.X" installed in my system. I want t update it to 
> "2.2.3" . 
> And I don't want to loose any of the profiles, repos present in my current 
> cobbler.
> I tried backing up the cobbler, don't know exactly that this will help
> Any idea on this?
>
> Thanks 
> Kavitha
>
>
>
>
>
>
>

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

[Puppet Users] Puppet Dashboard 1.2.23 issue deleting node

[Stefan Heijmans]

Hello,

we run Puppet Dashboard 1.2.23 in our sandbox and get an error deleting a 
node.
- first time we press the delete button nothing happens 
- second time we press the delete button we get the following error;

ActiveRecord::StatementInvalid in NodesController#destroy

Mysql::Error: Lock wait timeout exceeded; try restarting transaction: 
DELETE FROM `node_group_memberships` WHERE `id` = 53

RAILS_ROOT: /usr/share/puppet-dashboard
Application Trace | Framework Trace | Full Trace

Request

Parameters:

{"authenticity_token"=>"2LTYvT15OF9RXNjMXiDdVEGiXyCebbL3DNFgaamHMdk=",
 "id"=>"32",
 "_method"=>"delete"}

Show session dump
Response

Headers:

{"Cache-Control"=>"no-cache",
 "Content-Type"=>""}
After downgrading to 1.2.22, we can delete the node again.
Anyone else experience this?
 

Stefan

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

[Puppet Users] Re: How to optimize puppet class/module code ?

[Stefan Heijmans]

Or checkout this one from Ken Barber; modern module development 
http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-camp
http://www.youtube.com/watch?v=zNXSKv6987g
 

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

[Puppet Users] hiera & hiera-gpg

[Stefan Heijmans]

Hello,

We are looking into using hiera with hiera-gpg, installed puppet 3.1.1 & 
hiera 1.2.0 with rpm's.
Installing the hiera-gpg gem, it also depends on the hiera gem (used 
version 1.2.0).

The hiera rpm installs under /usr/lib/ruby/site_ruby/1.8/
The hiera gem installs under /usr/lib/ruby/gems/1.8/gems/

So what kind of trouble can be excepted using to version of hiera (rpm&gem)?
Other then updating both with future hiera updates.

Stefan

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

[Puppet Users] Re: How to optimize puppet class/module code ?

[Stefan Heijmans]

You could use sourceselect in source;
http://docs.puppetlabs.com/references/stable/type.html#file
 
or use parameter in the source statement;
source => "puppet:///modules/syslog/syslog.conf_${::$lsbmajdistrelease}", 
and create 2 syslog.conf files in the files directory;
syslog.conf_5
 syslog.conf_6
 

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

[Puppet Users] Re: How to optimize puppet class/module code ?

[Stefan Heijmans]

bad cp;
 
source => "puppet:///modules/syslog/syslog.conf_${::lsbmajdistrelease}", 

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

Re: [Puppet Users] Announce: Puppet Dashboard 1.2.10 Available

[Stefan Heijmans]

Op vrijdag 13 juli 2012 02:05:29 UTC+2 schreef Jo het volgende: 
>
>  Where is the documentation for this feature?  How do I invoke it?
>
> The maintaining page still just says to create a cron job.
>
 
the maintaining page also mentions;
 
If you run ‘rake reports:prune’ without any arguments, it will display 
further usage instructions.

Just installed in in our sandbox and it shows;

rake reports:prune
EXAMPLE:
  # Prune records upto 1 month old:
  rake reports:prune upto=1 unit=mon

UNITS:
  Valid units of time are: mon,yr,day,min,wk,hr

-- 
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/-/-2VsNh8ZsS0J.
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] Announce: Puppet Dashboard 1.2.10 Available

[Stefan Heijmans]

Op vrijdag 13 juli 2012 08:50:07 UTC+2 schreef Stefan Heijmans het 
volgende: 
>
>
> the maintaining page also mentions;
>  
> If you run ‘rake reports:prune’ without any arguments, it will display 
> further usage instructions.
>
my bad, that's not the one.
 
# rake cron:cleanup
ln -sf 
/usr/share/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron 
/etc/cron.monthly/puppet-dashboard.cleanup_reports.cron
It creates a link from the source to the /etc/cron.monthly.
One issue, if you have puppet-dashboard installed in a different location 
the source is not there.
# more /etc/cron.monthly/puppet-dashboard.cleanup_reports.cron
/etc/cron.monthly/puppet-dashboard.cleanup_reports.cron: No such file or 
directory
# ll 
/usr/share/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron
ls: 
/usr/share/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron: 
No such file or directory
# ll /opt/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron
-rwxr-xr-x 1 puppet-dashboard puppet-dashboard 597 Jul 12 20:50 
/opt/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron
#

-- 
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/-/NfidyMAbUNsJ.
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] Announce: Puppet Dashboard 1.2.10 Available

[Stefan Heijmans]

Op vrijdag 13 juli 2012 18:36:41 UTC+2 schreef Jo het volgende:
>
>
> Hm, yes. What does that have to do with my question about the new rake job 
> to install a cron script?
>
> absolutely nothing, as stated in my 2nd post about it :)
 

-- 
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/-/kotzCbdij7YJ.
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: How to automatically implement default configuration changes made by a package upgrade

[Stefan Heijmans]

Hi Matthew,

We are on Red Hat and do the following with config files which will be 
updated after yum update.

- our own customized config files of the rpm are in Puppet with an addon 
for rpm name&version (for instance; files/lvm.conf_lvm2-2.02.88-7.el5)
- we have a custom facter which determines this version (for instance; 
facter lvm2version)
- when we do an update in our sandbox environment the new rpm will create 
rpmnew (for instance; /etc/lvm/lvm.conf.rpmnew)
- after update we check on all created rpmnew/rpmsave files
- do a puppet run with noop, it will stop as there is no new version of the 
config file in Puppet available
- we merge the current and rmpnew into a new config file in Puppet 
(files/lvm.conf_lvm2-3.02.88-7.el5)
- do a puppet run and should be fine, new config file with Red Hat changes 
and our own changes.

Stefan


 

-- 
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/-/tAnhkbEAVd4J.
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] RHEL 5: Stuck on Puppet 2.7

[Stefan Heijmans]

How about switching to the gem version of passenger;
gem install passenger

-- 
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/-/A8FERt3aTbIJ.
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 3 docs are live

[Stefan Heijmans]

http://docs.puppetlabs.com/puppet/3/reference/release_notes.html#puppet-master-web-server-changes
>>This needs to be changed to Puppet::Util::CommandLine
but also the require seems to have changed 
from require 'puppet/application/master'
to   require 'puppet/util/command_line'
 
Op donderdag 4 oktober 2012 03:14:12 UTC+2 schreef Nick Fagerlund het 
volgende:

> Puppet 3 docs are now posted at 
> http://docs.puppetlabs.com/puppet/3/reference/ . We apologize for the 
> delay! This update adds release notes and a Puppet 3 language reference 
> with all of the relevant updated. Next on deck is improved Hiera 
> documentation. 
>

-- 
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/-/cfJfM1EnZC0J.
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: Announce: Puppet Dashboard 1.2.13 Available

[Stefan Heijmans]

Hi,

Just updated from 1.2.11 to 1.2.13 with the tarball (
http://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13.tar.gz)

Starting puppet-dashboard-workers it gives the following message;

# service puppet-dashboard-workers start
Starting puppet-dashboard-workers: 
/opt/puppet-dashboard/vendor/plugins/delayed_job/lib/delayed/command.rb:65:in 
`mkdir': No such file or directory - /opt/puppet-dashboard/tmp/pids 
(Errno::ENOENT)
from 
/opt/puppet-dashboard/vendor/plugins/delayed_job/lib/delayed/command.rb:65:in 
`daemonize'
from /opt/puppet-dashboard/script/delayed_job:5
   [FAILED]
#

# ll -d /opt/puppet-dashboard/tmp
ls: /opt/puppet-dashboard/tmp: No such file or directory
#

Creating this directory fixes it.


Checking the tarball shows that in 1.2.13 the tmp directory is not provided 
any more, in 1.2.11 it was still there.
# tar -tzvf puppet-dashboard-1.2.11.tar.gz|grep tmp
-rw-r--r-- matthaus/allstaff923 2011-08-24 22:37:13 
puppet-dashboard-1.2.11/vendor/rails/railties/lib/tasks/tmp.rake
drwxr-xr-x matthaus/allstaff  0 2012-09-13 23:28:22 
puppet-dashboard-1.2.11/tmp/
# tar -tzvf puppet-dashboard-1.2.13.tar.gz|grep tmp
-rw-r--r-- matthaus/allstaff923 2012-11-06 00:15:09 
puppet-dashboard-1.2.13/vendor/rails/railties/lib/tasks/tmp.rake
#

Stefan

-- 
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/-/8yrKNShvqbIJ.
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: Announce: Puppet Dashboard 1.2.13 Available

[Stefan Heijmans]

Matthaus,
I also noticed the following messages with the 1.2.13 db:migrate rake task, 
haven't seem them before;
# rake db:migrate RAILS_ENV=production
config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem rack-1.1.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem json_pure-1.5.1 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
 

Stefan

-- 
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/-/Yp3DpRU4t6EJ.
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] Announce: Puppet-Dashboard 1.2.14 Available

[Stefan Heijmans]

el5 was not supported, as it has an dependency on ruby 1.8.7 and el5 comes 
default with ruby 1.8.5.
now that they deliver ruby 1.8.7 with puppet 3 for el5, they perhaps can 
also build them for el5.
 
 
Op vrijdag 9 november 2012 14:11:52 UTC+1 schreef Heriyanto het volgende:

> Great..! 
> Its that any RPM for el5? because i don't see on 
> http://yum.puppetlabs.com/el/5/products/x86_64/.
>
> Thanks
>
>
> On Thu, Nov 8, 2012 at 5:36 AM, Moses Mendoza 
> 
> > wrote:
>
>> Puppet Dashboard 1.2.14 is a bugfix release of Puppet Dashboard.
>>
>> This release is available for download at:
>> https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.14.tar.gz
>>
>> Debian packages are available at https://apt.puppetlabs.com
>>
>> RPM packages are available at https://yum.puppetlabs.com
>>
>> See the Verifying Puppet Download section at:
>> http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet
>>
>> Please report feedback via the Puppet Labs Redmine site, using an
>> affected version of 1.2.14:
>> http://projects.puppetlabs.com/projects/dashboard
>>
>> Documentation is available at:
>> http://docs.puppetlabs.com/dashboard/index.html
>>
>> ===
>> ## Puppet Dashboard 1.2.14 Bug Fixes ##
>> ===
>>
>> An error in the packaging of Puppet Dashboard 1.2.13 resulted in
>> several empty directories normally shipped with Puppet Dashboard
>> getting excluded from the source tarball and packages, e.g. 'tmp',
>> 'log', and 'spool'. This release is a re-packaging of Puppet Dashboard
>> 1.2.13 to include these directories. It includes no other changes.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To post to this group, send email to puppet...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to 
>> puppet-users...@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 view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/v9ywYO1gVOQJ.
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: Scope problem in 2.7.12, bug?

[Stefan Heijmans]

No, i's not, it is correct, 
see http://docs.puppetlabs.com/guides/scope_and_puppet.html

At the moment you 'include mysql' only the top scope package variable is 
known, so there fore mysql package will be installed.
swap them around and mysql-server package will get installed.

 class mysql_server { 
  $package = 'mysql-server' 
  include mysql 
} 

On Sunday, November 18, 2012 4:00:26 PM UTC+1, Walter Heck - OlinData.com 
wrote:
>
> I was playing around with scopes, and I noticed the following 
> behaviour, which strikes me as odd? This was done with Puppet 
> Enterprise 2.5.3 which is really Puppet 2.7.12. 
> I'm not sure what I would expect, quite likely an error message or at 
> the very least 'mysql-server' package gettign installed. Instead, it 
> just seems to choose the top-scope variable 'mysql' 
>
> $package = 'mysql' 
>
> class mysql { 
>   package { $mysql_server::package: 
> ensure => present 
>   } 
> } 
>
> class mysql_server { 
>   include mysql 
>   $package = 'mysql-server' 
> } 
>
> include mysql_server 
>
>
> This yields: 
> [root@master test]# puppet apply manifests/init.pp 
> notice: /Stage[main]/Mysql/Package[mysql]/ensure: created 
> notice: Finished catalog run in 6.25 seconds 
>
>
> cheers, 
>
> -- 
> Walter Heck 
> CEO and Founder @ OlinData (http://olindata.com) 
> Puppet training and consulting 
> -- 
> 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/-/l4d_ZijNdZsJ.
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: Scope problem in 2.7.12, bug?

[Stefan Heijmans]

or here; http://docs.puppetlabs.com/puppet/2.7/reference/lang_scope.html

-- 
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/-/hVzytyGJ6rUJ.
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-dashboard - rake API not working

[Stefan Heijmans]

Yes, I noticed it in 1.2.13 (
https://groups.google.com/d/msg/puppet-users/-s07XIymxCo/Yp3DpRU4t6EJ) but 
not in 1.2.14.
Fixed it by running  the mentioned 'rake gems:refresh_specs' 

Stefan


On Monday, November 19, 2012 10:11:35 AM UTC+1, Jacob wrote:
>
> Hello all,
>
> I am quite new to the puppet arena, but I am really impressed with puppet 
> as a tool and the possibilities it gives you with regards to managing many 
> systems.
>
> I am running dashboard 1.2.14 and am trying to query via the rake API: 
> http://docs.puppetlabs.com/dashboard/manual/1.2/rake_api.html
>
> when I do, I get the following error:
>
> 
>
> # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 
> 'node:list'
> (in /var/log)
> config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no 
> specification file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem rack-1.1.2 in vendor/gems has no specification 
> file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification 
> file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification 
> file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no 
> specification file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no 
> specification file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification 
> file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no 
> specification file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem json_pure-1.5.1 in vendor/gems has no 
> specification file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification 
> file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification 
> file. Run 'rake gems:refresh_specs' to fix this.
> config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no 
> specification file. Run 'rake gems:refresh_specs' to fix this.
> DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are 
> deprecated. Use lib/tasks instead. (called from 
> /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10)
>
>
>
> 
>
>
>
> ...I fail to find any info on this online ... has anyone else seen this?
>
> Thanks,
>
> //Jacob.
>

-- 
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/-/3I-0_vYZfBAJ.
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: puppet-dashboard - rake API not working

[Stefan Heijmans]

And when you provide the RAILS_ENV you are using? For example;
 
sudo -u puppet-dashboard  rake -f /usr/share/puppet-dashboard/Rakefile 
RAILS_ENV=production  'node:list'
 
 

Op woensdag 21 november 2012 08:12:48 UTC+1 schreef Jacob het volgende:

> I don't get the expected output... (a list of my nodes)..
>
> only the deprecation warning.
>
>
>
>
>
> Il giorno martedì 20 novembre 2012 18:37:49 UTC+1, Bruno Leon ha scritto: 
>>
>>  Does it fail or only warn ?
>>
>> I can only see dprecation warnings in your message.
>>
>>  
>>
>> -- 
>>
>> Bruno
>>
>>  
>>
>> On November 19, 2012 11:36:17 PM Jacob wrote:
>>
>> Thanks :)
>>
>> Now I get
>>
>> 
>>
>> # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 
>> 'node:list'
>> (in /usr/share/puppet-dashboard)
>> DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are 
>> deprecated. Use lib/tasks instead. (called from 
>> /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10)
>>
>> 
>>
>>
>>
>> Il giorno lunedì 19 novembre 2012 19:37:43 UTC+1, Stefan Heijmans ha 
>> scritto:
>>
>> Yes, I noticed it in 1.2.13 (
>> https://groups.google.com/d/msg/puppet-users/-s07XIymxCo/Yp3DpRU4t6EJ) 
>> but not in 1.2.14.
>>
>> Fixed it by running  the mentioned 'rake gems:refresh_specs' 
>>
>>
>> Stefan
>>
>>
>>
>> On Monday, November 19, 2012 10:11:35 AM UTC+1, Jacob wrote:
>>
>> Hello all,
>>
>> I am quite new to the puppet arena, but I am really impressed with puppet 
>> as a tool and the possibilities it gives you with regards to managing many 
>> systems.
>>
>> I am running dashboard 1.2.14 and am trying to query via the rake API: 
>> http://docs.puppetlabs.com/dashboard/manual/1.2/rake_api.html
>>
>> when I do, I get the following error:
>>
>> 
>>
>> # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 
>> 'node:list'
>> (in /var/log)
>> config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no 
>> specification file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem rack-1.1.2 in vendor/gems has no specification 
>> file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification 
>> file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification 
>> file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no 
>> specification file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no 
>> specification file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification 
>> file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no 
>> specification file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem json_pure-1.5.1 in vendor/gems has no 
>> specification file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification 
>> file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification 
>> file. Run 'rake gems:refresh_specs' to fix this.
>> config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no 
>> specification file. Run 'rake gems:refresh_specs' to fix this.
>> DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are 
>> deprecated. Use lib/tasks instead. (called from 
>> /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10)
>>
>>
>>
>> 
>>
>>
>>
>> ...I fail to find any info on this online ... has anyone else seen this?
>>
>> Thanks,
>>
>> //Jacob.
>>
>> -- 
>> 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/-/Q-XcVfScapMJ.
>> To post to this group, send email to puppet...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> puppet-users...@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 view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/tg3uEymfq4UJ.
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] Hiera and hiera-gpg

[Stefan Heijmans]

did you read this;
http://www.craigdunn.org/2011/10/secret-variables-in-puppet-with-hiera-and-gpg/
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: using mco to manage puppet resources by class

[Stefan Heijmans]

Hi,
 
mco puppet --help 
says the following for tags;
   --tags, --tag TAGRestrict the run to specific tags
 
>>mco puppet runonce --noop --tags mysql::master
So, it would be correct that this runs over all puppet nodes, except the 
Puppet run will only process mysql::master.
--tags doesn't act as a node filter for MCollective.
 
If you want to filter you puppet run to nodes, only having the class 
mysql::master, use this filter;
   -C, --wc, --with-class CLASS Match hosts with a certain config 
management class
 
mco puppet runonce --noop --wc mysql::master
 
Stefan
 

Op zondag 8 december 2013 05:22:53 UTC+1 schreef jc.listmail:

> Has anyone successfully use the class selectors for the puppet MCollective 
> plugin? 
>
> Something like:
>
> $ mco puppet runonce --tags mysql::master
>
> From the docs:
>  *puppet_tags*
> *===*
>
>  *Validates that a comma seperated list of tags are valid Puppet class 
> names*
>
>  *  Author: R.I.Pienaar >*
> * Version: 1.0*
> * License: ASL 2.0*
> * Timeout: 1*
> *   Home Page: http://devco.net/ *
>
>  *   Puppet tags can be a comma seperated list of valid class names, for 
> details*
> *   about valid class names please see the puppet_variable validator 
> documentation.*
>
>  *   An example of 2 tags would be:*
>
>  *   apache,mysql::master*
>
>
> When I run that command, even though that class is only applied to a 
> single host, the list it compiles is all 43 of the hosts currently under 
> mco control:
>
>  $ mco puppet runonce --noop --tags mysql::master
>
>  * [ > ] 43 / 
> 43
>
>
>
>
> Finished processing 43 / 43 hosts in 3720.64 ms
>
> I've tried several variations and classes without success.  It always 
> processes the list of all servers.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/2544d7e8-e902-466e-bb51-27f91bc60bcf%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: When does puppet agent load newly installed facter facts?

[Stefan Heijmans]

Hi,

>>The Exec['installCassandra'] executed correctly immediately prior to the 
attempt to create the file['cassandraEnv'] resource. So I know the 
appropriate >>information is available from the file system.
It is a new server, so exec['installCassandra'] will install it but after 
that, your custom fact cassandra_home_dir (=empty) won't be updated anymore 
during the Puppet run, only at beginning. 
That's why it does work for the second run, as it is already installed.

Stefan

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/c767e2a1-9c50-4a33-b0ab-8a3452735048%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard Groups

[Stefan Heijmans]

>>I was looking for a way to group the servers dynamically
Don't know about this but how about making use of the provided rake tasks, 
like;
rake nodegroup:add # Add a new node group
rake nodegroup:add_all_nodes   # Automatically adds all 
nodes to a group
rake node:addgroup # Add group(s) to a node

Stefan

Op maandag 27 januari 2014 15:16:09 UTC+1 schreef kaustubh chaudhari:

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

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0656e682-855e-4a39-a3bc-bcd2ba772308%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard Groups

[Stefan Heijmans]

Do you have MCollective running? 
You could use this to generate a list based on specified facts (mco find 
--wf ) to use in those rake tasks.
Or create them by hand from the Inventory Search in the Dashboard, maybe 
even a custom rake task.
 
Stefan
 

Op dinsdag 28 januari 2014 11:24:08 UTC+1 schreef kaustubh chaudhari:

> Thanks for the Reply Stefan!
>
> I did looked into these options, but i dint find a way to add only windows 
> systems to windows group and linux system to linux group.
>
> -Kaustubh
>
> On Tuesday, January 28, 2014 4:15:39 AM UTC-5, Stefan Heijmans wrote: 
>>
>>  >>I was looking for a way to group the servers dynamically
>> Don't know about this but how about making use of the provided rake 
>> tasks, like;
>> rake nodegroup:add # Add a new node group
>> rake nodegroup:add_all_nodes   # Automatically adds all 
>> nodes to a group
>> rake node:addgroup # Add group(s) to a node
>>
>> Stefan
>>
>> Op maandag 27 januari 2014 15:16:09 UTC+1 schreef kaustubh chaudhari:
>>
>>> Hi,
>>>
>>> I was looking for a way to group the servers dynamically. Eg: create a 
>>> "Windows" Group and all the existing nodes and new nodes should be part of 
>>> "Windows" group.
>>> I edit a group and then add each server, but practically its not 
>>> possible with 2k servers in all!!
>>>
>>> Is there a way to do that?
>>>
>>> -Kaustubh
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6d1b71cb-77c4-4884-ac7f-ff06ce70f069%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard Groups

[Stefan Heijmans]

>>it will export all the node list 
That's not nice :(
So that will really be by hand; copy/paste & strip hostnames.
 
Stefan

Op dinsdag 28 januari 2014 13:36:11 UTC+1 schreef kaustubh chaudhari:

>   Hi Stefan,
>
> I am in process of setting up MCollective!
>
> In the mean while i can do the search using inventory search in Dashboard, 
> i do get the list, but when i try ti export the details in the cvs format, 
> it wont export only filtered, it will export all the node list ie: all 
> linux windows etc.
>
> where i an searching with the facts as osfamily = windows  and/or Linux.
>
> -Kaustubh
>
> With Warm Regards
> Kaustubh.A.Chaudhari
> (M)-09373102619
>
>
> On Tue, Jan 28, 2014 at 6:35 AM, Stefan Heijmans 
> 
> > wrote:
>
>>  Do you have MCollective running? 
>> You could use this to generate a list based on specified facts (mco find 
>> --wf ) to use in those rake tasks.
>> Or create them by hand from the Inventory Search in the Dashboard, maybe 
>> even a custom rake task.
>>  
>> Stefan
>>  
>>
>> Op dinsdag 28 januari 2014 11:24:08 UTC+1 schreef kaustubh chaudhari:
>>  
>>> Thanks for the Reply Stefan!
>>>
>>> I did looked into these options, but i dint find a way to add only 
>>> windows systems to windows group and linux system to linux group.
>>>
>>> -Kaustubh
>>>
>>> On Tuesday, January 28, 2014 4:15:39 AM UTC-5, Stefan Heijmans wrote: 
>>>>
>>>>  >>I was looking for a way to group the servers dynamically
>>>> Don't know about this but how about making use of the provided rake 
>>>> tasks, like;
>>>> rake nodegroup:add # Add a new node group
>>>> rake nodegroup:add_all_nodes   # Automatically adds 
>>>> all nodes to a group
>>>> rake node:addgroup # Add group(s) to a node
>>>>
>>>> Stefan
>>>>
>>>> Op maandag 27 januari 2014 15:16:09 UTC+1 schreef kaustubh chaudhari:
>>>>
>>>>> Hi,
>>>>>
>>>>> I was looking for a way to group the servers dynamically. Eg: create a 
>>>>> "Windows" Group and all the existing nodes and new nodes should be part 
>>>>> of 
>>>>> "Windows" group.
>>>>> I edit a group and then add each server, but practically its not 
>>>>> possible with 2k servers in all!!
>>>>>
>>>>> Is there a way to do that?
>>>>>
>>>>> -Kaustubh
>>>>>
>>>>  -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Puppet Users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/puppet-users/bzFuC0l3TPk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/6d1b71cb-77c4-4884-ac7f-ff06ce70f069%40googlegroups.com.
>>  
>>
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0e9146e4-cf79-4f2e-8440-f91adb4c0a58%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet and best way to append a new user to sshd_config AllowUsers with augeas

[Stefan Heijmans]

Hi,
 
You could also use the augeasproviders module [1] from the forge.
Checkout the sshd_config_provider examples here [2].
 
Stefan
 
[1] http://forge.puppetlabs.com/domcleal/augeasproviders
[2] 
http://augeasproviders.com/documentation/examples.html#sshd_config_provider

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b4b09474-8e90-45bc-ba4d-b41b1a502173%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet dashborad ENC script output blank

[Stefan Heijmans]

Hi,
 
Have you defined any classes *in* Puppet Dashbaord and assigned them 
node1.example.com?
 
Stefan

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

[Puppet Users] Re: puppet dashboard group and class

[Stefan Heijmans]

this one?
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#using-dashboard-for-node-classification
 

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

[Puppet Users] Re: File_line match

[Stefan Heijmans]

Hi,
 
how about using augeasprovider to manage PAM?
http://augeasproviders.com/documentation/examples.html#pam-provider
 
Stefan
 

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

[Puppet Users] Puppet 3.6.0 'issues'

[Stefan Heijmans]

Hello,

Just upgraded Puppet from 3.4.3 to 3.6.0 in our sandbox, noticed the 
following.

-  directory environments
Documentation says; "Set environmentpath = $confdir/environments in the 
puppet master’s puppet.conf (in the [master] or [main] section)."
Except environmentpath does not work in the [master] section, [main] 
section works fine
Checked with; puppet config print and value is empty when specified in 
[master] section.

- puppet run now shows warnings on file resources with sourceselect for 
files which are not available in /files directory.

May 16 10:58:41  puppet-agent[21561]: Find 
/tst/file_metadata/modules/iptables/iptables-config_iptables-1.4.7-11.el6.x86_64.?links=manage&source_permissions=use
 
resulted in 404 with the message: Not Found: Could not find file_metadata 
modules/iptables/iptables-config_iptables-1.4.7-11.el6.x86_64.

  file { '/etc/sysconfig/iptables-config' :
ensure   => present,
owner=> 'root',
group=> 'root',
mode => $iptables::params::mode_sysconfig,
source   =>
  [
  
"puppet:///modules/iptables/iptables-config_${::iptablesversion}.${::hostname}",
  "puppet:///modules/iptables/iptables-config_${::iptablesversion}"
  ],
sourceselect => first,
  }
ll iptables/files/iptables-config_iptables-1.4.7-11*
-rw-r-. 1 puppet puppet 1974 Feb 26  2013 
files/iptables-config_iptables-1.4.7-11.el6.x86_64

- puppet run on the puppet master, facts loaded twice, from modules 
directory and /var/lib/puppet

Info: Retrieving plugin
Info: Loading facts in 
/etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup_agent_version.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/multipath/lib/facter/lvm2version.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/multipath/lib/facter/multipathversion.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/common/lib/facter/vendor.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/common/lib/facter/runlevel.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/common/lib/facter/ictro_status.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/common/lib/facter/swap.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/selinux/lib/facter/c_selinux.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/vmware/lib/facter/vmware_tools_version.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/vmware/lib/facter/vmware_esx_version.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/ad/lib/facter/winbind.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/stdlib/lib/facter/root_home.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/stdlib/lib/facter/facter_dot_d.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/dell/lib/facter/omsa_version.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/ovo/lib/facter/ovo_agent_version.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/puppet/lib/facter/os_version.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/ssh/lib/facter/sshdversion.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/oracle/lib/facter/oracle.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/iptables/lib/facter/iptables.rb
Info: Loading facts in 
/etc/puppet/environments/tst/modules/iptables/lib/facter/iptablesversion.rb
Info: Loading facts in /var/lib/puppet/lib/facter/multipathversion.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ovo_agent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/vmware_esx_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/vmware_tools_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/lvm2version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/netbackup.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables.rb
Info: Loading facts in /var/lib/puppet/lib/facter/sshdversion.rb
Info: Loading facts in /var/lib/puppet/lib/facter/omsa_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/vendor.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptablesversion.rb
Info: Loading facts in /var/lib/puppet/lib/facter/oracle.rb
Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/lib/puppet/lib/facter/os_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/netbackup_agent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ictro_status.rb
Info: Loading facts in /var/lib/puppet/lib/facter/c_selinux.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: 

Re: [Puppet Users] Puppet 3.6.0 'issues'

[Stefan Heijmans]

Hi Felix,
 
>>puppet master --configprint all 
Does show that environmentpath is set when placed in [master] section, 
except client cannot find is modules anymore.
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Could not find class vmware for  on node 
 
>>some configuration issue 
Aha, if you could dig this up, that would be nice.
 
Stefan

On Friday, May 16, 2014 12:44:13 PM UTC+2, Felix.Frank wrote:

> On 05/16/2014 11:20 AM, Stefan Heijmans wrote: 
> > -  directory environments 
> > Documentation says; "Set environmentpath = $confdir/environments in the 
> > puppet master’s puppet.conf (in the [master] or [main] section)." 
> > Except environmentpath does not work in the [master] section, [main] 
> > section works fine 
> > Checked with; puppet config print and value is empty when specified in 
> > [master] section. 
>
> Hmm, 
>
> about this one - that doesn't look correct to me. 
>
> To see config as loaded by a master process, try 
>
>   puppet master --configprint all 
>
> The other issues look legitimate to me, although the dual loading of 
> ruby code reminds me of some configuration issue that we helped at least 
> one other user fix in the past... 
>
> Thanks, 
> Felix 
>

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

[Puppet Users] Re: Puppet 3.6.0 'issues'

[Stefan Heijmans]

Hi Josh,
 
Thanks for your email.
 
>>but isn't the facts loaded from both modulepath and var lib dir just a 
consequence of having pluginsync'd on the master?
I mentioned it, as this behaviour didn't happen with 3.4.3.
 
I'll wait for the 3.6.1 release before testing any further.
 
Stefan
 

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

[Puppet Users] Re: Puppet 3.6.0 'issues'

[Stefan Heijmans]

In 3.6.1 facts are also loaded twice when environmentpath is set in 
main-section of puppet.conf , see 
https://tickets.puppetlabs.com/browse/PUP-2651 

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

[Puppet Users] Re: Announce: Puppet 3.6.2 [ Security and Bug fix Release ]

[Stefan Heijmans]

Aha, experienced the same thing last week, didn't have time to look into it 
yet...

On Monday, June 16, 2014 3:30:31 PM UTC+2, Byron Miller wrote:

> Running puppet 3.6.2 and disable_warnings = deprecations appears to make 
> no difference to prohibiting the alert about environments.
>

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

[Puppet Users] Re: [Puppet-dev] Re: Announce: Puppet 3.6.2 [ Security and Bug fix Release ]

[Stefan Heijmans]

Hi Josh,

On Tuesday, June 17, 2014 6:35:19 PM UTC+2, Joshua Partlow wrote:

> Is that the issue you are seeing?
>
Sorry for the confustion but I had the deprecation warning from the package 
type; allow_virtual parameter.
Fixed it yesterday, had disable_warnings in the wrong location.
 
Stefan
 

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

[Puppet Users] Puppet module 'issue' with sysctl provider (augeasproviders)

[Stefan Heijmans]

Hello,

I've got 'something strange' with a Puppet module, using augeasproviders 
(v1.2.0 or master branch of today) on Puppet 3.6.2
Below a stripped version of it with the same results as the full version;

It installs an Oracle preinstall rpm which also updates /etc/sysctl.conf 
settings and use augeasproviders sysctl resource to watch these settings.

Puppet module with all resources in 1 file
===

init:pp
===
class oracle_t {
  include single
}

install.pp
==
class oracle_t::single {
  package { 'oracle-rdbms-server-11gR2-preinstall':
ensure => present,
  }
  sysctl { 'kernel.shmall':
ensure  => present,
value   => '1073741824',
require => Package['oracle-rdbms-server-11gR2-preinstall'],
  }
  sysctl { 'kernel.sem':
ensure  => present,
value   => '250 32000 100 128',
require => Package['oracle-rdbms-server-11gR2-preinstall'],
  }
}

Before; /etc/sysctl.conf 
-rw-r--r--. 1 root root 1327 Jun 19 12:49 /etc/sysctl.conf

kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.shmall = 4294967296
kernel.shmmax = 68719476736
kernel.sysrq = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1

kernel.sem is *not* available in /etc/sysctl.conf
kernel.shmall is available in /etc/sysctl.conf
kernel.shmall = 4294967296

Puppet run;
Info: Applying configuration version '1403175278'
Notice: 
/Stage[main]/Oracle_t::Single/Package[oracle-rdbms-server-11gR2-preinstall]/ensure:
 
created
Notice: Finished catalog run in 55.02 seconds

After; /etc/sysctl.conf
-rw-r--r--. 1 root root 2679 Jun 19 12:54 /etc/sysctl.conf

fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 128
kernel.shmall = 1073741824
kernel.shmmax = 4398046511104
kernel.shmmni = 4096
kernel.sysrq = 1
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.ip_local_port_range = 9000 65500
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1

kernel.sem is available in /etc/sysctl.conf
kernel.sem = 250 32000 100 128
kernel.shmall is available in /etc/sysctl.conf
kernel.shmall = 1073741824

Now I remove the rpm and use this module;

Puppet module with all resources in 2 files
===

init:pp
===
class oracle_t {
  include install, sysctl
}

install.pp
==
class oracle_t::install {
  package { 'oracle-rdbms-server-11gR2-preinstall':
ensure => present,
  }
}

sysctl.pp
=
class oracle_t::sysctl {
  sysctl { 'kernel.shmall':
ensure  => present,
value   => '1073741824',
require => Package['oracle-rdbms-server-11gR2-preinstall'],
  }
  sysctl { 'kernel.sem':
ensure  => present,
value   => '250 32000 100 128',
require => Package['oracle-rdbms-server-11gR2-preinstall'],
  }
}

Before: /etc/sysctl.conf
-rw-r--r--. 1 root root 1327 Jun 19 13:03 /etc/sysctl.conf

kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.shmall = 4294967296
kernel.shmmax = 68719476736
kernel.sysrq = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1

kernel.sem is *not* available in /etc/sysctl.conf
kernel.shmall is available in /etc/sysctl.conf
kernel.shmall = 4294967296

puppet run;
Info: Applying configuration version '1403175921'
Notice: 
/Stage[main]/Oracle_t::Install/Package[oracle-rdbms-server-11gR2-preinstall]/ensure:
 
created
Notice: /Stage[main]/Oracle_t::Sysctl/Sysctl[kernel.shmall]/value: changed 
configuration value from '4294967296' to '1073741824'
Notice: /Stage[main]/Oracle_t::Sysctl/Sysctl[kernel.sem]/ensure: created
Notice: Finished catalog run in 46.29 seconds

After; /etc/sysctl.conf
-rw-r--r--. 1 root root 1358 Jun 19 13:05 /etc/sysctl.conf

kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 128
kernel.shmall = 1073741824
kernel.shmmax = 68719476736
kernel.sysrq = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1

kernel.sem is available in /etc/sysctl.conf
kernel.sem = 250 32000 100 128
kernel.shmall is available in /etc/sysctl.conf
kernel.shmall = 1073741824


So, 
with Puppet module and resources in 1 file;
- sysctl resources are not set
- /etc/sysctl.conf updates from the rpm are there

with Puppet module and resources in 2 files;
- sysctl resources are set
- /etc/sysctl.conf updates from rpm are somehow removed

And I have no idea why :(

Thanks,
Stefan

-- 
You received this message because 

[Puppet Users] Re: Puppet module 'issue' with sysctl provider (augeasproviders)

[Stefan Heijmans]

anyone?

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

Re: [Puppet Users] Puppet module 'issue' with sysctl provider (augeasproviders)

[Stefan Heijmans]

Hi,
 
the difference is in the /etc/sysctl.conf;'
 
Puppet module with all resources in 1 file
===
After; /etc/sysctl.conf
-rw-r--r--. 1 root root 2679 Jun 19 12:54 /etc/sysctl.conf
fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 128
kernel.shmall = 1073741824
kernel.shmmax = 4398046511104
kernel.shmmni = 4096
kernel.sysrq = 1
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.ip_local_port_range = 9000 65500
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1
 
Puppet module with all resources in 2 files
===
After; /etc/sysctl.conf
-rw-r--r--. 1 root root 1358 Jun 19 13:05 /etc/sysctl.conf
kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 128
kernel.shmall = 1073741824
kernel.shmmax = 68719476736
kernel.sysrq = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1
 
Stefan

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

Re: [Puppet Users] Puppet module 'issue' with sysctl provider (augeasproviders)

[Stefan Heijmans]

Hi John/Felix,
 
thanks for the suggestions, will try them out next week and come back with 
the results
 
Stefan

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

Re: [Puppet Users] Puppet module 'issue' with sysctl provider (augeasproviders)

[Stefan Heijmans]

Hi,

Just did some tests with the suggestions;

class oracle_t {
  include  oracle_t::install
  include  oracle_t::sysctl
}
class oracle_t::install {
  package { 'oracle-rdbms-server-11gR2-preinstall':
ensure => present,
  }
}
class oracle_t::sysctl {
  sysctl { 'kernel.shmall':
ensure  => present,
value   => '1073741820',
require => Package['oracle-rdbms-server-11gR2-preinstall'],
  }
  sysctl { 'kernel.sem':
ensure  => present,
value   => '250 32000 100 129',
require => Package['oracle-rdbms-server-11gR2-preinstall'],
  }
  exec { 'Preserve intermediate sysctl.conf':
command => '/bin/cp -pf /etc/sysctl.conf /tmp/sysctl.conf.intermediate',
require => Package['oracle-rdbms-server-11gR2-preinstall'],
  } -> Sysctl<||>
}

Before; /etc/sysctl.conf 
-rw-r--r--. 1 root root 1327 Jul 25 10:07 /etc/sysctl.conf

kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.shmall = 4294967296
kernel.shmmax = 68719476736
kernel.sysrq = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1

Puppet run;
Info: Applying configuration version '1406274607'
Notice: 
/Stage[main]/Oracle_t::Install/Package[oracle-rdbms-server-11gR2-preinstall]/ensure:
 
created
Notice: /Stage[main]/Oracle_t::Sysctl/Exec[Preserve intermediate 
sysctl.conf]/returns: executed successfully
Notice: /Stage[main]/Oracle_t::Sysctl/Sysctl[kernel.shmall]/value: changed 
configuration value from '1073741824' to '1073741820' and live value from 
'1073741824' to '1073741820'
Notice: /Stage[main]/Oracle_t::Sysctl/Sysctl[kernel.sem]/value: changed 
configuration value from '250 32000 100 128' to '250 32000 100 129' and 
live value from '25032000   100 128' to '250 32000 100 129'
Notice: Finished catalog run in 58.47 seconds

Diff;
diff /etc/sysctl.conf /tmp/sysctl.conf.intermediate
48c48
< kernel.sem = 250 32000 100 129
---
> kernel.sem = 250 32000 100 128
55c55
< kernel.shmall = 1073741820
---
> kernel.shmall = 1073741824

After; /etc/sysctl.conf
-rw-r--r--. 1 root root 2679 Jul 25 10:11 /etc/sysctl.conf

fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 129
kernel.shmall = 1073741820
kernel.shmmax = 4398046511104
kernel.shmmni = 4096
kernel.sysrq = 1
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.ip_local_port_range = 9000 65500
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1

So 'suddenly' this works by adding the exec resource with dependencies to 
all sysctl resources.

Removing the exec resource and changing the package resource to the 
following
package { 'oracle-rdbms-server-11gR2-preinstall':
  ensure => present,
}-> Sysctl<||>

also works.

Before; /etc/sysctl.conf 
-rw-r--r--. 1 root root 1327 Jul 25 10:11 /etc/sysctl.conf

kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.shmall = 4294967296
kernel.shmmax = 68719476736
kernel.sysrq = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1

Puppet run;
Info: Applying configuration version '1406274883'
Notice: 
/Stage[main]/Oracle_t::Install/Package[oracle-rdbms-server-11gR2-preinstall]/ensure:
 
created
Notice: /Stage[main]/Oracle_t::Sysctl/Sysctl[kernel.shmall]/value: changed 
configuration value from '1073741824' to '1073741820' and live value from 
'1073741824' to '1073741820'
Notice: /Stage[main]/Oracle_t::Sysctl/Sysctl[kernel.sem]/value: changed 
configuration value from '250 32000 100 128' to '250 32000 100 129' and 
live value from '25032000   100 128' to '250 32000 100 129'
Notice: Finished catalog run in 63.95 seconds

After; /etc/sysctl.conf
-rw-r--r--. 1 root root 2679 Jul 25 10:19 /etc/sysctl.conf

fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.core_uses_pid = 1
kernel.msgmax = 65536
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 129
kernel.shmall = 1073741820
kernel.shmmax = 4398046511104
kernel.shmmni = 4096
kernel.sysrq = 1
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.ip_forward = 0
net.ipv4.ip_local_port_range = 9000 65500
net.ipv4.tcp_syncookies = 1
net.ipv6.conf.all.disable_ipv6 = 1

I still don't understand why it works now :(

Stefan

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

[Puppet Users] Re: Puppet Dashboard 1.2.23 disable link in Main html page

[Stefan Heijmans]

config/initializers/app_version_init.rb
Sets the URL based on VERSION file

app/views/shared/_global_nav.html.haml
Think that this is the html page

 

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

[Puppet Users] Re: Dashboard can't find classes

[Stefan Heijmans]

Hi,
 
>>However those classes on my puppet master are not being parsed into the 
dashboard. There is no classed shown in dashboard, even I am sure I 
downloaded a few modules.
You mean, you have not added classes manually to the Dashboard?
If so, you do need to do this. Modules available on your Puppet Master are 
*not* automatically detected by the Dashboard.
Use the "Add Class" option to add all needed classes from the Puppet Master 
to the Dashboard, after that use Group/Class option to assign them to a 
Node.
 
Stefan

On Thursday, July 31, 2014 2:58:10 AM UTC+2, Stella wrote:

> I followed this document to install and configure Puppet 3.6.2 and 
> Dashboard 1.2.23 on Red Hat Linux 6.5, both using Apache as web server.
>
> http://docs.puppetlabs.com/guides/install_puppet/pre_install.html
> http://docs.puppetlabs.com/guides/install_puppet/install_el.html
> http://docs.puppetlabs.com/guides/install_puppet/post_install.html
> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
>
> My puppet master and agent are working: master can push class to agent. 
> Also I can access the dashboard console and can see my nodes are listed: 
> http://localhost:3000
>
> However those classes on my puppet master are not being parsed into the 
> dashboard. There is no classed shown in dashboard, even I am sure I 
> downloaded a few modules.
> Do I missing any configuration (module path, or other parameters) ?
>
> NOTE:
> 1. I have added the following to the masters puppet configuration file and 
> the path is correct with the dashboard running on the master.
>  node_terminus  = exec
>  external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 
> /usr/share/puppet-dashboard/bin/external_node
>
> 2. I googled and someone mentioned that he changed the ruby path in the 
> dashboard external node script to use the ruby that was installed (original 
> /usr/bin/ruby doesn't work for ruby installs from source). I am using Ruby 
> 1.8.7. How to find out where is the new ruby installed? 
>
>
> I am stuck on this.  Please help.
>
> Thanks.
>
>

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

[Puppet Users] Re: Dashboard can't find classes

[Stefan Heijmans]

Hi Stella,

1. No, I don't think so but perharps ask Aaron Stone, he maintains dasboard 2.0
2. No, live management is not available in openspurce dashboard. You can use 
the MCollective command line to most of the same things (that is what we use). 
And there are a few webgui's out there for MCollective but I never have tried 
them.

Stefan

On Thursday, July 31, 2014 3:01:10 PM UTC+2, Stella wrote:
> Hi Stefan, thank you so much for the quick reply! That solves my puzzle. I 
> thought the modules available on my Puppet Master will be automatically 
> detected by the Dashboard. 
> 
> As you suggested, I use the "Add Class" option to add all needed classes from 
> the Puppet 
> Master to the Dashboard, after that I use Group/Class option to assign 
> them to a Node. It works!
> 
> Two more questions:
> 
> 1. I am using Dashboard 1.2.23 and I see there is a newer version Dashboard 
> 2.0. Will the new version provide the "classes-auto-detect" function?
> 2. In Enterprise Puppet there is "Live Management", but I don't see it in 
> this open source puppet and dashboard. What is the alternative then? And will 
> this function be available in the new dashboard?
> 
> Thanks a lot!
> 
> Stella
> 
> 
> On Thursday, July 31, 2014 1:55:32 AM UTC-4, Stefan Heijmans wrote:
> 
> Hi,
>  
> >>However those classes on my puppet master are not being parsed into the 
> >>dashboard. There is no classed shown in dashboard, even I am sure I 
> >>downloaded a few modules.
> You mean, you have not added classes manually to the Dashboard?
> If so, you do need to do this. Modules available on your Puppet Master are 
> *not* automatically detected by the Dashboard.
> Use the "Add Class" option to add all needed classes from the Puppet Master 
> to the Dashboard, after that use Group/Class option to assign them to a Node.
>  
> Stefan
> 
> On Thursday, July 31, 2014 2:58:10 AM UTC+2, Stella wrote:
> I followed this document to install and configure Puppet 3.6.2 and Dashboard 
> 1.2.23 on Red Hat Linux 6.5, both using Apache as web server.
> 
> http://docs.puppetlabs.com/guides/install_puppet/pre_install.html
> http://docs.puppetlabs.com/guides/install_puppet/install_el.html
> http://docs.puppetlabs.com/guides/install_puppet/post_install.html
> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
> 
> My puppet master and agent are working: master can push class to agent. 
> Also I can access the dashboard console and can see my nodes are listed: 
> http://localhost:3000
> 
> However those classes on my puppet master are not being parsed into the 
> dashboard. There is no classed shown in dashboard, even I am sure I 
> downloaded a few modules.
> Do I missing any configuration (module path, or other parameters) ?
> 
> NOTE:
> 1. I have added the following to the masters puppet configuration file and 
> the path is correct with the dashboard running on the master.
>  node_terminus  = exec
>  external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 
> /usr/share/puppet-dashboard/bin/external_node
> 
> 2. I googled and someone mentioned that he changed the ruby path in the 
> dashboard external node script to use the ruby that was installed (original 
> /usr/bin/ruby doesn't work for ruby installs from source). I am using Ruby 
> 1.8.7. How to find out where is the new ruby installed? 
> 
> 
> I am stuck on this.  Please help.
> 
> Thanks.

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

[Puppet Users] How to use Puppet Dashboard Group in MCollective?

[Stefan Heijmans]

Hi Stella,

Out of the box there is no support for this.
You can write your own MCollective discovery plugin to do this or use my basic 
version [1] and enhance it 😄

Stefan

[1] https://github.com/sheijmans/mcollective-discovery

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

[Puppet Users] Re: new to puppet - simple ordering question

[Stefan Heijmans]

Hi Phil,
 
checkout the resource ordering docs;
https://docs.puppetlabs.com/learning/ordering.html
 
Stefan.
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7fbec4b4-96d7-4ca9-9d6b-fc3b2b9a453a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet 3.7.1 parse problems with resource overrides.

[Stefan Heijmans]

Hi,

Received the same kind of error with a different message, using Puppet 
3.7.2 with future parser;
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Syntax error at '[' at 
/etc/puppet/environments/tst/modules/managesoft/manifests/install.pp:41:23 
on node 

Had the following in my require statement;
require => [ File ['/var/tmp/mgsft_rollout_response'], File 
['/var/tmp/ux.npl'] ]
fixed by removing spaces to;
require => [File['/var/tmp/mgsft_rollout_response'],File['/var/tmp/ux.npl']]

Stefan

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

[Puppet Users] puppet agent 3.0.2-1 on EL7 install error

[Stefan Heijmans]

Hi,
Is this a correct version?
The release notes show support from version 3.5

http://docs.puppetlabs.com/puppet/3.5/reference/release_notes.html#platform-support-updates

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

[Puppet Users] Re: Puppet opensource releases et releases notes

[Stefan Heijmans]

Hi,
 
What about the Google Group; Puppet Announce 
 
Stefan

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/809e744d-64ea-443a-91a6-9f2a7b00b7bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet 4 : questions about PXP agent and its goal

[Stefan Heijmans]

On Monday, January 4, 2016 at 8:44:12 PM UTC+1, Ryan Coleman wrote:
>
>
> The broker [1], agent [2] and client libraries [3] are open-source for 
> those not running PE but I'm not aware of anything using it beyond PE (yet).
>
> And what about this [1]?

"*A little further down the line, Puppet Labs will create a simplified 
version that will be open sourced and paired with the open version of the 
base Puppet tool. The Application Orchestration feature will be rolled out 
in the Puppet Enterprise 2015.3 update later this year, so presumably this 
open source variant will be let loose sometime in early 2016.*"

[1] 
http://www.nextplatform.com/2015/10/05/puppet-takes-orchestration-up-the-stack-to-apps/
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/84af127d-9b4f-4a0f-831b-520c05b0afcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Recommended way to get mcollective working with PC1

[Stefan Heijmans]

Hi,

See the comment Jo made here [1], activemq and plugins will work.

[1] https://tickets.puppetlabs.com/browse/MCO-722

Stefan

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

Re: [Puppet Users] Recommended way to get mcollective working with PC1

[Stefan Heijmans]

Hi,

On Saturday, January 16, 2016 at 6:38:24 AM UTC+1, François Lafont wrote:
>
> On 16/01/2016 06:14, Francois Lafont wrote:  

And I have just tested in Ubuntu Trusty but it doesn't work. If I force the 
> installation of a plugin, the package "puppet-agent" is removed (see the 
> paste 
> below). 
>
> So, with Trusty and Jessie, how can I install mcollective plugins in 
> "puppet4" nodes? I would like to avoid manual installation. 
>
> What I did on RHEL was;
- activate puppet-release-PC1 repo
- install package 'puppet-agent'
- activate puppet-release repo
- install MCollective plugin package, ie 'mcollective-puppet-agent' 

Installing MCollective plugin package before 'puppet-agent' then it will 
try to install the non-PC1 'mcollective-common' package.

Stefan

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

Re: [Puppet Users] Puppet 4.5 and git & R10K

[Stefan Heijmans]

HI,

Maybe you check the r10k workshop [1] which will do a complete walkthrough 
of r10k or just watch their video [2] of it.

[1] https://github.com/adrienthebo/r10k-workshop/blob/master/WORKSHOP.mkd
[2] https://www.youtube.com/watch?v=rQJbuqMCl9c

Stefan

On Thursday, June 2, 2016 at 2:32:46 AM UTC+2, Alex Samad wrote:
>
>
>
> But branches ??? I read I need to have a production branch ...
>

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

[Puppet Users] Announce: Puppet Agent 1.5.1 available

[Stefan Heijmans]

Hi Eric,

Think you ment these release notes:
https://docs.puppet.com/puppet/latest/reference/release_notes_agent.html

Stefan

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

[Puppet Users] Re: Trouble creating a release RPM from puppetlabs/puppet source repo

[Stefan Heijmans]

Have you tried using the source RPMs from here;

https://yum.puppetlabs.com/el/6/PC1/SRPMS/


On Friday, June 3, 2016 at 8:44:20 PM UTC+2, Matt Larson wrote:
>
>
> I'm trying to create an RPM from source on a stock RHEL6-based (CentOS6) 
> instance, but I'm seeing errors.  I also posted in 
> https://ask.puppet.com/question/26388/trouble-creating-a-release-rpm-from-puppetlabspuppet-source-repo/
>  
>
> The output actually gets pretty far along, but stops at with this error: 
> "install: cannot stat ext/redhat/puppet.conf: no such file or directory". 
> If I fix that problem by manually editing the SPEC file, I just get more 
> errors, so clearly there is no need to go down a rabbit hole since this 
> must work for someone else, right?
>
> I'm also posted in 
> https://ask.puppet.com/question/26388/trouble-creating-a-release-rpm-from-puppetlabspuppet-source-repo/
>
> Ideas?
>
> Thanks in Advance,
> Matt
>

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

[Puppet Users] Re: Trouble creating a release RPM from puppetlabs/puppet source repo

[Stefan Heijmans]

On Wednesday, June 8, 2016 at 11:03:09 AM UTC+2, Matt Larson wrote:
>
> I tried this, but where are the puppet-agent source RPMs ?
>

Indeed they are not there anymore as discussed in [1] and [2] .

[1] https://tickets.puppetlabs.com/browse/CPR-191
[2] https://groups.google.com/forum/#!topic/puppet-users/VdcIu56irMU

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

[Puppet Users] Re: BROKEN PUPPETDB

[Stefan Heijmans]

On Friday, July 1, 2016 at 12:04:19 AM UTC+2, Virat wrote:
>
> var/log/puppetlabs/puppetdb/puppetdb.log
>
>
> 2016-06-30 17:13:54,781 ERROR [p.p.s.storage] 
> *
> * PostgreSQL DB versions older than 9.4 are no longer supported.  Please 
> upgrade Postgres and restart PuppetDB.
> *
> 
>
>
Upgrade Postgres if it is really <9.4.

Stefan

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

[Puppet Users] Re: BROKEN PUPPETDB

[Stefan Heijmans]

Does puppetdb start normal now, no more errors in puppetdb.log?

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

[Puppet Users] Re: BROKEN PUPPETDB

[Stefan Heijmans]

And does this node have a proper node definiton?

On Wednesday, July 6, 2016 at 8:10:12 PM UTC+2, Virat wrote:
>
> view /var/log/puppetlabs/puppetdb/puppetdb.log
>
> 2016-07-06 14:06:11,444 INFO  [p.p.command] 
> [3a13ea71-ecd1-4c5b-b0fa-ffe9e7c8afb6] [replace facts] puppetagent.com 
> <http://www.google.com/url?q=http%3A%2F%2Fpuppetagent.com&sa=D&sntz=1&usg=AFQjCNERFUJgfIV7-T1L3INug28k8lFTqA>
> 2016-07-06 14:06:11,754 INFO  [p.p.command] 
> [50247290-61ba-49cf-bdcc-0e5825ec7907] [store report] puppet v4.5.2 - 
> puppetagent.com 
> <http://www.google.com/url?q=http%3A%2F%2Fpuppetagent.com&sa=D&sntz=1&usg=AFQjCNERFUJgfIV7-T1L3INug28k8lFTqA>
>
> I dont find any errors here puppetdb logs
>
>
> puppetserver --version
> puppetserver version: 2.4.0
>
> puppetdb --version
> puppetdb version: 4.1.2
>
>  puppet --version
> 4.5.2
>
>
>
> On Wednesday, July 6, 2016 at 2:00:06 PM UTC-4, Stefan Heijmans wrote:
>>
>> Does puppetdb start normal now, no more errors in puppetdb.log?
>
>

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

Re: [Puppet Users] Puppet 3.8 EOL Question

[Stefan Heijmans]

This shows the Satellite lifecycle:
https://access.redhat.com/support/policy/updates/satellite

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

[Puppet Users] Re: PuppetDB service not running

[Stefan Heijmans]

Hi,
 
These 2 values (Store limit , Temporary Store limit) are specified in 
/etc/puppetdb/conf.d/config.ini
and matched against your local diskspace.
 
Q: should it be an ERROR of just a WARN like the 'Store Limit' message.
 
>>And the puppetdb port (8081) isn't running
There should be messages in the logfile before these, where the 
ServerConnector is started;
[p.t.s.w.jetty9-service] Initializing web server.
[p.t.s.w.jetty9-service] Starting web server.
[o.e.j.s.Server] jetty-9.1.z-SNAPSHOT
[o.e.j.s.ServerConnector] Started 
ServerConnector@322efcd0{HTTP/1.1}{localhost:8080}
[o.e.j.s.ServerConnector] Started 
ServerConnector@1da50aba{SSL-HTTP/1.1}{0.0.0.0:8081}
[c.p.p.c.services] PuppetDB version 2.2.2
[c.p.p.s.migrate] There are no pending migrations
 
Stefan
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0169b6da-63f9-4e73-8df2-60a3be0eb779%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Razor and Dashboard for Puppet 4

[Stefan Heijmans]

Hi,
For Dashboard, Aaron Stone is doing it now @ 
https://github.com/sodabrew/puppet-dashboard.
Looking at this issue (
https://github.com/sodabrew/puppet-dashboard/issues/320), seems that it 
doens't support Puppet 4 reports yet.
 

Stefan
 

On Thursday, July 23, 2015 at 11:27:24 PM UTC+2, Stack Kororā wrote:

> Greetings,
>
> I am building out a new puppet master system based on 4. Razor and 
> Dashboard are two projects that I never got around to implementing before, 
> but since I have some motivation (and time from those on high to spend 
> working on puppet) I thought it would be nice to have them in my new 
> environment from the get-go.
>
> Except the Razor documentation takes me to 3.8PE...
>
> And Puppet Dashboard hasn't been updated in months
>
> Are these projects that will work with the new Puppet? Has anyone had any 
> luck with them yet?
>
> Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0552c4b7-ec72-4d25-883a-09ab8a280918%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] how were your puppet 3->4 upgrades?

[Stefan Heijmans]

On Wednesday, August 26, 2015 at 10:16:59 AM UTC+2, Fabrice Bacchella wrote:
>
>
> > Le 24 août 2015 à 21:59, Christopher Wood  > a écrit : 
> > 
> My biggest problem: there isn't any working dashboard working with Puppet 
> 4. The puppetdb APIv4 in puppet db 3.1 is not the same as the APIv4 in 
> puppetdb 2, so all of them are now broken, even the one that thought they 
> uses the v4 API. 
>
 
Hopefully PuppetDB 3.x.x will support Puppet 3 clients again, like 
PuppetServer.
 
In the PuppetDB release notes is says that version 2.3.0 supports Puppet 4 
[1], so will this not work together with PuppetExplorer 1.5.0 [2]?
 
1. https://docs.puppetlabs.com/puppetdb/latest/release_notes.html#section-11 
2. https://github.com/spotify/puppetexplorer/releases/tag/1.5.0
 
Stefan
 
 

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

[Puppet Users] Re: MCollective Plugins - Can I Install with Puppet Collections?

[Stefan Heijmans]

Nice one :) 
Think the MCO plugins where forgotten with the new puppet-agent setup, the 
plugin documentation still refers to the non-puppetlabs directories.
 

On Tuesday, September 1, 2015 at 12:34:08 AM UTC+2, Chad Thompson wrote:

> To all:
>
> This is hopefully a simple question:
>
> Prior to the Puppet 4 upgrade, I was using the Puppetlabs repo to install 
> the Puppet agent along with MCollective and a few (puppet, service) 
> MCollective plugins.
>
> With the upgraded install using Puppet Collections (which includes the mco 
> binary and client/server configurations) I can no longer find the plugin 
> packages for MCollective.
>
> (See:  https://docs.puppetlabs.com/mcollective/deploy/plugins.html and 
> the yum repositories at https://yum.puppetlabs.com/el/6.5/PC1/x86_64/ as 
> an example)
>
> Do I need to enable a different repository - or is there something else 
> I'm missing?
>
> Thanks!
>
> Chad
>
> ---
> chad.o@gmail.com 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8ec0a990-a876-4c7e-9ed0-09ace34e36a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: MCollective Plugins - Can I Install with Puppet Collections?

[Stefan Heijmans]

There are some jira tickets on this;
https://tickets.puppetlabs.com/browse/MCOP-516
https://tickets.puppetlabs.com/browse/MCOP-529
 

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

[Puppet Users] Re: Slow user resource-type when host is attached to LDAP directory

[Stefan Heijmans]

There is a user resource attribute; 
forcelocal [1]
Forces the management of local accounts when accounts are also being 
managed by some other NSS
 
Doens't this help?
 
 
[1] 
https://docs.puppetlabs.com/references/latest/type.html#user-attribute-forcelocal

On Tuesday, September 29, 2015 at 11:53:16 AM UTC+2, Alan Chalmers wrote:

> Josh,
>
> Did you ever get a resolution for this?
>
> thanks
>
> alan
>
> On Wednesday, 20 March 2013 04:34:23 UTC+11, Josh wrote:
>>
>> The majority of our servers are attached to large LDAP directories. 
>>  However, there are also cases when we need to define local service 
>> accounts for whatever reason.  We do this with the "user" resource-type. 
>>  If the host is attached to a LDAP directory, it takes Puppet a VERY long 
>> time to process the "user" resource-type.  In our case, it takes 60+ 
>> seconds to process each user type.  Running "puppet resource user username" 
>> on the host takes over 2 minutes.  During this time, the "puppet" process 
>> on each hosts is pegged at 100% CPU usage.
>>
>> Is there any way around this?  I have seen it brought up on the list, but 
>> not anytime recently (2008, last I searched).
>>
>> Thanks.
>>
>

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