date:20121105

Thanks again for you reply, but it seems like you don't fully understand 
what I'm having problems with. So I'll try to clarify it a little more:
1. The current way of using two defines is working flawlessly. So I (at 
least partly) understand the concepts surrounding those.
2. Because I have two types of machines: some with just sugar and some with 
sugar and wordpress, I now use two defines that overlap in part (define1 
contains all kinds of info about creating sugar db + unpacking tar, etc, 
while define2 contains all the sugar info of define1 + stuff about creating 
a wordpress db + unpacking wp tar, etc), this means editing two files when 
I change something in the sugar define. As this can lead to differing 
configurations because of editing errors (and always twice the work), I 
would like to be able to split the defines up, so I can call define1 
(sugar) on all machines and define1 (sugar) and sefine 2 (wordpress) on the 
other machines.
3. Some of the variables are shared, for example the mysqld_pwd is used 
twice, and I add a different suffix for sugar and wordpress to get two 
databases. For the httpd-configuration, I specify a different template, 
which is easy to to with defines. So all instances have unique resources, 
hence the choice for defines, not classes.

Does this help you help me?



On Thursday, November 1, 2012 3:27:10 PM UTC+1, Erwin Bogaard wrote:

 I'm having trouble getting the following scenario to work:
 - I have two defines, for example 'sugar' and 'wordpress'.
 - Some nodes need to have both applied, others only sugar.
 - Because you can't use the same resource twice (not that I want to), I 
 can't figure out how to apply two separate defines to one resource

 At  the moment I use the following workaround: I have two defines, one 
 with only sugar and one with both sugar and wordpress. As I have to change 
 both files if I change something for Sugar, this really isn't optimal.
 Anyone a suggestion?



-- 
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/-/rPV6a-6SduwJ.
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] puppetdb postgresql Connection refused

Greetings,

we are trying to setup puppetdb, nut our clients get the following error:

Warning: Unable to fetch my node definition, but the agent run will 
continue:
Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: 
Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
puppetdb:8081: Connection refused - connect(2)
Info: Retrieving plugin
Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb
Info: Loading facts in /var/lib/puppet/lib/facter/bstoragemanufacturer.rb
Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb
Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
puppetdb:8081: Connection refused - connect(2)
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run


The puppetdb is remote for the puppetmaster and is using postgresql.

Direct connect from puppetmaster to the postgresql puppetdb is vaild.

We don't see any hint in the logfiles.


R/ Daniel

-- 
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/-/wOXZdv8QliQJ.
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] Defining dynamic cron jobs

2012-11-05 Thread Alexander Holte-Davidsen

Hi all,

I have a application that I schedule via cron. This is a application that
runs once a week, either on Tuesday or Thursday. The scheduling is now done
via Puppet.

I now see that I need to redefine this, on some nodes the application
should for example only run the 3. Tuesday each month, not each Tuesday.
I want to do the scheduling using puppet and parameterized classes. For
example I want to be able to define:

foo {'Tuesday':
   week = '3',
   hour = '18',
   minute = '00',
}

This should generate a cron job ( that changes every month). For November
it should look like this:
00 18 20 11 *  /usr/bin/foo

Next month the crontab entry should be changed to:
00 18 18 20 * /usr/bin/foo

Has anyone done anything similar and are willing to give me some input on
how to solve this?

/ Alexander

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

[Puppet Users] Puppet NetApp Network device management...

Hi all

Following on from my previous post Puppet Network 
Devices..https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/fuXshtYmhhkI've
 now started work on creating a NetApp network device provider for 
Puppet... 

I'm trying to start simply by just gathering some facts from our filers. 

The code soo far is available here: 
https://github.com/fatmcgav/shrug-netapp/ Credit to the original author 
shrug for setting out the framework... 

Anyhow, onto my first challenge. 

I've downloaded and added the relevant NetApp SDK files into *
modules/shrug-netapp/lib/puppet/util/network_device/netapp/* as shown below:

$ ls -l modules/shrug-netapp/lib/puppet/util/network_device/netapp/
 total 88
 -rw-r--r--. 1 puppet puppet   924 Nov  2 17:13 device.rb
 -rw-r--r--. 1 puppet puppet  8229 Nov  2 17:16 DfmErrno.rb
 -rw-r--r--. 1 puppet puppet   228 Nov  2 17:00 facts.rb
 -rw-r--r--. 1 puppet puppet  9451 Nov  2 17:16 NaElement.rb
 -rw-r--r--. 1 puppet puppet 36089 Nov  2 17:15 NaErrno.rb
 -rw-r--r--. 1 puppet puppet 19036 Nov  2 17:15 NaServer.rb

 
The NaServer class is then included within the device.rb file above. 
However Puppet is currently failing with:

 Info: starting applying configuration to actint-star-nactl01 at 
 actint-star-nactl01
 Error: Could not run: no such file to load -- NaElement


This NaElement file is require'd by the NaServer class. 
However it seems to be failing due to the include path not including the 
NaElement.rb file... 
Therefore I'm guessing that Puppet/Ruby is looking for the NaElement file 
in some default location, rather than the same location as the NaServer 
class... 

I've generated the same error on some tests scripts by moving the NetApp 
SDK files into a sdk sub folder, and then just *require sdk/NaServer* in 
my script, which generates a very similar error:

 ruby hello_ontapi.rb  192.168.35.118 root xxx
 ./sdk/NaServer.rb:21:in `require': no such file to load -- NaElement 
 (LoadError)
 from ./sdk/NaServer.rb:21
 from hello_ontapi.rb:24:in `require'
 from hello_ontapi.rb:24


Any ideas how I could work around this? 

Cheers
Gavin 
 

-- 
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/-/m2-tzSNj7QwJ.
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] puppetdb postgresql Connection refused

On Mon, Nov 05, 2012 at 01:40:18AM -0800, linux@bami wrote:
 Greetings,
 
 we are trying to setup puppetdb, nut our clients get the following error:
 
 Warning: Unable to fetch my node definition, but the agent run will 
 continue:
 Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: 
 Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
 puppetdb:8081: Connection refused - connect(2)
 Info: Retrieving plugin
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bstoragemanufacturer.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb
 Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
 Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
 puppetdb:8081: Connection refused - connect(2)
 Warning: Not using cache on failed catalog
 Error: Could not retrieve catalog; skipping run
 
 
 The puppetdb is remote for the puppetmaster and is using postgresql.
Can you post your puppet.conf master section and puppetdb.conf please?
 
 Direct connect from puppetmaster to the postgresql puppetdb is vaild.
By direct you mean that you can run

puppet agent -t

on the master and it's working? Did you try to connect to the database
only with telnet as described here - 
http://docs.puppetlabs.com/puppetdb/0.9/install.html#troubleshooting-installation-problems


 
 We don't see any hint in the logfiles.
 
 
 R/ Daniel

Best, Nikola

-- 
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 NetApp Network device management...

Ok, after a bit more googling, have solved the NaElement load error...

Tweaked the NaServer.rb file as follows:

#require 'NaElement'
require File.dirname(__FILE__) + /NaElement

I've now successfully loaded the require Netapp SDK files, and started
working through the connection process...
Though it looks like it's hit another error:

Debug: Puppet::Device::Netapp: connecting to Netapp device
actint-star-nactl01.
Debug: Puppet::Device::Netapp: configdir is .
Error: Can't load netapp for actint-star-nactl01: undefined method `+' for
nil:NilClass

Tracked the above back to *device.rb*, where it's attempting to use *
'Puppet[:configdir]'* but is failing to find the value...

So now to work out what's going on there :)

Cheers
Gav

On Monday, 5 November 2012 10:47:56 UTC, Gavin Williams wrote:

Hi all

Following on from my previous post Puppet Network
Devices..https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/fuXshtYmhhkI've
now started work on creating a NetApp network device provider for
Puppet...

I'm trying to start simply by just gathering some facts from our filers.

The code soo far is available here:
https://github.com/fatmcgav/shrug-netapp/ Credit to the original author
shrug for setting out the framework...

Anyhow, onto my first challenge.

I've downloaded and added the relevant NetApp SDK files into *
modules/shrug-netapp/lib/puppet/util/network_device/netapp/* as shown
below:

$ ls -l modules/shrug-netapp/lib/puppet/util/network_device/netapp/
total 88
-rw-r--r--. 1 puppet puppet 924 Nov 2 17:13 device.rb
-rw-r--r--. 1 puppet puppet 8229 Nov 2 17:16 DfmErrno.rb
-rw-r--r--. 1 puppet puppet 228 Nov 2 17:00 facts.rb
-rw-r--r--. 1 puppet puppet 9451 Nov 2 17:16 NaElement.rb
-rw-r--r--. 1 puppet puppet 36089 Nov 2 17:15 NaErrno.rb
-rw-r--r--. 1 puppet puppet 19036 Nov 2 17:15 NaServer.rb

The NaServer class is then included within the device.rb file above.
However Puppet is currently failing with:

Info: starting applying configuration to actint-star-nactl01 at
actint-star-nactl01
Error: Could not run: no such file to load -- NaElement

This NaElement file is require'd by the NaServer class.
However it seems to be failing due to the include path not including the
NaElement.rb file...
Therefore I'm guessing that Puppet/Ruby is looking for the NaElement file
in some default location, rather than the same location as the NaServer
class...

I've generated the same error on some tests scripts by moving the NetApp
SDK files into a sdk sub folder, and then just *require sdk/NaServer*in my
script, which generates a very similar error:

ruby hello_ontapi.rb 192.168.35.118 root xxx
./sdk/NaServer.rb:21:in `require': no such file to load -- NaElement
(LoadError)
from ./sdk/NaServer.rb:21
from hello_ontapi.rb:24:in `require'
from hello_ontapi.rb:24

Any ideas how I could work around this?

Cheers
Gavin

--
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/-/PFZpeJZd03sJ.
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: puppetdb postgresql Connection refused

Hi Nikola,

thanks for the response!

here are our configs:

 cat /etc/puppet/puppet.conf

[main]
server = lx1ml.unix.lan
logdir = /var/log/puppet
rundir = /var/run/puppet
confdir = /app/puppet/etc
vardir = /app/puppet/var
ssldir = $vardir/ssl
modulepath = $confdir/modules
manifest = $confdir/manifests/site.pp
pluginsync = true

[master]
certname = lx1ml.unix.lan
dns_alt_names = lx1ml.unix.lan
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
reports = tagmail,http
reportfrom = linux-supp...@xx.de
#reporturl = http://lx1ml.unix.lan:3000/reports/upload
storeconfigs = true
storeconfigs_backend = puppetdb
#facts_terminus = yaml
#facts_terminus = inventory_active_record
#dbadapter = mysql
#dbname = dashboard
#dbuser = dashboard
#dbpassword = x
#dbserver = puppetdb.unix.lan
#dbport = 
[production]
modulepath = /app/puppet/env/production/modules
manifest = /app/puppet/env/production/manifests/site.pp
[development]
modulepath = /app/puppet/env/development/modules
manifest = /app/puppet/env/development/manifests/site.pp


cat /etc/puppet/puppetdb.conf
[main]
server = lxj2j.unix.lan
port = 8081


Direkt connect from the puppetmaster to the puppetdb postgresql via psql
[lx1ml ~]# psql -h lxj2j -U puppetdb -d puppetdb


Telnet Connect is working:
[root@lx1ml ~]# telnet lxj2j 8081
Trying 172.20.250.153...
Connected to lxj2j.
Escape character is '^]'.
^CConnection closed by foreign host.


Puppetdb config from lxj2j:

cat /etc/puppetdb/conf.d/jetty.ini
[jetty]
# Hostname to list for clear-text HTTP.  Default is localhost
#host = localhost
# Port to listen on for clear-text HTTP.
port = 8080

ssl-host = lxj2j.unix.lan
ssl-port = 8081
keystore = /etc/puppetdb/ssl/keystore.jks
truststore = /etc/puppetdb/ssl/truststore.jks
removed passwords from output

[root@lxj2j data]# cat /etc/puppetdb/conf.d/database.ini |grep -v ^#
[database]
classname = org.postgresql.Driver
subprotocol = postgresql
subname = //localhost:5432/puppetdb
log-slow-statements = 10
syntax_pgs = true
gc-interval = 60
username = puppetdb
password = puppetdb


Greetings 

Daniel


Am Montag, 5. November 2012 10:40:18 UTC+1 schrieb linux@bami:

 Greetings,

 we are trying to setup puppetdb, nut our clients get the following error:

 Warning: Unable to fetch my node definition, but the agent run will 
 continue:
 Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: 
 Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
 puppetdb:8081: Connection refused - connect(2)
 Info: Retrieving plugin
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bstoragemanufacturer.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb
 Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
 Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
 puppetdb:8081: Connection refused - connect(2)
 Warning: Not using cache on failed catalog
 Error: Could not retrieve catalog; skipping run


 The puppetdb is remote for the puppetmaster and is using postgresql.

 Direct connect from puppetmaster to the postgresql puppetdb is vaild.

 We don't see any hint in the logfiles.


 R/ Daniel



-- 
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/-/VI1kAWjPLPEJ.
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 NetApp Network device management...

Ok, have fixed that error aswell...

Replaced *':configdir' *with *':confdir'*.
However it's now failing due to the netapp.yml file not being present...
What's confused me is the path it's come up with for *':confdir'*.
According to the debug output, it's trying to use

ESC[0;36mDebugESC[0m: Puppet::Device::Netapp: connecting to Netapp device
actint-star-nactl01.
ESC[0;36mDebugESC[0m: Puppet::Device::Netapp: configdir is
/var/lib/puppet/devices/actint-star-nactl01.

However I would prefer it to use */etc/puppet* on the master...
Any way I could do this, other than hard-coding?

