[Puppet Users] F5 Module - proxy server

[mike r]

Hello, quick question, when setting up the F5 module and setting up the 
proxy server that talks to F5 balancer, can this proxy be a Windows machine 
or are there any specific OS or system requirements for this proxy?

-- 
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/99b793fa-a583-442b-8e51-cf92d7ff60f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Regenerated new master certs after alterning DNS aliases, Puppet Server not starting

[mike r]

Getting errors on checksums with DB

I had to regenerate certs for master and agent and nodes after altering DNS 
aliases

doesnt like the checksum

 
at 
org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
 
~[puppet-server-release.jar:na]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_101]
2016-08-24 11:10:28,271 WARN  [qtp1808023046-59]* [puppetserver] Puppet 
Error connecting to MASTERNAME on 8081 at route 
/pdb/cmd/v1?checksum=e31c9a403e4e76da070b6193aea5a4bab93618f7&version=4&certname=MASTERNAME&command=replace_facts,
 
error message received was 'Error executing http request'. Failing over to 
the next PuppetDB server_url in the 'server_urls' list*
2016-08-24 11:10:28,272 ERROR [qtp1808023046-59] [puppetserver] Puppet 
Failed to execute 
'/pdb/cmd/v1?checksum=e31c9a403e4e76da070b6193aea5a4bab93618f7&version=4&certname=MASTERNAME&command=replace_facts'
 
on at least 1 of the following 'server_urls': https://MASTERNAME:8081
2016-08-24 11:10:28,273 ERROR [qtp1808023046-59] [puppetserver] Puppet 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/http.rb:115:in 
`raise_request_error' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/http.rb:156:in 
`failover_action' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/http.rb:214:in 
`action' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/command.rb:63:in
 
`submit' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:101:in 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/command.rb:62:in
 
`submit' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:64:in 
`submit_command' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:101:in 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:61:in 
`submit_command' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/puppetdb.rb:37:in
 
`save' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:101:in 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/puppetdb.rb:20:in
 
`save' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:285:in
 
`save' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node/facts.rb:21:in 
`save' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:42:in
 
`extract_facts_from_request' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:23:in
 
`extract_facts_from_request' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:48:in
 
`find' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in
 
`find' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:132:in
 
`do_find' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in
 
`call' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in 
`override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:240:in 
`override' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in
 
`call' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in 
`process' org/jruby/RubyArray.java:1613:in `each' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in 
`process' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in 
`process' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in 
`process' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in
 
`process' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in 
`profile' 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:in
 
`process' 
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in
 
`handleRequest' Puppet$$Server$$Master_80906857.gen:13:in `

[Puppet Users] Re: Razor bootstrap load timing out

[mike r]

looks like it was the DNS on my Razor box, I changed the razor hostname in 
/var/lib/tftpboot/bootstrap.ipxe from hostname to an IP, 

:chain_boot
chain 
http://192.168.56.24:8150/svc/boot?net0=${net0/mac:hexhyp}&dhcp_mac=${dhcp_mac}&serial=${serial}&asset=${asset}&uuid=${uuid}
 
|| goto error

now its loading the kernel


On Saturday, August 20, 2016 at 9:21:04 PM UTC-4, mike r wrote:
>
> Running Razor provisioning
>
> PE Master: Ubuntu 14.04, puppet 4.5.2
> Razor on Centos 7
> Razor Server version: 1.3.0.0
> Razor Client version: 1.2.0
>
>
> Configured the dnsmasq DHCP and TFTP and stocked /var/lib/tftpboot with 
> the 2 files
> [root@razor tftpboot]# ls -la
> total 76
> drw-r-xr-x.  2 root root56 Aug 20 20:51 .
> drwxr-xr-x. 25 root root  4096 Aug 20 19:15 ..
> -rw-r-xr-x   1 root root   913 Aug 20 20:47 *bootstrap.ipxe*
> -rw-r-xr-x   1 root root 68389 Aug 20 00:15 *undionly-20140116.kpxe*
>
> dnsmasq service is running
>
> All I want to do at this point is have a test VM boot up on network, get a 
> DHCP address and load the bootstrap.ipxe from my Razor server
>
> the first part happens ok, its getting the address from dnsmasq w correct 
> Range
>
> tailing my Messages log, you can see its assigning the IP and trying to 
> send bootstrap file to my test VM
>
>
> Aug 20 21:00:48 razor dnsmasq-dhcp[892]: DHCPDISCOVER(enp0s8) 
> 08:00:27:68:4b:45
> Aug 20 21:00:48 razor dnsmasq-dhcp[892]: DHCPOFFER(enp0s8) 192.168.56.45 
> 08:00:27:68:4b:45
> Aug 20 21:00:49 razor dnsmasq-dhcp[892]: DHCPDISCOVER(enp0s8) 
> 08:00:27:68:4b:45
> Aug 20 21:00:49 razor dnsmasq-dhcp[892]: DHCPOFFER(enp0s8) 192.168.56.45 
> 08:00:27:68:4b:45
> Aug 20 21:00:51 razor dnsmasq-dhcp[892]: DHCPREQUEST(enp0s8) 192.168.56.45 
> 08:00:27:68:4b:45
> Aug 20 21:00:51 razor dnsmasq-dhcp[892]: DHCPACK(enp0s8) 192.168.56.45 
> 08:00:27:68:4b:45
> Aug 20 21:00:51 razor dnsmasq-tftp[892]: sent 
> /var/lib/tftpboot/bootstrap.ipxe to 192.168.56.45
>
> For some reason its timing out.
>   
> <https://lh3.googleusercontent.com/-c6jH4INq060/V7j9asZj19I/lW4/GfYw4wbwbPg_3IpZu286aRnQY9xPmsaKACLcB/s1600/Selection_027.jpg>
> 192.168.56.24 = Razor 
> 192.168.56.45 = Test VM
>
>
>
>
> <https://lh3.googleusercontent.com/-o39gxau-gvA/V7j95yoRj7I/lW8/paDJ21V8NfYBf6RXiCLn6PBXuWsz_FEmQCLcB/s1600/Selection_029.jpg>
>
>
>
> Not sure where else to check for the timeouts. 
>
>
>
>

-- 
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/562cbf77-d071-48ca-b920-baef97a6fef9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Razor bootstrap load timing out

[mike r]

Running Razor provisioning

PE Master: Ubuntu 14.04, puppet 4.5.2
Razor on Centos 7
Razor Server version: 1.3.0.0
Razor Client version: 1.2.0


Configured the dnsmasq DHCP and TFTP and stocked /var/lib/tftpboot with the 
2 files
[root@razor tftpboot]# ls -la
total 76
drw-r-xr-x.  2 root root56 Aug 20 20:51 .
drwxr-xr-x. 25 root root  4096 Aug 20 19:15 ..
-rw-r-xr-x   1 root root   913 Aug 20 20:47 *bootstrap.ipxe*
-rw-r-xr-x   1 root root 68389 Aug 20 00:15 *undionly-20140116.kpxe*

