[Puppet Users] Split Manifest Across Multiple Lines?
Is there a way I can split a line in a manifest across multiple lines, ala
shell style?
ie:
$include_postfix_module = extlookup("IncludePostfixModule", \
extlookup("IncludePostfixModule", \
extlookup("IncludePostfixModule", \
"",
"settings/nodes/_global"), \
"settings/nodes/${domain}"), \
"settings/nodes/${fqdn}")
Oh wait... maybe I can just do that without the "\"'s
Doug
--
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: New Puppet report processors...
treydock wrote: The report processor was synced to /var/lib/puppet/lib/reports/ . I enabled puppetmaster to run in debug mode but haven't seen anything mentioning reports when I run test runs. I purposly misspelled a module for the puppetmaster and run puppetd --test, but no reports except those in puppet-dashboard. I could be looking in the wrong place. Here's the debug output of the failed puppet run...(hostname replaced) Can I get the master log please. That's where the report is triggered. Regards James -- 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: New Puppet report processors...
The report processor was synced to /var/lib/puppet/lib/reports/ . I enabled puppetmaster to run in debug mode but haven't seen anything mentioning reports when I run test runs. I purposly misspelled a module for the puppetmaster and run puppetd --test, but no reports except those in puppet-dashboard. I could be looking in the wrong place. Here's the debug output of the failed puppet run...(hostname replaced) $ puppetd --test --debug -vvv debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ dscl does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows is missing debug: /File[/var/log/puppet/http.log]: Autorequiring File[/var/log/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys/puppetmaster.domain.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/ssl/private_keys/ puppetmaster.domain.pem]: Autorequiring File[/var/lib/puppet/ssl/ private_keys] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/ var/lib/puppet/state] debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/run/puppet/agent.pid]: Autorequiring File[/var/run/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs/puppetmaster.domain.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/ var/lib/puppet/ssl] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/ lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/ lib/puppet/state] debug: /File[/etc/puppet/namespaceauth.conf]: Autorequiring File[/etc/ puppet] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/classes.txt]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/ puppet] debug: Finishing transaction 23786215705400 debug: /File[/etc/puppet/namespaceauth.conf]: Autorequiring File[/etc/ puppet] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/ var/lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/public_keys/puppetmaster.domain.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/log/puppet/http.log]: Autorequiring File[/var/log/ puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys/ puppetmaster.domain.pem]: Autorequiring File[/var/lib/puppet/ssl/ private_keys] debug: /File[/var/lib/puppet/ssl/certs/puppetmaster.domain.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: Finishing transaction 23786215706160 debug: Using cached certificate for ca debug: Using cached certificate for puppetmaster.domain notice: Ignoring --listen on onetime run debug: Finishing transaction 23786215181380 debug: Loaded state in 0.00 seconds info: Retrieving plugin debug: Using cached certificate for ca debug: Using cached certificate for puppetmast
Re: [Puppet Users] Augeas match & Puppet
Thanks Aaron,
I reread that and this time found the snippet I needed ...
The following works ...
onlyif=> "match FW_CONFIGURATIONS_EXT/value[.='$svc'] size == 0",
Cheers
On 7 June 2011 08:51, Aaron Grewell wrote:
> I found this Wiki article tremendously valuable when dealing with Augeas.
> http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Augeas
>
> On Mon, Jun 6, 2011 at 3:45 PM, Michael Knox wrote:
>
>> Hi,
>> I'm working on a type to undertake some very simple management of the SuSE
>> firewall service (/etc/sysconfig/SuSEfirewall2), specifcally I need to
>> manage the contents of the list FW_CONFIGURATIONS_EXT which is handled as a
>> shell list.
>>
>> I've been able to use the shellvars_list.aug to manage the file, but I'm
>> struggling with the puppet filter / onlyif.
>>
>> The following works in augtool:
>> match FW_CONFIGURATIONS_EXT/value $svc
>> I then wanted to check that the size of this array was 0 before adding the
>> service.
>>
>> However this fails with ...
>> err:
>> /Stage[main]/Svn::Server/Firewall::Service[svn]/Augeas[fwservice_svn]: Could
>> not evaluate: Error sending command 'match' with params nil/Unknown command
>> svn
>>
>> So this filter argument for match is supported in Augeas, but not in the
>> Augeas provider.
>>
>> Is there a better way of doing this with the current provider?
>>
>> The manifest code in question
>> augeas {"fwservice_$svc":
>> context => "/files/etc/sysconfig/SuSEfirewall2",
>> onlyif=> "match FW_CONFIGURATIONS_EXT/value $svc size == 0",
>> #onlyif=> "match FW_CONFIGURATIONS_EXT/value not_include $svc",
>> changes => [
>>"set FW_CONFIGURATIONS_EXT/value[last()+1] $svc",
>> ],
>> load_path => "$augeas::params::lense_path",
>> require => Augeas::Lense['shellvars_list.aug'],
>> }
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
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 do you handle deleted nodes with exported resources in this situation?
I have an issue where for a file type of an exported resource I must define as such: force=> false, replace => false, Meaning the file is created, but do not replace after it's added. I do this because of the app modifies the config file after (I know bad idea on their part). How can I ensure this file is removed when I remove the node from the storeconfig database? In general, is there a way to trigger a event puppet when a instance is removed? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/NmI1RmUwTXY5YndK. 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] Augeas match & Puppet
I found this Wiki article tremendously valuable when dealing with Augeas.
http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Augeas
On Mon, Jun 6, 2011 at 3:45 PM, Michael Knox wrote:
> Hi,
> I'm working on a type to undertake some very simple management of the SuSE
> firewall service (/etc/sysconfig/SuSEfirewall2), specifcally I need to
> manage the contents of the list FW_CONFIGURATIONS_EXT which is handled as a
> shell list.
>
> I've been able to use the shellvars_list.aug to manage the file, but I'm
> struggling with the puppet filter / onlyif.
>
> The following works in augtool:
> match FW_CONFIGURATIONS_EXT/value $svc
> I then wanted to check that the size of this array was 0 before adding the
> service.
>
> However this fails with ...
> err: /Stage[main]/Svn::Server/Firewall::Service[svn]/Augeas[fwservice_svn]:
> Could not evaluate: Error sending command 'match' with params nil/Unknown
> command svn
>
> So this filter argument for match is supported in Augeas, but not in the
> Augeas provider.
>
> Is there a better way of doing this with the current provider?
>
> The manifest code in question
> augeas {"fwservice_$svc":
> context => "/files/etc/sysconfig/SuSEfirewall2",
> onlyif=> "match FW_CONFIGURATIONS_EXT/value $svc size == 0",
> #onlyif=> "match FW_CONFIGURATIONS_EXT/value not_include $svc",
> changes => [
>"set FW_CONFIGURATIONS_EXT/value[last()+1] $svc",
> ],
> load_path => "$augeas::params::lense_path",
> require => Augeas::Lense['shellvars_list.aug'],
> }
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Augeas match & Puppet
Hi,
I'm working on a type to undertake some very simple management of the SuSE
firewall service (/etc/sysconfig/SuSEfirewall2), specifcally I need to
manage the contents of the list FW_CONFIGURATIONS_EXT which is handled as a
shell list.
I've been able to use the shellvars_list.aug to manage the file, but I'm
struggling with the puppet filter / onlyif.
The following works in augtool:
match FW_CONFIGURATIONS_EXT/value $svc
I then wanted to check that the size of this array was 0 before adding the
service.
However this fails with ...
err: /Stage[main]/Svn::Server/Firewall::Service[svn]/Augeas[fwservice_svn]:
Could not evaluate: Error sending command 'match' with params nil/Unknown
command svn
So this filter argument for match is supported in Augeas, but not in the
Augeas provider.
Is there a better way of doing this with the current provider?
The manifest code in question
augeas {"fwservice_$svc":
context => "/files/etc/sysconfig/SuSEfirewall2",
onlyif=> "match FW_CONFIGURATIONS_EXT/value $svc size == 0",
#onlyif=> "match FW_CONFIGURATIONS_EXT/value not_include $svc",
changes => [
"set FW_CONFIGURATIONS_EXT/value[last()+1] $svc",
],
load_path => "$augeas::params::lense_path",
require => Augeas::Lense['shellvars_list.aug'],
}
--
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: backup files whith bad arborescence
The easiest way I can think of is using your favorite "find" program. I would assume that the unix find program will do this for you. On Jun 6, 2011, at 5:27 AM, florian wrote: > If i dont change this arborescence, how I can find a backup at > specific date ? > > Think > > On 3 juin, 17:26, Patrick wrote: >> On Jun 3, 2011, at 8:12 AM, florian wrote: >> >>> But it's possible to avoid this arborescence ? even if i lose in >>> performance ? >> >> My understanding is that the answer is "mo" because you're not even supposed >> to be using those files directly, so it shouldn't matter. You should be >> using the file bucket through puppet instead. >> >> Out of curiosity, why do you care? -- 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: backup files whith bad arborescence
On Jun 6, 2011, at 12:27 AM, florian wrote: > On 3 juin, 17:26, Patrick wrote: > >> Out of curiosity, why do you care? > > i think it damage to keep this arborescence with many intermediate > file. Do you mean you think it is bad to keep the file structure like this? If so, I still ask why. -- 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] Weird paramterized issue
Amazing!
Iv somehow missed that :)
There was another include that missed my eyes (never include within an
init.pp above a class)
Thank you!
Ronen
On Sat, Jun 4, 2011 at 11:16 PM, Ken Barber wrote:
> Ronen,
>
> Have you tried grepping through all your content to make sure your not
> using 'include "nodejs"' elsewhere - or some other usage of it where
> you are not specifying user. You might be seeing non-deterministic
> class loading order which may be why your symptoms are intermittent.
>
> ken.
>
> On Sat, Jun 4, 2011 at 6:56 PM, Ronen Narkis wrote:
> > Im using a parameterized class in my site.pp:
> >
> > class development($user) {
> > class{"basenode": user => $user}
> > class{"nodejs": user => $user}
> > include "coffeescript"
> > include "ruby"
> > }
> >
> > This class defines nodejs class that epects a user as input:
> >
> > class nodejs($user) {
> >
> > class {"nodejs::npm": user => $user}
> >
> > $node_ver = "v0.4.7"
> > $node_tar = "node-$node_ver.tar.gz"
> >
> >
> > # ...
> > }
> >
> >
> > The first time I run this all works fine, still on the second run Im
> > getting:
> >
> > err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> > Must pass user to Class[Nodejs] at
> > /etc/puppet/modules/nodejs/manifests/init.pp:1 on node
> >
> > When I touch the site.pp file or restart puppet master all things work
> > again, any idea what Im doing wrong?
> >
> > Thanks
> > Ronen
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
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] Unable to use types from modules
David,
Are you using environments?
If so, you're probably hitting bug #4409 (
https://projects.puppetlabs.com/issues/4409 )
If not, have you restarted your puppet master?
Cheers
2011/6/7 Davíð Steinn Geirsson
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> I'm having some problems using modules which define their own types and
> providers. It seems the puppet client does not recognise them, even
> though they are set up according to the structure suggested in
> http://docs.puppetlabs.com/guides/plugins_in_modules.html
>
>
> I was initially trying to use the glassfish class from
> https://github.com/larstobi/puppet-glassfish. Since then I've tried some
> others, including this very simple VCS provider:
>
>
> https://github.com/jamtur01/puppet/commit/a1fcf677759858f22fccba0a383f2aa4e6a92e54
>
> My module tree (/opt/puppet/etc/modules/subversiontest) is set up as
> follows:
>
> ./puppet/type/repo/repo.pp
> ./puppet/provider/repo/svn.pp
> ./puppet/provider/repo/git.pp
> ./manifests/init.pp
>
> My init.pp simply defines a basic resource from this:
> class subversiontest {
>repo { "wp":
>source => "http://core.svn.wordpress.org/trunk/";,
>path => "/tmp/wp",
>ensure => present,
>}
> }
>
>
> I have set
> pluginsync = true
> under the [main] section of both the master and agent.
>
> Howver, when I try to apply this module, I always get an error regarding
> the type being unknown:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Could not find resource type repo at
> /opt/puppet/etc/modules/subversiontest/manifests/init.pp:6 on node
> rhel6test.skyrr.median.local
>
>
> My versions are:
> root@pmonitor02 ~ # puppetmasterd --version
> 0.25.4
> root@rhel6test puppet # puppetd --version
> 0.25.5
>
>
> I'm sure my mistake is very basic, but I've been stuck on this for a while.
>
> Can anyone provide suggestions on what could be wrong in my setup?
>
> Best regards,
> David
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk3tDIUACgkQKXQCZqH9wfxVbwCePEvfHFQQUTNGSuYtLMt47YWk
> ya0An0ngLa0Ozrpf3LoqVd6ucozB7AiV
> =d9vP
> -END PGP SIGNATURE-
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
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] No matching value for selector param '1' with case and ? statements
I have been getting an error message " No matching value for selector
param '1'" when ever I use the following code in a class. What is
strange is if I run the code directly with "puppet -v filename" where
the code is in the filename or I stick the code in the nodes.pp file
it works perfectly. When I put it into a class and include in the
node it breaks.
$client_env = $hostname ? {
/^mr/ => "mirror",
default => "UNKNOWN"
}
info "hostname=[${hostname}], client_env=[${client_env}]"
I'm running Puppet 2.6.8, Ruby 1.8.5, and Passenger 2.2.11.
Any thoughts?
TIA,
John
--
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] Unable to use types from modules
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm having some problems using modules which define their own types and
providers. It seems the puppet client does not recognise them, even
though they are set up according to the structure suggested in
http://docs.puppetlabs.com/guides/plugins_in_modules.html
I was initially trying to use the glassfish class from
https://github.com/larstobi/puppet-glassfish. Since then I've tried some
others, including this very simple VCS provider:
https://github.com/jamtur01/puppet/commit/a1fcf677759858f22fccba0a383f2aa4e6a92e54
My module tree (/opt/puppet/etc/modules/subversiontest) is set up as
follows:
./puppet/type/repo/repo.pp
./puppet/provider/repo/svn.pp
./puppet/provider/repo/git.pp
./manifests/init.pp
My init.pp simply defines a basic resource from this:
class subversiontest {
repo { "wp":
source => "http://core.svn.wordpress.org/trunk/";,
path => "/tmp/wp",
ensure => present,
}
}
I have set
pluginsync = true
under the [main] section of both the master and agent.
Howver, when I try to apply this module, I always get an error regarding
the type being unknown:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find resource type repo at
/opt/puppet/etc/modules/subversiontest/manifests/init.pp:6 on node
rhel6test.skyrr.median.local
My versions are:
root@pmonitor02 ~ # puppetmasterd --version
0.25.4
root@rhel6test puppet # puppetd --version
0.25.5
I'm sure my mistake is very basic, but I've been stuck on this for a while.
Can anyone provide suggestions on what could be wrong in my setup?
Best regards,
David
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3tDIUACgkQKXQCZqH9wfxVbwCePEvfHFQQUTNGSuYtLMt47YWk
ya0An0ngLa0Ozrpf3LoqVd6ucozB7AiV
=d9vP
-END PGP SIGNATURE-
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: use a custom fact value in a manifest
Ok forget my message, pluginsync=true works perfectly, problem was between chair and keyboard ... Etienne On 6 juin, 18:11, Etienne F wrote: > Hi everybody, > > i'm a lucky Puppet user for a few weeks and i'm currently "blocked" > for a "simple" thing. > > I try to use facter custom values deployed with pluginsync feature in > one manifest. Unfortunately, values aren't available when manifest is > executed. > > I tried to use pre/main stage in order to deploy my facts with a pre > stage class but it doesn't work... > > Do yo know how i can handle this kind of thing? For example force > puppet to "reload" facter values. > > Thanks a lot for your help > > Etienne -- 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] use a custom fact value in a manifest
Hi everybody, i'm a lucky Puppet user for a few weeks and i'm currently "blocked" for a "simple" thing. I try to use facter custom values deployed with pluginsync feature in one manifest. Unfortunately, values aren't available when manifest is executed. I tried to use pre/main stage in order to deploy my facts with a pre stage class but it doesn't work... Do yo know how i can handle this kind of thing? For example force puppet to "reload" facter values. Thanks a lot for your help Etienne -- 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] logging output at err level, success as just a notice?
On Mon, 06 Jun 2011 09:37:48 -0500, Jennings, Jared L CTR USAF AFMC 46 SK/CCI
wrote:
>
> I'm trying to run pwck with Puppet 2.6.4. pwck checks the passwd file
> and makes sure that, for example, each user's home directory exists.
> (And other stuff.) When everything is OK, it doesn't say anything. So if
> it says something, I want to know it, and I want it to stand out from
> other exec output.
>
> So I have
>
> exec { "pwck":
> command => "/usr/sbin/pwck -r",
> logoutput => true,
> loglevel => err,
> }
>
> If pwck gives any output, it shows up at the err loglevel. But if
> everything is OK, I get:
>
> err: /Stage[main]/User::Valid/Exec[pwck]/returns: executed successfully
>
> (in purple, of course). I don't want an err message when everything is
> fine.
>
> The documentation for the exec resource type
> () says, about
> logoutput, "Values are true, false, on_failure, and any legal log level.
> Valid values are true, false, on_failure." (Take a second and read that
> again.) So I tried setting logoutput => err and no loglevel, and got:
> 'err: Could not run Puppet configuration client: Parameter logoutput
> failed: Invalid value "err". Valid values are true, false, on_failure.'
>
> How can I make "executed successfully" a notice, and any output from
> pwck an err?
>
> If logoutput can indeed be set to any legal log level, does anyone know
> in what version of Puppet this works?
>
Unfortunately, the documentation is just plain wrong. loglevel is the
only one that supports "any legal log level". logoutput really does
only support true, false, and on_failure.
Is pwck exiting non-zero when there is output? That should be
sufficient to trigger the behavior it seems like you're looking for if
you have 'logoutput => on_failure' in the exec.
I tried running 'pwck -r' on my Ubuntu machine, and it exited 2 with a
bunch of warnings. I presume it would have exited 0 had there not been
any warnings.
--
Jacob Helwig
signature.asc
Description: Digital signature
Re: [Puppet Users] Weird paramterized issue
Ronen,
Have you tried grepping through all your content to make sure your not
using 'include "nodejs"' elsewhere - or some other usage of it where
you are not specifying user. You might be seeing non-deterministic
class loading order which may be why your symptoms are intermittent.
ken.
On Sat, Jun 4, 2011 at 6:56 PM, Ronen Narkis wrote:
> Im using a parameterized class in my site.pp:
>
> class development($user) {
> class{"basenode": user => $user}
> class{"nodejs": user => $user}
> include "coffeescript"
> include "ruby"
> }
>
> This class defines nodejs class that epects a user as input:
>
> class nodejs($user) {
>
> class {"nodejs::npm": user => $user}
>
> $node_ver = "v0.4.7"
> $node_tar = "node-$node_ver.tar.gz"
>
>
> # ...
> }
>
>
> The first time I run this all works fine, still on the second run Im
> getting:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Must pass user to Class[Nodejs] at
> /etc/puppet/modules/nodejs/manifests/init.pp:1 on node
>
> When I touch the site.pp file or restart puppet master all things work
> again, any idea what Im doing wrong?
>
> Thanks
> Ronen
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Pushing changes to nodes
Hi Pavel, We implemented something similar to what you are asking on our own servers using commonly available tools: * pssh - cluster ssh tools * cron/etc on puppetmaster + puppetrun - our sysadmins or the puppetmaster itself determines when puppet configuration runs should be performed. * modified agent configs to be active on clients, but not to execute unless they receive a request directly from puppetmaster (no interval based runs) * NFSv4 to clients from puppet master We implemented the above because puppet's default method of execution is OK for binary based distributions, but not really for source based linux distributions. Using a "run only when puppet master tells us to" allows us to update source repositories on the master, and then have the master execute the necessary code on the clients to update before forcing a puppet update. In general, this means puppet only runs about once/week for most nodes. We add some additional bash/ruby code to create groups of nodes to update. Matt On Sun, Jun 5, 2011 at 4:48 AM, Pavel Shevaev wrote: > Hi! > > I've finally managed to migrate our servers deployment process to the > puppet and so far it works just fine. Puppet is great, but its default > pull model doesn't fit our requirements. I'm thinking about usage of > clusterssh(or something similar) in order to trigger the following > command on the nodes: > > sudo puppet agent --no-daemonize --verbose --onetime > > In our setup puppet agent is not running as a service on the nodes. > > I think it would be really nice to have this feature available in the > future versions of puppet, e.g: > > #puppet push > > What do you think? > > -- > Best regards, Pavel > > -- > 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. > > -- Matthew Marlowe Tel: 805-857-9144 http://www.professionalsysadmin.com/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] logging output at err level, success as just a notice?
I'm trying to run pwck with Puppet 2.6.4. pwck checks the passwd file
and makes sure that, for example, each user's home directory exists.
(And other stuff.) When everything is OK, it doesn't say anything. So if
it says something, I want to know it, and I want it to stand out from
other exec output.
So I have
exec { "pwck":
command => "/usr/sbin/pwck -r",
logoutput => true,
loglevel => err,
}
If pwck gives any output, it shows up at the err loglevel. But if
everything is OK, I get:
err: /Stage[main]/User::Valid/Exec[pwck]/returns: executed successfully
(in purple, of course). I don't want an err message when everything is
fine.
The documentation for the exec resource type
() says, about
logoutput, "Values are true, false, on_failure, and any legal log level.
Valid values are true, false, on_failure." (Take a second and read that
again.) So I tried setting logoutput => err and no loglevel, and got:
'err: Could not run Puppet configuration client: Parameter logoutput
failed: Invalid value "err". Valid values are true, false, on_failure.'
How can I make "executed successfully" a notice, and any output from
pwck an err?
If logoutput can indeed be set to any legal log level, does anyone know
in what version of Puppet this works?
--
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 & Augeas
On 06/06/11 10:01, Kris Buytaert wrote:
> To actual errors "change from need_to_run to 0 failed: Save failed with
> return code false" when trying to experiment with a syntax like below.
> ...
> augeas{"sipxprofile" :
> lens=> "Xml",
> incl=>
> "/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml",
> context =>
> "/files/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml",
> changes => [
> "set profile/settings/param[16]/#attribute/value 10.0.0.2",
> "set profile/settings/param[17]/#attribute/value 10.0.0.2",
> ],
> }
>
>
> Is there some way to implement the "load" function in augeas in puppet ?
> Or any documentation around regarding the correct use of lens, incl
> etc ?
Rather than setting lens to "Xml", set it to "Xml.lns", as documented here:
http://docs.puppetlabs.com/references/stable/type.html#augeas
The rest looks OK to me (though I'd suggest using XPath type expressions
rather than hard-coding the numbers 16 and 17).
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7818 512168
--
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: Should puppet manage its own client configs?
Felix, Would you mind sharing how you implemented the process to restart Puppet after an update? Thanks, John On May 24, 6:34 am, Felix Frank wrote: > On 05/24/2011 12:29 PM, Jonathan Gazeley wrote: > > >> If youmanageto deploy an utterly broken config,puppetwon't be able > >> to get itself back up to speed because it cannot start anymore. > > >> Am I missing something here? > > > No, you are correct. If I deploy a garbage config, it will break the > >puppetclients. But the benefit is that I can easily deploy a modified > >puppetconfig to many clients if we need to add extra config parameters > > in future. > > > I can mitigate the risk by carefully testing the newpuppet.conf on an > > isolated dev machine. > > That's an utter relief. > > I've deployed a mechanism that will deploy apuppet.conf alongside the > actual one and notify a script that becomes active after the catalog run > proper. > It activates the new config, but ifpuppetis found to not run correctly > afterwards, the original config is restored instead. > > Cheers, > Felix -- 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: Module variables missing during some puppet runs
On Jun 3, 11:58 am, treydock wrote:
> I am getting the following error on about every other manual run of
> puppet... (hostnames removed)
>
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Failed to parse template zabbix/userparameter_mysql_conf.erb:
> Could not find value for 'zabbix_mysql_user_parameters' at /etc/puppet/
> modules/zabbix/manifests/classes/mysql.pp:7 on node
> puppetclient.domain
If runs sometimes succeed and sometimes fail for the same node then
you probably have a missing dependency somewhere. If there were
exactly one missing dependency involved then the first-order estimate
would be that half your runs would fail.
> If I then do another puppet run, I do not receive the error. It seems
> that just about every other manual run during testing of new module
> changes has this happen. This is occuring on ALL my puppet clients
> that are using the zabbix::mysql module. All systems running
> Puppet-2.6.8. Below is the full debug log and my zabbix module.
>
> The $zabbix_mysql_user_parameters variable is optional...right now
> only one node has it defined explicitly, like so:
>
> $zabbix_mysql_user_parameters = {
> item1 => { 'name' => 'mediawiki.usercount[*]', 'command' =>
> 'mysql -B -s -e "SELECT count(*) FROM user" $1'},
> }
>
> This is the mysql class for zabbix where the empty variable is defined
> so that if no node has it defined it shouldn't fail...
>
> $zabbix_mysql_user_parameters = []
>
> class zabbix::mysql inherits zabbix::agent {
>
> file {
> "$zabbix_userparameter_config_dir/userparameter_mysql.conf":
> content => template("zabbix/
> userparameter_mysql_conf.erb"),
> group => "zabbix",
> owner => "zabbix",
> mode => "600",
> require => Package["zabbix-agent"];
>
> "$zabbix_user_home_dir/.my.cnf":
> source => "puppet:///modules/zabbix/.my.cnf",
> group => "zabbix",
> owner => "zabbix",
> mode => "600",
> require => [ Package["zabbix-agent"],
> File["$zabbix_user_home_dir"] ];
> }
>
> }
The variable definition is at top level in the class's file? And
you're relying on that to provide a default definition of the
variable? Ew. Now you have dynamic scoping thrown in. But that
ought to be parse-order dependent, so although it could explain some
nodes succeeding but others failing, I don't think it explains
individual nodes flopping back and forth between success and failure.
> Here's the variables usage in the template...
> <% zabbix_mysql_user_parameters.each do |key, value_hash| -%>
> UserParameter=<%= value_hash['name'] %>,HOME=<%= zabbix_user_home_dir
> %> <%= value_hash['command'] %>
> <% end -%>
>
> Would the solution be to make the template call use this instead??
>
> <% if has_variable?("zabbix_mysql_user_parameters") -%>
> <% zabbix_mysql_user_parameters.each do |key, value_hash| -%>
> UserParameter=<%= value_hash['name'] %>,HOME=<%= zabbix_user_home_dir
> %> <%= value_hash['command'] %>
> <% end -%>
> <% end -%>
Maybe. Does the node that has a customized value for the variable
ever fail? Does it always get the userparameter_mysql.conf template
filled correctly? If so then yes, your template change should do the
trick, and you could then also remove the default variable definition
(which isn't reliably working anyway).
Otherwise, probably not. That solution would likely make the errors
disappear, but it wouldn't fix the actual problem. Chances are that
nodes with customized $zabbix_mysql_user_parameters would flip flop.
In that case, the solution would probably require figuring out what
dependency is needed and putting it in.
John
--
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 error 500 when trying to view a report detail
Hello,
I have got an error 500 when I try to view a report in the dashboard
Here is the log :
ERROR: compiling
_run_haml_app47views47reports47_resource_statuses46html46haml_locals_object_report_resource_statuses
RAISED Input/output error
Function body: def
_run_haml_app47views47reports47_resource_statuses46html46haml_locals_object_report_resource_statuses(local_assigns)
old_output_buffer = output_buffer;object =
local_assigns[:object];resource_statuses =
local_assigns[:resource_statuses];report =
local_assigns[:report];;begin;extend Haml::Helpers;_hamlout = @haml_buffer =
Haml::Buffer.new(@haml_buffer, {:autoclose=>["meta", "img", "link", "br",
"hr", "input", "area", "param", "col", "base"], :ugly=>true,
:escape_html=>false, :encoding=>nil, :preserve=>["textarea", "pre", "code"],
:attr_wrapper=>"'", :format=>:xhtml});_erbout =
_hamlout.buffer;__in_erb_template = true;; if
report.resource_statuses.present?;
_hamlout.buffer << "\n\nEvents\n";
_hamlout.open_tag("a", false, true, false, false, {}, false, false, nil,
"(expand all)", :href => '#', :class => 'expand-all' );_hamlout.buffer <<
"\n\n\n";
report.resource_statuses.sort_by(&:time).each_with_index do |status,
index|;
_hamlout.open_tag("dt", false, false, false, false, {}, false, false, nil,
nil, :class => cycle( 'odd', 'even' ));_hamlout.buffer << "\n";
if status.events.empty?;
_hamlout.buffer << "#{status.name
}\n"; else;
_hamlout.buffer << "#{ link_to h(status.name), {}, {:class =>
'expandable-link collapsed-link', :id => "expand-#{index}"}
}\n";end;_hamlout.buffer << "\n"; if status.file or status.line;
_hamlout.buffer << "#{ "(#{status.file}:#{status.line})"
}\n";end;_hamlout.buffer << "\n";_hamlout.open_tag("dd", false, false,
false, false, {"class"=>"expandable collapsed"}, false, false, nil, nil, :id
=> "expandable-#{index}");_hamlout.buffer <<
"\n\nProperty\nMessage\n\n";
status.events.each do |event|;
_hamlout.open_tag("tr", false, false, false, false, {}, false, false, nil,
nil, :class => "status #{event.status}");_hamlout.buffer << "#{
event.property
}\n#{popup_md5s( h event.message )
}\n\n";end;_hamlout.buffer <<
"\n\n";end;_hamlout.buffer <<
"\n\n\n";end;_erbout;ensure;@haml_buffer =
@haml_buffer.upper;end;
ensure
self.output_buffer = old_output_buffer
end
Backtrace:
/usr/share/puppet-dashboard/app/views/reports/_resource_statuses.html.haml:25:in
`write'
ActionView::TemplateError (Input/output error) on line #25 of
app/views/reports/_resource_statuses.html.haml:
22: - status.events.each do |event|
23: %tr{:class => "status #{event.status}"}
24: %td= event.property
25: %td= popup_md5s( h event.message )
app/views/reports/_resource_statuses.html.haml:25:in `write'
Rendering /usr/share/puppet-dashboard/public/500.html (500 Internal Server
Error)
--
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 & Augeas
I`m struggling with getting puppet to do do an agueas run correctly.
When I make the modifications using augtool on the cli
Everything works like expected .
augtool --noload
augtool>
set /augeas/load/Xml/incl[last()+1]
/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml
augtool> load
augtool>
set
/files/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml/profile/settings/param[16]/#attribute/value
10.0.0.2
augtool>
set
/files/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml/profile/settings/param[17]/#attribute/value
10.0.0.2
augtool> save
Saved 1 file(s)
cat sipX_profile.xml | grep 10
When I try to do the same from puppet ..
augeas{"sipxprofile" :
changes => [
"set /augeas/load/Xml/incl[last()+1]
/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml",
"set
/files/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml/profile/settings/param[16]/#attribute/value
10.0.0.2",
"set
/files/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml/profile/settings/param[17]/#attribute/value
10.0.0.2",
],
}
I've noticed different behaviour ranging from only the changed code to
be written to disk rather than the whole file.
cat sipX_profile.xml
To actual errors "change from need_to_run to 0 failed: Save failed with
return code false" when trying to experiment with a syntax like below.
...
augeas{"sipxprofile" :
lens=> "Xml",
incl=>
"/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml",
context =>
"/files/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml",
changes => [
"set profile/settings/param[16]/#attribute/value 10.0.0.2",
"set profile/settings/param[17]/#attribute/value 10.0.0.2",
],
}
Is there some way to implement the "load" function in augeas in puppet ?
Or any documentation around regarding the correct use of lens, incl
etc ?
thnx in advance
Kris
--
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: backup files whith bad arborescence
On 3 juin, 17:26, Patrick wrote: > Out of curiosity, why do you care? i think it damage to keep this arborescence with many intermediate file. -- 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.