Cheers
Gavin

On Monday, 5 November 2012 11:24:16 UTC, Gavin Williams wrote:

Ok, after a bit more googling, have solved the NaElement load error...

Tweaked the NaServer.rb file as follows:

#require 'NaElement'
require File.dirname(__FILE__) + /NaElement

I've now successfully loaded the require Netapp SDK files, and started
working through the connection process...
Though it looks like it's hit another error:

Tracked the above back to *device.rb*, where it's attempting to use *
'Puppet[:configdir]'* but is failing to find the value...

So now to work out what's going on there :)

Cheers
Gav

On Monday, 5 November 2012 10:47:56 UTC, Gavin Williams wrote:

Hi all

I'm trying to start simply by just gathering some facts from our filers.

The code soo far is available here:
https://github.com/fatmcgav/shrug-netapp/ Credit to the original author
shrug for setting out the framework...

Anyhow, onto my first challenge.

I've downloaded and added the relevant NetApp SDK files into *
modules/shrug-netapp/lib/puppet/util/network_device/netapp/* as shown
below:

The NaServer class is then included within the device.rb file above.
However Puppet is currently failing with:

Info: starting applying configuration to actint-star-nactl01 at
actint-star-nactl01
Error: Could not run: no such file to load -- NaElement

I've generated the same error on some tests scripts by moving the NetApp
SDK files into a sdk sub folder, and then just *require sdk/NaServer*in my
script, which generates a very similar error:

Any ideas how I could work around this?

Cheers
Gavin

--
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/-/UCHkWT5GWG0J.
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] compiling ruby on HP-UX / PA-RISC

2012-11-05 Thread Alex Harvey

On Monday, November 5, 2012 4:27:54 PM UTC+11, Michael Stanhke wrote:


 1.  You may need to file a bug with ruby-lang.org 
 2.  Would static linking help at all with being maintainable? 

 Thanks Michael.  Actually static linking should be fine - I didn't think 
of it.  I also raised a bug as you suggested, 
https://bugs.ruby-lang.org/issues/7279.  I'll see how it goes.

-- 
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/-/bIVrG6etHBMJ.
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: Call for Speakers for PuppetCamp Singapore dec 3rd

2012-11-05 Thread Walter Heck

Anyone, noone? The PC has been confirmed now, you can sign up 
here: https://www.flickevents.com/puppetcamp-sea-blk-71

Looking forward to seeing you there!

Walter

On Wednesday, 31 October 2012 23:26:52 UTC+1, Walter Heck - OlinData.com 
wrote:

 Hello, 

 after doing a successful PuppetCamp in Kuala Lumpur last June, we are 
 now in the works of organising a PC in Singapore. This will be the 
 first PC in Singapore and the 2nd in Southeast Asia. The date is 
 December 3rd and the location will be the amongst startups famous Blk 
 71. 

 PuppetLabs is sending a speaker (currently 90% confirmed), and we're 
 looking into doing a second session over a Live Hangout. Besides that 
 we're looking for other speakers interested to come and talk about 
 Puppet. 

 If you have any questions or want to propose a session, feel free to 
 respond here publicly or to me privately. 

 Keep an eye out for the opening of the registrations, we expect quite 
 a busy day! 

 regards, 

 -- 
 Walter Heck 
 Founder // OlinData 
 -- 
 Puppet training and consulting @ http://www.olindata.com 
 Follow @olindata on Twitter and/or 'Like' our Facebook page at 
 http://www.facebook.com/olindata 


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/VT4hVIpf9g0J.
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: puppetdb postgresql Connection refused

On Mon, Nov 05, 2012 at 03:32:21AM -0800, linux@bami wrote:
 Hi Nikola,
 
 thanks for the response!
 
 here are our configs:
 
  cat /etc/puppet/puppet.conf
 
 [main]
 server = lx1ml.unix.lan
 logdir = /var/log/puppet
 rundir = /var/run/puppet
 confdir = /app/puppet/etc
 vardir = /app/puppet/var
 ssldir = $vardir/ssl
 modulepath = $confdir/modules
 manifest = $confdir/manifests/site.pp
 pluginsync = true
 
 [master]
 certname = lx1ml.unix.lan
 dns_alt_names = lx1ml.unix.lan
 ssl_client_header = SSL_CLIENT_S_DN
 ssl_client_verify_header = SSL_CLIENT_VERIFY
 reports = tagmail,http
 reportfrom = linux-supp...@xx.de
 #reporturl = http://lx1ml.unix.lan:3000/reports/upload
 storeconfigs = true
 storeconfigs_backend = puppetdb
 #facts_terminus = yaml
 #facts_terminus = inventory_active_record
 #dbadapter = mysql
 #dbname = dashboard
 #dbuser = dashboard
 #dbpassword = x
 #dbserver = puppetdb.unix.lan
 #dbport = 
 [production]
 modulepath = /app/puppet/env/production/modules
 manifest = /app/puppet/env/production/manifests/site.pp
 [development]
 modulepath = /app/puppet/env/development/modules
 manifest = /app/puppet/env/development/manifests/site.pp
 
 
 cat /etc/puppet/puppetdb.conf
 [main]
 server = lxj2j.unix.lan
 port = 8081
 
 
 Direkt connect from the puppetmaster to the puppetdb postgresql via psql
 [lx1ml ~]# psql -h lxj2j -U puppetdb -d puppetdb
 
 
 Telnet Connect is working:
 [root@lx1ml ~]# telnet lxj2j 8081
 Trying 172.20.250.153...
 Connected to lxj2j.
 Escape character is '^]'.
 ^CConnection closed by foreign host.
 
 
 Puppetdb config from lxj2j:
 
 cat /etc/puppetdb/conf.d/jetty.ini
 [jetty]
 # Hostname to list for clear-text HTTP.  Default is localhost
 #host = localhost
 # Port to listen on for clear-text HTTP.
 port = 8080
 
 ssl-host = lxj2j.unix.lan
 ssl-port = 8081
 keystore = /etc/puppetdb/ssl/keystore.jks
 truststore = /etc/puppetdb/ssl/truststore.jks
 removed passwords from output
 
 [root@lxj2j data]# cat /etc/puppetdb/conf.d/database.ini |grep -v ^#
 [database]
 classname = org.postgresql.Driver
 subprotocol = postgresql
 subname = //localhost:5432/puppetdb
 log-slow-statements = 10
 syntax_pgs = true
 gc-interval = 60
 username = puppetdb
 password = puppetdb
 
 
 Greetings 
 
 Daniel
 
 
 Am Montag, 5. November 2012 10:40:18 UTC+1 schrieb linux@bami:
 
  Greetings,
 
  we are trying to setup puppetdb, nut our clients get the following error:
 
  Warning: Unable to fetch my node definition, but the agent run will 
  continue:
  Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: 
  Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
  puppetdb:8081: Connection refused - connect(2)
  Info: Retrieving plugin
  Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb
  Info: Loading facts in /var/lib/puppet/lib/facter/bstoragemanufacturer.rb
  Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb
  Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb
  Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
  Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
  puppetdb:8081: Connection refused - connect(2)
  Warning: Not using cache on failed catalog
  Error: Could not retrieve catalog; skipping run
 
 
  The puppetdb is remote for the puppetmaster and is using postgresql.
 
  Direct connect from puppetmaster to the postgresql puppetdb is vaild.
 
  We don't see any hint in the logfiles.
 
 
  R/ Daniel
 
 

Strange ;; everything seems fine to me. Recheck the logs of the master,
the agent and the db please. Can you also make sure that you have a
signed certificate on the puppetdb host as described here -
http://docs.puppetlabs.com/puppetdb/0.9/install.html#step-1-install-and-configure-puppet.
i.e make sure that 

puppet agent -t

runs properly there. 

P.S. Also did you add a routes.yaml file?

Best, Nikola

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

Re: [Puppet Users] Defining dynamic cron jobs

2012-11-05 Thread Matt Zagrabelny

On Mon, Nov 5, 2012 at 4:23 AM, Alexander Holte-Davidsen
alexander.david...@gmail.com wrote:
 Hi all,

 I have a application that I schedule via cron. This is a application that
 runs once a week, either on Tuesday or Thursday. The scheduling is now done
 via Puppet.

 I now see that I need to redefine this, on some nodes the application should
 for example only run the 3. Tuesday each month, not each Tuesday.
 I want to do the scheduling using puppet and parameterized classes. For
 example I want to be able to define:

 foo {'Tuesday':
week = '3',
hour = '18',
minute = '00',
 }

 This should generate a cron job ( that changes every month). For November it
 should look like this:
 00 18 20 11 *  /usr/bin/foo

 Next month the crontab entry should be changed to:
 00 18 18 20 * /usr/bin/foo

Hmmm. Should that be:

00 18 18 12 *

?

20 is an invalid month.

 Has anyone done anything similar and are willing to give me some input on
 how to solve this?

Instead of using the wildcard ('*') month, could you (simply) specify
the months?

0 18 20 1 *
0 18 18 2 *
0 18 20 3 *
0 18 18 4 *
0 18 20 5 *
0 18 18 6 *
0 18 20 7 *
0 18 18 8 *
0 18 20 9 *
0 18 18 10 *
0 18 20 11 *
0 18 18 12 *

-mz

-- 
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: puppetdb postgresql Connection refused

Hi Nikola,

yes on the puppet master there ist a routes.yaml

[root@lx1ml puppet]# cat routes.yaml
---
master:
  facts:
terminus: puppetdb
cache: yaml

And the puppet agent -t runs fine on the puppetdb if we remove the 
storeconfig settings from our master puppet.conf

Is it possible to increase the jetty log, because we don't the any 
connection attempts or Connection refused.


greetings 

daniel


Am Montag, 5. November 2012 10:40:18 UTC+1 schrieb linux@bami:

 Greetings,

 we are trying to setup puppetdb, nut our clients get the following error:

 Warning: Unable to fetch my node definition, but the agent run will 
 continue:
 Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: 
 Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
 puppetdb:8081: Connection refused - connect(2)
 Info: Retrieving plugin
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bstoragemanufacturer.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb
 Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
 Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
 puppetdb:8081: Connection refused - connect(2)
 Warning: Not using cache on failed catalog
 Error: Could not retrieve catalog; skipping run


 The puppetdb is remote for the puppetmaster and is using postgresql.

 Direct connect from puppetmaster to the postgresql puppetdb is vaild.

 We don't see any hint in the logfiles.


 R/ Daniel



-- 
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/-/OxMm0hZvrTcJ.
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] Defining dynamic cron jobs

2012-11-05 Thread Dan White

You cannot directly set up a cron job to run on the N-th (day-of-the-week).

From the manpage crontab(5):
 
Note:  The  day of a command’s execution can be specified by two fields — day 
of month, and day of week.  If both fields are restricted (ie, aren’t *), the 
command will  be  run  when  either field matches the current time.  For 
example, 30  4  1,15 * 5 would cause a command to be run at 4:30 am on the 
1st and 15th of each month, plus every Friday.
--

To get a script that runs on the N-th Tuesday, I did this:

today=`date +%u`

if [ $today -eq $1 ]
then

fi

Then, I call the script from cron like this:
# Run patch script on second Tuesday of every month
05  02  8-14 *   *   root
/usr/local/scripts/cronScript.sh 2

-
So, the script will run once a day from the 8th thru the 14th and only execute 
the guts of the conditional on Tuesday

Adjust the day-of-the-month field accordingly to get the week you want. 


“Sometimes I think the surest sign that intelligent life exists elsewhere in 
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin  Hobbes)

- Original Message -
From: Alexander Holte-Davidsen alexander.david...@gmail.com
To: puppet-users@googlegroups.com
Sent: Monday, November 5, 2012 5:23:24 AM
Subject: [Puppet Users] Defining dynamic cron jobs

Hi all, 


I have a application that I schedule via cron. This is a application that runs 
once a week, either on Tuesday or Thursday. The scheduling is now done via 
Puppet. 


I now see that I need to redefine this, on some nodes the application should 
for example only run the 3. Tuesday each month, not each Tuesday. 
I want to do the scheduling using puppet and parameterized classes. For example 
I want to be able to define: 


foo {'Tuesday': 
week = '3', 
hour = '18', 
minute = '00', 
} 


This should generate a cron job ( that changes every month). For November it 
should look like this: 
00 18 20 11 * /usr/bin/foo 


Next month the crontab entry should be changed to: 
00 18 18 20 * /usr/bin/foo 


Has anyone done anything similar and are willing to give me some input on how 
to solve this? 


/ Alexander 

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

-- 
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: puppetdb postgresql Connection refused

Hi,

so we figured out the first problem.
We had an alias puppetdb.fqdn which was pointing to out puppet dashboard 
db. It seems that despite from the entry in the puppetdb.conf, puppet uses 
puppetdb as database server.

we changed the alias and now we are getting an ssl error:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
puppetdb:8081: SSL_connect returned=1 errno=0 state=SSLv3 read server 
certificate B: certificate verify failed: [unable to get local issuer 
certificate for /CN=lxj2j.unix.lan]
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

any idea ?! 

thanks and greetings.

Daniel

Am Montag, 5. November 2012 14:36:39 UTC+1 schrieb linux@bami:

 Hi Nikola,

 yes on the puppet master there ist a routes.yaml

 [root@lx1ml puppet]# cat routes.yaml
 ---
 master:
   facts:
 terminus: puppetdb
 cache: yaml

 And the puppet agent -t runs fine on the puppetdb if we remove the 
 storeconfig settings from our master puppet.conf

 Is it possible to increase the jetty log, because we don't the any 
 connection attempts or Connection refused.


 greetings 

 daniel


 Am Montag, 5. November 2012 10:40:18 UTC+1 schrieb linux@bami:

 Greetings,

 we are trying to setup puppetdb, nut our clients get the following error:

 Warning: Unable to fetch my node definition, but the agent run will 
 continue:
 Warning: Error 400 on SERVER: Could not retrieve facts for 
 lxa7t.unix.lan: Failed to submit 'replace facts' command for lxa7t.unix.lan 
 to PuppetDB at puppetdb:8081: Connection refused - connect(2)
 Info: Retrieving plugin
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bstoragemanufacturer.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb
 Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb
 Error: Could not retrieve catalog from remote server: Error 400 on 
 SERVER: Failed to submit 'replace facts' command for lxa7t.unix.lan to 
 PuppetDB at puppetdb:8081: Connection refused - connect(2)
 Warning: Not using cache on failed catalog
 Error: Could not retrieve catalog; skipping run


 The puppetdb is remote for the puppetmaster and is using postgresql.

 Direct connect from puppetmaster to the postgresql puppetdb is vaild.

 We don't see any hint in the logfiles.


 R/ Daniel



-- 
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/-/atH0EqHpJrUJ.
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] Bug when using array in file resource?



On Monday, November 5, 2012 12:37:45 AM UTC-6, pdurkin wrote:

 I'm not convinced that Justin wasn't correct about this being a bug.  I'm 
 having a similar issue



How many people do you need to tell you that the behavior you observe is 
intended?  File a ticket against the documentation if you like, but the 
behavior is as designed, well-entrenched, broadly relied-upon, and useful.

 


 class myclass (...) {

   # some extra stuff here

   $file_list = [ 'a', 'b' ..., 'n' ]
   file { $file_list : 
ensure = 'file',
source = puppet://modules/myclass/$title,
path   = /tmp/$title
   }

 results in the cannot alias file [a] to [/tmp/myclass].  For some reason 
 the resource title in my file is resolving to the class name rather than 
 the file name.



Yes.  That's as it should be.  Variables are always resolved in the 
innermost scope in which they appear.  Other than the top-level scope, 
scopes are established only by node bocks, definition bodies, and class 
bodies.  In particular, they are *not* established by resource declarations 
such as your example file declaration.  Nor is there a functionality gap -- 
Nan already explained how to get the behavior you want.

 


 The solution provided above seems to change the semantics.  myclass 
 becomes a defined type instead and the list of files is moved outside and 
 passed in as multiple instances are created.  That's a work around.



You are hypothesizing an implementation to criticize, instead of 
considering how to model your problem in a way that harmonizes with 
Puppet.  Consider this:

define mymodule::modulefile() {
  file { $name : 
ensure = 'file',
source = puppet:///mymodule/$name,
path   = /tmp/$name
  }
}

class mymodule::myclass {
  $file_list = [ 'a', 'b' ..., 'n' ]
  mymodule::modulefile { $file_list : }
}

Your class remains a class, and continues to define the file list itself.  
The definition 'mymodule::modulefile' represents a type of file that has 
the particular relationship you want between its 'path' and 'source'.
 


 Another would be to not use a list and simply define each file separately 
 in the class, that avoids having to use the $title to abstract the 
 definition into a single resource definition.  I can do that quite easily 
 but in my case I have about 100 files so it makes this much less readable.  
 Found someone had already explained the issue here: 
 http://www.nico.schottelius.org/blog/puppet-name-is-not-as-expected-but-classname/
 .

 Does anyone have an answer as to why $title in this case is resolving to 
 the class title rather than the resource title?  Is that expected and is 
 there a variable I could use instead that would resolve to the name of the 
 resource I'm declaring rather than the class or defined type I'm declaring 
 it in?

 I also tested this and it's not to do with the list, if I use put in each 
 file individually and use $title or $name it still resolves to the class 
 name



Look at it another way: if you were invoking a function, would you expect 
variable references among the parameters to be resolved by the caller or by 
the function?  They are resolved by the caller, of course.  Resource 
declarations are not function calls, but they work analogously in this 
regard.


John

-- 
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/-/OmwBZ88LvzIJ.
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: Apply multiple defines in sequence



On Monday, November 5, 2012 3:48:58 AM UTC-6, Erwin Bogaard wrote:

 Thanks again for you reply, but it seems like you don't fully understand 
 what I'm having problems with. So I'll try to clarify it a little more:
 1. The current way of using two defines is working flawlessly. So I (at 
 least partly) understand the concepts surrounding those.
 2. Because I have two types of machines: some with just sugar and some 
 with sugar and wordpress, I now use two defines that overlap in part 
 (define1 contains all kinds of info about creating sugar db + unpacking 
 tar, etc, while define2 contains all the sugar info of define1 + stuff 
 about creating a wordpress db + unpacking wp tar, etc), this means editing 
 two files when I change something in the sugar define. As this can lead to 
 differing configurations because of editing errors (and always twice the 
 work), I would like to be able to split the defines up, so I can call 
 define1 (sugar) on all machines and define1 (sugar) and sefine 2 
 (wordpress) on the other machines.
 3. Some of the variables are shared, for example the mysqld_pwd is used 
 twice, and I add a different suffix for sugar and wordpress to get two 
 databases. For the httpd-configuration, I specify a different template, 
 which is easy to to with defines. So all instances have unique resources, 
 hence the choice for defines, not classes.

 Does this help you help me?



No, not really.  You have been relatively clear about what you are trying 
to accomplish, but I don't understand what is preventing you from 
accomplishing it.  Perhaps that means you're stumbling over something that 
seems trivial to me.  For example, if the real question is how to share 
data between two or more defined types, then you have at least three 
choices:

   1. Define the data in a class, and have each definition reference the 
   class variables instead of taking that data in the form of parameters.
   2. Externalize the data (e.g. into an Hiera data store), and have each 
   definition reference the needed values by the same fixed key.
   3. Record the data in global variables, and have each definition 
   reference the global values.  (I wouldn't recommend this one except as a 
   temporary hack.)

If that doesn't help then perhaps you should try reducing the problem to 
the simplest possible example that captures the issue.  Often such an 
exercise will itself help you work out the problem, but if it doesn't then 
we can be a lot more helpful to you with actual (simple) manifests to 
critique.


John

-- 
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/-/X60w8VUoFjIJ.
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: puppetdb postgresql Connection refused

On Mon, Nov 05, 2012 at 05:36:39AM -0800, linux@bami wrote:
 Hi Nikola,
 
 yes on the puppet master there ist a routes.yaml
 
 [root@lx1ml puppet]# cat routes.yaml
 ---
 master:
   facts:
 terminus: puppetdb
 cache: yaml
 
 And the puppet agent -t runs fine on the puppetdb if we remove the 
 storeconfig settings from our master puppet.conf
 
 Is it possible to increase the jetty log, because we don't the any 
 connection attempts or Connection refused.

Well on my machine the file is at /etc/puppetdb/log4j.properties. There
you can configure the logging level which in my case is INFO and this should
be more than enough. Did you check the system log for your environment
for problems. For example on my ubuntu machine most of the messages from
the master go to /var/log/syslog. 

Where are you looking for the puppetdb and puppet logs

 
 
 greetings 
 
 daniel

Best, Nikola

 
 
 Am Montag, 5. November 2012 10:40:18 UTC+1 schrieb linux@bami:
 
  Greetings,
 
  we are trying to setup puppetdb, nut our clients get the following error:
 
  Warning: Unable to fetch my node definition, but the agent run will 
  continue:
  Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: 
  Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
  puppetdb:8081: Connection refused - connect(2)
  Info: Retrieving plugin
  Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb
  Info: Loading facts in /var/lib/puppet/lib/facter/bstoragemanufacturer.rb
  Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb
  Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb
  Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
  Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
  puppetdb:8081: Connection refused - connect(2)
  Warning: Not using cache on failed catalog
  Error: Could not retrieve catalog; skipping run
 
 
  The puppetdb is remote for the puppetmaster and is using postgresql.
 
  Direct connect from puppetmaster to the postgresql puppetdb is vaild.
 
  We don't see any hint in the logfiles.
 
 
  R/ Daniel
 
 
 
 -- 
 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/-/OxMm0hZvrTcJ.
 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.

Re: [Puppet Users] Re: puppetdb postgresql Connection refused

On Mon, Nov 05, 2012 at 06:26:35AM -0800, linux@bami wrote:
 Hi,
 
 so we figured out the first problem.
 We had an alias puppetdb.fqdn which was pointing to out puppet dashboard 
 db. It seems that despite from the entry in the puppetdb.conf, puppet uses 
 puppetdb as database server.
 
 we changed the alias and now we are getting an ssl error:
 
 Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
 Failed to submit 'replace facts' command for lxa7t.unix.lan to PuppetDB at 
 puppetdb:8081: SSL_connect returned=1 errno=0 state=SSLv3 read server 
 certificate B: certificate verify failed: [unable to get local issuer 
 certificate for /CN=lxj2j.unix.lan]
 Warning: Not using cache on failed catalog
 Error: Could not retrieve catalog; skipping run
 

This looks like an SSL error to me. Try to remove the storeconfigs and
make a clean

puppet agent -t

from puppetdb host before you enable it again.

 any idea ?! 
 
 thanks and greetings.
 
 Daniel
 
 Am Montag, 5. November 2012 14:36:39 UTC+1 schrieb linux@bami:
 
  Hi Nikola,
 
  yes on the puppet master there ist a routes.yaml
 
  [root@lx1ml puppet]# cat routes.yaml
  ---
  master:
facts:
  terminus: puppetdb
  cache: yaml
 
  And the puppet agent -t runs fine on the puppetdb if we remove the 
  storeconfig settings from our master puppet.conf
 
  Is it possible to increase the jetty log, because we don't the any 
  connection attempts or Connection refused.
 
 
  greetings 
 
  daniel
 
 
  Am Montag, 5. November 2012 10:40:18 UTC+1 schrieb linux@bami:
 
  Greetings,
 
  we are trying to setup puppetdb, nut our clients get the following error:
 
  Warning: Unable to fetch my node definition, but the agent run will 
  continue:
  Warning: Error 400 on SERVER: Could not retrieve facts for 
  lxa7t.unix.lan: Failed to submit 'replace facts' command for 
  lxa7t.unix.lan 
  to PuppetDB at puppetdb:8081: Connection refused - connect(2)
  Info: Retrieving plugin
  Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb
  Info: Loading facts in /var/lib/puppet/lib/facter/bstoragemanufacturer.rb
  Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb
  Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb
  Error: Could not retrieve catalog from remote server: Error 400 on 
  SERVER: Failed to submit 'replace facts' command for lxa7t.unix.lan to 
  PuppetDB at puppetdb:8081: Connection refused - connect(2)
  Warning: Not using cache on failed catalog
  Error: Could not retrieve catalog; skipping run
 
 
  The puppetdb is remote for the puppetmaster and is using postgresql.
 
  Direct connect from puppetmaster to the postgresql puppetdb is vaild.
 
  We don't see any hint in the logfiles.
 
 
  R/ Daniel
 
 
 
 -- 
 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/-/atH0EqHpJrUJ.
 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] Re: Puppet NetApp Network device management...

Me again...

I pressed on using the /var/lib/puppet... configdir for the time-being, and
with a bit more jiggery pokery, I've managed to successfully register a
NetApp device, and extract some facts from it... And here's the
photographic proof :) :D http://ow.ly/i/15SLN

Now to start looking at how to handle the next steps, such as volume
creation, quota creation, export creation... :D

Latest code has been pushed to
Githubhttps://github.com/fatmcgav/fatmcgav-netapp
...

Still need to work out how to use a central confdir rather than agent
specific ones, but can come back to that :)

Cheers
Gavin

On Monday, 5 November 2012 11:35:26 UTC, Gavin Williams wrote:

Ok, have fixed that error aswell...

ESC[0;36mDebugESC[0m: Puppet::Device::Netapp: connecting to Netapp device
actint-star-nactl01.
ESC[0;36mDebugESC[0m: Puppet::Device::Netapp: configdir is
/var/lib/puppet/devices/actint-star-nactl01.

However I would prefer it to use */etc/puppet* on the master...
Any way I could do this, other than hard-coding?