dnsmasq service is running

All I want to do at this point is have a test VM boot up on network, get a 
DHCP address and load the bootstrap.ipxe from my Razor server

the first part happens ok, its getting the address from dnsmasq w correct 
Range

tailing my Messages log, you can see its assigning the IP and trying to 
send bootstrap file to my test VM


Aug 20 21:00:48 razor dnsmasq-dhcp[892]: DHCPDISCOVER(enp0s8) 
08:00:27:68:4b:45
Aug 20 21:00:48 razor dnsmasq-dhcp[892]: DHCPOFFER(enp0s8) 192.168.56.45 
08:00:27:68:4b:45
Aug 20 21:00:49 razor dnsmasq-dhcp[892]: DHCPDISCOVER(enp0s8) 
08:00:27:68:4b:45
Aug 20 21:00:49 razor dnsmasq-dhcp[892]: DHCPOFFER(enp0s8) 192.168.56.45 
08:00:27:68:4b:45
Aug 20 21:00:51 razor dnsmasq-dhcp[892]: DHCPREQUEST(enp0s8) 192.168.56.45 
08:00:27:68:4b:45
Aug 20 21:00:51 razor dnsmasq-dhcp[892]: DHCPACK(enp0s8) 192.168.56.45 
08:00:27:68:4b:45
Aug 20 21:00:51 razor dnsmasq-tftp[892]: sent 
/var/lib/tftpboot/bootstrap.ipxe to 192.168.56.45

For some reason its timing out.
  

192.168.56.24 = Razor 
192.168.56.45 = Test VM







Not sure where else to check for the timeouts. 



-- 
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/70180d00-599b-4b47-9771-9552909f8814%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Changes to module not picked up by agent

[mike r]

restarted pe-puppetserver seems to clear cache on master, and the node got 
the updated version. But if I make any other changes to my modules, node 
isnt getting the updated catalog, its using cached version again.


Master running on Ubuntu 14.04  puppet 4.5.2
node running on centos7 puppet 4.5.2




On Thursday, August 18, 2016 at 12:32:12 PM UTC-4, mike r wrote:
>
> Im trying to run an Nginx module, my install.pp has the following line
>
>
>
> $agent_version = $::puppetversion
>   
> #  if $agent_version < 3.8 {
> #fail(" Node ${::fqdn} has a Puppet agent version: 
> ${agent_version} which is not compatible with this module. Need to have 
> minimum Puppet agent 3.8 -")
>  # }
>  
> the IF statement is commented out, yet when I run agent on target, it 
> looks like its cached the old version of the manifest, it still tries to do 
> the IF statement
>
> [root@centos7node state]# puppet agent -t
> Info: Using configured environment 'production'
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Evaluation Error: Error while evaluating a Resource Statement, Evaluation 
> Error: *Error while evaluating a Function Call,  Node centos7node has 
> a Puppet agent version: 4.5.2 which is not compatible with this module. 
> Need to have minimum Puppet agent 3.8 - at 
> /etc/puppetlabs/code/environments/production/modules/nginx/manifests/install.pp:18:3
>  
> on node centos7node*
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
>
>
> Not sure where the caching is occuring, on Master or Agent, Im guessing on 
> master. Any way to clear the cache on both ends? Didnt see anything in 
> docs. 
>
>
>

-- 
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/8f59511f-243d-4fc1-8782-cc5ebf5e7585%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Changes to module not picked up by agent

[mike r]

Puppet 4.5.2



On Thursday, August 18, 2016 at 12:32:12 PM UTC-4, mike r wrote:
>
> Im trying to run an Nginx module, my install.pp has the following line
>
>
>
> $agent_version = $::puppetversion
>   
> #  if $agent_version < 3.8 {
> #fail(" Node ${::fqdn} has a Puppet agent version: 
> ${agent_version} which is not compatible with this module. Need to have 
> minimum Puppet agent 3.8 -")
>  # }
>  
> the IF statement is commented out, yet when I run agent on target, it 
> looks like its cached the old version of the manifest, it still tries to do 
> the IF statement
>
> [root@centos7node state]# puppet agent -t
> Info: Using configured environment 'production'
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Evaluation Error: Error while evaluating a Resource Statement, Evaluation 
> Error: *Error while evaluating a Function Call,  Node centos7node has 
> a Puppet agent version: 4.5.2 which is not compatible with this module. 
> Need to have minimum Puppet agent 3.8 - at 
> /etc/puppetlabs/code/environments/production/modules/nginx/manifests/install.pp:18:3
>  
> on node centos7node*
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
>
>
> Not sure where the caching is occuring, on Master or Agent, Im guessing on 
> master. Any way to clear the cache on both ends? Didnt see anything in 
> docs. 
>
>
>

-- 
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/0d078221-7c0d-41b6-bf01-61dd46b76a84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Changes to module not picked up by agent

[mike r]

Im trying to run an Nginx module, my install.pp has the following line



$agent_version = $::puppetversion
  
#  if $agent_version < 3.8 {
#fail(" Node ${::fqdn} has a Puppet agent version: ${agent_version} 
which is not compatible with this module. Need to have minimum Puppet 
agent 3.8 -")
 # }
 
the IF statement is commented out, yet when I run agent on target, it looks 
like its cached the old version of the manifest, it still tries to do the 
IF statement

[root@centos7node state]# puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Evaluation Error: Error while evaluating a Resource Statement, Evaluation 
Error: *Error while evaluating a Function Call,  Node centos7node has a 
Puppet agent version: 4.5.2 which is not compatible with this module. Need 
to have minimum Puppet agent 3.8 - at 
/etc/puppetlabs/code/environments/production/modules/nginx/manifests/install.pp:18:3
 
on node centos7node*
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run



Not sure where the caching is occuring, on Master or Agent, Im guessing on 
master. Any way to clear the cache on both ends? Didnt see anything in 
docs. 


-- 
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/fc6d2627-42d8-4662-86b7-217329ec1fca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] new CIS Benchmark compliance module for RHEL 7

[mike r]

testing welcome. thanks.

https://forge.puppet.com/perfecto25/cis_rhel7

-- 
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/1e5045af-c1e9-41b0-be75-794c00512944%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] File_line help (regex?)

[mike r]

trying to make sure my grub conf file contains a string,


cat /etc/default/grub

GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
*GRUB_CMDLINE_LINUX="crashkernel=auto audit=1 rd.lvm.lv=rhel/root 
rd.lvm.lv=rhel/swap rhgb quiet"*
GRUB_DISABLE_RECOVERY="true"

my manifest has this,


$file = '/etc/default/grub'

file_line { "(5.2.3) - ${file}: audit=1":
 ensure=> present,
 path  => $file,
 line  => 'audit=1',
 match => *'^GRUB_CMDLINE_LINUX=".*audit=1.*$*',
}

