Hi,
On my puppet node, there are many facter variables that are empty in
my manifests.
But, there are not empty when I start "facter" on the node.
why ?
ex in a module:
class resolver {
if $::ipaddress6 {
...
}
$domainename = "$domain"
}
In this manifest, $domain and $ipaddress6 are empty
In the facter command line, there not empty.
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Hi, Can you be a little clearer on your issue? Are you saying they are empty when you compile the manifest for the node? Good things to include are logs, version number and basic set up (puppet/passenger, puppet/mongrel, puppet/webrick). Cheers, Den On 04/10/2011, at 18:52, joffrey <joff.au@gmail.com> wrote:> Hi, > > On my puppet node, there are many facter variables that are empty in > my manifests. > But, there are not empty when I start "facter" on the node. > > why ? > > ex in a module: > > class resolver { > if $::ipaddress6 { > ... > } > $domainename = "$domain" > } > > In this manifest, $domain and $ipaddress6 are empty > In the facter command line, there not empty. > > -- > 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+unsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
hmm.. I''m new too puppet and I don''t understand "compile
the manifest
for the node".
I write my manifests on the puppetmaster node.
And I test on the client node with :
puppetd --test --debug --trace
there is no error in the debug trace :
debug: [.. many auotorequiring File[/var/puppet/... ]
info: Caching catalog for puppetmaster.domain.fr
debug: Creating default schedules
debug: Loaded state in 0.00 seconds
info: Applying configuration version ''1317710581''
debug: /Schedule[never]: Skipping device resources because running on
a host
...
debug: /Stage[main]/Resolver/File[resolv.conf]/content: Executing
''diff -u /etc/resolv.conf
/tmp/puppet-file20111005-54594-14mbicj-0''
--- /etc/resolv.conf 2011-10-05 13:36:43.866046102 +0200
+++ /tmp/puppet-file20111005-54594-14mbicj-0 2011-10-05
13:37:01.470405023 +0200
@@ -1,3 +1,3 @@
-domain mydomain.fr
+domain
nameserver 1.1.1.1
nameserver 2.2.2.2
debug: Finishing transaction 17215353320
info: FileBucket got a duplicate file {md5}
84490558380d7e3f5e2475700843ced1
info: /Stage[main]/Resolver/File[resolv.conf]: Filebucketed /etc/
resolv.conf to puppet with sum 84490558380d7e3f5e2475700843ced1
notice: /Stage[main]/Resolver/File[resolv.conf]/content: content
changed ''{md5}84490558380d7e3f5e2475700843ced1'' to
''{md5}
8f6a1d5e20142e3b879651ecaf67d91a''
debug: /Stage[main]/Resolver/File[resolv.conf]: The container
resolv.conf will propagate my refresh event
debug: resolv.conf: The container Class[Resolver] will propagate my
refresh event
debug: Class[Resolver]: The container Stage[main] will propagate my
refresh event
debug: Finishing transaction 17215842100
debug: Storing state
debug: Stored state in 0.01 seconds
notice: Finished catalog run in 0.14 seconds
debug: Value of ''preferred_serialization_format'' (pson) is
invalid for
report, using default (b64_zlib_yaml)
debug: report supports formats: b64_zlib_yaml marshal raw yaml; using
b64_zlib_yaml
debug: Using cached certificate for ca
debug: Using cached certificate for puppetmaster.mydomain.fr
debug: Using cached certificate_revocation_list for ca
But, I know, with the new generated resolv.conf, that facter variables
like $domain an $ipadresse6 are empty.
puppet --version : 2.7.3
facter --version : 1.6.0
client node, puppet.conf :
[main]
server=puppetmaster.mydomain.fr
pluginsync=false
master node, puppet.conf is empty because all default variable are
good
OS: FreeBSD 8.2
puppet + mongrel + nginx
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Hi, sounds like it could be a similar issue of puppet with mongrel. This was raised recently on the list. Have a look at those. Also paste the code you are trying to apply so we can see what you''re attempting to do. Here is a link that you can use to see some tips on debugging issues. http://www.devco.net/archives/2009/08/19/tips_and_tricks_for_puppet_debugging.php Cheers, Den On 05/10/2011, at 22:44, joffrey <joff.au@gmail.com> wrote:> hmm.. I''m new too puppet and I don''t understand "compile the manifest > for the node". > I write my manifests on the puppetmaster node. > And I test on the client node with : > puppetd --test --debug --trace > there is no error in the debug trace : > > debug: [.. many auotorequiring File[/var/puppet/... ] > info: Caching catalog for puppetmaster.domain.fr > debug: Creating default schedules > debug: Loaded state in 0.00 seconds > info: Applying configuration version ''1317710581'' > debug: /Schedule[never]: Skipping device resources because running on > a host > ... > debug: /Stage[main]/Resolver/File[resolv.conf]/content: Executing > ''diff -u /etc/resolv.conf /tmp/puppet-file20111005-54594-14mbicj-0'' > --- /etc/resolv.conf 2011-10-05 13:36:43.866046102 +0200 > +++ /tmp/puppet-file20111005-54594-14mbicj-0 2011-10-05 > 13:37:01.470405023 +0200 > @@ -1,3 +1,3 @@ > -domain mydomain.fr > +domain > nameserver 1.1.1.1 > nameserver 2.2.2.2 > debug: Finishing transaction 17215353320 > info: FileBucket got a duplicate file {md5} > 84490558380d7e3f5e2475700843ced1 > info: /Stage[main]/Resolver/File[resolv.conf]: Filebucketed /etc/ > resolv.conf to puppet with sum 84490558380d7e3f5e2475700843ced1 > notice: /Stage[main]/Resolver/File[resolv.conf]/content: content > changed ''{md5}84490558380d7e3f5e2475700843ced1'' to ''{md5} > 8f6a1d5e20142e3b879651ecaf67d91a'' > debug: /Stage[main]/Resolver/File[resolv.conf]: The container > resolv.conf will propagate my refresh event > debug: resolv.conf: The container Class[Resolver] will propagate my > refresh event > debug: Class[Resolver]: The container Stage[main] will propagate my > refresh event > debug: Finishing transaction 17215842100 > debug: Storing state > debug: Stored state in 0.01 seconds > notice: Finished catalog run in 0.14 seconds > debug: Value of ''preferred_serialization_format'' (pson) is invalid for > report, using default (b64_zlib_yaml) > debug: report supports formats: b64_zlib_yaml marshal raw yaml; using > b64_zlib_yaml > debug: Using cached certificate for ca > debug: Using cached certificate for puppetmaster.mydomain.fr > debug: Using cached certificate_revocation_list for ca > > > But, I know, with the new generated resolv.conf, that facter variables > like $domain an $ipadresse6 are empty. > > puppet --version : 2.7.3 > facter --version : 1.6.0 > > client node, puppet.conf : > [main] > server=puppetmaster.mydomain.fr > pluginsync=false > > master node, puppet.conf is empty because all default variable are > good > > OS: FreeBSD 8.2 > > puppet + mongrel + nginx > > -- > 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+unsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I found it : http://projects.puppetlabs.com/issues/8342 I switch to passenger and it works now. Thanks you On 5 oct, 23:41, Denmat <tu2bg...@gmail.com> wrote:> Hi, > > sounds like it could be a similar issue of puppet with mongrel. This was raised recently on the list. Have a look at those. > > Also paste the code you are trying to apply so we can see what you''re attempting to do. > > Here is a link that you can use to see some tips on debugging issues.http://www.devco.net/archives/2009/08/19/tips_and_tricks_for_puppet_d... > > Cheers, > Den-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.