Cheers
Gavin

On Monday, 5 November 2012 11:24:16 UTC, Gavin Williams wrote:

Ok, after a bit more googling, have solved the NaElement load error...

Tweaked the NaServer.rb file as follows:

#require 'NaElement'
require File.dirname(__FILE__) + /NaElement

I've now successfully loaded the require Netapp SDK files, and started
working through the connection process...
Though it looks like it's hit another error:

Tracked the above back to *device.rb*, where it's attempting to use *
'Puppet[:configdir]'* but is failing to find the value...

So now to work out what's going on there :)

Cheers
Gav

On Monday, 5 November 2012 10:47:56 UTC, Gavin Williams wrote:

Hi all

I'm trying to start simply by just gathering some facts from our filers.

The code soo far is available here:
https://github.com/fatmcgav/shrug-netapp/ Credit to the original author
shrug for setting out the framework...

Anyhow, onto my first challenge.

I've downloaded and added the relevant NetApp SDK files into *
modules/shrug-netapp/lib/puppet/util/network_device/netapp/* as shown
below:

The NaServer class is then included within the device.rb file above.
However Puppet is currently failing with:

Info: starting applying configuration to actint-star-nactl01 at
actint-star-nactl01
Error: Could not run: no such file to load -- NaElement

This NaElement file is require'd by the NaServer class.
However it seems to be failing due to the include path not including the
NaElement.rb file...
Therefore I'm guessing that Puppet/Ruby is looking for the NaElement
file in some default location, rather than the same location as the
NaServer class...

I've generated the same error on some tests scripts by moving the NetApp
SDK files into a sdk sub folder, and then just *require sdk/NaServer*in
my script, which generates a very similar error:

Any ideas how I could work around this?

Cheers
Gavin

--
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/-/tYRDCDwxjlsJ.
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: puppetdb postgresql Connection refused

Hi,

we solved the problem. removed all files from /etc/puppetdb/ssl and 
ran /usr/sbin/puppetdb-ssl-setup.

Thanks for the support!!

greetings

Daniel

Am Montag, 5. November 2012 16:07:43 UTC+1 schrieb nikolavp:

 On Mon, Nov 05, 2012 at 05:36:39AM -0800, linux@bami wrote: 
  Hi Nikola, 
  
  yes on the puppet master there ist a routes.yaml 
  
  [root@lx1ml puppet]# cat routes.yaml 
  --- 
  master: 
facts: 
  terminus: puppetdb 
  cache: yaml 
  
  And the puppet agent -t runs fine on the puppetdb if we remove the 
  storeconfig settings from our master puppet.conf 
  
  Is it possible to increase the jetty log, because we don't the any 
  connection attempts or Connection refused. 

 Well on my machine the file is at /etc/puppetdb/log4j.properties. There 
 you can configure the logging level which in my case is INFO and this 
 should 
 be more than enough. Did you check the system log for your environment 
 for problems. For example on my ubuntu machine most of the messages from 
 the master go to /var/log/syslog. 

 Where are you looking for the puppetdb and puppet logs 

  
  
  greetings 
  
  daniel 

 Best, Nikola 

  
  
  Am Montag, 5. November 2012 10:40:18 UTC+1 schrieb linux@bami: 
   
   Greetings, 
   
   we are trying to setup puppetdb, nut our clients get the following 
 error: 
   
   Warning: Unable to fetch my node definition, but the agent run will 
   continue: 
   Warning: Error 400 on SERVER: Could not retrieve facts for 
 lxa7t.unix.lan: 
   Failed to submit 'replace facts' command for lxa7t.unix.lan to 
 PuppetDB at 
   puppetdb:8081: Connection refused - connect(2) 
   Info: Retrieving plugin 
   Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb 
   Info: Loading facts in 
 /var/lib/puppet/lib/facter/bstoragemanufacturer.rb 
   Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb 
   Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb 
   Error: Could not retrieve catalog from remote server: Error 400 on 
 SERVER: 
   Failed to submit 'replace facts' command for lxa7t.unix.lan to 
 PuppetDB at 
   puppetdb:8081: Connection refused - connect(2) 
   Warning: Not using cache on failed catalog 
   Error: Could not retrieve catalog; skipping run 
   
   
   The puppetdb is remote for the puppetmaster and is using postgresql. 
   
   Direct connect from puppetmaster to the postgresql puppetdb is vaild. 
   
   We don't see any hint in the logfiles. 
   
   
   R/ Daniel 
   
   
  
  -- 
  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/-/OxMm0hZvrTcJ. 
  To post to this group, send email to 
  puppet...@googlegroups.comjavascript:. 

  To unsubscribe from this group, send email to 
 puppet-users...@googlegroups.com javascript:. 
  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/-/QuC4XBMIDjoJ.
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] tags and template

2012-11-05 Thread Fabrice Bacchella

I'm trying to use tags in templates.

I have a resource declared as :

define apache::instance($instance_name=$title,$mpm='worker') {
tag(declared-apache-$instance_name)
...
}

this resource is called in the class apache :

class apache{
...
   apache::instance{$instances: }
}

and then a class declared is called after the apache class :
class{'declared::log':
require = Class['apache']
}

this class create a file :
class declared::log {
file {'/var/lib/puppet/declared.txt':
content = template('declared/declared.txt.erb'),
mode= '0640',
owner   = 'root',
group   = '0',
}
}

And then in declared.txt.erb, I enumerated every tags :
% all_tags.sort.each do |tag| -%
The tag %= tag % is defined
% end -%
% tags.sort.each do |tag| -%
The tag %= tag % is part of the current scope
% end -%


So the file /var/lib/puppet/declared.txt is created after the tag 
declared-apache-$instance_name has been created.

But in the file /var/lib/puppet/declared.txt, I can't see this tag. I see all 
the implicite tags, for example :
...
The tag apache is defined
...

So I'm sure it have been created in the right order, after the class apache.

But my manually declared tag is nowhere to be seen. Does someone have any idea 
what am i doing wrong ?



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

Re: [Puppet Users] Puppet 3.0 rspec and custom resources

2012-11-05 Thread Nathan Huff

So I dug into this a little more.  It has something to do with how puppet 
is loading the type definitions. 
There appears to be some kind of cache that gets loaded with type 
definitions when the first manifest gets processed.
If the first test that gets run is for a class that contains all the types 
necessary for classes that get tested later everything runs fine.
If on the other hand if the first test run is for a class that doesn't 
contain all the types used in later classes the later test fails. 

Given the example I posted
This works correctly.
rspec spec/classes/test_spec.rb spec/classes/test__c_spec.rb
This doesn't
rspec spec/classes/test__c_spec.rb spec/classes/test_spec.rb

Running them both separately works too.

On Monday, October 29, 2012 2:48:25 PM UTC-5, Nathan Huff wrote:

 Looks like the subnamespace thing isn't important either.  Just having two 
 classes triggers this as well.

 On Monday, October 29, 2012 1:13:05 PM UTC-5, Nathan Huff wrote:

 OK so I have what I think is a minimal test case here:

 https://github.com/nhuff/spec-failure

 The readme has a list of gems I have installed in it.

 You seem to need spec tests for two classes, one of which is in a sub 
 namespace of the other.
 In this case 'test' and 'test::c'.  With both spec files in place the 
 system complains about anchor not being defined.
 If you remove the test file for test::c the test for class test will pass.



-- 
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/-/6MSfkla3fzMJ.
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] err: Could not request certificate when I run puppet device

2012-11-05 Thread meiji wang



1.   I get the following error when I run “puppet device’

err: Could not request certificate: Could not write 
/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to 
privatekeydir: Permission denied - 
/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem

Any thought?


Thanks,

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/rcg_UPtqyEsJ.
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: err: Could not request certificate when I run puppet device

Looks like a file permissions error - I had similar when I started playing 
with puppet device... 

Check if the user you're running puppet as has permissions to write to 
'/var/opt/lib/pe-puppet/devices'.

HTH

Gav

On Monday, 5 November 2012 16:18:03 UTC, meiji wang wrote:

 1.   I get the following error when I run “puppet device’

 err: Could not request certificate: Could not write 
 /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to 
 privatekeydir: Permission denied - 
 /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem

 Any thought?


 Thanks,


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/BOdba0ATai4J.
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 NetApp Network device management...

Ok, moving on then...

I've created a 'netapp_volume' type and provider, and am trying to test it
against one of the existing NetApp device nodes:
*manifests/site.pp* contains:

node 'actint-star-nactl01' {

# Test NetApp volume provider
netapp_volume { 'v_puppet_test':
ensure = present,
}

}

When running *'puppet device -v'*, I get:

$ sudo puppet device -v
Info: starting applying configuration to actint-star-nactl01 at
actint-star-nactl01
Warning: Local environment: production doesn't match server specified
node environment development, switching agent to development.
Info: Retrieving plugin
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/type/netapp_volume.rb]/content:

content changed '{md5}2f3e20a3878f9ed94a5fffc4a9811ef7' to
'{md5}ebe14c73783c97063d9b6ae0bc791896'
Error: Could not autoload puppet/provider/netapp_volume/netapp_volume:
uninitialized constant Puppet::Provider::Netapp
Error: Could not autoload puppet/type/netapp_volume: Could not autoload
puppet/provider/netapp_volume/netapp_volume: uninitialized constant
Puppet::Provider::Netapp
Error: Could not retrieve catalog from remote server: Could not intern
from pson: Could not autoload puppet/type/netapp_volume: Could not autoload
puppet/provider/netapp_volume/netapp_volume: uninitialized constant
Puppet::Provider::Netapp
Using cached catalog
Info: Applying configuration version '1352132516'
Error:
/Stage[main]//Node[actint-star-nactl01]/Netapp_volume[v_puppet_test]: Could
not evaluate: No ability to determine if netapp_volume exists
Finished catalog run in 0.21 seconds

So it's failing to autoload my new provider, however I'm not sure what
'uninitialised constant' means :s
The class *Puppet::Provider::Netapp* is defined in *
lib/puppet/provider/netapp.rb*.

I've pushed the latest edits into
Githubhttps://github.com/fatmcgav/fatmcgav-netapp.

Ideas welcome.

Cheers
Gavin

On Monday, 5 November 2012 15:26:08 UTC, Gavin Williams wrote:

Me again...

I pressed on using the /var/lib/puppet... configdir for the time-being,
and with a bit more jiggery pokery, I've managed to successfully register a
NetApp device, and extract some facts from it... And here's the
photographic proof :) :D http://ow.ly/i/15SLN

Now to start looking at how to handle the next steps, such as volume
creation, quota creation, export creation... :D

Latest code has been pushed to
Githubhttps://github.com/fatmcgav/fatmcgav-netapp
...

Still need to work out how to use a central confdir rather than agent
specific ones, but can come back to that :)

Cheers
Gavin

On Monday, 5 November 2012 11:35:26 UTC, Gavin Williams wrote:

Ok, have fixed that error aswell...

ESC[0;36mDebugESC[0m: Puppet::Device::Netapp: connecting to Netapp device
actint-star-nactl01.
ESC[0;36mDebugESC[0m: Puppet::Device::Netapp: configdir is
/var/lib/puppet/devices/actint-star-nactl01.

However I would prefer it to use */etc/puppet* on the master...
Any way I could do this, other than hard-coding?