I used Rubular regex editor and the regex works in rubular, it should match 
the line and pass, since hte line contains "audit=1", but during puppet 
run, it throws an exception,

/Stage[main]/Cis_rhel7::Rule::Rule_5_2_3/File_line[(5.2.3) - 
/etc/default/grub: audit=1]/ensure: current_value absent, should be present 
(noop)

Cant figure out why its not matching. 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/e1f77ab6-f07a-4ef8-871c-c7592da1a818%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] File_line only if the file exists

[mike r]

Quick question, Im writing a module that makes sure file_line exists but 
cant figure out how to only apply this if the target file exists, heres the 
module so far


$file = '/etc/modprobe.d/CIS.conf'

file { $file :
  ensure => file,
  mode   => '0600',
  owner  => 'root',
  group  => 'root',
}


file_line { "(1.1.18) ${file} - cramfs":
  ensure  => present,
  path=> $file,
  line=> 'install cramfs /bin/true',
  require => File[$file],
}

file_line { "(1.1.19) ${file} - freevxfs":
  ensure  => present,
  path=> $file,
  line=> 'install freevxfs /bin/true',
  require => File[$file],
}


I added the Require for each file_line but when I test on a node I get 
this, 

*Notice: 
/Stage[main]/Cis_rhel7::Rule::Rule_1_1_18/File[/etc/modprobe.d/CIS.conf]/ensure:
 
current_value absent, should be file (noop)*


*Error: /Stage[main]/Cis_rhel7::Rule::Rule_1_1_18/File_line[(1.1.18) 
/etc/modprobe.d/CIS.conf - cramfs]: Could not evaluate: No such file or 
directory @ rb_sysopen - /etc/modprobe.d/CIS.confError: 
/Stage[main]/Cis_rhel7::Rule::Rule_1_1_18/File_line[(1.1.19) 
/etc/modprobe.d/CIS.conf - freevxfs]: Could not evaluate: No such file or 
directory @ rb_sysopen - /etc/modprobe.d/CIS.confError: 
/Stage[main]/Cis_rhel7::Rule::Rule_1_1_18/File_line[(1.1.20) 
/etc/modprobe.d/CIS.conf - jffs2]: Could not evaluate: No such file or 
directory @ rb_sysopen - /etc/modprobe.d/CIS.conf*
Error: /Stage[main]/Cis_rhel7::Rule::Rule_1_1_18/File_line[(1.1.21) 
/etc/modprobe.d/CIS.conf - hfs]: Could not evaluate: No such file or 
directory @ rb_sysopen - /etc/modprobe.d/CIS.conf
Error: /Stage[main]/Cis_rhel7::Rule::Rule_1_1_18/File_line[(1.1.22) 
/etc/modprobe.d/CIS.conf - hfsplus]: Could not evaluate: No such file or 
directory @ rb_sysopen - /etc/modprobe.d/CIS.conf
Error: /Stage[main]/Cis_rhel7::Rule::Rule_1_1_18/File_line[(1.1.23) 
/etc/modprobe.d/CIS.conf - squashfs]: Could not evaluate: No such file or 
directory @ rb_sysopen - /etc/modprobe.d/CIS.conf
Error: /Stage[main]/Cis_rhel7::Rule::Rule_1_1_18/File_line[(1.1.24) 
/etc/modprobe.d/CIS.conf - udf]: Could not evaluate: No such file or 
directory @ rb_sysopen - /etc/modprobe.d/CIS.conf
Info: Class[Cis_rhel7::Rule::Rule_1_1_18]: Unscheduling all events on 
Class[Cis_rhel7::Rule::Rule_1_1_18]

All my resources are have a resource default of NOOP, since Im doing a 
compliance check. Cant figure out how to make File_line only get applied if 
the file exists. 

-- 
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/dbcdf341-8f37-4a5a-a67e-a8150f34d949%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: cached file in module

[mike r]

using PE 2016.1.2 (4.4.2)



On Thursday, July 7, 2016 at 11:15:19 AM UTC-4, mike r wrote:
>
> Hi all, Im writing a module that serves a shell script located in 
> $basemodulepath/module/files/script.sh
>
> I recently had to update the shell script, but my agents are receiving the 
> old version of the script. 
>
> I checked the node's /opt/puppetlabs/puppet/cache but its not cached 
> there. Cant find a cached copy on the puppet master as well. 
>
> also checked /opt/puppetlabs/server on master and cached script isnt 
> there. 
>

-- 
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/c7130902-a0c6-4e52-a368-8cbcad710beb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] cached file in module

[mike r]

Hi all, Im writing a module that serves a shell script located in 
$basemodulepath/module/files/script.sh

I recently had to update the shell script, but my agents are receiving the 
old version of the script. 

I checked the node's /opt/puppetlabs/puppet/cache but its not cached there. 
Cant find a cached copy on the puppet master as well. 

also checked /opt/puppetlabs/server on master and cached script isnt there. 

-- 
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/f08f447f-3073-4ff2-b472-9da7de6b5758%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Augeas help

[mike r]

Hello, Im tryign to use Augeas in my manifest to manage /etc/fstab file

specifically I want to make sure my /etc/fstab file has the following line

/tmp /tmp nodev,noexec 0 0


Augeas syntax is like learning Chinese, Im trying to make my manifest 
figure out whether 

1) /etc/fstab has a line ^/tmp, if not add a new line with /tmp

2) if this line exists, then if it has nodev option, if not, append the 
'nodev' to this line (/tmp nodev)

3) if this line exists, check if noexec option is there, of not, append to 
the line (/tmp nodev, noexec)

anyone have idea how to actually write this out? 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/48405a04-ab52-4b78-bb05-64d4c3f59a1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppetserver crashes when using Code-Manager and file sync

[mike r]

env: PE2016.1, puppet 4.4.2 on Centos7x64 (VM), monolithic

PuppetMaster VM has 6GB of RAM with 4 CPUs

I recently setup and enabled Code Manager (Code Manager autoconfigure = 
True)

I am seeing lots of puppetserver crashes, cant startup my puppetserver due 
to java errors


