[Puppet Users] Re: Problems with wdijkerman/zabbix module
On Wed, 20 May 2015 15:06:57 +0200
Arnau Bria wrote:
Hello,
me again with answer to both problems :-)
> Now I've been modifying its conf in hiera :
>
> zabbix::zabbix_url: 'zabbix.linux.crg.es'
> zabbix::zabbix_version: '2.2'
> zabbix::manage_repo: 'false'
>
> But seems that the module is ignoring those parameters.
> I've to modify them in zabbix::params .
https://github.com/dj-wasabi/puppet-zabbix/pull/88
> then I have a second question. If I use postgres DDBB, the run fails
> with the error:
>
[...]
>
> where are those pgsql files? I dont' have any pgsql file in my system.
# Allow to customize the path to the Database Schema,
if ! $database_schema_path {
case $::operatingsystem {
'centos','redhat','oraclelinux' : {
$schema_path =
"/usr/share/doc/zabbix-*-pgsql-${zabbix_version}*/create" }
default : {
$schema_path = '/usr/share/zabbix-*-pgsql'
}
}
I'm runnnig Scientifi Linux which is not listed in the above case
statement.
Sorry for the noise,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/20150520152639.68a01401%40eidolon.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Problems with wdijkerman/zabbix module
Dear all, I've installed wdijkerman/zabbix module in puppet server. Now I've been modifying its conf in hiera : zabbix::zabbix_url: 'zabbix.linux.crg.es' zabbix::zabbix_version: '2.2' zabbix::manage_repo: 'false' But seems that the module is ignoring those parameters. I've to modify them in zabbix::params . So, anyone how is using this module has seen the same problem? then I have a second question. If I use postgres DDBB, the run fails with the error: Notice: /Stage[main]/Zabbix::Database::Postgresql/Exec[zabbix_server_create.sql]/returns: /bin/sh: line 0: cd: /usr/share/zabbix-*-pgsql: No such file or directory Error: cd /usr/share/zabbix-*-pgsql && psql -h 'localhost' -U 'zabbix_server' -d 'zabbix_server' -f schema.sql && touch /etc/zabbix/.schema.done returned 1 instead of one of [ 0] Error: /Stage[main]/Zabbix::Database::Postgresql/Exec[zabbix_server_create.sql]/returns: change from notrun to 0 failed: cd /usr/share/zabbix-*-pgsql && psql -h 'localhost' -U 'zabbix_server' -d 'zabbix_server' -f schema.sql && touch /etc/zabbix/.schema.done returned 1 instead of one of [0] Notice: /Stage[main]/Zabbix::Database::Postgresql/Exec[zabbix_server_images.sql]: Dependency Exec[zabbix_server_create.sql] has failures: true where are those pgsql files? I dont' have any pgsql file in my system. TIA, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20150520150657.54299e31%40eidolon. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: puppet link and automount
On Thu, 23 Apr 2015 16:02:19 +0200 Julien Pivotto wrote: > On Thu, Apr 23, 2015 at 06:53:27AM -0700, jcbollinger wrote: > > > > > > On Thursday, April 23, 2015 at 5:44:37 AM UTC-5, Arnau wrote: > > > > > > Hello all, > > > > > > we had some NFS mounts in /nfs/mount1. Then we created a link > > > from /nfs/mount1 to /mount1. Both resources were defined using > > > puppet (mount and file). As the mounts were defined in fstab, the > > > file resource was applied every time with no problem (it ensured > > > that the link was created). > > > > > > Now we have moved from fstab mounts to automount, and now the > > > file resource that creates the link triggers an automatic mount > > > everytime puppet runs (not desired). > > > > > > A part from creating those links in an exec, anyone has a better > > > idea on how to manage this somehow more elegant? > > > > > > > > > > Puppet needs to gather information about the managed file (symlink) > > on every run. I don't see why this would need to involve the link > > *target* being stat()ed, but if it does, and if the target path is > > on an autofs file system, then that will trigger a mount. > > Maybe replace => no might help as well. Thanks to both. I'm going to give it a try. Cheers, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20150427110703.67b3391e%40eidolon. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] puppet link and automount
Hello all, we had some NFS mounts in /nfs/mount1. Then we created a link from /nfs/mount1 to /mount1. Both resources were defined using puppet (mount and file). As the mounts were defined in fstab, the file resource was applied every time with no problem (it ensured that the link was created). Now we have moved from fstab mounts to automount, and now the file resource that creates the link triggers an automatic mount everytime puppet runs (not desired). A part from creating those links in an exec, anyone has a better idea on how to manage this somehow more elegant? TIA, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20150423124413.6693185d%40eidolon. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] mysql module v 1.0 mysql_grant - database_grant
Hi,
I'm using mysql module version 0.6.1 and I wanted to upgrade. After
reading a little I saw that migrating from v 1 to 2 must be studied, so
I decided to upgrde to version 1.
BUT, I've seen a couple of warnings on my first run and I'm updating my
code, but I've found that my old sysntax for database_grant is not
compatible with mysql_grant.
So, if I had something like:
mysql_database{ [ 'biosql' , 'biosql-test' ] :
ensure => present,
require => Class['mysql::server'],
}
database_user { 'biocore@%.X' :
password_hash => mysql_password('X') ;
}
database_grant { [ 'biocore@%.XX/biosql' ,
'biocore@%./biosql-test' ] :
privileges => ['all'] ;
}
now I must write soemthing like:
mysql_grant { 'biocore' :
user=> 'biocore@%.X',
table => 'biosql.*',
privileges => ['all'];
}
So, for each user/DB pair, now I must specify much more info. ( I have
hundrets of DDBBs)...
I've been reading the type code but I do not understand if I can still
use some simpler syntax as before...
Anyone using the module knows how to write it?
Cheers,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/20131209133410.6a41c7ee%40eidolon.linux.crg.es.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: ssh_keys created every puppet run
Hi, the key is not the problem (i copy it into 3 users' home and only one complained). What's special about thta one user? it's home. it's nfs and had file permission problems. Solved. Thanks a lot! Cheers, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] ssh_keys created every puppet run
Hi,
I haveA class with several ssh_key resources:
class web_cluster::ssh_keys( $ensure='present') {
if ! ($ensure in [ "present", "absent" ]) {
fail("cluster ensure parameter must be absent or present")
}
# Set local variables based on the desired state
if ($ensure == "present") {
$service_enable = true
$service_ensure = running
$package_ensure = latest
$file_ensure= file
$user_ensure= present
}elsif ($ensure == "absent") {
$service_enable = false
$service_ensure = stopped
$package_ensure = absent
$file_ensure= absent
$user_ensure= absent
}
Ssh_authorized_key {
type=> 'ssh-rsa',
}
ssh_authorized_key {
[...]
'user@key_3':
ensure => $hostname ? {
/host/=> $user_ensure,
default => absent,
},
user=> 'www-bi',
key => 'XXXx1zKQ==';
}
and every time I run puppet it says:
notice:
/Stage[main]/Web_cluster::Ssh_keys/Ssh_authorized_key[user@key_3]/ensure:
created
notice: Finished catalog run in 15.78 seconds
but I only have a key there:
$ cat .ssh/authorized_keys
# HEADER: This file was autogenerated at Tue Apr 23 11:27:37 +0200 2013
# HEADER: by puppet. While it can still be managed manually, it
# HEADER: is definitely not recommended.
ssh-rsa user@key_3
Running it with debug:
notice:
/Stage[main]/Web_cluster::Ssh_keys/Ssh_authorized_key[user@key_3]/ensure:
created
debug: Flushing ssh_authorized_key provider target
/data/www-bi/.ssh/authorized_keys
debug: /Stage[main]/Web_cluster::Ssh_keys/Ssh_authorized_key[user@key_3]: The
container Class[Web_cluster::Ssh_keys] will propagate my refresh event
I cannot figure out why puppet is pushing the key everytime it runs.
I happens with other keys in other servers.
Could it be becuase of some strange charactes in the key?
# rpm -qa|grep puppet
puppet-2.7.21-1.el6.noarch
TIA,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet MySQL Module
On Tue, 5 Mar 2013 10:48:16 +0200 Nikola Petrov wrote: > You can use the database_grant resource type. Here is an example: But how may I set its password? (it's working cause my user was correctly created and I set its passwd before). *Sorry, I did reply too early.. Cheers, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet MySQL Module
On Tue, 5 Mar 2013 10:48:16 +0200
Nikola Petrov wrote:
Hi Nikola,
> You can use the database_grant resource type. Here is an example:
>
> database_grant { "${user}@${::hostname}/${db}":
> privileges => ['select'], # anything you want
> require=> Database_user["${user}@${::hostname}"],
> }
>
> set the $user and $db variables to what you want ;)
>
> More information can be found on the github README file for module.
thanks alot, I already had one database_grant but I've realized that I
had a typo in the dtaabses (well, I was refering to antoher...
galaxytest, for that reason it was not working.
thanks a lot,
Cheers,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet MySQL Module
Hi all,
I'm using the MySQL module
https://forge.puppetlabs.com/puppetlabs/mysql and I can't find the way
to give certain permission to a secondary user over an already created
DB (which has it own user):
mysql::db { 'galaxy':
user => 'galaxy',
password => 'XX',
host => 'localhost',
grant=> ['all'],
}
Now I would like to give select privileges on galaxy DB to user arnau,
but I can't find the way for doing so.
Could someone give a hand?
TIA,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] managing java with puppet (RH)
On Tue, 20 Nov 2012 14:13:01 +0100 Johan De Wit wrote: > Hi, Hi, > I' ve attached my java module. thanks! > We needed to install multiple java versions on the same hosts, so, i > repackaged them to make that possible. That's why i use the > alternatives to set a default system wide java version. I also > added a spec file as example. > > This version is made to run on sles11spX. I'm now making the deb > packages for the custom java version. > > I hope this will put you on the right track for a possible solution. yes, I took some ideas from your code. > Any comments are welcome. > Grts > > johan Many thanks for your help, Cheers, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] managing java with puppet (RH)
Hi all, In my systems (SL 6.3, RH like) I'm installing Oracle's Java. I'm managing the package and several links under /etc/alternatives with puppet, but for configuring it, all the 'official' docs recommends 'alternatives'. I've been looking for some module which already deals with it, but I've not found any... anyone knows any module with deals with alternatives? TIA, Arnau -- 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: Compile catalog time: 2.6 vs 2.7.X
On Tue, 8 May 2012 13:07:04 +0200 Arnau Bria wrote: I should add more info on servers and "manifests": > 1.-) Centos 5.8 puppet-2.6.14-1.el5 + rubygem-mongrel-1.0.1-6.el5 > > Client: > Compiled catalog for td055.pic.es in environment production in 4.25 > seconds Server: > time puppet master --verbose --compile td055.pic.es > [...] > real 0m14.891s > user 0m11.263s > sys 0m1.793s > > puppet master --verbose --compile td055.pic.es|wc -l > 22930 4 x Intel(R) Xeon(R) CPU5160 @ 3.00GHz & 8GB of RAM > 2.-) SL 6.1 puppet-2.7.11-2.el6.noarch + passenger-3.0.11 > > Client: > Compiled catalog for td055.pic.es in environment production in 76.99 > seconds Server: > time puppet master --verbose --compile td055.pic.es > [...] > real 1m10.661s > user 1m5.739s > sys 0m4.903s > puppet master --verbose --compile td055.pic.es|wc -l > 22933 4 x Intel(R) Xeon(R) CPU5160 @ 3.00GHz & 8GB of RAM > 3.-) SL 6.1 puppet-2.7.14-1.el6.noarch + passenger-3.0.12 > > Client: > err: Could not retrieve catalog from remote server: execution expired > Server: > real 2m13.377s > user 2m7.615s > sys 0m5.728s > > puppet master --verbose --compile td055.pic.es|wc -l > 23008 8 x Quad-Core AMD Opteron(tm) Processor 2356 & 16 GB of RAM My code has about 40 classes. I do use Stages (not a lot, for few repos) and I have many interclass dependecy (Service require file which require package). Puppet is installed via yum using puppetlabs repo. First server is shared by ~600 hosts, second one shared by ~200 nodes and last one is only used by this test node. I don't know If I could more info... I'm quiete lost. Cheers, Arnau -- 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] 12% of my puppet clients -- Could not retrieve catalog from remote server: execution expired
On Tue, 8 May 2012 05:35:34 -0700 (PDT) Tim Lank wrote: > how do I troubleshoot this error that occurs for about 12% of the > puppet clients (~70 out of ~550.) do they run as daemon? always the 70 same hosts are failling? do they run at same time? Cheers, Arnau -- 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] Compile catalog time: 2.6 vs 2.7.X
Hi all, I'm in the procedure of migrating my old puppet server (puppet-2.6.14-1.el5) with mongrel to a new one (puppet-2.7.14-1.el6.noarch) with passenger. I'm facing a really strange behaviour with the catalog compilation time. I've 3 servers: 1.-) Centos 5.8 puppet-2.6.14-1.el5 + rubygem-mongrel-1.0.1-6.el5 Client: Compiled catalog for td055.pic.es in environment production in 4.25 seconds Server: time puppet master --verbose --compile td055.pic.es [...] real0m14.891s user0m11.263s sys 0m1.793s puppet master --verbose --compile td055.pic.es|wc -l 22930 2.-) SL 6.1 puppet-2.7.11-2.el6.noarch + passenger-3.0.11 Client: Compiled catalog for td055.pic.es in environment production in 76.99 seconds Server: time puppet master --verbose --compile td055.pic.es [...] real1m10.661s user1m5.739s sys 0m4.903s puppet master --verbose --compile td055.pic.es|wc -l 22933 3.-) SL 6.1 puppet-2.7.14-1.el6.noarch + passenger-3.0.12 Client: err: Could not retrieve catalog from remote server: execution expired Server: real2m13.377s user2m7.615s sys 0m5.728s puppet master --verbose --compile td055.pic.es|wc -l 23008 * Obviously I'm trying to compile the same code in all cases ** I've only 8 warnings about dyanmic lookup. As you can see, in last version it gets a timeout because it takes too long to compile. So, at this point, I'm wondering what could be causing this behaviour. Why my code is being compiled fast in 2.6 but not in 2.7? What language programing considerations do I have to take into account when migrating? TIA, Arnau -- 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-dashboard running on puppet-server (SL6)
On Tue, 13 Mar 2012 10:20:37 -0400 Peter Bukowinski wrote: Hi Peter, > This is documented here: > http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#starting-and-managing-delayed-job-workers Thanks a lot, I can't figure out how I did not see that part of the doc. Cheers, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] puppet-dashboard running on puppet-server (SL6)
Hi all,
I've installed a new puppet-server and I wanted to add
puppet-dash-board for reports (only).
# rpm -qa|grep puppet|sort
puppet-2.7.11-2.el6.noarch
puppet-dashboard-1.2.6-1.el6.noarch
puppet-server-2.7.11-2.el6.noarch
So, I've followed
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
+
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#configuring-puppet
but I don't see any report in my dash-board.
Logs periodically show:
Processing ReportsController#upload (for X.Y.Z.W at 2012-03-13 14:38:09) [POST]
Parameters: {"controller"=>"reports", "action"=>"upload"}
Completed in 104ms (View: 0, DB: 100) | 200 OK
[http://puppet-server-alias.domain.com/reports/upload]
and dashboard shows:
456 pending tasks.
My database.tml looks like:
production:
database: dashboard
username: X
password: Y
encoding: utf8
adapter: mysql
Mysql databases has the correct tables;
mysql> show tables
-> ;
+--+
| Tables_in_dashboard |
+--+
| delayed_job_failures |
| delayed_jobs |
[...]
| timeline_events |
+--+
18 rows in set (0.00 sec)
Puppet.conf at master:
[master]
[...]
reports = http, store
reporturl = http://puppet-server-alias.domain.com:3000/reports/upload
and clients have reports enabled (but they run puppet 2.6.X).
I can see reports in the master:
# ls -lsa /var/lib/puppet/reports/
Display all 101 possibilities? (y or n)
Could someone help me to find what I'm missing in this conf?
TIA,
Arnau
--
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] Doc about RH6 + Passenger
On Tue, 28 Feb 2012 09:02:09 -0500 Eric Lake wrote: > If I remember right I used a combination of mostly > http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger and a > little of > http://www.uncompiled.com/centos-6-puppet-27-mcollective-foreman-rabbitto > get my install working on CentOS 6. Thanks! I'll take a look. Cheers, Arnau -- 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] Doc about RH6 + Passenger
Hi all, I'm installing a new puppet server and I'd like to move from mongrel to passenger. So, I'm looking for official doc abou passenger and found: http://docs.puppetlabs.com/guides/passenger.html the doc does not talk about RH6 nor 2.7.* ... Anyone has configured his server with the above doc? any other official doc with same subject? TIA, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] custom facts loaded twice
Hi all, Every time I run puppet manually I see the message: # puppetd --test --server $SERVER info: Retrieving plugin info: Loading facts in hwtype info: Loading facts in odd_ip info: Loading facts in default_gateway info: Loading facts in hwtype info: Loading facts in odd_ip info: Loading facts in default_gateway info: Caching catalog for XX As you can see facts are loaded twice. Everything works fine, but I'm wondering if this is normal or we have some missconfiguration. Honestly, I don't know what conf provide apart from client's puppet conf file: [main] # Where Puppet stores dynamic and growing data. # The default value is '/var/puppet'. vardir = /var/lib/puppet # The Puppet log directory. # The default value is '$vardir/log'. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is '$vardir/run'. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is '$confdir/ssl'. ssldir = $vardir/ssl pluginsync = true [agent] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is '$confdir/classes.txt'. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is '$confdir/localconfig'. localconfig = $vardir/localconfig report = false Cheers, Arnau -- 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] Templates + Parameterised classes
On Mon, 28 Nov 2011 16:20:13 +0200 Graham Leggett wrote: > Hi all, Hi, [...] > I am trying to embed the parameter name using <% parameter_name %> maybe: <%= parameter %> [...] > Regards, > Graham HTH, Arnau -- 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] declare and include classes
Hi all, after moving to parametrized classes, I've started to declare them instead of including. Now, I'm trying to understand the differences (internal) between declare and include, and, reading http://docs.puppetlabs.com/guides/parameterized_classes.html again, I found some sentence which confuses me: "Since include wasn’t designed for use with parameterized classes" I know you can't include a resource, so a class eith parameters must be declared. But, If I don't use params, I can include the class... so, what are the big differnces between declare and include? TIA, Arnau -- 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] Multiple nodes.pp files
On Wed, 16 Nov 2011 15:32:41 +0100 Hugo Deprez wrote: > Dear community, Hi Hugo, > I would like to know if it is possible to use different files for the > nodes.pp > > Can we use in nodes.pp the following syntax : > > include nodes2.pp we have several node files but use import. [...] > Thank you. > > hugo HTH, Arnau -- 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] yumrepo absent not working on 2.6.12
Ok, thnaks a lot. Cheers, Arnau -- 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: yumrepo absent not working on 2.6.12
On Tue, 15 Nov 2011 10:06:43 -0500 Nan Liu wrote: [...] > A quick glance at the type shows you need to set 1 or 0, absent means > the property should not exist rather than puppet should configure the > value to 0. Ok. I understood that absent removes the file. My fault. any way for removing the repo without using a file type? Many thanks for your reply Nan, Arnau -- 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: yumrepo absent not working on 2.6.12
Sorry, forgot to mention that if we set 0 instead of absent, the parameter works: notice: /Stage[pre]/Common::Os::Release5::Sl55::Repos/Yumrepo[sl-5.5-base]/enabled: enabled changed '' to '0' Cheers, Arnau -- 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] yumrepo absent not working on 2.6.12
Hi all, Seems that ensure => absent is not working on puppet 2.6.12 yumrepo type. 'sl-5.5-base' : baseurl => 'http://reposerver/computing-SL-55-base-x86_64/RPMS.base/', descr => 'SL 5.5 base', enabled => absent, exclude => 'yum-conf* c-ares'; # ls -lsa /etc/yum.repos.d/sl-5.5-base.repo 4 -rw-r--r-- 1 root root 187 Nov 15 15:35 /etc/yum.repos.d/sl-5.5-base.repo #puppetd --test --server $server [...] info: create new repo sl-5.5-base in file /etc/yum.repos.d/sl-5.5-base.repo notice: /Stage[pre]/Common::Os::Release5::Sl55::Repos/Yumrepo[sl-5.5-base]/descr: descr changed '' to 'SL 5.5 base' notice: /Stage[pre]/Common::Os::Release5::Sl55::Repos/Yumrepo[sl-5.5-base]/baseurl: baseurl changed '' to 'http://reposerver/computing-SL-55-base-x86_64/RPMS.bas e/' notice: /Stage[pre]/Common::Os::Release5::Sl55::Repos/Yumrepo[sl-5.5-base]/gpgcheck: gpgcheck changed '' to '0' notice: /Stage[pre]/Common::Os::Release5::Sl55::Repos/Yumrepo[sl-5.5-base]/exclude: exclude changed '' to 'yum-conf* c-ares' notice: /Stage[pre]/Common::Os::Release5::Sl55::Repos/Yumrepo[sl-5.5-base]/enablegroups: enablegroups changed '' to '1' notice: /Stage[pre]/Common::Os::Release5::Sl55::Repos/Yumrepo[sl-5.5-base]/metadata_expire: metadata_expire changed '' to '43200' info: changing mode of /etc/yum.repos.d/sl-5.5-base.repo from 600 to 644 info: create new repo sl-5.5-fastbugs in file /etc/yum.repos.d/sl-5.5-fastbugs.repo [...] notice that "enabled" parameter is ignored I've been looking at list and bug and only found something nearly related: http://projects.puppetlabs.com/issues/9410 but it's not my problem. Is this a know problem/bug? TIA, Arnau -- 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] problems with concat
On Wed, 02 Nov 2011 11:22:05 - (GMT)
R.I.Pienaar R.I.Pienaar wrote:
> you're missing the concat{"/etc/sudoers": }
>
> # set up a file for being managed by snippets
> concat{"somefile": }
>
> # add a snippet to it:
> concat::fragment{"foo":.}
>
> needs both
solved.
Thanks !
Arnau
--
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] problems with concat
Hi all,
I've downloaded and installed puppet-concat module and was trying to
use it.
After reading doc, I've set concatdir to /tmp only for test purpose,
but I'm wondering what is a good value for concatdir.
Maybe /var/lib/puppet/concat? I guess I have to create it, am I right?
So, following the example at github, I've created some code like:
class common::sudo {
include concat::setup
concat::fragment{'test_2' :
target => '/etc/sudoers' ,
content => "test";
}
}
And then:
node 'Node' {
class {
'common::sudo' : ;
}
}
But I get the error:
err: Failed to apply catalog: Could not find dependent
Exec[concat_/etc/sudoers] for
File[/tmp/_etc_sudoers/fragments/10_test_2]
at /etc/puppet/modules/concat/manifests/fragment.pp:48
What am I doing wrong? Anyone has seen this error before?
TIA,
Arnau
--
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] rpm packages for el4
On Thu, 27 Oct 2011 11:04:35 +0200 Arnau Bria wrote: > Mike, > > where is the tarball for 2.6.12-2 ? > > I can't find it at http://downloads.puppetlabs.com/puppet/ I found src.rpm for el5. http://yum.puppetlabs.com/el/5/products/SRPMS/ Cheers, Arnau -- 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] rpm packages for el4
Mike, where is the tarball for 2.6.12-2 ? I can't find it at http://downloads.puppetlabs.com/puppet/ Cheers, Arnau -- 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] rpm packages for el4
On Wed, 26 Oct 2011 14:29:32 -0700 Michael Stahnke wrote: Hi Michael, > We've discussed it. The issue is that el4 ships with ruby 1.8.1. > Puppet doesn't work to well with 1.8.1 any more. If you rebuild or > pull in a newer ruby stack (even 1.8.5) then the el5 rpms probably > work. Ok. I'll look if thoses hosts have any ruby dependency more than pupppet. > Keep in mind el4 goes End of Life Feb 29, 2012. So, there isn't too > much time left on it either. I know. But we have some services which are still not ported to el5. > > Mike Thanks, Arnau -- 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] rpm packages for el4
Hi all, anyone has created the rpm packages of new versions for el4? only 5/6 at http://yum.puppetlabs.com/el/ TIA, Arnau -- 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] Variables syntax
Sent to early :-)
source => $::operatingsystem ? {
*without quotes.
> Isn't that supposed to work?
>
> Best regards,
> Martijn Grendelman
HTH,
Arnau
--
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] Variables syntax
On Mon, 17 Oct 2011 17:53:39 +0200
Martijn Grendelman wrote:
> Hi,
Hi,
[...]
> These give me errors like:
>
> Could not parse for environment production: Could not match
> ${::operatingsystem} at...
Where are you setting those vars?
I've seen that, on 2.6, setting those vars in selectors does not work.
source => $operatingsystem ? {
> Isn't that supposed to work?
>
> Best regards,
> Martijn Grendelman
HTH,
Arnau
--
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: how to modify a parameter inside a parametrized class
On Fri, 7 Oct 2011 06:34:00 -0700 (PDT)
jcbollinger jcbollinger wrote:
> On Oct 7, 8:11Â am, Arnau Bria wrote:
> > On Fri, 7 Oct 2011 05:55:34 -0700 (PDT)
> >
> > jcbollinger jcbollinger wrote:
> > > While I'm on this topic, I'll throw in that I would find it
> > > terribly confusing if a class or definition failed to honor my
> > > specification for a parameter named 'ensure'. Â
> >
> > Sorry John, but I don't understand this point.
>
> Because of the consistent manner of "ensure" parameters' use in
> Puppet's built-in resources, and the associated conventions even for
> custom and defined types, I would be very surprised if I ever declared
> something with "ensure => 'absent'" but that specification was
> overridden to the opposite. Indeed, I would be at least somewhat
> surprised by that with *any* parameter. Don't give me the option if
> you don't intend to honor it.
Ok, now it's clear.
I should put that logic outside the class, in node/param definitions ..
something like:
if ($::kernel=='Linux') and ($::lsbmajdistrelease=='6') {
class { 'common::nrpe' :
ensure => absnet,
}else{
class { 'common::nrpe' :
ensure => present,
}
> Inasmuch as this is for testing purposes, however, that's a different
> story. I don't think I would test in the way you are doing, but then
> again, maybe I would.
>
> John
>
Many thanks for your reply,
Arnau
--
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: how to modify a parameter inside a parametrized class
On Fri, 7 Oct 2011 05:55:34 -0700 (PDT)
jcbollinger jcbollinger wrote:
Hi John,
> You are misunderstanding that Puppet variables' values can never be
> reassigned. Once a variable has a value, it never changes throughout
> the compilation of that catalog. This is an aspect of Puppet DSL's
> declarative nature.
>
> As to how to accomplish what you ask, the usual way would be to use
> the parameter and any other data you want to select the value of a
> *different* variable, and then use that second variable. The same
> thing is fairly common practice in defined types:
>
> class common::nrpe($ensure='absent') {
> [...]
>
> if ($::kernel=='Linux') and ($::lsbmajdistrelease=='6') {
> $really_ensure = 'present'
> } else {
> $really_ensure = $ensure
> }
>
> [...]
>
> }
Ok, I solved the issue with something like that but I thought it was
some kind of ugly workaround... but if it's common I feel better with my
code.
> While I'm on this topic, I'll throw in that I would find it terribly
> confusing if a class or definition failed to honor my specification
> for a parameter named 'ensure'.
Sorry John, but I don't understand this point.
> I'd also find it confusing, though
> less so, for the default value of an 'ensure' parameter to be
> 'absent'. I recommend that you tweak your design a bit so as to not
> leave little traps like those for yourself and others to stumble over
> later. Or at least document the wazoo out of that thing.
I'm playing with this class. First time I do something like above.
Our production services have a default present, but this one is still
in test and I'd like to test it only on Linux 6., so I was playing with
logic inside new class :-)
> John
Many thanks for your reply,
Arnau
--
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] how to modify a parameter inside a parametrized class
Hi all,
I think I'm not understanding something...
from http://docs.puppetlabs.com/guides/parameterized_classes.html :
"The parameters you name can be used as normal local variables
throughout the class definition"
so, I have a class like:
class common::nrpe($ensure='absent') {
[...]
if ($::kernel=='Linux') and ($::lsbmajdistrelease=='6') {
$ensure='present'
}
so, by default the class is dissabled, but if it's a Linux release 6,
the value must be present.
so, I define the class in a Linux release 6 like:
nodes 'test' {
class { 'common::nrpe' : }
}
pupet fails with error:
Cannot reassign variable ensure
So, what am I missunderstanding? What is the correct way for doing what
I'm trying?
TIA,
Arnau
--
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: qualified variables in templates
Ok. so template and class share the scope and tehre's no need to qualify its vars. Thanks for your replies and for the link. Cheers, Arnau -- 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] Parameterized class of Parameterized classes
Hi all,
is there any problem in creating a parameterized class of parameterized
classes?
something like:
class A ($var1,$var2,$var3) {
class { 'B' :
param => ${var1} ;
'C' :
param => ${var2} ;
'D' :
param => ${var3} ;
}
}
node "Z" {
class { 'A' :
var1=> 'value1',
var2=> 'value2',
var3=> 'value3',
}
}
This is working fine in my test set (2.7.3), but I'm wondering if this
could cause issues in any way (most probably scope), or there's a
better way for grouping several classes into one (avoiding inheritance).
TIA,
Arnau
--
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] qualified variables in templates
Hi all,
is there a way for qualifying variables inside a template?
I've tried :
Name = <%= "${::hostname}" %>
but the var gets "${::hostname}" value.
thinking in version 2.8, is it needed?
http://docs.puppetlabs.com/guides/scope_and_puppet.html says nothing
about this...
TIA,
Arnau
--
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: Scope and puppet 2.7
On Wed, 14 Sep 2011 15:16:45 +0200 Arnau Bria wrote: > Hi all, Hi ! I reply myself... maybe it's useful for someone in the future. > I'm planning to upgrade our server/client to 2.7 and would like to > completely understand the big change in the dynamic scope deprecation. > > > It says that 2.7 will issue deprecation warning. Ok, so I've upgraded > a test server, test node and moved my code there. ran puppet and no > warnings. Great! Warning are logged into puppetmaster log, not at client level. [...] > So,i.e, $mcast_ip and $cluster which refer to ganglia module should > they be renamed to $common::ganglia::mcast_ip and > $common::ganglia::cluster ? > > Cause this is not working and giving a error: > > Cannot assign to variables in other namespaces from: http://docs.puppetlabs.com/guides/language_guide.html "Qualified variables are read-only — you cannot set a variable’s value from other class." so, the var's value must be set inside the class (local scope) or in the top (outside any class in site.pp). Cheers, Arnau -- 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] Scope and puppet 2.7
Hi all,
I'm planning to upgrade our server/client to 2.7 and would like to
completely understand the big change in the dynamic scope deprecation.
It says that 2.7 will issue deprecation warning. Ok, so I've upgraded a
test server, test node and moved my code there. ran puppet and no
warnings. Great!
So, now, I'd like to qualify my vars. In a code like:
class global_defaults {
include common::ganglia
include common::bacula
[...]
include common::snmp
}
node 'mynode' {
$mcast_ip = '22.22.11.11'
$cluster = 'Test'
$pakiti_tag = 'tag1'
$grid_service = 'ui'
$root_password = 'ui'
$rootkit_detector_mail = 'arnaubria_at_my_domain'
include global_defaults
}
all the vars defined into "mynode" refer to classes included in
global_defaults.
So,i.e, $mcast_ip and $cluster which refer to ganglia module should
they be renamed to $common::ganglia::mcast_ip and
$common::ganglia::cluster ?
Cause this is not working and giving a error:
Cannot assign to variables in other namespaces
**same if I declare them "global" variables $::mcast_ip
So, what's wrong with my code? why I can't rename my vars to new syntax?
TIA,
Arnau
--
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] Module organization: file serving
On Tue, 30 Aug 2011 09:44:59 -0400
Nan Liu wrote:
Hi Nan,
> No, files in the manifests directory are not accesible through source
> => puppet:///... The manifests directory is intended to be
> inaccessible to the agent since it contains files that should be
> compiled on the master.
thanks. now it's clear. What I request is impossible.
> Any reason, you intend to give the agent
> access to the manifests directory instead of using the files
> directory?
No, I simply thought that could be easy to manage files if they are
stored under each subdirectory. Anyway, I'll create a similar
manifests tree under files directory.
> MODULE_PATH
> |-module_name
>|-files
>|-bar
> |-baz
>|-manifests
>|-foo.pp
>|-bar
>|-bar.pp
>
> So for the agent to retrieve files/bar/baz:
> source => "${module_name}/bar/baz"
Yep, that's how we current work.
Thanks for your reply.
> Thanks,
> Nan
Cheers,
Arnau
--
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] Module organization: file serving
On Mon, 29 Aug 2011 10:04:42 -0700 Nigel Kersten wrote: > On Mon, Aug 29, 2011 at 8:23 AM, Arnau Bria wrote: Hi Nigel, I think my question was not clear: > > MODULE_PATH > > |-module_name > >|-files > >|-manifests > >|-foo.pp > >|-bar > >|-bar.pp > > > > > > My question is: is there a similar behaviour for file serving? May I > > create a file dir under bar directory and serve files from there? > > > > Yes. > > $module_name/files/foo/bar/baz > > is > > puppet:///modules/$module_name/foo/bar/baz and: $module_name/manifests/bar/files/baz? is accessible? Cheers, Arnau -- 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] Module organization: file serving
Hi all, Puppet's module organization looks like: MODULE_PATH |-module_name |-files |-manifests |-foo.pp |-bar |-bar.pp And module autoloading will find bar.pp if I define it as module_name::bar::bar My question is: is there a similar behaviour for file serving? May I create a file dir under bar directory and serve files from there? I don't find find refenreces to such behaviour at http://docs.puppetlabs.com/guides/modules.html ... and my test don't work. TIA, Arnau -- 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] mount "remounts" not working
On Tue, 16 Aug 2011 18:31:48 +0200 Stefan Schulte wrote: [...] > Solution: remove the name (so name will implicitly be /srv/cloud) or > change name to /srv/cloud (with no trailing slash) > > FTW: This is filed as https://projects.puppetlabs.com/issues/6793 thanks a lot! > -Stefan Cheers, Arnau -- 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] mount "remounts" not working
Hi all,
I have some code like:
{
'/srv/cloud' :
name => '/srv/cloud/' ,
atboot => true ,
device => 'iscsidisk01.domain.org:/volumes/POOL/one' ,
fstype => 'nfs' ,
remounts => true ,
options => 'defaults' ,
ensure => 'mounted' ,
require => File['/srv/cloud'] ;
}
So I'd like to use "remount" at mount time, but puppet does:
Execution of '/bin/mount -o defaults /srv/cloud/' instead of:
/bin/mount -o remount /srv/cloud/
and that make puppet fail.
Am I miss-understanding remount option? is there any problem with it?
$rpm -qa|grep puppet
puppet-2.6.8-1.el6.noarch
$cat /etc/redhat-release
Scientific Linux release 6.0 (Carbon)
TIA,
Arnau
--
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: cleaning puppet dashboard
On Thu, 11 Aug 2011 08:36:41 -0700 (PDT) Luke Bigum wrote: > Hi Arnau, Hi Luke, [...] > dump the database out, blow away the InnoDB data files and import the > dump (see > http://dev.mysql.com/doc/refman/5.5/en/innodb-data-log-reconfiguration.html). I'm dumping my dashboard data. My cron prunes de DB and keeps 1 week info. I have about ~100 nodes in that server and the dump is 6GB and grwoing... is that size normal? I mean, what's the "normal" size for the scenario I've described? (I know it depends on the amount os resoruces, but do you have any approach?) > Hope that helps, > > -Luke Cheers, Arnau -- 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: cleaning puppet dashboard
On Thu, 11 Aug 2011 08:36:41 -0700 (PDT) Luke Bigum wrote: > Hi Arnau, Hi Luke, > This is not a Puppet Dashboard problem, it's a MySQL "feature" of > InnoDB. You're using per-table InnoDB data files. InnoDB data files > grow. They never, ever, ever shrink. So what you've got there is a > 22GB sparse file that MySQL will fill up with more resource_statuses > rows. It won't use that space for any other table because you've for > per-table InnoDB data files configured on. You're right!! > I *think* one solution is to convert the resource_statuses to MyISAM > then back to InnoDB again but I've never done it. Another way is to > dump the database out, blow away the InnoDB data files and import the > dump (see > http://dev.mysql.com/doc/refman/5.5/en/innodb-data-log-reconfiguration.html). I'll try to do so. > Hope that helps, it does. > -Luke Cheers, Arnau -- 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] cleaning puppet dashboard
Hi all, I have a cron that follows http://docs.puppetlabs.com/dashboard/manual/1.2/maintaining.html and cleans our puppet dashboard: [...] rake RAILS_ENV=production reports:prune upto=1 unit=wk rake RAILS_ENV=production db:raw:optimize [...] but I've found a table which is 22GB and I'm not able to clean its space: 22G -rw-rw 1 mysql mysql 22G Aug 11 17:15 resource_statuses.ibd Our DB started to work on March, so I've removed all table entries before July, but the table is still 22GB . mysql> delete from resource_statuses where time < "2011-07-12%"; Query OK, 76040474 rows affected (1 hour 50 min 2.07 sec) So, how may I get some free space from dashboard DB? TIA, Arnau -- 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] facter 1.5.9 does not display lsbmajdistrelease
Hi all, few time ago I already asked about lsbmajdistrelease. https://groups.google.com/group/puppet-users/browse_thread/thread/9432108a8835f09a The solution to my previous problems was installing redhat-lsb. It worked fine, but facter 1.5.9 misses lsbmajdistrelease again, even with redhat-lsb installed: # facter lsbmajdistrelease 5 # rpm -qa |grep facter facter-1.5.8-1.el5.noarch # yum update facter [...] --> Running transaction check ---> Package facter.noarch 0:1.5.9-0.4.rc6.el5 set to be updated --> Finished Dependency Resolution [...] # rpm -qa |grep facter facter-1.5.9-0.4.rc6.el5.noarch # facter lsbmajdistrelease # lsbdistrelease works fine: # facter lsbdistrelease 5.3 #cat /etc/redhat-release Scientific Linux SL release 5.3 (Boron) Is this issue a known bug? TIA, Arnau -- 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] autosign by hostname not working?
On Thu, 19 May 2011 23:46:32 + Nan Liu wrote: thanks Nan, with your help and Patrick's I've understood the problem and solved. Many thanks for you reply! Cheers, Arnau -- 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] autosign by hostname not working?
On Thu, 19 May 2011 09:10:22 -0700 Patrick Patrick wrote: Hi, > Sorry. I ready your whole email backwords. I can only blame being > tired. no problem! > Did you clean using "puppetca --clean hostname" on the server, by > using "rm" on the client, or both? clean on the server. > Are you using Passenger? Mongrel That was the source of the issue I had to restart http/puppetmaster for new autosign to take effect. Now it works fine. I can block/unblock hosts with autosign. Thanks! Cheers, Arnau -- 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] autosign by hostname not working?
On Thu, 19 May 2011 08:03:38 -0700 Patrick Patrick wrote: Hi Patrick, Maybe I haven't explained myself correctly. > 1) Are you sure you want this? Sounds like a bad idea. I want to restrict puppet service to a list of known hosts. Is this a bad idea? I don't want all the nodes in our domain to be able to autosign the certifciate. > 2) As the documentation you have open shows, you can get the same > effect by setting "autosign = true" yep, but I don't want autosign. Iwant to sign certificates as I add client to puppet master- > 3) Try "*.*" instead. I think I remember Puppet won't work with just > an asterisk. *.my.dmain has woked fine. Thanks for your reply, Cheers, Arnau -- 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] autosign by hostname not working?
Hi all, till today we had a *.our.doamin in autosign.conf. So any host from our.domain could get a signed certificate if it contacts our master. But we've decide to move that "*" to a complet list of hostnames. So, I've pasted all the names to autosign file, restarted master (not sure if needed) So far, so good. So, I removed one name from autosign file, clean its cert, and ran puppet on the host, but it's still able to contact master and get its catalogue when it's supposed to get any kind of error. So, how is it possible? where am I'm missunderstanding autosign behiavour? # puppetmasterd --genconfig|grep autosign # Whether to enable autosign. Valid values are true (which # autosigns any key request, and is a very bad idea), false (which # never autosigns any key request), and the path to a file, which # The default value is '$confdir/autosign.conf'. autosign = /etc/puppet/autosign.conf # wc -l /etc/puppet/autosign.conf 660 /etc/puppet/autosign.conf # grep tditaller027.pic.es /etc/puppet/autosign.conf # [root@tditaller027 ~]# puppetd --test --server ser01.pic.es info: Retrieving plugin info: Loading facts in odd_ip info: Loading facts in odd_ip info: Caching catalog for tditaller027.pic.es info: Applying configuration version '1305815351' notice: Finished catalog run in 33.76 seconds # rpm -qa|grep puppet puppet-2.6.1-0.6.el5 puppet-server-2.6.1-0.6.el5 same version on client. TIA, Arnau -- 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] how to add same ssh_key to two diff accounts
On Thu, 12 May 2011 09:59:21 +0200
Felix Frank wrote:
> On 05/11/2011 05:36 PM, Arnau Bria wrote:
> >> If you're keen to get it anyway, you may want to open a ticket.
> > I think I've already asked here... but I have an example where that
> > feature is really interesting: we have some user pool, aout 1000
> > users, and I'd like to distrbute one key to all those users. Why the
> > trivial workaround, I could do it, but with 1000 lines :-)
>
> That's just not true.
>
> You surely have some defined type for your users, no? Such as
Nop, we use an other software for creating those users.
So, I must redefine each key for each user, and then my problem
appears.
[...]
> my_user($fullname) {
> user { "$name": fullname => $fullname, ... }
> ssh_authorized_key { "key-for-$name":
> user => $name,
> key => "AAznbwet...",
> ...
> }
> }
> That's what I meant - the workaround is really *that* trivial.
>
> I'm quite sure you'll have a hard time finding a use case that really
> requires the authorized key resource to be effective for multiple
> target users.
>From your example I think I can play with a false define for something
else trivial and add my key there
> Regards,
> Felix
Cheers,
Arnau
--
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] how to add same ssh_key to two diff accounts
On Tue, 10 May 2011 12:48:21 +0200 Felix Frank wrote: > > Do you know if this is going to be supportted in future? > > Redeclaration of the same resource is not going to work ;-) :-) > As for the distribution of one authorized_key to multiple user > accounts...I'm not sure that it's as useful as it sounds, given the > trivial workaround. > > If you're keen to get it anyway, you may want to open a ticket. I think I've already asked here... but I have an example where that feature is really interesting: we have some user pool, aout 1000 users, and I'd like to distrbute one key to all those users. Why the trivial workaround, I could do it, but with 1000 lines :-) so, I'll open a ticket and pray for developers finding it interesting too. > Regards, > Felix Many thanks for your reply, Cheers, Arnau -- 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] how to add same ssh_key to two diff accounts
On Tue, 10 May 2011 12:26:06 +0200 Felix Frank wrote: > Hi, Hi Felix, > > Am I trying to do something not supported? > > Yes. Do you know if this is going to be supportted in future? > Just rename on of the keys. The "name" of a public key is really quite > arbitrary and SSH doesn't use it for anything important (that I am > aware of). thanks, that worked perfectly! > Cheers, > Felix Cheers, Arnau -- 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] how to add same ssh_key to two diff accounts
Hi all, I'm trying to add same ssh key to two diff accounts and I'm getting an error. My code: 'key_1' name=> 'arnau@my_pc.domain', user=> 'user1', key => "rsa_key"; 'key_2': name=> 'arnau@my_pc.domain', user=> 'user2', key => "rsa_key"; On the client the error is: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Cannot alias Ssh_authorized_key[key_1] to ["arnau@my_pc.domain"]; resource ["Ssh_authorized_key", ["arnau@my_pc.domain"]] already exists at /etc/puppet/manifests/services/common/modules/common_si/manifests/init.pp:165 on node X.pic.es Is there something wrong in my code? Am I trying to do something not supported? Anyone faced this before? how did you solve it? TIA, Arnau -- 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] help with template and has_variable?
On Mon, 02 May 2011 15:31:01 +0200 Felix Frank wrote: [...] > "Constant"? > > This is a complete shot in the dark, but have you tried downcasing > those to "cvmfs_mountpoint" and "cvmfs_file"? that worked! > Looks to me like ruby thinks its dealing with constants, whereas it > should be looking for variables. so, any ideawhy is ruby doing it? > HTH, > Felix Thanks a lot Felix, Cheers, Arnau -- 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] help with template and has_variable?
Hi all,
I'm getting crazy with this... I have some templates where I use
has_variable? with no problem. But now I have problems in new one.
nods.pp
node 'my_node' {
$CVMFS_mountpoint = "/mnt/cvmfs"
$CVMFS_file = "/etc/auto.cvmfs"
[...]
include some_class_that_already_includes_autofs_class
}
[...]
'/etc/auto.master.test':
content => template('computing_autofs/auto.master.erb');
[...]
auto.master.erb
/nfsfile:/etc/auto.home
-rw,hard,intr,tcp,async,rsize=32768,wsize=32768,timeo=600
<% if has_variable?("CVMFS_mountpoint") and has_variable?("CVMFS_file") %>
<%= CVMFS_mountpoint %> <%= CVMFS_file %>
<% end %>
This gives :
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed
to parse template computing_autofs/auto.master.erb: uninitialized constant
Puppet::Parser::TemplateWrapper::CVMFS_mountpoint at
/etc/puppet/manifests/services/workernode/modules/computing_autofs/manifests/init.pp:35
If I change :
<%= CVMFS_mountpoint %> <%= CVMFS_file %>
for some static text (like KK), the templae works as expected:
# cat /etc/auto.master.test
#Autofs file
/nfsfile:/etc/auto.home
-rw,hard,intr,tcp,async,rsize=32768,wsize=32768,timeo=600
KK
and removes KK if I remove some of the above defined vars
So, why is it complaining about the uninitilized constant if it's
defined? and why it complains if the funtions already does something if
the var is not defined?
Anyone could give me a hand on this?
TIA,
Arnau
--
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] Advice for managing package versions with CentOS/yum
On Tue, 12 Apr 2011 16:02:56 -0700 (PDT) elliott elliott wrote: Hi, > Anyone have any advice for dealing with this? I'd rather not mirror > the entire CentOS-Base repository locally at version 5.5 just so my > few packages are available... why don't you mirror locally those few packages and add an exclude to CentOS repos? * So you'll have your local repo with your desired versions, and CentOs repos but excluding your particualr packages. We mirror all repos and use "latest" for most of the packages. > Thanks! Cheers, Arnau -- 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: add ssh key to several user accounts
Hi again,
I've been thinking a little more and got more ideas, but I
don't know if they're possible, so I'll appreciate some expert opinion
on them:
1.-) modify authorized_key provider (create my own) where user
param accepts an array of elements (users)
user => [ 'user1' , 'user2' , ...]
I'm not sure if this is correct (or even possible, I don't know all
puppet types, but I don't remember any param that accepts and array
and forces the execution of the provider several times ).
2.-) New type/provider where name is user in place of ssh_key.
Something like:
my_own_ssh_authorized_key { ' [ 'user1', 'user2', 'user3' ] :
source => me@mycomputer
key => jkladbglbsdlgb
type=>
}
this makes more sense as the provider will be called for each user, and
the code seems easy to implement (I'm ruby begginer) cause is an
adaptaion of current type/provider
Any advice?
TIA,
Arnau
--
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: add ssh key to several user accounts
On Thu, 7 Apr 2011 02:07:52 -0700 (PDT)
ccm ccm wrote:
> Hey.
Hi ccm.
> have a look at my last posting:
>
> http://groups.google.com/group/puppet-users/browse_thread/thread/d74262daca8c0e8f
>
> I wrote a small wrapper that might help you here.
Nice, but how to add same key to several accounts?
cause in your last example:
$team = [ 'ad...@domain.tld', 'us...@domain.tld' ]
sshauthkeys{ user2: keys => $team }
sshauthkeys{ user3: keys => $team }
I have to define user2/3/ so I'll have to define my 1500 accounts,
am I right? or am I missunderstanding your code?
> Best,
>
> ccm.
Thanks!
Arnau
--
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] add ssh key to several user accounts
Hi all,
I'd like to add one ssh_key to several (1500) user accounts.
Accounts share some prefix, so I was thinking on a regular expression,
but after reading language_guide, I understood that I cannot use
reg.expr for that.
So, I have a couple of ideas:
1.) define authorized_keys file like:
file { [ '/home/XXXuser1' , '/home/XXXuser2' ] :
content => $key,
mode=> ...
2.-) exec some kind of script which creates the .ssh dir and adds
content.
3.-) define 1500 authorized keys
Anyone could give more elegant/efficient ideas for this purpose?
TIA,
Arnau
--
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-dashboard
On Mon, 4 Apr 2011 11:33:54 +0100 FRLinux FRLinux wrote: > Hello, Hi, > I have another quick one about puppet dashboard. We are using the > Debian one for Squeeze (1.0.4) and as the database has significantly > grown, if/when we click on a list of unresponsive nodes to check them, > the web interface sits there doing nothing then the puppetmaster > process starts timing out for all nodes compiling their catalogs. > > Has anyone got a workaround for this? Does it involve cleaning the > database from time to time? We added a cron which does: rake RAILS_ENV=production reports:prune upto=1 unit=wk rake RAILS_ENV=production db:raw:optimize from /opt/puppet-dashboard once per week. since then, the server has increased its performance significally and we see no more timeout errors. > The box is a VM with 3G of allocated RAM, our ibdata1 file is pretty > big, reached 8G recently. > > So what do others do? > > Cheers, > Steph HTH, Arnau -- 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: Managing directories, recursively?
On Fri, 01 Apr 2011 15:22:03 +0200
Felix Frank wrote:
Hi,
just checking puppet mail list now.
as the author of the "great" example I want to say that my main
purpose was to say that instead of mkdir, you can declare as many dirs
as you want and then, create some kind of relationship between them. The
values where senseless and the syntax was not checked (require/s).
Apart from that, didn't know about
file { [ "/usr/local/nagios", "/usr/local/nagios/libexec" ]:
which automagically creates file dependency. so I declared it in two
diff files.
sorry for confusing you Forrie, and thanks to the others for you
extended explanation. Next reply will be more extended/accurate , I
promise.
Cheers,
Arnau
--
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: Managing directories, recursively?
On Thu, 31 Mar 2011 13:19:21 -0700 (PDT)
Forrie Forrie wrote:
> I only have a directory like:
>
> /usr/local/nagios/libexec
>
> for which I want to manage the plugins on the clients. It's pretty
> simple.
>
> So are you suggesting the better approach may be to exec a mkdir -p as
> a requirement in the head of the *.pp as a dependency? Meaning, it
> would detect if the directory structure is already there and if not,
> mkdir -p.
or simply, add more directories as depency...
file {
'/usr/local/nagios': ;
'/usr/local/nagios/libexec':
requires => File['/usr/local/nagios'],
owner => 'nagios',
mode => 755;
}
HTH,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Possible bug in configure script (torque 2.5.5)
> Wrong mailing list? Sure... I'm always thinking on puppet. sorry dudes! -- 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] Possible bug in configure script (torque 2.5.5)
Hi all,
it comes from another issue where David Beer is helping me, but
I faced a configure related issue when applying his solution:
I should build torque 2.5.5 with :
--with-tcp-retry-limit=2
After doing so, I should have a define in pbs_config.h, but
it isn't:
# grep -r TCP_RETRY_LIMIT src/*|grep define
#
I'm not bash expert and maybe I'm assuming something wrong, but looking
at configure script:
# Check whether --with-tcp_retry_limit or --without-tcp_retry_limit was given.
if test "${with_tcp_retry_limit+set}" = set; then
withval="$with_tcp_retry_limit"
TCP_RETRY_LIMIT=${withval}
else
TCP_RETRY_LIMIT=0
fi;
cat >>confdefs.h <<_ACEOF
#define TCP_RETRY_LIMIT ${TCP_RETRY_LIMIT}
_ACEOF
TCP_RETRY_LIMIT define should ALWAYS have be defined and with some
value ( 0 or own specified value).
So, I think this is a bug in configure because:
1.-) If the param should NOT be written always, there's a bug when
enabling it.
2.-) If the param should be written always, there's a bug when writing
.h files.
Find config.log attached.
Cheers,
Arnau
--
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.
config.log.gz
Description: GNU Zip compressed data
Re: [Puppet Users] pupet dashboard taking more than 10 minutes to destroy a node
Hi, After some prune /all excpet last week)/optimize the destroy action works great.. Thanks for the tips, now I have to take a lokk at mysql links. Cheers, Arnau -- 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] pupet dashboard taking more than 10 minutes to destroy a node
Hi Cody, Thanks for both replies! tomorrow morning I'll take a look to links. Cheers, Arnau -- 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] pupet dashboard taking more than 10 minutes to destroy a node
Hi again, I'm cleaning my DB (which was 15GB) following: https://github.com/puppetlabs/puppet-dashboard I did: rake RAILS_ENV=production reports:prune upto=1 unit=wk rake RAILS_ENV=development reports:prune upto=1 unit=wk (It has been running for about 3 months) and after: rake RAILS_ENV=production db:raw:optimize rake RAILS_ENV=development db:raw:optimize It has removed lots of entries, but it's still 15GB. Am I doing something wrong? why is it not decreasing its size? TIA, Arnau -- 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] pupet dashboard taking more than 10 minutes to destroy a node
On Thu, 24 Mar 2011 17:06:33 +0100 Stefan Goethals wrote: > Dashboard removes the reports for nodes one by one... > This can take a long time with many reports. > > Solutions : > - Delete reports in the db with a delete statement. > - run the cleanup rake task for reports as explained on the github > page. thanks. 'll take a look. > > Regards, > > Stefan - Zipkid - Goethals Cheers, Arnau -- 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] pupet dashboard taking more than 10 minutes to destroy a node
Hi all, I've noticed that puppet-dashboard takes a lot of time to refresh some webs, but today, I've started to remove some old nodes and it takes more than 10 minutes to remove one. The host hasn't a really high load: [root@puppet01 ~]# uptime 16:54:31 up 14 days, 5:17, 1 user, load average: 1.67, 1.48, 1.08 [root@puppet01 ~]# free -m total used free sharedbuffers cached Mem: 2026 1890136 0 4266 # grep -c "^proc" /proc/cpuinfo 2 and, obviously, ruby & mysql are eating all the cpu: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 31770 mysql 22 0 138m 28m 4616 S 117.2 1.4 18:42.69 mysqld 5111 root 16 0 861m 839m 2492 S 1.0 41.4 931:05.87 ruby Anyone notices this behaviour? any advice for solving this? puppet-dashboard-1.0.4.tgz TIA, Arnau -- 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] variable scope woes
On Mon, 28 Feb 2011 12:28:43 -0800 (PST) draeath draeath wrote: Hi, you could add some notify to see what value has $my_role in some classes. http://www.devco.net/archives/2009/08/19/tips_and_tricks_for_puppet_debugging.php We use same schema and variable scope works fine. what puppet version? Cheers, Arnau -- 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] duplicate base name error
Hi, not main but [base] you have only one [base] section in your working conf and twon on broken one. Try changin one base to something else. Cheers, Arnau -- 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] duplicate base name error
On Thu, 10 Feb 2011 12:10:54 -0500 Tim Dunphy wrote: > Hello list! Hello, [...] > [root@mclient ~]# puppetd --test > info: Caching catalog for mclient.acadaca.net > info: Applying configuration version '1297357383' > err: //centos/Yumrepo[rpmforge]: Failed to retrieve current state of > resource: A section with name base already exists > notice: Finished catalog run in 1.23 seconds [...] > I've also grepped my manifests directory for the term 'base' and didnt > find a duplicate repo definition that included it... thee problem is that you have many [main] sections in your repos (grep main /etc/yum.repos.d/*) and puppet doesn't like it (but yum does). > thanks in advance! HTH, Arnau -- 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: user authorized_keys with wrong perms
On Fri, 4 Feb 2011 06:30:10 -0800 (PST) jcbollinger jcbollinger wrote: [...] > So Puppet is sometimes failing with a permission failure while > attempting to synchronize the authorized_keys resource. Supposing > that the agent is running as root, there aren't very many things that > could cause it to be denied permission to access or change a file. Yes, agent runs as root. > Here's my short list: homes are local and selinux is disabled. > The fact that removing the .ssh directory and allowing Puppet to > recreate it fixes the problem is more consistent with (2). Even if > you think SELinux is not running or is not in enforcing mode, I > encourage you to check: package updates sometimes silently change > SELinux settings. I'm not familiar to selinux, maybe disabled is not enough... but seems to me that it's diasbled: # grep -v "#" /etc/selinux/config SELINUX=disabled SELINUXTYPE=targeted SETLOCALDEFS=0 > Cheers, > > John thanks for your reply, Cheers, Arnau -- 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] user authorized_keys with wrong perms
Hi,
I sometimes get a strange problem with some user's authorized_keys file.
The file should belong to user:users_group but puppet sets it as
root:root:
i.e:
err: /Stage[os]/Computing_ssh/Ssh_authorized_key[neuro...@si.pic.es]:
Could not evaluate: Permission denied - /home/neuroadm/.ssh/authorized_keys
# ls -lsa /home/neuroadm/.ssh/
total 12
4 drwx-- 2 neuroadm neuro 4096 Feb 3 21:02 .
4 drwx-- 3 neuroadm neuro 4096 Feb 3 21:02 ..
4 -rw--- 1 root root 578 Feb 3 21:02 authorized_keys
My code looks like:
file{
'ssh_neuroadm' :
name=> '/home/neuroadm/.ssh',
owner => 'neuroadm',
group => 'neuro',
mode=> 700,
ensure => directory,
require => File['home_neuroadm'];
'home_neuroadm' :
name=> '/home/neuroadm/',
owner => 'neuroadm',
group => 'neuro',
mode=> 700,
ensure => directory;
'neuro...@si.pic.es' :
user=> 'neuroadm',
key => 'Key';
The most strange thing is that it works sometimes and sometimes not...
The problem is solved if I remove .ssh dir and rerun puppet.
Anyone could help to find a reasonable explanation for this behaviour?
TIA,
Arnau
--
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] Configuration not applied, Finished catalog run in 0.01 seconds
On Wed, 26 Jan 2011 05:19:11 -0800 (PST) Adriana Adriana wrote: > Hello, Hi, [...] > When launching puppetd on the client and after having signed the > certificate, I always get the same > info: Caching catalog for pc001 > info: Applying configuration version '1296044901' > notice: Finished catalog run in 0.01 seconds > it doesn't matter what I change in my site on the server, the > configuration is never applied. what is it supposed to do? could you please paste your site/node files? is pc001 the real hostname? did you include it without domain? **simple try will be adding a file in site.pp. Cheers, Arnau -- 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: Problems with autoloading modules
On Thu, 13 Jan 2011 06:39:28 -0800 (PST) luke.bigum luke.bigum wrote: > Just to give you some examples of auto loading complex modules with > multiple classes and how that relates to class names: > > modules/puppet/init.pp => include puppet > modules/puppet/master.pp => include puppet::master > modules/puppet/params.pp => include puppet::params > modules/puppet/master/something.pp => include > puppet::master::something > modules/puppet/master/woof.pp => include puppet::master::woof Thanks again. I'll probably do that on next future, by now, I still have to "migrate" some old code to new one... I wouldn't like to mix 2 king of "modules"... Anyway, your examples are self-explanatory. Thanks. cheers, Arnau -- 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: Problems with autoloading modules
On Thu, 13 Jan 2011 02:41:31 -0800 (PST) luke.bigum luke.bigum wrote: > Hi Arnau, Hi Luke, > Your module folder name is called 'common_puppet' but you're class is > called 'common_puppet_conf'. O!! did not read about this requisite. > Option 1, rename the common_puppet class to common_puppet_conf, as > according to your grep, the only class inside common_puppet/init.pp is > "class common_puppet_conf". The class definition in init.pp of a > module should match the name of the module itself so the auto loader > can find it. > Option 2, move the class declaration of common_puppet_conf out of > init.pp and into common_puppet_conf.pp in the same directory, then you > should be able to do this (note the use of the namespace > common_puppet, which is your module name): > > include common_puppet::common_puppet_conf > > You can then have a common_puppet class, which you can have install > Puppet software and start Puppet services. Depends on how you want to > organise your modules. I'll choose first option as it's clearer to me . > HTH, > > -Luke Many thanks for your reply, Luke. Cheers, Arnau -- 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] Problems with autoloading modules
HI all,
we've been explicity importing modules since we started working with puppet.
We'd like to start using modules autoloading so I followed:
p://docs.puppetlabs.com/guides/modules.html
which only sys that puppet will load all modules under modulepath. Ok, so I
have this modulepath:
modulepath =
/etc/puppet/manifests/services/common/modules:/etc/puppet/manifests/services/workernode/modules/:/etc/puppet/manifests/services/tier_2/modules:
...
(Yes, many module paths, but I see no limitation there)
My default node includes common_puppet:
node default {
include common_puppet_conf
}
and the class is under:
# ls /etc/puppet/manifests/services/common/modules
common_bacula common_defaults common_puppet common_snmpd common_ssh
# grep class
/etc/puppet/manifests/services/common/modules/common_puppet/manifests/init.pp
# No dependencies with other classes/modules. We need Linux and Solaris conf
class common_puppet_conf {
So, from my pointof view, puppet should autoload that class, but it doesn't:
# puppetd --test --server ser01-test.pic.es
err: Could not retrieve catalog: Could not find class common_puppet_conf at
/etc/puppet/manifests/nodes.pp:8 on node tditaller019.pic.es
Am I doing something wrong? Cause module autoload seem very easy and it's
not working for me...
TIA,
Arnau
--
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: A section with name main already exists (Bug 5231)
On Tue, 11 Jan 2011 07:04:19 -0800 (PST) jcbollinger jcbollinger wrote: Hi, > Bug 5231 is about the lack of clarity and specificity in error > messages about conflicts between yum repos, not about the fact that an > error was raised in the first place. It sounds like you are expecting > Puppet to successfully apply your manifest. If indeed it should do > so, then you should file a separate ticket. Ok then, sorry for confusing things. As I have a repo conflict problem I thought it was the same case. > However, it's not clearcut to me that Puppet should do that. Do > versions of yum more recent than 3.2.22 in fact allow [main] sections > to appear in .repo files? Version 3.2.22 does not. From the man page > for yum.conf(5): "There should be only one [main] section. [...] The > [main] section must exist" (perforce in yum.conf) "for yum to do > anything." If the yum configuration on your system is faulty then I > think it reasonable for Puppet to raise an error in response. My version is yum-2.4.1-11.slc4, its man says same as yours but I have a main section per repo, which is "correct/acceptable" as yum works perfectly and it's distro default. I've tested my conf (adding some empty main sections per repo ) in Centos 5 with yum 3.2.22 and yum still works fine, ignoring those section. # yum install foo Loading "changelog" plugin Loading "installonlyn" plugin [...] No Match for argument: foo Nothing to do > I assume that yum itself is not complaining, so perhaps it is silently > ignoring the [main] sections in your .repo files. If that's the case > then the best workaround is probably to just remove those sections. Ok, I will do that, but seems strange to me that puppet is failing when yum doesn't resulting in puppet more restrictive than yum... > Alternatively, if yum is in fact using all those [main] sections then > you may be able to work around the problem by, for example, merging > all the [main] sections together into yum.conf (if that's indeed > equivalent to what yum does with them). > Cheers, > John Many thanks for your reply John, Cheers, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] A section with name main already exists (Bug 5231)
Hi all, I'm facing the bug 5231 when running puppet: host has some repos with many section main defined: # grep main * atrpms.repo:[main] cern-extra.repo:[main] cern-extra-srpms.repo:[main] cern-only.repo:[main] cern-only-srpms.repo:[main] cern.repo:[main] cern-srpms.repo:[main] cern-test.repo:[main] cern-test-srpms.repo:[main] cern-update.repo:[main] cern-update-srpms.repo:[main] dag.repo:[main] rhaps2.repo:[main] rhaps2-srpms.repo:[main] and puppet complains about it when adding a repo with no main section: # cat puppet-local-repo.repo [puppet-local-repo] name=puppet-local-repo I see no solution on puppet-bug and the only way I found to by-pass it is moving yum.repos.d direcotry. anyone who already faced it could give me a workaround? Cheers, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Could not find user "kbarber"
Hi, looking for more modules: * puppet-iptables * puppet-archive * puppet-bugzilla * puppet-sshd give an error about kbarber user... was him deleted by error? http://forge.puppetlabs.com/bobsh/sshd http://bob.sh/puppet TIA, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] sysctl type not available
On Mon, 10 Jan 2011 16:41:02 +0100 Peter Meier wrote: > As far as I remember this one: > http://git.puppet.immerda.ch/?p=module-sysctl.git;a=summary > > was originally based on that one. Thanks! > ~pete Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] sysctl type not available
Hi all, from http://projects.puppetlabs.com/projects/1/wiki/Puppet_Modules wanted to take a look at sysctl type but it's not available. http://spook.wpi.edu/sysctl Anyone could give it a look? TIA, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet definitions and inheritance
On Thu, 06 Jan 2011 13:49:56 +0100 Felix Frank wrote: Hi Felix, > > In our work, we're 4 people sharing a puppet server and puppet > > structure. We define our definitions inside our classes, and > > sometimes we see that some of we use same def but defined in its > > our class (i. e. add_line definiton). > > > > So, why ios the correct procdeure (or other's experince) to define > > "shared" definitons? > > First off, you *do* each work on distinct modules, right? So moving > stuff to your init.pp is not going to inflict anything on your > coworkers. Yes, we do use our own modules. (our own vars and our own tree branch). we also have a common part with common moduleswhich are included by "default"... > Apart from that - why would you require everyone to reinvent all the > wheels? Why *wouldn't* you want to define a central add_line > definition? Mmmm... I'm not sure if I'm undesratnding you. We don't want to reinvent the wheel, so I'm asking other admins if you use others one code, and if yes, where do they (you) define this kind of things... some king of common definition "available" in every module? > Regards, > Felix Cheers, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet definitions and inheritance
On Mon, 3 Jan 2011 08:11:50 -0800 (PST) jcbollinger jcbollinger wrote: Hi, looking for some other's experience... [...] > You could also try using ::main::luser, and perhaps even changing > "main" to something with less potential for name collision. Better, > however, would probably be to move luser to the top level of your > module's init.pp (you are using modules, right?). In our work, we're 4 people sharing a puppet server and puppet structure. We define our definitions inside our classes, and sometimes we see that some of we use same def but defined in its our class (i. e. add_line definiton). So, why ios the correct procdeure (or other's experince) to define "shared" definitons? TIA, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: lsbmajdistrelease fact
Thanks to both.. > redhat-lsb seems trivial now... an hour looking for diff and it was so easy... thanks again! Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: lsbmajdistrelease fact
On Tue, 21 Dec 2010 17:02:20 +0100 Arnau Bria wrote: > Hi all, > > I've noticed that facter version superior from epel do not > display lsbmajdistrelease fact: Sorry for the noise, that's not true. it works in some systems and it doesn't in others. I'm sure I have some diff between systems, so, I have to change my question: anyone could tell me what package could be causing this diff behaivour between hosts? TIA, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] lsbmajdistrelease fact
Hi all, I've noticed that facter version superior from epel do not display lsbmajdistrelease fact: # facter lsbmajdistrelease 5 # rpm -qa|grep facter facter-1.5.5-1.el5 # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) # facter lsbmajdistrelease # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) # rpm -qa|grep facter facter-1.5.8-1.el5 package from http://download.fedora.redhat.com/pub/epel/5/x86_64/facter-1.5.8-1.el5.noarch.rpm I've looked at bugtracker and seen no ref to this behaviour ... am I doing something wrong? is it a real bug? TIA, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] tmz repo
Hi all, maybe it's a little OT... anyone knows if old puppet version from tmz repos are still available somewhere? TIA, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] variables with no value
On Sun, 19 Dec 2010 16:57:06 +0100 Stefan Schulte wrote: > On Fri, Dec 10, 2010 at 11:31:18AM +0100, Arnau Bria wrote: > > Hi all, Hi, > > When I run the client in nodeb, and add a notify of root_password, > > I see that nodeb's root_password has a value and it's serviceA!?!? > > This can happen when you have set the var in top scope (nodes.pp > directly or in site.pp) or you have some missing bracket somewhere and > your nodedefinition still works magically while scope is totally > mixed up (happened to me a few times) that was what happened. Someone defined it at node's top, and it became a "global" defined var. > -Stefan Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] how to us a var in define as $namevar
On Thu, 16 Dec 2010 07:29:18 -0700 Nan Liu wrote: > If you want to use the resource title, simply use $title or $name > within the define. yes it has more sense .. > Thanks, > > Nan Thanks, Arnau -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] how to us a var in define as $namevar
Hi,
I have this code:
define software_mount ($vo_name) {
[...]
device => "server:/$vo_name",
[...]
}
And I'd like to use $vo_name a type name, so I could use it like:
software_mount { ['vo_name1' , 'vo_name2', ..., 'vo_nameN' ] }
or even:
software_mount { ['vo_name1' , 'vo_name2', ..., 'vo_nameN' ] : vo_name =>
$namevar }
I've been playing with $namevar inside the define, but all my tries fail
(I have a collection of errros and has no sense to post all of them).
Anyone could give a hand on this?
TIA,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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: File type: no success using array
On Wed, 15 Dec 2010 11:04:27 +0100
Peter Meier wrote:
Hi Pete,
> >> file { [ '/software/atlas' , '/software/cms' , '/software/lhcb' ,
> >> '/software/magic' , '/software/at3' , '/software/paus' ,
> >> '/software/mice' , '/software/ops.vo.ibergrid.eu' ,
> >> '/software/supernemo.vo.eu-egee.org' ]: require=>
> >> File['/software'] ; }
>
> not that you don't need this require, as puppet automagically orders
> file resources according to their path. So File['/software/atlas']
> automatically depends on File['/software']
thanks! didn't know.
> ~pete
Cheers,
Arnau
PS: I love automagically word!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