Cheers
Gavin

On Monday, 5 November 2012 11:24:16 UTC, Gavin Williams wrote:

Ok, after a bit more googling, have solved the NaElement load error...

Tweaked the NaServer.rb file as follows:

#require 'NaElement'
require File.dirname(__FILE__) + /NaElement

I've now successfully loaded the require Netapp SDK files, and started
working through the connection process...
Though it looks like it's hit another error:

Tracked the above back to *device.rb*, where it's attempting to use *
'Puppet[:configdir]'* but is failing to find the value...

So now to work out what's going on there :)

Cheers
Gav

On Monday, 5 November 2012 10:47:56 UTC, Gavin Williams wrote:

Hi all

I'm trying to start simply by just gathering some facts from our
filers.

The code soo far is available here:
https://github.com/fatmcgav/shrug-netapp/ Credit to the original
author shrug for setting out the framework...

Anyhow, onto my first challenge.

I've downloaded and added the relevant NetApp SDK files into *
modules/shrug-netapp/lib/puppet/util/network_device/netapp/* as shown
below:

$ ls -l modules/shrug-netapp/lib/puppet/util/network_device/netapp/
total 88
-rw-r--r--. 1 puppet

Re: [Puppet Users] intercept/pre-process cert request?

2012-11-05 Thread Dean Wilson

On Mon, Oct 29, 2012 at 04:36:44PM -0700, Lou wrote:

Hi Lou,

 I'm assuming this is possible, but I can't find a good starting point 
 anywhere, so I'm hoping someone here can help. What I want to do is, 
 somewhere in the cert approval process, run an extra check before saying 
 yes.

 Is this even possible, and if so, how do I accomplish it? Even pointers to 
 the code that gets executed would help, but I'd really like to avoid 
 mucking with the ca code itself and just add something in the chain. 
 Filtering on domain in autosign.conf is not sufficient.

I've got some sample code to do this (in puppet 2.6) that might be helpful

https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/FR0KCOCIrrE

It's an intrusive change to the code base so it might not be a good fit
but it might give you some hints.

  Dean
-- 
Dean Wilson
http://www.unixdaemon.net   @unixdaemon
http://www.puppetcookbook.com   @puppetcookbook

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

Re: [Puppet Users] Re: puppetdb postgresql Connection refused

On Mon, Nov 05, 2012 at 07:52:02AM -0800, linux@bami wrote:
 Hi,
 
 we solved the problem. removed all files from /etc/puppetdb/ssl and 
 ran /usr/sbin/puppetdb-ssl-setup.
 
 Thanks for the support!!
 
 greetings
 
 Daniel
 

I am glad that you managed to solve it.

Best, Nikola

 Am Montag, 5. November 2012 16:07:43 UTC+1 schrieb nikolavp:
 
  On Mon, Nov 05, 2012 at 05:36:39AM -0800, linux@bami wrote: 
   Hi Nikola, 
   
   yes on the puppet master there ist a routes.yaml 
   
   [root@lx1ml puppet]# cat routes.yaml 
   --- 
   master: 
 facts: 
   terminus: puppetdb 
   cache: yaml 
   
   And the puppet agent -t runs fine on the puppetdb if we remove the 
   storeconfig settings from our master puppet.conf 
   
   Is it possible to increase the jetty log, because we don't the any 
   connection attempts or Connection refused. 
 
  Well on my machine the file is at /etc/puppetdb/log4j.properties. There 
  you can configure the logging level which in my case is INFO and this 
  should 
  be more than enough. Did you check the system log for your environment 
  for problems. For example on my ubuntu machine most of the messages from 
  the master go to /var/log/syslog. 
 
  Where are you looking for the puppetdb and puppet logs 
 
   
   
   greetings 
   
   daniel 
 
  Best, Nikola 
 
   
   
   Am Montag, 5. November 2012 10:40:18 UTC+1 schrieb linux@bami: 

Greetings, 

we are trying to setup puppetdb, nut our clients get the following 
  error: 

Warning: Unable to fetch my node definition, but the agent run will 
continue: 
Warning: Error 400 on SERVER: Could not retrieve facts for 
  lxa7t.unix.lan: 
Failed to submit 'replace facts' command for lxa7t.unix.lan to 
  PuppetDB at 
puppetdb:8081: Connection refused - connect(2) 
Info: Retrieving plugin 
Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryhugepages.rb 
Info: Loading facts in 
  /var/lib/puppet/lib/facter/bstoragemanufacturer.rb 
Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmmax.rb 
Info: Loading facts in /var/lib/puppet/lib/facter/bmemoryshmall.rb 
Error: Could not retrieve catalog from remote server: Error 400 on 
  SERVER: 
Failed to submit 'replace facts' command for lxa7t.unix.lan to 
  PuppetDB at 
puppetdb:8081: Connection refused - connect(2) 
Warning: Not using cache on failed catalog 
Error: Could not retrieve catalog; skipping run 


The puppetdb is remote for the puppetmaster and is using postgresql. 

Direct connect from puppetmaster to the postgresql puppetdb is vaild. 

We don't see any hint in the logfiles. 


R/ Daniel 


   
   -- 
   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/-/OxMm0hZvrTcJ. 
   To post to this group, send email to 
   puppet...@googlegroups.comjavascript:. 
 
   To unsubscribe from this group, send email to 
  puppet-users...@googlegroups.com javascript:. 
   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/-/QuC4XBMIDjoJ.
 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] Re: Puppet NetApp Network device management...

Looks like the below error was caused by some locally cached code that 
hadn't been updated by my Git pull :s

Resolved that, and now am getting the following:

$ sudo puppet device -v
 Info: starting applying configuration to actint-star-nactl01 at 
 actint-star-nactl01
 Warning: Local environment: production doesn't match server specified 
 node environment development, switching agent to development.
 Info: Retrieving plugin
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet]/mode: mode 
 changed '0775' to '0755'
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider]/mode: 
 mode changed '0775' to '0755'
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider/netapp.rb]/content:
  
 content changed '{md5}399796914d8aeb68387455de5b24f735' to 
 '{md5}3be2121ab99116c4bc89db21d5d4b54b'
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider/netapp_volume/netapp_volume.rb]/content:
  
 content changed '{md5}46b2a0004e0245c577974e7a645e08f7' to 
 '{md5}1b06628868826a8ea64744a7ae8ec8da'
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/type]/mode: 
 mode changed '0775' to '0755'
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/type/netapp_volume.rb]/content:
  
 content changed '{md5}ebe14c73783c97063d9b6ae0bc791896' to 
 '{md5}2fb244482c7d760e6cc132f104be619d'
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/util/network_device/netapp/facts.rb]/content:
  
 content changed '{md5}c7e59e79e19486cba9ae7e5314b2a061' to 
 '{md5}b0c912dc663d5251219bbad895455834'
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/util/network_device/netapp/device.rb]/content:
  
 content changed '{md5}7354a748bd41582fcf76bf2643098fcd' to 
 '{md5}9d2e26f97c7ea6ea16177acb8df85714'
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/util/network_device/netapp/NaServer.rb]/content:
  
 content changed '{md5}cd815964f9a2dfe757f5365a848b80d5' to 
 '{md5}63f12abed9d1145b6d326c9fc06eb0c0'
 Info: Caching catalog for actint-star-nactl01
 Info: Applying configuration version '1352132516'
 Error: 
 /Stage[main]//Node[actint-star-nactl01]/Netapp_volume[v_puppet_test]: Could 
 not evaluate: undefined method `transport' for 
 #Puppet::Util::NetworkDevice::Netapp::Device:0x7ff3142c80f8
 Finished catalog run in 0.11 seconds


If I change *provider/netapp_volume/netapp_volume.rb *as follows*:*


 /File[/var/lib/puppet/lib/puppet/provider/netapp_volume/netapp_volume.rb]/content:
 --- /var/lib/puppet/lib/puppet/provider/netapp_volume/netapp_volume.rb  
 2012-11-05 17:26:56.257616498 +
 +++ /tmp/puppet-file20121105-8521-10tepn6-0 2012-11-05 
 17:40:16.440612301 +
 @@ -19,7 +19,7 @@

def exists?
  Puppet.debug(Puppet::Provider::Netapp_volume: checking existance of 
 Netapp Volume #{resource[:name]})
 -transport.invoke(volume-list-info).include?(resource[:name])
 +@transport.invoke(volume-list-info).include?(resource[:name])
end

I get:

  Info: starting applying configuration to actint-star-nactl01 at 
 actint-star-nactl01
 Warning: Local environment: production doesn't match server specified 
 node environment development, switching agent to development.
 Info: Retrieving plugin
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider/netapp_volume/netapp_volume.rb]/content:
  
 content changed '{md5}1b06628868826a8ea64744a7ae8ec8da' to 
 '{md5}feb535835cefd0921c8be5d0af6e11f2'
 Info: Caching catalog for actint-star-nactl01
 Info: Applying configuration version '1352132516'
 Error: 
 /Stage[main]//Node[actint-star-nactl01]/Netapp_volume[v_puppet_test]: Could 
 not evaluate: undefined method `invoke' for nil:NilClass
 Finished catalog run in 0.20 seconds


So not sure why it's not working either way... 

Any ideas???

Cheers
Gavin  
 

On Monday, 5 November 2012 16:44:15 UTC, Gavin Williams wrote:

 Ok, moving on then... 

 I've created a 'netapp_volume' type and provider, and am trying to test it 
 against one of the existing NetApp device nodes:
 *manifests/site.pp* contains:

 node 'actint-star-nactl01' {

 # Test NetApp volume provider
 netapp_volume { 'v_puppet_test':
 ensure = present,
 }

 }


 When running *'puppet device -v'*, I get:

 $ sudo puppet device -v
 Info: starting applying configuration to actint-star-nactl01 at 
 actint-star-nactl01
 Warning: Local environment: production doesn't match server specified 
 node environment development, switching agent to development.
 Info: Retrieving plugin
 /File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/type/netapp_volume.rb]/content:
  
 content changed '{md5}2f3e20a3878f9ed94a5fffc4a9811ef7' to 
 '{md5}ebe14c73783c97063d9b6ae0bc791896'
 Error: Could not autoload puppet/provider/netapp_volume/netapp_volume: 
 uninitialized constant Puppet::Provider::Netapp
 Error: Could not autoload puppet/type/netapp_volume: Could not autoload 
 puppet/provider/netapp_volume/netapp_volume:

Re: [Puppet Users] mco status returns different number of hosts each time I run it

2012-11-05 Thread Bill James

posted reply in mcollective-users group. Sorry for duplicate posts.

On Friday, November 2, 2012 11:34:39 AM UTC-7, R.I. Pienaar wrote:

 - Original Message - 
  From: Bill James billj...@gmail.com javascript: 
  To: puppet...@googlegroups.com javascript: 
  Sent: Friday, November 2, 2012 6:07:00 PM 
  Subject: [Puppet Users] mco status returns different number of hosts 
 each time I run it 

  trying to use mco to run commands on hosts I don't get the full list 
  of hosts. Doing a command like mco puppetd --with-fact domain=
 test.j2noc.com 
  status returns a different number of hosts each time. 

  How do I get it to use the full list? 

 Will need to see some debug logs, when you run this command and you 
 have a node that does not respond in debug logging mode what do you 
 see in the logs. 

 Do you see the same behaviour with 'mco ping' when using the same filter? 

-- 
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/-/3MVFv1Z4nxQJ.
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] shouldn't this be considered a bug?

2012-11-05 Thread Jist Anidiot

So I thought puppet didn't care about the order of things unless 
specifically told.  However I've come across one case where it apparently 
does care.

This works as expected:

node /^univ\d+\.foo\.edu$/ {

$myvar = foo

include module_that_uses_myvar

}


This one doesn't work as expected


node /^univ\d+\.foo\.edu$/ {

include module_that_uses_myvar

$myvar = foo

}

In the 2nd one, module_that_uses_myvar seems to think $myvar is undef or 
null or something that is most certainly not foo If it matters any, 
$myvar is actually used in an erb template that the module has.  Our puppet 
master is 2.7.12 and the client is 2.6.17.

I didn't see any bug reports about this.  Is this a known problem or just 
not considered a bug?

-- 
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_pDE14z0CYJ.
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] shouldn't this be considered a bug?

2012-11-05 Thread Christopher Wood

To the best of my knowledge, it is resources that can be applied in any order, 
not scoped variables.

Your puppet agent will create these files in any order, given that the file 
resources have no require/before dependencies:

node myserver {
  file { '/tmp/1':
content = 123\n,
  }
  file { '/tmp/2':
content = 456\n,
  }
}

But here, no file will contain the string what:

node myserver {
  file { '/tmp/1':
content = ${what}123\n,
  }
  file { '/tmp/2':
content = ${what}456\n,
  }
  $var = 'what'
}

On Mon, Nov 05, 2012 at 12:06:08PM -0800, Jist Anidiot wrote:
So I thought puppet didn't care about the order of things unless
specifically told.  However I've come across one case where it apparently
does care.
 
This works as expected:
 
node /^univ\d+\.foo\.edu$/ {
 
$myvar = foo
 
include module_that_uses_myvar
 
}
 
This one doesn't work as expected
 
node /^univ\d+\.foo\.edu$/ {
 
include module_that_uses_myvar
 
$myvar = foo
 
}
 
In the 2nd one, module_that_uses_myvar seems to think $myvar is undef or
null or something that is most certainly not foo If it matters any,
$myvar is actually used in an erb template that the module has.  Our
puppet master is 2.7.12 and the client is 2.6.17.
 
I didn't see any bug reports about this.  Is this a known problem or just
not considered a bug?
 
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
[1]https://groups.google.com/d/msg/puppet-users/-/Q_pDE14z0CYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
 
 References
 
Visible links
1. https://groups.google.com/d/msg/puppet-users/-/Q_pDE14z0CYJ

-- 
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: Apply multiple defines in sequence

As I'm in over my head, let's supply you with (part of) the manifests in 
question:

The define:

define sugar::definitions_sug_wp (
  $template   = 'sugar/etc/httpd/conf.d/sugar6x.conf.erb',
  $client_domain  = $title,
  $mysql_rootpwd  = $mysql_password,
  $mysql_dbname,
  $mysql_pwd,
  $sugar_admin,
  $sugar_pwd,

) {

# This is for example to create the httpd.conf and the sugar-folder. So 
this has to be in both. As you can see, I parametrized the httpd-conf, so I 
can specify it in my class. Also, the  ${client_domain}-variable is used 
throughout this define.
file {
/etc/httpd/conf.d/sug-${client_domain}.conf:
  content = template($template),
  owner   = 'root',
  group   = 'root',
  mode= '0644',
  notify  = Service['httpd'];
/var/log/sugar/${client_domain}:
  ensure  = 'directory';
   }


# The following is specific to the WordPress-installation and doesn't need 
to be applied to every machine. So this part isn't in the define 'define 
sugar::definitions_sug'.
file {
# Configuratie van publieke html
/var/www/html/${client_domain}:
  owner   = 'apache',
  group   = 'apache',
  mode= '0744',
  ensure  = 'directory';
# Configuratiefile WordPress
/var/www/html/${client_domain}/wp-config.php:
  owner   = 'apache',
  group   = 'apache',
  mode= '0744',
  require = File[/var/www/html/${client_domain}],
  content = template('sugar/wordpress/wp-config.php.erb');

I call both defines ('sugar::definitions_sug_wp' and 'define 
sugar::definitions_sug') in the following class:
class sugar::instances {

sugar::definitions_sug {
# SugarCRM - ECM2
'node1':
  mysql_dbname = 'dbname1',
  mysql_pwd= 'password1';

sugar::definitions_sug_wp {
'node2':
  sugar_admin  = 'text1',
  sugar_pwd= 'password2',
  mysql_dbname = 'dbname2',
  mysql_pwd= 'password3';

I include this class on one node to get several sugar-only vhosts and 
several sugar+wordpress-nodes on that node.

Hope this helps you explain things to me!



On Monday, November 5, 2012 3:41:37 PM UTC+1, jcbollinger wrote:



 On Monday, November 5, 2012 3:48:58 AM UTC-6, Erwin Bogaard wrote:

 Thanks again for you reply, but it seems like you don't fully understand 
 what I'm having problems with. So I'll try to clarify it a little more:
 1. The current way of using two defines is working flawlessly. So I (at 
 least partly) understand the concepts surrounding those.
 2. Because I have two types of machines: some with just sugar and some 
 with sugar and wordpress, I now use two defines that overlap in part 
 (define1 contains all kinds of info about creating sugar db + unpacking 
 tar, etc, while define2 contains all the sugar info of define1 + stuff 
 about creating a wordpress db + unpacking wp tar, etc), this means editing 
 two files when I change something in the sugar define. As this can lead to 
 differing configurations because of editing errors (and always twice the 
 work), I would like to be able to split the defines up, so I can call 
 define1 (sugar) on all machines and define1 (sugar) and sefine 2 
 (wordpress) on the other machines.
 3. Some of the variables are shared, for example the mysqld_pwd is used 
 twice, and I add a different suffix for sugar and wordpress to get two 
 databases. For the httpd-configuration, I specify a different template, 
 which is easy to to with defines. So all instances have unique resources, 
 hence the choice for defines, not classes.

 Does this help you help me?



 No, not really.  You have been relatively clear about what you are trying 
 to accomplish, but I don't understand what is preventing you from 
 accomplishing it.  Perhaps that means you're stumbling over something that 
 seems trivial to me.  For example, if the real question is how to share 
 data between two or more defined types, then you have at least three 
 choices:

1. Define the data in a class, and have each definition reference the 
class variables instead of taking that data in the form of parameters.
2. Externalize the data (e.g. into an Hiera data store), and have each 
definition reference the needed values by the same fixed key.
3. Record the data in global variables, and have each definition 
reference the global values.  (I wouldn't recommend this one except as a 
temporary hack.)

 If that doesn't help then perhaps you should try reducing the problem to 
 the simplest possible example that captures the issue.  Often such an 
 exercise will itself help you work out the problem, but if it doesn't then 
 we can be a lot more helpful to you with actual (simple) manifests to 
 critique.


 John



-- 
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/-/OtbcKBd0GgIJ.
To post to this group,

[Puppet Users] Re: Apply multiple defines in sequence

After my previous post, I did some more thinking and reasearch. What do you 
think about:
- using an if/else-conditional. Would that work?
- using virtual resources? would that work?

On Monday, November 5, 2012 9:17:11 PM UTC+1, Erwin Bogaard wrote:

 As I'm in over my head, let's supply you with (part of) the manifests in 
 question:

 The define:

 define sugar::definitions_sug_wp (
   $template   = 'sugar/etc/httpd/conf.d/sugar6x.conf.erb',
   $client_domain  = $title,
   $mysql_rootpwd  = $mysql_password,
   $mysql_dbname,
   $mysql_pwd,
   $sugar_admin,
   $sugar_pwd,

 ) {

 # This is for example to create the httpd.conf and the sugar-folder. So 
 this has to be in both. As you can see, I parametrized the httpd-conf, so I 
 can specify it in my class. Also, the  ${client_domain}-variable is used 
 throughout this define.
 file {
 /etc/httpd/conf.d/sug-${client_domain}.conf:
   content = template($template),
   owner   = 'root',
   group   = 'root',
   mode= '0644',
   notify  = Service['httpd'];
 /var/log/sugar/${client_domain}:
   ensure  = 'directory';
}


 # The following is specific to the WordPress-installation and doesn't need 
 to be applied to every machine. So this part isn't in the define 'define 
 sugar::definitions_sug'.
 file {
 # Configuratie van publieke html
 /var/www/html/${client_domain}:
   owner   = 'apache',
   group   = 'apache',
   mode= '0744',
   ensure  = 'directory';
 # Configuratiefile WordPress
 /var/www/html/${client_domain}/wp-config.php:
   owner   = 'apache',
   group   = 'apache',
   mode= '0744',
   require = File[/var/www/html/${client_domain}],
   content = template('sugar/wordpress/wp-config.php.erb');

 I call both defines ('sugar::definitions_sug_wp' and 'define 
 sugar::definitions_sug') in the following class:
 class sugar::instances {

 sugar::definitions_sug {
 # SugarCRM - ECM2
 'node1':
   mysql_dbname = 'dbname1',
   mysql_pwd= 'password1';

 sugar::definitions_sug_wp {
 'node2':
   sugar_admin  = 'text1',
   sugar_pwd= 'password2',
   mysql_dbname = 'dbname2',
   mysql_pwd= 'password3';

 I include this class on one node to get several sugar-only vhosts and 
 several sugar+wordpress-nodes on that node.

 Hope this helps you explain things to me!



 On Monday, November 5, 2012 3:41:37 PM UTC+1, jcbollinger wrote:



 On Monday, November 5, 2012 3:48:58 AM UTC-6, Erwin Bogaard wrote:

 Thanks again for you reply, but it seems like you don't fully understand 
 what I'm having problems with. So I'll try to clarify it a little more:
 1. The current way of using two defines is working flawlessly. So I (at 
 least partly) understand the concepts surrounding those.
 2. Because I have two types of machines: some with just sugar and some 
 with sugar and wordpress, I now use two defines that overlap in part 
 (define1 contains all kinds of info about creating sugar db + unpacking 
 tar, etc, while define2 contains all the sugar info of define1 + stuff 
 about creating a wordpress db + unpacking wp tar, etc), this means editing 
 two files when I change something in the sugar define. As this can lead to 
 differing configurations because of editing errors (and always twice the 
 work), I would like to be able to split the defines up, so I can call 
 define1 (sugar) on all machines and define1 (sugar) and sefine 2 
 (wordpress) on the other machines.
 3. Some of the variables are shared, for example the mysqld_pwd is used 
 twice, and I add a different suffix for sugar and wordpress to get two 
 databases. For the httpd-configuration, I specify a different template, 
 which is easy to to with defines. So all instances have unique resources, 
 hence the choice for defines, not classes.

 Does this help you help me?



 No, not really.  You have been relatively clear about what you are trying 
 to accomplish, but I don't understand what is preventing you from 
 accomplishing it.  Perhaps that means you're stumbling over something that 
 seems trivial to me.  For example, if the real question is how to share 
 data between two or more defined types, then you have at least three 
 choices:

1. Define the data in a class, and have each definition reference the 
class variables instead of taking that data in the form of parameters.
2. Externalize the data (e.g. into an Hiera data store), and have 
each definition reference the needed values by the same fixed key.
3. Record the data in global variables, and have each definition 
reference the global values.  (I wouldn't recommend this one except as a 
temporary hack.)

 If that doesn't help then perhaps you should try reducing the problem to 
 the simplest possible example that captures the issue.  Often such an 
 exercise will itself help you work out the problem, but if it doesn't then 
 we

Re: [Puppet Users] Re: Apply multiple defines in sequence

2012-11-05 Thread Tim Mooney


In regard to: [Puppet Users] Re: Apply multiple defines in sequence, Erwin...:


Thanks again for you reply, but it seems like you don't fully understand
what I'm having problems with. So I'll try to clarify it a little more:
1. The current way of using two defines is working flawlessly. So I (at
least partly) understand the concepts surrounding those.
2. Because I have two types of machines: some with just sugar and some with
sugar and wordpress, I now use two defines that overlap in part (define1
contains all kinds of info about creating sugar db + unpacking tar, etc,
while define2 contains all the sugar info of define1 + stuff about creating
a wordpress db + unpacking wp tar, etc), this means editing two files when
I change something in the sugar define.


So have one additional parameter to your define,

sugar_with_wordpress = 'no'

and then in the body of your define, after you've done all the necessary
setup for sugar, that is always present, have

  if $sugar_with_wordpress == 'yes' {
 # wordpress-specific stuff here
  }

I use yes/no strings instead of boolean true/false because you'll
eventually want to have those settings come from hiera, and as things
currently stand booleans from hiera are just a trap for the unwary.

I would actually do the wordpress stuff as a separate class, which has
its own wordpress::instance define, and then call that define from within
your sugar::instance define.

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing  Infrastructure  701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
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: shouldn't this be considered a bug?



On Monday, November 5, 2012 2:06:09 PM UTC-6, Jist Anidiot wrote:

 So I thought puppet didn't care about the order of things unless 
 specifically told.  However I've come across one case where it apparently 
 does care.



You had a serious misunderstanding.  Puppet has numerous sensitivities to 
the order in which it parses declarations in your manifests.  You were 
probably thinking about how Puppet does not promise to apply resources in 
any particular order unless you tell it otherwise by declaring 
relationships, but there it's *you* who may not care, not Puppet.

 


 This works as expected:

 node /^univ\d+\.foo\.edu$/ {

 $myvar = foo

 include module_that_uses_myvar

 }


 This one doesn't work as expected


 node /^univ\d+\.foo\.edu$/ {

 include module_that_uses_myvar

 $myvar = foo

 }

 In the 2nd one, module_that_uses_myvar seems to think $myvar is undef or 
 null or something that is most certainly not foo If it matters any, 
 $myvar is actually used in an erb template that the module has.  Our puppet 
 master is 2.7.12 and the client is 2.6.17.

 I didn't see any bug reports about this.  Is this a known problem or just 
 not considered a bug?



It is not considered a bug.  It is the manifest author's responsibility to 
ensure that any reference to a class, resource, or variable is preceded by 
a declaration of that entity in Puppet's parse order.

Use of dynamically-scoped variables is considered poor practice, however, 
including any use of node-scoped variables outside their node blocks.  Your 
v. 2.7 master ought to be emitting warnings about that.


John

-- 
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/-/28RuMye2nc8J.
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: err: Could not request certificate when I run puppet device

2012-11-05 Thread meiji wang

Although I change the mode to 0777, Puppet forces the mode to 0750

debug: /File[/var/opt/lib/pe-puppet/devices/certname/state]: Autorequiring 
File[/var/opt/lib/pe-puppet/devices/certname]
debug: /File[/var/opt/lib/pe-puppet/devices/certname/clientbucket]/mode: 
mode changed '0777' to '0750'
debug: /File[/var/opt/lib/pe-puppet/devices/certname/ssl]/mode: mode 
changed '0777' to '0771'
debug: /File[/var/opt/lib/pe-puppet/devices/certname/ssl/private]/mode: 
mode changed '0777' to '0750'
debug: /File[/var/opt/lib/pe-puppet/devices/certname/state]/mode: mode 
changed '0777' to '1755'
debug: 
/File[/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys]/mode: mode 
changed '0777' to '0750'
debug: /File[/var/opt/lib/pe-puppet/devices/certname/client_yaml]/mode: 
mode changed '0777' to '0750'
debug: /File[/var/opt/lib/pe-puppet/devices/certname/client_data]/mode: 
mode changed '0777' to '0750'
info: Creating a new SSL key for certname
..
err: Could not request certificate: Could not write 
/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to 
privatekeydir: Permission denied - 
/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem


then Puppet throws error message..

Meiji


On Monday, November 5, 2012 8:18:03 AM UTC-8, meiji wang wrote:

 1.   I get the following error when I run “puppet device’

 err: Could not request certificate: Could not write 
 /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to 
 privatekeydir: Permission denied - 
 /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem

 Any thought?


 Thanks,


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/CEDQ4q9o5uEJ.
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] Run Exec without notifying Puppet as a change

2012-11-05 Thread Thomas Biddle

I just switched from an in-house APT module to the Puppetlabs one thinking 
that it may solve this, but after looking at the code (And installing to 
confirm) it did not.

Seeing Puppet be notified of a change just when `apt-get update` is run 
is a bit annoying to me. I was wondering if there was a way to avoid 
notifying Puppet of a change when an Exec command is run? (Or if there's 
another way we can run this)

TJ

-- 
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/-/fN1guXxULUMJ.
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: err: Could not request certificate when I run puppet device

2012-11-05 Thread fatmcgav

Try changing the file owner/group to match what you're running puppet as...

Gav

On 5 November 2012 20:51, meiji wang wangme...@gmail.com wrote:

 Although I change the mode to 0777, Puppet forces the mode to 0750

 debug: /File[/var/opt/lib/pe-puppet/devices/certname/state]: Autorequiring
 File[/var/opt/lib/pe-puppet/devices/certname]
 debug: /File[/var/opt/lib/pe-puppet/devices/certname/clientbucket]/mode:
 mode changed '0777' to '0750'
 debug: /File[/var/opt/lib/pe-puppet/devices/certname/ssl]/mode: mode
 changed '0777' to '0771'
 debug: /File[/var/opt/lib/pe-puppet/devices/certname/ssl/private]/mode:
 mode changed '0777' to '0750'
 debug: /File[/var/opt/lib/pe-puppet/devices/certname/state]/mode: mode
 changed '0777' to '1755'
 debug:
 /File[/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys]/mode: mode
 changed '0777' to '0750'
 debug: /File[/var/opt/lib/pe-puppet/devices/certname/client_yaml]/mode:
 mode changed '0777' to '0750'
 debug: /File[/var/opt/lib/pe-puppet/devices/certname/client_data]/mode:
 mode changed '0777' to '0750'
 info: Creating a new SSL key for certname
 ..
 err: Could not request certificate: Could not write
 /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to
 privatekeydir: Permission denied -
 /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem


 then Puppet throws error message..

 Meiji


 On Monday, November 5, 2012 8:18:03 AM UTC-8, meiji wang wrote:

 1.   I get the following error when I run “puppet device’

 err: Could not request certificate: Could not write
 /var/opt/lib/pe-puppet/**devices/certname/ssl/private_**keys/certname.pem
 to privatekeydir: Permission denied - /var/opt/lib/pe-puppet/**
 devices/certname/ssl/private_**keys/certname.pem

 Any thought?


 Thanks,

  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/puppet-users/-/CEDQ4q9o5uEJ.
 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] Re: Apply multiple defines in sequence



On Monday, November 5, 2012 2:17:11 PM UTC-6, Erwin Bogaard wrote:

 As I'm in over my head, let's supply you with (part of) the manifests in 
 question:

 The define:

 define sugar::definitions_sug_wp (
   $template   = 'sugar/etc/httpd/conf.d/sugar6x.conf.erb',
   $client_domain  = $title,
   $mysql_rootpwd  = $mysql_password,
   $mysql_dbname,
   $mysql_pwd,
   $sugar_admin,
   $sugar_pwd,

 ) {

 # This is for example to create the httpd.conf and the sugar-folder. So 
 this has to be in both. As you can see, I parametrized the httpd-conf, so I 
 can specify it in my class. Also, the  ${client_domain}-variable is used 
 throughout this define.
 file {
 /etc/httpd/conf.d/sug-${client_domain}.conf:
   content = template($template),
   owner   = 'root',
   group   = 'root',
   mode= '0644',
   notify  = Service['httpd'];
 /var/log/sugar/${client_domain}:
   ensure  = 'directory';
}


 # The following is specific to the WordPress-installation and doesn't need 
 to be applied to every machine. So this part isn't in the define 'define 
 sugar::definitions_sug'.
 file {
 # Configuratie van publieke html
 /var/www/html/${client_domain}:
   owner   = 'apache',
   group   = 'apache',
   mode= '0744',
   ensure  = 'directory';
 # Configuratiefile WordPress
 /var/www/html/${client_domain}/wp-config.php:
   owner   = 'apache',
   group   = 'apache',
   mode= '0744',
   require = File[/var/www/html/${client_domain}],
   content = template('sugar/wordpress/wp-config.php.erb');

 I call both defines ('sugar::definitions_sug_wp' and 'define 
 sugar::definitions_sug') in the following class:
 class sugar::instances {

 sugar::definitions_sug {
 # SugarCRM - ECM2
 'node1':
   mysql_dbname = 'dbname1',
   mysql_pwd= 'password1';

 sugar::definitions_sug_wp {
 'node2':
   sugar_admin  = 'text1',
   sugar_pwd= 'password2',
   mysql_dbname = 'dbname2',
   mysql_pwd= 'password3';

 I include this class on one node to get several sugar-only vhosts and 
 several sugar+wordpress-nodes on that node.

 Hope this helps you explain things to me!



You're still making me guess about what the actual problem is.  Have you 
actually tried anything, or is this all hypothetical?  If you tried and 
failed, then what error messages were produced?

Bits and pieces of your manifests are not particularly helpful.  I'm 
looking for something manageable that provides a complete example of the 
problem.  Ideally something as stripped-down as possible.  If you are 
totally new to Puppet then you might consider playing with a simplified 
model before moving on to a full-blown solution.

My best guess at this point is that the problem -- if there is one -- 
concerns resources that both your definitions declare, such that you get 
duplicate resource declarations if you try to instantiate some combinations 
of those definitions.  I suggested such a problem a couple of posts ago, 
however, and you more or less ignored it.

If duplicate resource declarations are indeed the problem then the solution 
is simple: don't do that!  Every managed resource should have exactly one 
owner -- generally either a class or defined-type instance.  Resources 
should be declared only by their owners.  If you stick to that -- 
remembering that defined-type instances are themselves resources -- then 
you will not have problems with duplicate resource declarations.

So, what obstacles must you overcome to (re-)structure your manifests so 
that each resource has exactly one owner?  (Not a rhetorical question.)  
Virtual resources and conditionals are some of the tools at your disposal 
for overcoming such obstacles, but it's all about how you use them.  In 
particular, just making a declaration virtual does not inherently prevent 
duplicate declaration issues.

Tim's suggestion of combining the definitions and using a parameter to 
direct whether to include WordPress components would be one possible 
solution.  There are several others.  Which would be best depends on the 
details of the problem.


John

-- 
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/-/XGFuEULdHvcJ.
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: Apply multiple defines in sequence