[root@puppetmaster3 ~]# tail -f 
/var/log/puppetlabs/puppetserver/puppetserver.log
at clojure.lang.AFn.run(AFn.java:22) [puppet-server-release.jar:na]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_91]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
2016-05-13 12:54:37,715 INFO  [main] [p.t.internal] Beginning shutdown 
sequence
2016-05-13 12:54:37,722 INFO  [async-dispatch-2] 
[p.e.s.j.pe-jruby-metrics-service] PE JRuby Metrics Service: stopping 
metrics sampler job
2016-05-13 12:54:37,731 INFO  [async-dispatch-2] 
[p.e.s.j.pe-jruby-metrics-service] PE JRuby Metrics Service: stopped 
metrics sampler job
2016-05-13 12:54:37,738 INFO  [async-dispatch-2] 
[p.e.s.f.file-sync-client-service] Stopping file sync client service
2016-05-13 13:24:20,006 INFO  [main] [o.e.j.u.log] Logging initialized 
@149083ms
2016-05-13 14:25:48,102 INFO  [main] [o.e.j.u.log] Logging initialized 
@71630ms
2016-05-13 14:26:01,476 INFO  [async-dispatch-2] [p.t.s.w.jetty9-service] 
Initializing web server(s).
2016-05-13 14:26:01,781 INFO  [async-dispatch-2] 
[p.e.s.f.file-sync-storage-core] Initializing file sync server data dir: 
/opt/puppetlabs/server/data/puppetserver/filesync/storage
2016-05-13 14:26:01,817 INFO  [async-dispatch-2] 
[p.e.s.f.file-sync-storage-core] Initializing Git repository at 
/opt/puppetlabs/server/data/puppetserver/filesync/storage/puppet-code.git
2016-05-13 14:26:02,117 INFO  [async-dispatch-2] 
[p.e.s.f.file-sync-storage-service] File sync storage service mounting 
repositories at /file-sync-git
2016-05-13 14:26:03,455 INFO  [async-dispatch-2] 
[p.e.s.f.file-sync-storage-service] Registering file sync storage HTTP API
2016-05-13 14:26:03,461 INFO  [async-dispatch-2] [p.t.s.s.status-service] 
Registering status callback function for file-sync-storage-service service
2016-05-13 14:26:03,481 INFO  [async-dispatch-2] [p.c.services] Starting 
code-manager v1 API...
2016-05-13 14:26:03,520 INFO  [async-dispatch-2] [p.t.s.s.status-service] 
Registering status callback function for code-manager-service service
2016-05-13 14:26:03,931 INFO  [async-dispatch-2] [p.c.config] Writing r10k 
config to "/opt/puppetlabs/server/data/code-manager/r10k.yaml"
2016-05-13 14:26:04,124 INFO  [async-dispatch-2] [p.t.s.s.status-service] 
Registering status callback function for pe-puppet-profiler service
2016-05-13 14:26:04,178 INFO  [async-dispatch-2] 
[p.s.j.jruby-puppet-service] Initializing the JRuby service
2016-05-13 14:26:04,244 INFO  [async-dispatch-2] 
[p.s.p.puppet-admin-service] Starting Puppet Admin web app
2016-05-13 14:26:04,367 INFO  [clojure-agent-send-pool-0] 
[p.s.j.jruby-puppet-internal] Creating JRuby instance with id 1.
2016-05-13 14:26:32,728 WARN  [clojure-agent-send-pool-0] [puppet-server] 
Puppet Setting 'pluginsync' is deprecated.
   (at 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/defaults.rb:1623:in 
`handle')
2016-05-13 14:26:32,824 INFO  [clojure-agent-send-pool-0] [puppet-server] 
Puppet Puppet settings initialized; run mode: master
2016-05-13 14:26:36,743 INFO  [clojure-agent-send-pool-0] 
[p.s.j.jruby-puppet-agents] Finished creating JRubyPuppet instance 1 of 3
2016-05-13 14:26:36,744 INFO  [clojure-agent-send-pool-0] 
[p.s.j.jruby-puppet-internal] Creating JRuby instance with id 2.
2016-05-13 14:26:36,831 INFO  [async-dispatch-2] 
[p.s.c.puppet-server-config-core] Not overriding webserver settings with 
values from core Puppet
2016-05-13 14:26:36,872 INFO  [async-dispatch-2] 
[p.e.s.f.file-sync-client-service] Initializing file sync client service
2016-05-13 14:26:36,908 INFO  [async-dispatch-2] [p.t.s.s.status-service] 
Registering status callback function for file-sync-client-service service
2016-05-13 14:26:36,922 INFO  [async-dispatch-2] 
[p.e.s.f.file-sync-client-service] Registering file sync client HTTP API
2016-05-13 14:26:38,560 ERROR [async-dispatch-2] [p.t.internal] Error 
during service init!!!
java.lang.NullPointerException: null
at 
org.eclipse.jgit.internal.storage.file.UnpackedObjectCache$Table.index(UnpackedObjectCache.java:146)
 
~[puppet-server-release.jar:na]
at 
org.eclipse.jgit.internal.storage.file.UnpackedObjectCache$Table.contains(UnpackedObjectCache.java:109)
 
~[puppet-server-release.jar:na]
at 
org.eclipse.jgit.internal.storage.file.UnpackedObjectCache.isUnpacked(UnpackedObjectCache.java:64)
 
~[puppet-server-release.jar:na]
at 
org.eclipse.jgit.internal.storage.file.ObjectDirectory.openObject(ObjectDirectory.java:37

[Puppet Users] Puppet Cheat Sheet - updated

[mike r]

new cheat sheet up,

https://perfecto25.wordpress.com/puppet/puppet-cheat-sheet/


-- 
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/f83edbd1-2a34-4a44-b627-b5c69c4e8e06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PE Puppet Server startup error - .git removed

[mike r]

figured out the problem, was missing a .git file in 
my /etc/puppetlabs/code/environments/production path


[root@puppetmaster3 production]# pwd
/etc/puppetlabs/code/environments/production
[root@puppetmaster3 production]# ll
total 12
drwxr-xr-x.  4 pe-puppet pe-puppet   70 Apr  5 09:01 .
drwxr-xr-x.  4 pe-puppet pe-puppet   34 Apr  5 09:03 ..
-rw-r--r--.  1 pe-puppet pe-puppet  879 Apr  4 23:49 environment.conf
-rw-r--r--.  1 pe-puppet pe-puppet  112 Apr  4 23:48 .git
drwxr-xr-x.  2 pe-puppet pe-puppet   20 Apr  5 14:42 manifests
drwxr-xr-x. 19 root  root  4096 Apr  5 10:41 modules
[root@puppetmaster3 production]# cat .git
gitdir: 
/opt/puppetlabs/server/data/puppetserver/filesync/client/puppet-code.git/modules/environments/production[root@puppetmaster3
 
production]# 





On Friday, April 8, 2016 at 2:20:48 PM UTC-4, mike r wrote:
>
> Hi all, trying to startup my PE 4.2 server, its complaining about a .git 
> missing from puppet-code
>
>
> from puppetserver.conf
>
>
>
> 2016-04-08 13:53:34,273 INFO  [main] [o.e.j.u.log] Logging initialized 
> @13448ms
> 2016-04-08 13:53:36,189 INFO  [main] [p.t.s.w.jetty9-service] Initializing 
> web server(s).
> 2016-04-08 13:53:36,288 INFO  [main] [p.t.s.s.status-service] Registering 
> status callback function for pe-puppet-profiler service
> 2016-04-08 13:53:36,293 INFO  [main] [p.s.j.jruby-puppet-service] 
> Initializing the JRuby service
> 2016-04-08 13:53:36,349 INFO  [main] [p.t.s.s.status-service] Registering 
> status callback function for pe-jruby-metrics service
> 2016-04-08 13:53:36,388 INFO  [main] [p.s.p.puppet-admin-service] Starting 
> Puppet Admin web app
> 2016-04-08 13:53:50,415 INFO  [clojure-agent-send-pool-0] [puppet-server] 
> Puppet Puppet settings initialized; run mode: master
> 2016-04-08 13:53:51,344 INFO  [clojure-agent-send-pool-0] 
> [p.s.j.jruby-puppet-agents] Finished creating JRubyPuppet instance 1 of 1
> 2016-04-08 13:53:51,357 INFO  [main] [p.s.c.puppet-server-config-core] Not 
> overriding webserver settings with values from core Puppet
> 2016-04-08 13:53:51,358 INFO  [main] [p.e.s.f.file-sync-client-service] 
> Initializing file sync client service
> 2016-04-08 13:53:51,372 INFO  [main] [p.e.s.f.file-sync-client-service] 
> Registering file sync client HTTP API
> 2016-04-08 13:53:51,373 INFO  [main] [p.t.s.s.status-service] Registering 
> status callback function for file-sync-client-service service
> *2016-04-08 13:53:53,260 ERROR [main] [p.t.internal] Error during service 
> init!!!*
> *clojure.lang.ExceptionInfo: throw+: {:type 
> ":puppetlabs.enterprise.file-sync-errors/submodule-error", :repo-name 
> "puppet-code", :repo-path 
> "/opt/puppetlabs/server/data/puppetserver/filesync/client/puppet-code.git", 
> :submodule-path "environments/production", :live-dir 
> "/etc/puppetlabs/code", :message "Submodule environments/production of 
> repository puppet-code has had its .git file removed. Please delete all of 
> the files (including hidden files) in the live directory at 
> /etc/puppetlabs/code and perform another commit on the storage server to 
> restore the contents of the live directory to the correct state."}*
> at 
> puppetlabs.enterprise.services.file_sync_client.file_sync_client_core$eval17850$dirty_submodules__17851$fn__17852$fn__17853.invoke(file_sync_client_core.clj:676)
>  
> ~[na:na]
> at clojure.core.protocols$fn__6086.invoke(protocols.clj:143) 
> ~[puppet-server-release.jar:na]
> at clojure.core.protocols$fn__6057$G__6052__6066.invoke(protocols.clj:19) 
> ~[puppet-server-release.jar:na]
> at clojure.core.protocols$seq_reduce.invoke(protocols.clj:31) 
> ~[puppet-server-release.jar:na]
> at clojure.core.protocols$fn__6080.invoke(protocols.clj:48) 
> ~[puppet-server-release.jar:na]
>
>
> My modulepath has a git repo where I track all my changes to a repo on 
> github,
>
> [root@puppetmaster3 code]# pwd
> /etc/puppetlabs/code
> [root@puppetmaster3 code]# ls -a
> .  ..  environments * .git*  .gitmodules  hieradata  hiera.yaml
> [root@puppetmaster3 code]# 
>
>
> puppet-code.git is also there, 
> /opt/puppetlabs/server/data/puppetserver/filesync/client
> [root@puppetmaster3 client]# ls -a
> .  ..  puppet-code  puppet-code.git
> [root@puppetmaster3 client]# 
>
> Why is it asking me to delete my /etc/puppetlabs/code directory?
>

-- 
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/5e5ff2af-aa07-4109-96ec-a245d1e0c0d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PE Puppet Server startup error - .git removed

[mike r]

Hi all, trying to startup my PE 4.2 server, its complaining about a .git 
missing from puppet-code


from puppetserver.conf



2016-04-08 13:53:34,273 INFO  [main] [o.e.j.u.log] Logging initialized 
@13448ms
2016-04-08 13:53:36,189 INFO  [main] [p.t.s.w.jetty9-service] Initializing 
web server(s).
2016-04-08 13:53:36,288 INFO  [main] [p.t.s.s.status-service] Registering 
status callback function for pe-puppet-profiler service
2016-04-08 13:53:36,293 INFO  [main] [p.s.j.jruby-puppet-service] 
Initializing the JRuby service
2016-04-08 13:53:36,349 INFO  [main] [p.t.s.s.status-service] Registering 
status callback function for pe-jruby-metrics service
2016-04-08 13:53:36,388 INFO  [main] [p.s.p.puppet-admin-service] Starting 
Puppet Admin web app
2016-04-08 13:53:50,415 INFO  [clojure-agent-send-pool-0] [puppet-server] 
Puppet Puppet settings initialized; run mode: master
2016-04-08 13:53:51,344 INFO  [clojure-agent-send-pool-0] 
[p.s.j.jruby-puppet-agents] Finished creating JRubyPuppet instance 1 of 1
2016-04-08 13:53:51,357 INFO  [main] [p.s.c.puppet-server-config-core] Not 
overriding webserver settings with values from core Puppet
2016-04-08 13:53:51,358 INFO  [main] [p.e.s.f.file-sync-client-service] 
Initializing file sync client service
2016-04-08 13:53:51,372 INFO  [main] [p.e.s.f.file-sync-client-service] 
Registering file sync client HTTP API
2016-04-08 13:53:51,373 INFO  [main] [p.t.s.s.status-service] Registering 
status callback function for file-sync-client-service service
*2016-04-08 13:53:53,260 ERROR [main] [p.t.internal] Error during service 
init!!!*
*clojure.lang.ExceptionInfo: throw+: {:type 
":puppetlabs.enterprise.file-sync-errors/submodule-error", :repo-name 
"puppet-code", :repo-path 
"/opt/puppetlabs/server/data/puppetserver/filesync/client/puppet-code.git", 
:submodule-path "environments/production", :live-dir 
"/etc/puppetlabs/code", :message "Submodule environments/production of 
repository puppet-code has had its .git file removed. Please delete all of 
the files (including hidden files) in the live directory at 
/etc/puppetlabs/code and perform another commit on the storage server to 
restore the contents of the live directory to the correct state."}*
at 
puppetlabs.enterprise.services.file_sync_client.file_sync_client_core$eval17850$dirty_submodules__17851$fn__17852$fn__17853.invoke(file_sync_client_core.clj:676)
 
~[na:na]
at clojure.core.protocols$fn__6086.invoke(protocols.clj:143) 
~[puppet-server-release.jar:na]
at clojure.core.protocols$fn__6057$G__6052__6066.invoke(protocols.clj:19) 
~[puppet-server-release.jar:na]
at clojure.core.protocols$seq_reduce.invoke(protocols.clj:31) 
~[puppet-server-release.jar:na]
at clojure.core.protocols$fn__6080.invoke(protocols.clj:48) 
~[puppet-server-release.jar:na]


My modulepath has a git repo where I track all my changes to a repo on 
github,

[root@puppetmaster3 code]# pwd
/etc/puppetlabs/code
[root@puppetmaster3 code]# ls -a
.  ..  environments * .git*  .gitmodules  hieradata  hiera.yaml
[root@puppetmaster3 code]# 


puppet-code.git is also there, 
/opt/puppetlabs/server/data/puppetserver/filesync/client
[root@puppetmaster3 client]# ls -a
.  ..  puppet-code  puppet-code.git
[root@puppetmaster3 client]# 

Why is it asking me to delete my /etc/puppetlabs/code directory?

-- 
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/1f5542d0-7900-4e0e-b0d3-71df041c15e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Windows Remote Desktop Services (Could not find a suitable provider for dism)

[mike r]

I had the same error trying to run DISM module on a Win2008 box, then I 
realized win2008 doesnt have dism, only 2008 R2.

module is not compatible with target OS

On Wednesday, March 6, 2013 at 8:42:10 AM UTC-5, jim wrote:
>
> Hello all
>
> Was wondering if someone could help or advise where i'm going wrong 
>
> i'm trying to install Windows 2008 R2 Remote Desktop Services via Puppet 
> using either DISM or Powershell modules from the forge and getting the same 
> error
>
> When using DISM
>
>
> class roles::trm::remote_desktop_services {
> dism { 'AppServer':
> ensure => present,
> }
> dism { 'AppServer-UI':
> ensure => present,
> }
> dism { 'Printing-XPSServices-Features':
> ensure => present,
> }
> }
>
> when this initially runs, I get pink error messages which I assume its 
> because it requires a reboot to complete the install of this service.
>
> Question: Best approach for rebooting host, when installing features ?
>
> Once i've rebooted the host, and rerun the puppet agent I get the 
> following error:
>
> *err: Could not find a suitable provider for dism*
>
> So I thought it could be the dism module doesn't support Remote Desktop 
> Services.
>
> then tried the Powershell Module
>
> #exec { 'install_remote_desktop_services':
> #command   => 'Import-Module ServerManager
> #  Add-WindowsFeature -Name RDS-RD-Server -Restart  | 
> Out-File 
> c:\Installs\Puppet_Confirmation\install_remote_desktop_services.txt',
> #provider  => powershell,
> #creates   => 
> 'C:/Installs/Puppet_Confirmation/install_remote_desktop_services.txt',
> #}
>
>
> which installs fine and reboots the host etc, but upon running the agent 
> again, I get the same error as above:
>
> *err: Could not find a suitable provider for dism*
>
> If anyone could help, it would be much appreciated
>
> regards
>
> Jim 
>
>
>
>

-- 
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/8213641a-6d82-4b9a-ab6b-6ff843ab07e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] MCO fails to listen to puppetmaster AMQ

[mike r]

HI all, Im playing around with PE 4.2, trying to learn MCO architecture

I have 1 PE master on Ubuntu with AMQ broker
1 test node running Centos7 with PE agent
1 test node running Centos 5.7 with Open source puppet agent

first question, is it possible to enable the open source puppet agent to 
talk to PE AMQ broker? Or can PE Master talk and manage PE agents only?

2nd question:
my Centos7 (with PE agent) is setup correctly, I can run "mco ping" from PE 
Master and Centos7 replies back

on Centos5, I installed mcollective rpm on this Centos5 node and configured 
my certs and priv/pub keys

[root@centos57 ssl]# pwd
/etc/mcollective/ssl

[root@centos57 ssl]# tree
.
|-- ca.cert.pem
|-- centos57.cert.pem
|-- centos57.private_key.pem
|-- clients
|   |-- peadmin-public.pem
|   `-- puppet-dashboard-public.pem
|-- mcollective-private.pem
`-- mcollective-public.pem

1 directory, 7 files


I copied the* centos57.cert.pem, centos57.private_key.pem *files from the 
/var/lib/puppet/ssl dir. This node however isnt talking to Puppetmaster, 

cat /var/log/mcollective.log

I, [2016-04-01T21:58:14.535657 #5270]  INFO -- : activemq.rb:129:in 
`on_connectfail' TCP Connection to 
stomp+ssl://mcollective@puppetmaster2:61613 failed on attempt 42
E, [2016-04-01T21:58:44.537839 #5270] ERROR -- : activemq.rb:149:in 
`on_ssl_connectfail' SSL session creation with 
stomp+ssl://mcollective@puppetmaster2:61613 failed: nested asn1 error
I, [2016-04-01T21:58:44.538121 #5270]  INFO -- : activemq.rb:129:in 
`on_connectfail' TCP Connection to 
stomp+ssl://mcollective@puppetmaster2:61613 failed on attempt 43
E, [2016-04-01T21:59:14.539604 #5270] ERROR -- : activemq.rb:149:in 
`on_ssl_connectfail' SSL session creation with 
stomp+ssl://mcollective@puppetmaster2:61613 failed: nested asn1 error
I, [2016-04-01T21:59:14.539953 #5270]  INFO -- : activemq.rb:129:in 
`on_connectfail' TCP Connection to 
stomp+ssl://mcollective@puppetmaster2:61613 failed on attempt 44
E, [2016-04-01T21:59:44.541296 #5270] ERROR -- : activemq.rb:149:in 
`on_ssl_connectfail' SSL session creation with 
stomp+ssl://mcollective@puppetmaster2:61613 failed: nested asn1 error
I, [2016-04-01T21:59:44.541629 #5270]  INFO -- : activemq.rb:129:in 
`on_connectfail' TCP Connection to 
stomp+ssl://mcollective@puppetmaster2:61613 failed on attempt 45
E, [2016-04-01T22:00:14.543349 #5270] ERROR -- : activemq.rb:149:in 
`on_ssl_connectfail' SSL session creation with 
stomp+ssl://mcollective@puppetmaster2:61613 failed: nested asn1 error
I, [2016-04-01T22:00:14.543682 #5270]  INFO -- : activemq.rb:129:in 
`on_connectfail' TCP Connection to 
stomp+ssl://mcollective@puppetmaster2:61613 failed on attempt 46

my Centos57 mcollective server.cfg is setup like this

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

# Plugins
securityprovider = psk
plugin.psk = unset

connector = activemq
plugin.activemq.pool.size = 1
plugin.activemq.pool.1.host = puppetmaster2
plugin.activemq.pool.1.port = 61613
plugin.activemq.pool.1.user = mcollective
plugin.activemq.pool.1.password = gKtrMuPIK5k3Fh621FYX
plugin.activemq.pool.1.ssl = true
plugin.activemq.pool.1.ssl.ca = /etc/mcollective/ssl/ca.cert.pem
plugin.activemq.pool.1.ssl.cert = /etc/mcollective/ssl/centos57.cert.pem
plugin.activemq.pool.1.ssl.key = 
/etc/mcollective/ssl/centos57.private_key.pem
plugin.activemq.heartbeat_interval = 120
plugin.activemq.max_hbrlck_fails = 0

# Security plugin settings (required):
# ---
securityprovider   = ssl

# SSL plugin settings:
plugin.ssl_server_private  = /etc/mcollective/ssl/mcollective-private.pem
plugin.ssl_server_public   = /etc/mcollective/ssl/mcollective-public.pem
plugin.ssl_client_cert_dir = /etc/mcollective/ssl/clients
plugin.ssl_serializer  = yaml

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

identity = centos57

Trying to understand what other config Im missing on my Centos57 box to 
make it listen to PE Master AMQ broker. 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/9a7becdb-2e65-4ca1-bd33-badbaf2c8d06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Schedule Vcsrepo to sync local with remote

[mike r]

Hello everyone, 

Im trying to use vcsrepo to sync my PE Master files with a remote git 
repository

I wanted to sync every 15 min in case there are new commits on remote. Is 
there a way to set vcsrepo to run on PE Master periodically without using a 
cron job?

this is what my vcsrepo class looks like,


cat vcsrepo.pp

 vcsrepo { "${modulepath}/nginx/files/repo":
ensure   => latest,
provider => git,
source   => https://github.com/myremote.git,
revision => 'master',
force=> true,
  }

Trying to avoid using cron but cant figure if its possible to run this on 
PE Master as 'puppet apply vcsrepo.pp' every 15 min or so. 

-- 
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/69ac8a70-7d36-425c-a08d-36163ec32691%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] scheduling a Git repo sync on PE master

[mike r]

Hi everyone quick question, 

Im trying to update some files in my one of my modules/nginx/files based on 
a file located in some remote repo. My nginx module is distributing a HTML 
file to all managed nodes, and I need to make sure this HTML file is the 
latest commit from the remote repo. Im pulling this HTML file from Git 
remote into my nginx/files/repo folder, and from there, serving the HTML 
file to my managed nodes.

I installed the vcsrepo module on my PE master but trying to decide a good 
way to schedule a periodic pull from the remote repo to my nginx/files 
directory. 

I have a pull_repo.pp 


 vcsrepo { 
'/etc/puppetlabs/code/environments/production/modules/nginx/files/repo':
ensure => latest,
provider   => git,
source => 'https://github.com/puppetlabs/exercise-webpage.git',
revision   => 'master',
force  => true,
  }
  
This works and pulls in the freshest HTML file each time. Whats a good way 
of scheduling this to run on my PE master? Should I setup a regular cron 
job 'crontab -e'  and have it do 'puppet apply pull_repo.pp' or is there a 
more recomended method to run something scheduled on PE master?

-- 
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/357d8208-08b8-4a24-85da-eba24f27a246%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Getting Yum errors for nginx install

[mike r]

looks like issues w  my repos.d, had to install 

sudo yum install epel-release



On Wednesday, January 27, 2016 at 8:12:16 AM UTC-5, mike r wrote:
>
> running nginx module on centos 6.6 (only getting this error for centos 66, 
> also tried centos 7 and ubuntu 12,14 and no errors,)
>
> wondering if anyone has seen this output.
>
> *Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install nginx' returned 1: 
> Error: Nothing to do*
> *Error: /Stage[main]/Nginx::Install/Package[nginx]/ensure: change from 
> purged to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install 
> nginx' returned 1: Error: Nothing to do*
>
>
>
> my install.pp looks like this,
>
>
>  # check node agent version
> $fqdn = $::fqdn
>
> if $puppet_agent_version < '3.8' {
>   fail(" Node ${fqdn} has a Puppet agent version: 
> ${puppet_agent_version} which is not compatible with this module. Need to 
> have minimum Puppet agent 3.8 -")
> }
>
>
> package { 'nginx':
>   name   => $package_name,
>   ensure => present,
> }
>
>
> file { [$nginx_dirs]:
>   ensure  => directory,
>   mode=> '0644',
>   owner   => 'root',
>   group   => 'root',
>   require => Package['nginx'],
> }
>
>
> user { 'nginx_user':
>   name => $user,
>   ensure   => 'present',
>   comment  => "${user}",
>   home => '/var/www',
>   password => '*',
>   password_max_age => '9',
>   password_min_age => '0',
>   shell=> '/usr/sbin/nologin',
>   require  => Package['nginx'],
> }
>
>
> }
>
>
>
>

-- 
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/80477951-d429-4dbc-b27e-3e41809510bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Getting Yum errors for nginx install

[mike r]

running nginx module on centos 6.6 (only getting this error for centos 66, 
also tried centos 7 and ubuntu 12,14 and no errors,)

wondering if anyone has seen this output.

*Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install nginx' returned 1: 
Error: Nothing to do*
*Error: /Stage[main]/Nginx::Install/Package[nginx]/ensure: change from 
purged to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install 
nginx' returned 1: Error: Nothing to do*



my install.pp looks like this,


 # check node agent version
$fqdn = $::fqdn

if $puppet_agent_version < '3.8' {
  fail(" Node ${fqdn} has a Puppet agent version: 
${puppet_agent_version} which is not compatible with this module. Need to 
have minimum Puppet agent 3.8 -")
}


package { 'nginx':
  name   => $package_name,
  ensure => present,
}


file { [$nginx_dirs]:
  ensure  => directory,
  mode=> '0644',
  owner   => 'root',
  group   => 'root',
  require => Package['nginx'],
}


user { 'nginx_user':
  name => $user,
  ensure   => 'present',
  comment  => "${user}",
  home => '/var/www',
  password => '*',
  password_max_age => '9',
  password_min_age => '0',
  shell=> '/usr/sbin/nologin',
  require  => Package['nginx'],
}


}



-- 
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/605d8d82-5ffe-4400-9700-e7faee6f6092%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Does puppet allow Resource References of different types?

[Mike R]

I read the Puppet documentation regarding Resource References: 
http://docs.puppetlabs.com/puppet/latest/reference/lang_datatypes.html#resource-references

I know Multi-Resouce references are allowed:

file { 'some-a':
...
require => File['file-b', 'file-c']
}

However what if my resource depends on a File type and some other type?
Is there a syntax for that?

Thanks

-Mike

-- 
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/caa03139-5b3f-4ad3-8b73-1aef93da3748%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet is not updating user passwords

[Mike R]

I tested on a different machine with a newer version of puppet (v 3.4.3) 
and it worked fine there :)

/etc/shadow 
test4:$6$plwk1mgalbEBBF$ificPYixcMcaotnm8.aayRDa9GDgBp3OgbrFkkU1ZahT/BAf5JvIkR9WjJZNkhIVcsrFkGY/OAs5ZSMvd0Yl3/:16184:0:9:7:::

-- 
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/8e055217-8638-45e5-8714-782bc451e540%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet is not updating user passwords

[Mike R]

Thanks for the help Brian,

I installed *libshadow-ruby1.8* however it still failed to update, however 
this time I ran in debug mode:




















































*vagrant@precise64:/tmp$ sudo puppet apply --verbose --debug 
main.ppwarning: Could not retrieve fact fqdndebug: Failed to load library 
'shadow' for feature 'libshadow'debug: Puppet::Type::User::ProviderPw: file 
pw does not existdebug: Puppet::Type::User::ProviderLdap: true value when 
expecting falsedebug: Puppet::Type::User::ProviderUser_role_add: file 
rolemod does not existdebug: Puppet::Type::User::ProviderDirectoryservice: 
file /usr/bin/dscl does not existdebug: /User[test5]: Provider useradd does 
not support features manages_passwords; not managing attribute 
passworddebug: Creating default schedulesdebug: Failed to load library 
'selinux' for feature 'selinux'debug: Failed to load library 'ldap' for 
feature 'ldap'debug: /File[/var/lib/puppet/client_data]: Autorequiring 
File[/var/lib/puppet]debug: /File[/var/lib/puppet/state/state.yaml]: 
Autorequiring File[/var/lib/puppet/state]debug: 
/File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]debug: 
/File[/var/lib/puppet/state/graphs]: Autorequiring 
File[/var/lib/puppet/state]debug: /File[/etc/puppet/ssl/private]: 
Autorequiring File[/etc/puppet/ssl]debug: /File[/var/lib/puppet/run]: 
Autorequiring File[/var/lib/puppet]debug: /File[/var/lib/puppet/log]: 
Autorequiring File[/var/lib/puppet]debug: /File[/etc/puppet/ssl]: 
Autorequiring File[/etc/puppet]debug: /File[/var/lib/puppet/clientbucket]: 
Autorequiring File[/var/lib/puppet]debug: 
/File[/etc/puppet/ssl/private_keys]: Autorequiring 
File[/etc/puppet/ssl]debug: /File[/etc/puppet/ssl/certs]: Autorequiring 
File[/etc/puppet/ssl]debug: 
/File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring 
File[/var/lib/puppet/state]debug: /File[/etc/puppet/ssl/public_keys]: 
Autorequiring File[/etc/puppet/ssl]debug: /File[/var/lib/puppet/lib]: 
Autorequiring File[/var/lib/puppet]debug: 
/File[/var/lib/puppet/client_yaml]: Autorequiring 
File[/var/lib/puppet]debug: 
/File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring 
File[/var/lib/puppet/state]debug: /File[/var/lib/puppet/facts]: 
Autorequiring File[/var/lib/puppet]debug: 
/File[/etc/puppet/ssl/certificate_requests]: Autorequiring 
File[/etc/puppet/ssl]debug: /File[/var/lib/puppet/state/state.yaml]/mode: 
mode changed '0640' to '0660'debug: Finishing transaction 
70361834010940debug: Loaded state in 0.00 secondsdebug: Loaded state in 
0.00 secondsinfo: Applying configuration version '1398300274'debug: 
/Schedule[daily]: Skipping device resources because running on a hostdebug: 
/Schedule[monthly]: Skipping device resources because running on a 
hostdebug: /Schedule[hourly]: Skipping device resources because running on 
a hostdebug: /Schedule[never]: Skipping device resources because running on 
a hostdebug: User[test5](provider=useradd): Executing '/usr/sbin/useradd -s 
/bin/bash test5'notice: /User[test5]/ensure: createddebug: /User[test5]: 
The container Class[Main] will propagate my refresh eventdebug: 
/Schedule[weekly]: Skipping device resources because running on a 
hostdebug: /Schedule[puppet]: Skipping device resources because running on 
a hostdebug: Class[Main]: The container Stage[main] will propagate my 
refresh eventdebug: Finishing transaction 70361834425240debug: Storing 
statedebug: Stored state in 0.00 secondsnotice: Finished catalog run in 
0.05 secondsdebug: Finishing transaction 70361834090100debug: Received 
report to process from precise64debug: Processing report from precise64 
with processor Puppet::Reports::Store*


I did notice that there was a another package (libshadow-ruby1.8:i386) but 
I think that is for 32 bit, I am running 64 bit ubuntu. 


On Wednesday, April 23, 2014 5:30:07 PM UTC-5, Brian Mathis wrote:
>
> The issue you have is that Puppet is not updating the /etc/shadow file, 
> but even once it's doing that correctly, Method 1 still will not work. The 
> sha1() and md5() functions do not produce passwd/shadow compatible values 
> because that is not what they are for. Generating encrypted passwords is 
> more complex than a simple hash of the password.
>
> Method 2 *should* work, but since it's not, you have something else going 
> on. Have you tried to apply the manifest using debug and/or verbose mode?
>
> I will guess that you're missing the ruby-shadow package, which Puppet 
> needs to manage those files. Check your package provider and/or gem to make 
> sure you have it installed.
>
>
> ❧ Brian Mathis
>
>

-- 
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/4cb19f68-c3a8-40e8-8fb0-71b993eb1cfc%40googlegroups.com.
For more options, visit

[Puppet Users] Puppet is not updating user passwords

[Mike R]

I can't get puppet to update the password for any users that I declare, 
this is my manifest:

user {'test1':
ensure => present,
password => sha1('vagrant'),
shell => '/bin/bash',
}


I also tried with the md5() function, and with raw password hash. I am on 
Ubuntu 12.04, using Puppet 2.7.19, Vagrant 1.5.3.

When I check /etc/shadow, all I see is ! (exclamation points where the 
password should be)

test4:!:16183:0:9:7:::
test3:!:16183:0:9:7:::
test1:!:16183:0:9:7:::
test2:!:16183:0:9:7:::



I posted my question to stackoverflow with more details: 
http://stackoverflow.com/questions/23253271/not-updating-the-user-password
I also looked over this old post 
https://groups.google.com/forum/#!topic/puppet-users/gXpt-YjROMw 

-- 
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/4c1b1ad3-2d3f-41dd-8709-7bb3f83c7c21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Debian jessie, puppetlabs dist-upgrade problem

[Mike R.]

Using wheezy or unstable puppetlabs release, dist-upgrade wants to remove 
puppet and puppet-common to upgrade libruby. Anyone seen this?


root@enigma:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer 
required:
  facter hiera libaugeas-ruby1.8 libjson-ruby libruby libshadow-ruby1.8 
ruby-rgen virt-what
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  puppet puppet-common
The following packages will be upgraded:
  libruby
1 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 7,296 B of archives.
After this operation, 5,186 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
root@enigma:~# 

-- 
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/ce5a9804-9488-4aa0-9a04-f92bb273d962%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.