Alexander Azarov
2011-Oct-31 16:25 UTC
[Puppet Users] Incorrect "architecture" fact value during catalog run
Hi all, Can you help me diagnose a problem please? I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens is that I rely on "architecture" fact in my manifests and this fact looks correct when I run Facter and it is set to incorrect value during catalog run: r4:/var/log# facter -p | grep architecture architecture => amd64 r4:/var/log# puppet facts find r4.osinka.int ....,"architecture":"amd64",... r4:/var/log# puppet agent --test --noop info: Retrieving plugin info: Loading facts in ec2_facts info: Loading facts in ec2_facts info: Caching catalog for r4.osinka.int info: Applying configuration version ''1320071507'' notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: current_value absent, should be Architecture x86_64 (noop) Any ideas? Where to dig? Regards, Alexander Azarov -- 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/-/cUN13TbZXaMJ. 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.
Adrien Thebo
2011-Oct-31 16:43 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
What operating system is this? I''m looking at the documentation for the architecture fact, and theres this: # Resolution: # On OpenBSD, Linux and Debian''s kfreebsd, use the hardwaremodel fact. # Gentoo and Debian call "x86_86" "amd64". # Gentoo also calls "i386" "x86". On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov <alaz.at@gmail.com> wrote:> Hi all, > > Can you help me diagnose a problem please? > > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens is that I > rely on "architecture" fact in my manifests and this fact looks correct when > I run Facter and it is set to incorrect value during catalog run: > > r4:/var/log# facter -p | grep architecture > architecture => amd64 > > r4:/var/log# puppet facts find r4.osinka.int > ....,"architecture":"amd64",... > > r4:/var/log# puppet agent --test --noop > info: Retrieving plugin > info: Loading facts in ec2_facts > info: Loading facts in ec2_facts > info: Caching catalog for r4.osinka.int > info: Applying configuration version ''1320071507'' > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: > current_value absent, should be Architecture x86_64 (noop) > > Any ideas? Where to dig? > > Regards, > Alexander Azarov > > -- > 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/-/cUN13TbZXaMJ. > 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.
Alexander Azarov
2011-Oct-31 17:55 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
This is Debian 6.0.3 On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo wrote:> > What operating system is this? I''m looking at the documentation for > the architecture fact, and theres this: > > # Resolution: > # On OpenBSD, Linux and Debian''s kfreebsd, use the hardwaremodel fact. > # Gentoo and Debian call "x86_86" "amd64". > # Gentoo also calls "i386" "x86". > > On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov <ala...@gmail.com> > wrote: > > Hi all, > > > > Can you help me diagnose a problem please? > > > > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens is that I > > rely on "architecture" fact in my manifests and this fact looks correct > when > > I run Facter and it is set to incorrect value during catalog run: > > > > r4:/var/log# facter -p | grep architecture > > architecture => amd64 > > > > r4:/var/log# puppet facts find r4.osinka.int > > ....,"architecture":"amd64",... > > > > r4:/var/log# puppet agent --test --noop > > info: Retrieving plugin > > info: Loading facts in ec2_facts > > info: Loading facts in ec2_facts > > info: Caching catalog for r4.osinka.int > > info: Applying configuration version ''1320071507'' > > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: > > current_value absent, should be Architecture x86_64 (noop) > > > > Any ideas? Where to dig? > > > > Regards, > > Alexander Azarov > > > > -- > > 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/-/cUN13TbZXaMJ. > > To post to this group, send email to puppet...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users...@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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. 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.
Adrien Thebo
2011-Oct-31 18:28 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
Just as a curiosity, what web server are you using for your puppet master? On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov <alaz.at@gmail.com> wrote:> This is Debian 6.0.3 > > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo wrote: >> >> What operating system is this? I''m looking at the documentation for >> the architecture fact, and theres this: >> >> # Resolution: >> # On OpenBSD, Linux and Debian''s kfreebsd, use the hardwaremodel fact. >> # Gentoo and Debian call "x86_86" "amd64". >> # Gentoo also calls "i386" "x86". >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov <ala...@gmail.com> >> wrote: >> > Hi all, >> > >> > Can you help me diagnose a problem please? >> > >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens is that >> > I >> > rely on "architecture" fact in my manifests and this fact looks correct >> > when >> > I run Facter and it is set to incorrect value during catalog run: >> > >> > r4:/var/log# facter -p | grep architecture >> > architecture => amd64 >> > >> > r4:/var/log# puppet facts find r4.osinka.int >> > ....,"architecture":"amd64",... >> > >> > r4:/var/log# puppet agent --test --noop >> > info: Retrieving plugin >> > info: Loading facts in ec2_facts >> > info: Loading facts in ec2_facts >> > info: Caching catalog for r4.osinka.int >> > info: Applying configuration version ''1320071507'' >> > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: >> > current_value absent, should be Architecture x86_64 (noop) >> > >> > Any ideas? Where to dig? >> > >> > Regards, >> > Alexander Azarov >> > >> > -- >> > 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/-/cUN13TbZXaMJ. >> > To post to this group, send email to puppet...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users...@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 view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. > 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.
Alexander Azarov
2011-Oct-31 18:33 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
The simplest default, that is WEBrick I guess. On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote:> > Just as a curiosity, what web server are you using for your puppet master? > > On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov <ala...@gmail.com> > wrote: > > This is Debian 6.0.3 > > > > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo wrote: > >> > >> What operating system is this? I''m looking at the documentation for > >> the architecture fact, and theres this: > >> > >> # Resolution: > >> # On OpenBSD, Linux and Debian''s kfreebsd, use the hardwaremodel fact. > >> # Gentoo and Debian call "x86_86" "amd64". > >> # Gentoo also calls "i386" "x86". > >> > >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov <ala...@gmail.com> > >> wrote: > >> > Hi all, > >> > > >> > Can you help me diagnose a problem please? > >> > > >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens is > that > >> > I > >> > rely on "architecture" fact in my manifests and this fact looks > correct > >> > when > >> > I run Facter and it is set to incorrect value during catalog run: > >> > > >> > r4:/var/log# facter -p | grep architecture > >> > architecture => amd64 > >> > > >> > r4:/var/log# puppet facts find r4.osinka.int > >> > ....,"architecture":"amd64",... > >> > > >> > r4:/var/log# puppet agent --test --noop > >> > info: Retrieving plugin > >> > info: Loading facts in ec2_facts > >> > info: Loading facts in ec2_facts > >> > info: Caching catalog for r4.osinka.int > >> > info: Applying configuration version ''1320071507'' > >> > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: > >> > current_value absent, should be Architecture x86_64 (noop) > >> > > >> > Any ideas? Where to dig? > >> > > >> > Regards, > >> > Alexander Azarov > >> > > >> > -- > >> > 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/-/cUN13TbZXaMJ. > >> > To post to this group, send email to pupp...@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > puppet-...@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 view this discussion on the web visit > > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. > > To post to this group, send email to puppet...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users...@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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. 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.
Adrien Thebo
2011-Nov-03 16:27 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
Could you post the operatingsystem fact alongside the architecture fact for facter by itself, and then the facts as presented by puppet? On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov <alaz.at@gmail.com> wrote:> The simplest default, that is WEBrick I guess. > > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote: >> >> Just as a curiosity, what web server are you using for your puppet master? >> >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov <ala...@gmail.com> >> wrote: >> > This is Debian 6.0.3 >> > >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo wrote: >> >> >> >> What operating system is this? I''m looking at the documentation for >> >> the architecture fact, and theres this: >> >> >> >> # Resolution: >> >> # On OpenBSD, Linux and Debian''s kfreebsd, use the hardwaremodel >> >> fact. >> >> # Gentoo and Debian call "x86_86" "amd64". >> >> # Gentoo also calls "i386" "x86". >> >> >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov <ala...@gmail.com> >> >> wrote: >> >> > Hi all, >> >> > >> >> > Can you help me diagnose a problem please? >> >> > >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens is >> >> > that >> >> > I >> >> > rely on "architecture" fact in my manifests and this fact looks >> >> > correct >> >> > when >> >> > I run Facter and it is set to incorrect value during catalog run: >> >> > >> >> > r4:/var/log# facter -p | grep architecture >> >> > architecture => amd64 >> >> > >> >> > r4:/var/log# puppet facts find r4.osinka.int >> >> > ....,"architecture":"amd64",... >> >> > >> >> > r4:/var/log# puppet agent --test --noop >> >> > info: Retrieving plugin >> >> > info: Loading facts in ec2_facts >> >> > info: Loading facts in ec2_facts >> >> > info: Caching catalog for r4.osinka.int >> >> > info: Applying configuration version ''1320071507'' >> >> > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: >> >> > current_value absent, should be Architecture x86_64 (noop) >> >> > >> >> > Any ideas? Where to dig? >> >> > >> >> > Regards, >> >> > Alexander Azarov >> >> > >> >> > -- >> >> > 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/-/cUN13TbZXaMJ. >> >> > To post to this group, send email to pupp...@googlegroups.com. >> >> > To unsubscribe from this group, send email to >> >> > puppet-...@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 view this discussion on the web visit >> > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. >> > To post to this group, send email to puppet...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users...@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 view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. > 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.
Alexander Azarov
2011-Nov-04 05:25 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote:> > Could you post the operatingsystem fact alongside the architecture > fact for facter by itself, and then the facts as presented by puppet?r3:/var/log# facter | grep -e ''\(operatingsys\|architec\)'' architecture => amd64 operatingsystem => Debian operatingsystemrelease => 6.0.3 r3:/var/log# puppet agent --test .... notice: operatingsystem=''Debian'' architecture=''x86_64'' notice: /Stage[main]/Nginx/Notify[operatingsystem=''Debian'' architecture=''x86_64'']/message: defined ''message'' as ''operatingsystem=''Debian'' architecture=''x86_64''''> On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov <ala...@gmail.com> > wrote: > > The simplest default, that is WEBrick I guess. > > > > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote: > >> > >> Just as a curiosity, what web server are you using for your puppet > master? > >> > >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov <ala...@gmail.com> > >> wrote: > >> > This is Debian 6.0.3 > >> > > >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo wrote: > >> >> > >> >> What operating system is this? I''m looking at the documentation for > >> >> the architecture fact, and theres this: > >> >> > >> >> # Resolution: > >> >> # On OpenBSD, Linux and Debian''s kfreebsd, use the hardwaremodel > >> >> fact. > >> >> # Gentoo and Debian call "x86_86" "amd64". > >> >> # Gentoo also calls "i386" "x86". > >> >> > >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov <ala...@gmail.com> > >> >> wrote: > >> >> > Hi all, > >> >> > > >> >> > Can you help me diagnose a problem please? > >> >> > > >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens is > >> >> > that > >> >> > I > >> >> > rely on "architecture" fact in my manifests and this fact looks > >> >> > correct > >> >> > when > >> >> > I run Facter and it is set to incorrect value during catalog run: > >> >> > > >> >> > r4:/var/log# facter -p | grep architecture > >> >> > architecture => amd64 > >> >> > > >> >> > r4:/var/log# puppet facts find r4.osinka.int > >> >> > ....,"architecture":"amd64",... > >> >> > > >> >> > r4:/var/log# puppet agent --test --noop > >> >> > info: Retrieving plugin > >> >> > info: Loading facts in ec2_facts > >> >> > info: Loading facts in ec2_facts > >> >> > info: Caching catalog for r4.osinka.int > >> >> > info: Applying configuration version ''1320071507'' > >> >> > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: > >> >> > current_value absent, should be Architecture x86_64 (noop) > >> >> > > >> >> > Any ideas? Where to dig? > >> >> > > >> >> > Regards, > >> >> > Alexander Azarov > >> >> > > >> >> > -- > >> >> > 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/-/cUN13TbZXaMJ. > >> >> > To post to this group, send email to pup...@googlegroups.com. > >> >> > To unsubscribe from this group, send email to > >> >> > puppe...@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 view this discussion on the web visit > >> > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. > >> > To post to this group, send email to pupp...@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > puppet-...@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 view this discussion on the web visit > > https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. > > To post to this group, send email to puppet...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users...@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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/dXELg-ThY_AJ. 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.
Adrien Thebo
2011-Nov-04 19:34 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
Okay, that''s seriously weird. The only thing that comes to mind is that running facter on the command line is using one version of facter, and puppet''s using another. Could you post the output of facter and puppet with the architecture, operatingsystem, and facterversion facts? On Thu, Nov 3, 2011 at 10:25 PM, Alexander Azarov <alaz.at@gmail.com> wrote:> > > On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote: >> >> Could you post the operatingsystem fact alongside the architecture >> fact for facter by itself, and then the facts as presented by puppet? > > r3:/var/log# facter | grep -e ''\(operatingsys\|architec\)'' > architecture => amd64 > operatingsystem => Debian > operatingsystemrelease => 6.0.3 > > r3:/var/log# puppet agent --test > .... > notice: operatingsystem=''Debian'' architecture=''x86_64'' > notice: /Stage[main]/Nginx/Notify[operatingsystem=''Debian'' > architecture=''x86_64'']/message: defined ''message'' as > ''operatingsystem=''Debian'' architecture=''x86_64'''' > > >> >> On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov <ala...@gmail.com> >> wrote: >> > The simplest default, that is WEBrick I guess. >> > >> > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote: >> >> >> >> Just as a curiosity, what web server are you using for your puppet >> >> master? >> >> >> >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov <ala...@gmail.com> >> >> wrote: >> >> > This is Debian 6.0.3 >> >> > >> >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo wrote: >> >> >> >> >> >> What operating system is this? I''m looking at the documentation for >> >> >> the architecture fact, and theres this: >> >> >> >> >> >> # Resolution: >> >> >> # On OpenBSD, Linux and Debian''s kfreebsd, use the hardwaremodel >> >> >> fact. >> >> >> # Gentoo and Debian call "x86_86" "amd64". >> >> >> # Gentoo also calls "i386" "x86". >> >> >> >> >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov <ala...@gmail.com> >> >> >> wrote: >> >> >> > Hi all, >> >> >> > >> >> >> > Can you help me diagnose a problem please? >> >> >> > >> >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens is >> >> >> > that >> >> >> > I >> >> >> > rely on "architecture" fact in my manifests and this fact looks >> >> >> > correct >> >> >> > when >> >> >> > I run Facter and it is set to incorrect value during catalog run: >> >> >> > >> >> >> > r4:/var/log# facter -p | grep architecture >> >> >> > architecture => amd64 >> >> >> > >> >> >> > r4:/var/log# puppet facts find r4.osinka.int >> >> >> > ....,"architecture":"amd64",... >> >> >> > >> >> >> > r4:/var/log# puppet agent --test --noop >> >> >> > info: Retrieving plugin >> >> >> > info: Loading facts in ec2_facts >> >> >> > info: Loading facts in ec2_facts >> >> >> > info: Caching catalog for r4.osinka.int >> >> >> > info: Applying configuration version ''1320071507'' >> >> >> > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: >> >> >> > current_value absent, should be Architecture x86_64 (noop) >> >> >> > >> >> >> > Any ideas? Where to dig? >> >> >> > >> >> >> > Regards, >> >> >> > Alexander Azarov >> >> >> > >> >> >> > -- >> >> >> > 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/-/cUN13TbZXaMJ. >> >> >> > To post to this group, send email to pup...@googlegroups.com. >> >> >> > To unsubscribe from this group, send email to >> >> >> > puppe...@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 view this discussion on the web visit >> >> > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. >> >> > To post to this group, send email to pupp...@googlegroups.com. >> >> > To unsubscribe from this group, send email to >> >> > puppet-...@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 view this discussion on the web visit >> > https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. >> > To post to this group, send email to puppet...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users...@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 view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/dXELg-ThY_AJ. > 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.
Daniel Pittman
2011-Nov-04 19:36 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
You can see results like this if you have the same fact in multiple places; one thing to check would be what `facter --puppet` returns, since that includes any facts that were sent to the client through pluginsync. Daniel On Fri, Nov 4, 2011 at 12:34, Adrien Thebo <adrien@puppetlabs.com> wrote:> Okay, that''s seriously weird. The only thing that comes to mind is > that running facter on the command line is using one version of > facter, and puppet''s using another. Could you post the output of > facter and puppet with the architecture, operatingsystem, and > facterversion facts? > > On Thu, Nov 3, 2011 at 10:25 PM, Alexander Azarov <alaz.at@gmail.com> wrote: >> >> >> On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote: >>> >>> Could you post the operatingsystem fact alongside the architecture >>> fact for facter by itself, and then the facts as presented by puppet? >> >> r3:/var/log# facter | grep -e ''\(operatingsys\|architec\)'' >> architecture => amd64 >> operatingsystem => Debian >> operatingsystemrelease => 6.0.3 >> >> r3:/var/log# puppet agent --test >> .... >> notice: operatingsystem=''Debian'' architecture=''x86_64'' >> notice: /Stage[main]/Nginx/Notify[operatingsystem=''Debian'' >> architecture=''x86_64'']/message: defined ''message'' as >> ''operatingsystem=''Debian'' architecture=''x86_64'''' >> >> >>> >>> On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov <ala...@gmail.com> >>> wrote: >>> > The simplest default, that is WEBrick I guess. >>> > >>> > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote: >>> >> >>> >> Just as a curiosity, what web server are you using for your puppet >>> >> master? >>> >> >>> >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov <ala...@gmail.com> >>> >> wrote: >>> >> > This is Debian 6.0.3 >>> >> > >>> >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo wrote: >>> >> >> >>> >> >> What operating system is this? I''m looking at the documentation for >>> >> >> the architecture fact, and theres this: >>> >> >> >>> >> >> # Resolution: >>> >> >> # On OpenBSD, Linux and Debian''s kfreebsd, use the hardwaremodel >>> >> >> fact. >>> >> >> # Gentoo and Debian call "x86_86" "amd64". >>> >> >> # Gentoo also calls "i386" "x86". >>> >> >> >>> >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov <ala...@gmail.com> >>> >> >> wrote: >>> >> >> > Hi all, >>> >> >> > >>> >> >> > Can you help me diagnose a problem please? >>> >> >> > >>> >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens is >>> >> >> > that >>> >> >> > I >>> >> >> > rely on "architecture" fact in my manifests and this fact looks >>> >> >> > correct >>> >> >> > when >>> >> >> > I run Facter and it is set to incorrect value during catalog run: >>> >> >> > >>> >> >> > r4:/var/log# facter -p | grep architecture >>> >> >> > architecture => amd64 >>> >> >> > >>> >> >> > r4:/var/log# puppet facts find r4.osinka.int >>> >> >> > ....,"architecture":"amd64",... >>> >> >> > >>> >> >> > r4:/var/log# puppet agent --test --noop >>> >> >> > info: Retrieving plugin >>> >> >> > info: Loading facts in ec2_facts >>> >> >> > info: Loading facts in ec2_facts >>> >> >> > info: Caching catalog for r4.osinka.int >>> >> >> > info: Applying configuration version ''1320071507'' >>> >> >> > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: >>> >> >> > current_value absent, should be Architecture x86_64 (noop) >>> >> >> > >>> >> >> > Any ideas? Where to dig? >>> >> >> > >>> >> >> > Regards, >>> >> >> > Alexander Azarov >>> >> >> > >>> >> >> > -- >>> >> >> > 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/-/cUN13TbZXaMJ. >>> >> >> > To post to this group, send email to pup...@googlegroups.com. >>> >> >> > To unsubscribe from this group, send email to >>> >> >> > puppe...@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 view this discussion on the web visit >>> >> > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. >>> >> > To post to this group, send email to pupp...@googlegroups.com. >>> >> > To unsubscribe from this group, send email to >>> >> > puppet-...@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 view this discussion on the web visit >>> > https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. >>> > To post to this group, send email to puppet...@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > puppet-users...@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 view this discussion on the web visit >> https://groups.google.com/d/msg/puppet-users/-/dXELg-ThY_AJ. >> 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. > >-- ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
Alexander Azarov
2011-Nov-04 20:53 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
Yes, I had an idea I have different versions and simply searched the system for different RubyGems installations.. for no result. I have the only one. Here it is the output you requested: r3:/var/log# facter --puppet | grep ''\(archit\|facterv\|operatings\)'' architecture => amd64 facterversion => 1.6.2 operatingsystem => Debian operatingsystemrelease => 6.0.3 r3:/var/log# facter | grep ''\(archit\|facterv\|operatings\)'' architecture => amd64 facterversion => 1.6.2 operatingsystem => Debian operatingsystemrelease => 6.0.3 r3:/var/log# puppet agent --test ... notice: operatingsystem: Debian facterversion: 1.6.2 architecture: x86_64 notice: /Stage[main]/Nginx/Notify[operatingsystem: Debian facterversion: 1.6.2 architecture: x86_64]/message: defined ''message'' as ''operatingsystem: Debian facterversion: 1.6.2 architecture: x86_64'' On Friday, November 4, 2011 11:34:19 PM UTC+4, Adrien Thebo wrote:> > Okay, that''s seriously weird. The only thing that comes to mind is > that running facter on the command line is using one version of > facter, and puppet''s using another. Could you post the output of > facter and puppet with the architecture, operatingsystem, and > facterversion facts? > > On Thu, Nov 3, 2011 at 10:25 PM, Alexander Azarov <ala...@gmail.com> > wrote: > > > > > > On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote: > >> > >> Could you post the operatingsystem fact alongside the architecture > >> fact for facter by itself, and then the facts as presented by puppet? > > > > r3:/var/log# facter | grep -e ''\(operatingsys\|architec\)'' > > architecture => amd64 > > operatingsystem => Debian > > operatingsystemrelease => 6.0.3 > > > > r3:/var/log# puppet agent --test > > .... > > notice: operatingsystem=''Debian'' architecture=''x86_64'' > > notice: /Stage[main]/Nginx/Notify[operatingsystem=''Debian'' > > architecture=''x86_64'']/message: defined ''message'' as > > ''operatingsystem=''Debian'' architecture=''x86_64'''' > > > > > >> > >> On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov <ala...@gmail.com> > >> wrote: > >> > The simplest default, that is WEBrick I guess. > >> > > >> > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote: > >> >> > >> >> Just as a curiosity, what web server are you using for your puppet > >> >> master? > >> >> > >> >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov <ala...@gmail.com > > > >> >> wrote: > >> >> > This is Debian 6.0.3 > >> >> > > >> >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo wrote: > >> >> >> > >> >> >> What operating system is this? I''m looking at the documentation > for > >> >> >> the architecture fact, and theres this: > >> >> >> > >> >> >> # Resolution: > >> >> >> # On OpenBSD, Linux and Debian''s kfreebsd, use the hardwaremodel > >> >> >> fact. > >> >> >> # Gentoo and Debian call "x86_86" "amd64". > >> >> >> # Gentoo also calls "i386" "x86". > >> >> >> > >> >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov < > ala...@gmail.com> > >> >> >> wrote: > >> >> >> > Hi all, > >> >> >> > > >> >> >> > Can you help me diagnose a problem please? > >> >> >> > > >> >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens > is > >> >> >> > that > >> >> >> > I > >> >> >> > rely on "architecture" fact in my manifests and this fact looks > >> >> >> > correct > >> >> >> > when > >> >> >> > I run Facter and it is set to incorrect value during catalog > run: > >> >> >> > > >> >> >> > r4:/var/log# facter -p | grep architecture > >> >> >> > architecture => amd64 > >> >> >> > > >> >> >> > r4:/var/log# puppet facts find r4.osinka.int > >> >> >> > ....,"architecture":"amd64",... > >> >> >> > > >> >> >> > r4:/var/log# puppet agent --test --noop > >> >> >> > info: Retrieving plugin > >> >> >> > info: Loading facts in ec2_facts > >> >> >> > info: Loading facts in ec2_facts > >> >> >> > info: Caching catalog for r4.osinka.int > >> >> >> > info: Applying configuration version ''1320071507'' > >> >> >> > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: > >> >> >> > current_value absent, should be Architecture x86_64 (noop) > >> >> >> > > >> >> >> > Any ideas? Where to dig? > >> >> >> > > >> >> >> > Regards, > >> >> >> > Alexander Azarov > >> >> >> > > >> >> >> > -- > >> >> >> > 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/-/cUN13TbZXaMJ. > >> >> >> > To post to this group, send email to pup...@googlegroups.com. > >> >> >> > To unsubscribe from this group, send email to > >> >> >> > pupp...@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 view this discussion on the web visit > >> >> > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. > >> >> > To post to this group, send email to pup...@googlegroups.com. > >> >> > To unsubscribe from this group, send email to > >> >> > puppe...@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 view this discussion on the web visit > >> > https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. > >> > To post to this group, send email to pupp...@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > puppet-...@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 view this discussion on the web visit > > https://groups.google.com/d/msg/puppet-users/-/dXELg-ThY_AJ. > > To post to this group, send email to puppet...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users...@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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/9Mwav4wzIQsJ. 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.
Adrien Thebo
2011-Nov-11 19:07 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
Sorry for the slow response on this, it''s been a chaotic few days. I''m still very baffled by this. Could you do something like `find / -name ''architecture.rb''` to see if there''s any way there could be another fact definition for this? Although at this point I''m starting to suspect bogons. On Fri, Nov 4, 2011 at 1:53 PM, Alexander Azarov <alaz.at@gmail.com> wrote:> Yes, I had an idea I have different versions and simply searched the system > for different RubyGems installations.. for no result. I have the only one. > > Here it is the output you requested: > > r3:/var/log# facter --puppet | grep ''\(archit\|facterv\|operatings\)'' > architecture => amd64 > facterversion => 1.6.2 > operatingsystem => Debian > operatingsystemrelease => 6.0.3 > > > > r3:/var/log# facter | grep ''\(archit\|facterv\|operatings\)'' > architecture => amd64 > facterversion => 1.6.2 > operatingsystem => Debian > operatingsystemrelease => 6.0.3 > > > r3:/var/log# puppet agent --test > ... > notice: operatingsystem: Debian facterversion: 1.6.2 architecture: x86_64 > notice: /Stage[main]/Nginx/Notify[operatingsystem: Debian facterversion: > 1.6.2 architecture: x86_64]/message: defined ''message'' as ''operatingsystem: > Debian facterversion: 1.6.2 architecture: x86_64'' > > > On Friday, November 4, 2011 11:34:19 PM UTC+4, Adrien Thebo wrote: >> >> Okay, that''s seriously weird. The only thing that comes to mind is >> that running facter on the command line is using one version of >> facter, and puppet''s using another. Could you post the output of >> facter and puppet with the architecture, operatingsystem, and >> facterversion facts? >> >> On Thu, Nov 3, 2011 at 10:25 PM, Alexander Azarov <ala...@gmail.com> >> wrote: >> > >> > >> > On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote: >> >> >> >> Could you post the operatingsystem fact alongside the architecture >> >> fact for facter by itself, and then the facts as presented by puppet? >> > >> > r3:/var/log# facter | grep -e ''\(operatingsys\|architec\)'' >> > architecture => amd64 >> > operatingsystem => Debian >> > operatingsystemrelease => 6.0.3 >> > >> > r3:/var/log# puppet agent --test >> > .... >> > notice: operatingsystem=''Debian'' architecture=''x86_64'' >> > notice: /Stage[main]/Nginx/Notify[operatingsystem=''Debian'' >> > architecture=''x86_64'']/message: defined ''message'' as >> > ''operatingsystem=''Debian'' architecture=''x86_64'''' >> > >> > >> >> >> >> On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov <ala...@gmail.com> >> >> wrote: >> >> > The simplest default, that is WEBrick I guess. >> >> > >> >> > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote: >> >> >> >> >> >> Just as a curiosity, what web server are you using for your puppet >> >> >> master? >> >> >> >> >> >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov >> >> >> <ala...@gmail.com> >> >> >> wrote: >> >> >> > This is Debian 6.0.3 >> >> >> > >> >> >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo wrote: >> >> >> >> >> >> >> >> What operating system is this? I''m looking at the documentation >> >> >> >> for >> >> >> >> the architecture fact, and theres this: >> >> >> >> >> >> >> >> # Resolution: >> >> >> >> # On OpenBSD, Linux and Debian''s kfreebsd, use the >> >> >> >> hardwaremodel >> >> >> >> fact. >> >> >> >> # Gentoo and Debian call "x86_86" "amd64". >> >> >> >> # Gentoo also calls "i386" "x86". >> >> >> >> >> >> >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov >> >> >> >> <ala...@gmail.com> >> >> >> >> wrote: >> >> >> >> > Hi all, >> >> >> >> > >> >> >> >> > Can you help me diagnose a problem please? >> >> >> >> > >> >> >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what happens >> >> >> >> > is >> >> >> >> > that >> >> >> >> > I >> >> >> >> > rely on "architecture" fact in my manifests and this fact looks >> >> >> >> > correct >> >> >> >> > when >> >> >> >> > I run Facter and it is set to incorrect value during catalog >> >> >> >> > run: >> >> >> >> > >> >> >> >> > r4:/var/log# facter -p | grep architecture >> >> >> >> > architecture => amd64 >> >> >> >> > >> >> >> >> > r4:/var/log# puppet facts find r4.osinka.int >> >> >> >> > ....,"architecture":"amd64",... >> >> >> >> > >> >> >> >> > r4:/var/log# puppet agent --test --noop >> >> >> >> > info: Retrieving plugin >> >> >> >> > info: Loading facts in ec2_facts >> >> >> >> > info: Loading facts in ec2_facts >> >> >> >> > info: Caching catalog for r4.osinka.int >> >> >> >> > info: Applying configuration version ''1320071507'' >> >> >> >> > notice: /Stage[main]/Nginx/Notify[Architecture x86_64]/message: >> >> >> >> > current_value absent, should be Architecture x86_64 (noop) >> >> >> >> > >> >> >> >> > Any ideas? Where to dig? >> >> >> >> > >> >> >> >> > Regards, >> >> >> >> > Alexander Azarov >> >> >> >> > >> >> >> >> > -- >> >> >> >> > 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/-/cUN13TbZXaMJ. >> >> >> >> > To post to this group, send email to pup...@googlegroups.com. >> >> >> >> > To unsubscribe from this group, send email to >> >> >> >> > pupp...@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 view this discussion on the web visit >> >> >> > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. >> >> >> > To post to this group, send email to pup...@googlegroups.com. >> >> >> > To unsubscribe from this group, send email to >> >> >> > puppe...@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 view this discussion on the web visit >> >> > https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. >> >> > To post to this group, send email to pupp...@googlegroups.com. >> >> > To unsubscribe from this group, send email to >> >> > puppet-...@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 view this discussion on the web visit >> > https://groups.google.com/d/msg/puppet-users/-/dXELg-ThY_AJ. >> > To post to this group, send email to puppet...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users...@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 view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/9Mwav4wzIQsJ. > 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. >-- Adrien Thebo | Puppet Labs pgp: 0x6F1C4519 pgp.mit.edu -- 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.
Alexander Azarov
2011-Nov-12 07:01 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
No problems, I''ve isolated the part of manifest that depends on "architecture", so everything works through a hack right now. # find / -name architecture.rb /usr/lib/ruby/vendor_ruby/facter/architecture.rb /var/lib/vservers/worker/usr/lib/ruby/1.8/facter/architecture.rb /var/lib/vservers/mongo/usr/lib/ruby/1.8/facter/architecture.rb On Friday, November 11, 2011 11:07:42 PM UTC+4, Adrien Thebo wrote:> > Sorry for the slow response on this, it''s been a chaotic few days. I''m > still very baffled by this. Could you do something like `find / -name > ''architecture.rb''` to see if there''s any way there could be another > fact definition for this? Although at this point I''m starting to > suspect bogons. > > On Fri, Nov 4, 2011 at 1:53 PM, Alexander Azarov <ala...@gmail.com> wrote: > > Yes, I had an idea I have different versions and simply searched the > system > > for different RubyGems installations.. for no result. I have the only > one. > > > > Here it is the output you requested: > > > > r3:/var/log# facter --puppet | grep ''\(archit\|facterv\|operatings\)'' > > architecture => amd64 > > facterversion => 1.6.2 > > operatingsystem => Debian > > operatingsystemrelease => 6.0.3 > > > > > > > > r3:/var/log# facter | grep ''\(archit\|facterv\|operatings\)'' > > architecture => amd64 > > facterversion => 1.6.2 > > operatingsystem => Debian > > operatingsystemrelease => 6.0.3 > > > > > > r3:/var/log# puppet agent --test > > ... > > notice: operatingsystem: Debian facterversion: 1.6.2 architecture: x86_64 > > notice: /Stage[main]/Nginx/Notify[operatingsystem: Debian facterversion: > > 1.6.2 architecture: x86_64]/message: defined ''message'' as > ''operatingsystem: > > Debian facterversion: 1.6.2 architecture: x86_64'' > > > > > > On Friday, November 4, 2011 11:34:19 PM UTC+4, Adrien Thebo wrote: > >> > >> Okay, that''s seriously weird. The only thing that comes to mind is > >> that running facter on the command line is using one version of > >> facter, and puppet''s using another. Could you post the output of > >> facter and puppet with the architecture, operatingsystem, and > >> facterversion facts? > >> > >> On Thu, Nov 3, 2011 at 10:25 PM, Alexander Azarov <ala...@gmail.com> > >> wrote: > >> > > >> > > >> > On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote: > >> >> > >> >> Could you post the operatingsystem fact alongside the architecture > >> >> fact for facter by itself, and then the facts as presented by puppet? > >> > > >> > r3:/var/log# facter | grep -e ''\(operatingsys\|architec\)'' > >> > architecture => amd64 > >> > operatingsystem => Debian > >> > operatingsystemrelease => 6.0.3 > >> > > >> > r3:/var/log# puppet agent --test > >> > .... > >> > notice: operatingsystem=''Debian'' architecture=''x86_64'' > >> > notice: /Stage[main]/Nginx/Notify[operatingsystem=''Debian'' > >> > architecture=''x86_64'']/message: defined ''message'' as > >> > ''operatingsystem=''Debian'' architecture=''x86_64'''' > >> > > >> > > >> >> > >> >> On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov <ala...@gmail.com > > > >> >> wrote: > >> >> > The simplest default, that is WEBrick I guess. > >> >> > > >> >> > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote: > >> >> >> > >> >> >> Just as a curiosity, what web server are you using for your puppet > >> >> >> master? > >> >> >> > >> >> >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov > >> >> >> <ala...@gmail.com> > >> >> >> wrote: > >> >> >> > This is Debian 6.0.3 > >> >> >> > > >> >> >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo > wrote: > >> >> >> >> > >> >> >> >> What operating system is this? I''m looking at the documentation > >> >> >> >> for > >> >> >> >> the architecture fact, and theres this: > >> >> >> >> > >> >> >> >> # Resolution: > >> >> >> >> # On OpenBSD, Linux and Debian''s kfreebsd, use the > >> >> >> >> hardwaremodel > >> >> >> >> fact. > >> >> >> >> # Gentoo and Debian call "x86_86" "amd64". > >> >> >> >> # Gentoo also calls "i386" "x86". > >> >> >> >> > >> >> >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov > >> >> >> >> <ala...@gmail.com> > >> >> >> >> wrote: > >> >> >> >> > Hi all, > >> >> >> >> > > >> >> >> >> > Can you help me diagnose a problem please? > >> >> >> >> > > >> >> >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what > happens > >> >> >> >> > is > >> >> >> >> > that > >> >> >> >> > I > >> >> >> >> > rely on "architecture" fact in my manifests and this fact > looks > >> >> >> >> > correct > >> >> >> >> > when > >> >> >> >> > I run Facter and it is set to incorrect value during catalog > >> >> >> >> > run: > >> >> >> >> > > >> >> >> >> > r4:/var/log# facter -p | grep architecture > >> >> >> >> > architecture => amd64 > >> >> >> >> > > >> >> >> >> > r4:/var/log# puppet facts find r4.osinka.int > >> >> >> >> > ....,"architecture":"amd64",... > >> >> >> >> > > >> >> >> >> > r4:/var/log# puppet agent --test --noop > >> >> >> >> > info: Retrieving plugin > >> >> >> >> > info: Loading facts in ec2_facts > >> >> >> >> > info: Loading facts in ec2_facts > >> >> >> >> > info: Caching catalog for r4.osinka.int > >> >> >> >> > info: Applying configuration version ''1320071507'' > >> >> >> >> > notice: /Stage[main]/Nginx/Notify[Architecture > x86_64]/message: > >> >> >> >> > current_value absent, should be Architecture x86_64 (noop) > >> >> >> >> > > >> >> >> >> > Any ideas? Where to dig? > >> >> >> >> > > >> >> >> >> > Regards, > >> >> >> >> > Alexander Azarov > >> >> >> >> > > >> >> >> >> > -- > >> >> >> >> > 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/-/cUN13TbZXaMJ. > >> >> >> >> > To post to this group, send email to pup...@googlegroups.com > . > >> >> >> >> > To unsubscribe from this group, send email to > >> >> >> >> > pup...@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 view this discussion on the web visit > >> >> >> > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. > >> >> >> > To post to this group, send email to pup...@googlegroups.com. > >> >> >> > To unsubscribe from this group, send email to > >> >> >> > pupp...@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 view this discussion on the web visit > >> >> > https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. > >> >> > To post to this group, send email to pup...@googlegroups.com. > >> >> > To unsubscribe from this group, send email to > >> >> > puppe...@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 view this discussion on the web visit > >> > https://groups.google.com/d/msg/puppet-users/-/dXELg-ThY_AJ. > >> > To post to this group, send email to pupp...@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > puppet-...@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 view this discussion on the web visit > > https://groups.google.com/d/msg/puppet-users/-/9Mwav4wzIQsJ. > > To post to this group, send email to puppet...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > -- > Adrien Thebo | Puppet Labs > pgp: 0x6F1C4519 pgp.mit.edu > >-- 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/-/n8DbrLLp2z4J. 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.
Adrien Thebo
2011-Nov-13 00:08 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
Could you get the versions of facter in /usr/lib/ruby/vendor_ruby/facter.rb and /usr/lib/vservers/*/usr/lib/ruby/1.8/facter.rb and see if they differ? On Fri, Nov 11, 2011 at 11:01 PM, Alexander Azarov <alaz.at@gmail.com> wrote:> No problems, I''ve isolated the part of manifest that depends on > "architecture", so everything works through a hack right now. > > # find / -name architecture.rb > /usr/lib/ruby/vendor_ruby/facter/architecture.rb > /var/lib/vservers/worker/usr/lib/ruby/1.8/facter/architecture.rb > /var/lib/vservers/mongo/usr/lib/ruby/1.8/facter/architecture.rb > > > On Friday, November 11, 2011 11:07:42 PM UTC+4, Adrien Thebo wrote: >> >> Sorry for the slow response on this, it''s been a chaotic few days. I''m >> still very baffled by this. Could you do something like `find / -name >> ''architecture.rb''` to see if there''s any way there could be another >> fact definition for this? Although at this point I''m starting to >> suspect bogons. >> >> On Fri, Nov 4, 2011 at 1:53 PM, Alexander Azarov <ala...@gmail.com> wrote: >> > Yes, I had an idea I have different versions and simply searched the >> > system >> > for different RubyGems installations.. for no result. I have the only >> > one. >> > >> > Here it is the output you requested: >> > >> > r3:/var/log# facter --puppet | grep ''\(archit\|facterv\|operatings\)'' >> > architecture => amd64 >> > facterversion => 1.6.2 >> > operatingsystem => Debian >> > operatingsystemrelease => 6.0.3 >> > >> > >> > >> > r3:/var/log# facter | grep ''\(archit\|facterv\|operatings\)'' >> > architecture => amd64 >> > facterversion => 1.6.2 >> > operatingsystem => Debian >> > operatingsystemrelease => 6.0.3 >> > >> > >> > r3:/var/log# puppet agent --test >> > ... >> > notice: operatingsystem: Debian facterversion: 1.6.2 architecture: >> > x86_64 >> > notice: /Stage[main]/Nginx/Notify[operatingsystem: Debian facterversion: >> > 1.6.2 architecture: x86_64]/message: defined ''message'' as >> > ''operatingsystem: >> > Debian facterversion: 1.6.2 architecture: x86_64'' >> > >> > >> > On Friday, November 4, 2011 11:34:19 PM UTC+4, Adrien Thebo wrote: >> >> >> >> Okay, that''s seriously weird. The only thing that comes to mind is >> >> that running facter on the command line is using one version of >> >> facter, and puppet''s using another. Could you post the output of >> >> facter and puppet with the architecture, operatingsystem, and >> >> facterversion facts? >> >> >> >> On Thu, Nov 3, 2011 at 10:25 PM, Alexander Azarov <ala...@gmail.com> >> >> wrote: >> >> > >> >> > >> >> > On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote: >> >> >> >> >> >> Could you post the operatingsystem fact alongside the architecture >> >> >> fact for facter by itself, and then the facts as presented by >> >> >> puppet? >> >> > >> >> > r3:/var/log# facter | grep -e ''\(operatingsys\|architec\)'' >> >> > architecture => amd64 >> >> > operatingsystem => Debian >> >> > operatingsystemrelease => 6.0.3 >> >> > >> >> > r3:/var/log# puppet agent --test >> >> > .... >> >> > notice: operatingsystem=''Debian'' architecture=''x86_64'' >> >> > notice: /Stage[main]/Nginx/Notify[operatingsystem=''Debian'' >> >> > architecture=''x86_64'']/message: defined ''message'' as >> >> > ''operatingsystem=''Debian'' architecture=''x86_64'''' >> >> > >> >> > >> >> >> >> >> >> On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov >> >> >> <ala...@gmail.com> >> >> >> wrote: >> >> >> > The simplest default, that is WEBrick I guess. >> >> >> > >> >> >> > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote: >> >> >> >> >> >> >> >> Just as a curiosity, what web server are you using for your >> >> >> >> puppet >> >> >> >> master? >> >> >> >> >> >> >> >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov >> >> >> >> <ala...@gmail.com> >> >> >> >> wrote: >> >> >> >> > This is Debian 6.0.3 >> >> >> >> > >> >> >> >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo >> >> >> >> > wrote: >> >> >> >> >> >> >> >> >> >> What operating system is this? I''m looking at the >> >> >> >> >> documentation >> >> >> >> >> for >> >> >> >> >> the architecture fact, and theres this: >> >> >> >> >> >> >> >> >> >> # Resolution: >> >> >> >> >> # On OpenBSD, Linux and Debian''s kfreebsd, use the >> >> >> >> >> hardwaremodel >> >> >> >> >> fact. >> >> >> >> >> # Gentoo and Debian call "x86_86" "amd64". >> >> >> >> >> # Gentoo also calls "i386" "x86". >> >> >> >> >> >> >> >> >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov >> >> >> >> >> <ala...@gmail.com> >> >> >> >> >> wrote: >> >> >> >> >> > Hi all, >> >> >> >> >> > >> >> >> >> >> > Can you help me diagnose a problem please? >> >> >> >> >> > >> >> >> >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what >> >> >> >> >> > happens >> >> >> >> >> > is >> >> >> >> >> > that >> >> >> >> >> > I >> >> >> >> >> > rely on "architecture" fact in my manifests and this fact >> >> >> >> >> > looks >> >> >> >> >> > correct >> >> >> >> >> > when >> >> >> >> >> > I run Facter and it is set to incorrect value during catalog >> >> >> >> >> > run: >> >> >> >> >> > >> >> >> >> >> > r4:/var/log# facter -p | grep architecture >> >> >> >> >> > architecture => amd64 >> >> >> >> >> > >> >> >> >> >> > r4:/var/log# puppet facts find r4.osinka.int >> >> >> >> >> > ....,"architecture":"amd64",... >> >> >> >> >> > >> >> >> >> >> > r4:/var/log# puppet agent --test --noop >> >> >> >> >> > info: Retrieving plugin >> >> >> >> >> > info: Loading facts in ec2_facts >> >> >> >> >> > info: Loading facts in ec2_facts >> >> >> >> >> > info: Caching catalog for r4.osinka.int >> >> >> >> >> > info: Applying configuration version ''1320071507'' >> >> >> >> >> > notice: /Stage[main]/Nginx/Notify[Architecture >> >> >> >> >> > x86_64]/message: >> >> >> >> >> > current_value absent, should be Architecture x86_64 (noop) >> >> >> >> >> > >> >> >> >> >> > Any ideas? Where to dig? >> >> >> >> >> > >> >> >> >> >> > Regards, >> >> >> >> >> > Alexander Azarov >> >> >> >> >> > >> >> >> >> >> > -- >> >> >> >> >> > 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/-/cUN13TbZXaMJ. >> >> >> >> >> > To post to this group, send email to >> >> >> >> >> > pup...@googlegroups.com. >> >> >> >> >> > To unsubscribe from this group, send email to >> >> >> >> >> > pup...@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 view this discussion on the web visit >> >> >> >> > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. >> >> >> >> > To post to this group, send email to pup...@googlegroups.com. >> >> >> >> > To unsubscribe from this group, send email to >> >> >> >> > pupp...@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 view this discussion on the web visit >> >> >> > https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. >> >> >> > To post to this group, send email to pup...@googlegroups.com. >> >> >> > To unsubscribe from this group, send email to >> >> >> > puppe...@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 view this discussion on the web visit >> >> > https://groups.google.com/d/msg/puppet-users/-/dXELg-ThY_AJ. >> >> > To post to this group, send email to pupp...@googlegroups.com. >> >> > To unsubscribe from this group, send email to >> >> > puppet-...@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 view this discussion on the web visit >> > https://groups.google.com/d/msg/puppet-users/-/9Mwav4wzIQsJ. >> > To post to this group, send email to puppet...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/puppet-users?hl=en. >> > >> >> -- >> >> Adrien Thebo | Puppet Labs >> pgp: 0x6F1C4519 pgp.mit.edu > > -- > 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/-/n8DbrLLp2z4J. > 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. >-- Adrien Thebo | Puppet Labs pgp: 0x6F1C4519 pgp.mit.edu -- 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.
R.I.Pienaar
2011-Nov-13 00:12 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
----- Original Message -----> Could you get the versions of facter in > /usr/lib/ruby/vendor_ruby/facter.rb and > /usr/lib/vservers/*/usr/lib/ruby/1.8/facter.rb and see if they > differ?Not been following this thread but this kind of wrong facts was previously observed under heavily loaded webrick based installs. What web server are you using? -- 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.
Alexander Azarov
2011-Nov-13 14:31 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
On Sunday, November 13, 2011 4:08:37 AM UTC+4, Adrien Thebo wrote:> > Could you get the versions of facter in > /usr/lib/ruby/vendor_ruby/facter.rb and >1.6.2> /usr/lib/vservers/*/usr/lib/ruby/1.8/facter.rb and see if they differ?Old (1.5.x), but these are old vservers, not in use. I can safely remove them, but I doubt it will help.> On Fri, Nov 11, 2011 at 11:01 PM, Alexander Azarov <ala...@gmail.com> > wrote: > > No problems, I''ve isolated the part of manifest that depends on > > "architecture", so everything works through a hack right now. > > > > # find / -name architecture.rb > > /usr/lib/ruby/vendor_ruby/facter/architecture.rb > > /var/lib/vservers/worker/usr/lib/ruby/1.8/facter/architecture.rb > > /var/lib/vservers/mongo/usr/lib/ruby/1.8/facter/architecture.rb > > > > > > On Friday, November 11, 2011 11:07:42 PM UTC+4, Adrien Thebo wrote: > >> > >> Sorry for the slow response on this, it''s been a chaotic few days. I''m > >> still very baffled by this. Could you do something like `find / -name > >> ''architecture.rb''` to see if there''s any way there could be another > >> fact definition for this? Although at this point I''m starting to > >> suspect bogons. > >> > >> On Fri, Nov 4, 2011 at 1:53 PM, Alexander Azarov <ala...@gmail.com> > wrote: > >> > Yes, I had an idea I have different versions and simply searched the > >> > system > >> > for different RubyGems installations.. for no result. I have the only > >> > one. > >> > > >> > Here it is the output you requested: > >> > > >> > r3:/var/log# facter --puppet | grep ''\(archit\|facterv\|operatings\)'' > >> > architecture => amd64 > >> > facterversion => 1.6.2 > >> > operatingsystem => Debian > >> > operatingsystemrelease => 6.0.3 > >> > > >> > > >> > > >> > r3:/var/log# facter | grep ''\(archit\|facterv\|operatings\)'' > >> > architecture => amd64 > >> > facterversion => 1.6.2 > >> > operatingsystem => Debian > >> > operatingsystemrelease => 6.0.3 > >> > > >> > > >> > r3:/var/log# puppet agent --test > >> > ... > >> > notice: operatingsystem: Debian facterversion: 1.6.2 architecture: > >> > x86_64 > >> > notice: /Stage[main]/Nginx/Notify[operatingsystem: Debian > facterversion: > >> > 1.6.2 architecture: x86_64]/message: defined ''message'' as > >> > ''operatingsystem: > >> > Debian facterversion: 1.6.2 architecture: x86_64'' > >> > > >> > > >> > On Friday, November 4, 2011 11:34:19 PM UTC+4, Adrien Thebo wrote: > >> >> > >> >> Okay, that''s seriously weird. The only thing that comes to mind is > >> >> that running facter on the command line is using one version of > >> >> facter, and puppet''s using another. Could you post the output of > >> >> facter and puppet with the architecture, operatingsystem, and > >> >> facterversion facts? > >> >> > >> >> On Thu, Nov 3, 2011 at 10:25 PM, Alexander Azarov <ala...@gmail.com> > >> >> wrote: > >> >> > > >> >> > > >> >> > On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote: > >> >> >> > >> >> >> Could you post the operatingsystem fact alongside the architecture > >> >> >> fact for facter by itself, and then the facts as presented by > >> >> >> puppet? > >> >> > > >> >> > r3:/var/log# facter | grep -e ''\(operatingsys\|architec\)'' > >> >> > architecture => amd64 > >> >> > operatingsystem => Debian > >> >> > operatingsystemrelease => 6.0.3 > >> >> > > >> >> > r3:/var/log# puppet agent --test > >> >> > .... > >> >> > notice: operatingsystem=''Debian'' architecture=''x86_64'' > >> >> > notice: /Stage[main]/Nginx/Notify[operatingsystem=''Debian'' > >> >> > architecture=''x86_64'']/message: defined ''message'' as > >> >> > ''operatingsystem=''Debian'' architecture=''x86_64'''' > >> >> > > >> >> > > >> >> >> > >> >> >> On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov > >> >> >> <ala...@gmail.com> > >> >> >> wrote: > >> >> >> > The simplest default, that is WEBrick I guess. > >> >> >> > > >> >> >> > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo > wrote: > >> >> >> >> > >> >> >> >> Just as a curiosity, what web server are you using for your > >> >> >> >> puppet > >> >> >> >> master? > >> >> >> >> > >> >> >> >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov > >> >> >> >> <ala...@gmail.com> > >> >> >> >> wrote: > >> >> >> >> > This is Debian 6.0.3 > >> >> >> >> > > >> >> >> >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo > >> >> >> >> > wrote: > >> >> >> >> >> > >> >> >> >> >> What operating system is this? I''m looking at the > >> >> >> >> >> documentation > >> >> >> >> >> for > >> >> >> >> >> the architecture fact, and theres this: > >> >> >> >> >> > >> >> >> >> >> # Resolution: > >> >> >> >> >> # On OpenBSD, Linux and Debian''s kfreebsd, use the > >> >> >> >> >> hardwaremodel > >> >> >> >> >> fact. > >> >> >> >> >> # Gentoo and Debian call "x86_86" "amd64". > >> >> >> >> >> # Gentoo also calls "i386" "x86". > >> >> >> >> >> > >> >> >> >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov > >> >> >> >> >> <ala...@gmail.com> > >> >> >> >> >> wrote: > >> >> >> >> >> > Hi all, > >> >> >> >> >> > > >> >> >> >> >> > Can you help me diagnose a problem please? > >> >> >> >> >> > > >> >> >> >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what > >> >> >> >> >> > happens > >> >> >> >> >> > is > >> >> >> >> >> > that > >> >> >> >> >> > I > >> >> >> >> >> > rely on "architecture" fact in my manifests and this fact > >> >> >> >> >> > looks > >> >> >> >> >> > correct > >> >> >> >> >> > when > >> >> >> >> >> > I run Facter and it is set to incorrect value during > catalog > >> >> >> >> >> > run: > >> >> >> >> >> > > >> >> >> >> >> > r4:/var/log# facter -p | grep architecture > >> >> >> >> >> > architecture => amd64 > >> >> >> >> >> > > >> >> >> >> >> > r4:/var/log# puppet facts find r4.osinka.int > >> >> >> >> >> > ....,"architecture":"amd64",... > >> >> >> >> >> > > >> >> >> >> >> > r4:/var/log# puppet agent --test --noop > >> >> >> >> >> > info: Retrieving plugin > >> >> >> >> >> > info: Loading facts in ec2_facts > >> >> >> >> >> > info: Loading facts in ec2_facts > >> >> >> >> >> > info: Caching catalog for r4.osinka.int > >> >> >> >> >> > info: Applying configuration version ''1320071507'' > >> >> >> >> >> > notice: /Stage[main]/Nginx/Notify[Architecture > >> >> >> >> >> > x86_64]/message: > >> >> >> >> >> > current_value absent, should be Architecture x86_64 (noop) > >> >> >> >> >> > > >> >> >> >> >> > Any ideas? Where to dig? > >> >> >> >> >> > > >> >> >> >> >> > Regards, > >> >> >> >> >> > Alexander Azarov > >> >> >> >> >> > > >> >> >> >> >> > -- > >> >> >> >> >> > 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/-/cUN13TbZXaMJ. > >> >> >> >> >> > To post to this group, send email to > >> >> >> >> >> > pup...@googlegroups.com. > >> >> >> >> >> > To unsubscribe from this group, send email to > >> >> >> >> >> > pup...@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 view this discussion on the web visit > >> >> >> >> > https://groups.google.com/d/msg/puppet-users/-/Y16JfpyutBUJ. > >> >> >> >> > To post to this group, send email to pup...@googlegroups.com > . > >> >> >> >> > To unsubscribe from this group, send email to > >> >> >> >> > pup...@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 view this discussion on the web visit > >> >> >> > https://groups.google.com/d/msg/puppet-users/-/p4LKkKnYaJcJ. > >> >> >> > To post to this group, send email to pup...@googlegroups.com. > >> >> >> > To unsubscribe from this group, send email to > >> >> >> > pupp...@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 view this discussion on the web visit > >> >> > https://groups.google.com/d/msg/puppet-users/-/dXELg-ThY_AJ. > >> >> > To post to this group, send email to pup...@googlegroups.com. > >> >> > To unsubscribe from this group, send email to > >> >> > puppe...@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 view this discussion on the web visit > >> > https://groups.google.com/d/msg/puppet-users/-/9Mwav4wzIQsJ. > >> > To post to this group, send email to pupp...@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > puppet-...@googlegroups.com. > >> > For more options, visit this group at > >> > http://groups.google.com/group/puppet-users?hl=en. > >> > > >> > >> -- > >> > >> Adrien Thebo | Puppet Labs > >> pgp: 0x6F1C4519 pgp.mit.edu > > > > -- > > 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/-/n8DbrLLp2z4J. > > To post to this group, send email to puppet...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > -- > Adrien Thebo | Puppet Labs > pgp: 0x6F1C4519 pgp.mit.edu > >-- 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/-/o8wpPhsVtcIJ. 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.
Alexander Azarov
2011-Nov-13 14:33 UTC
Re: [Puppet Users] Incorrect "architecture" fact value during catalog run
On Sunday, November 13, 2011 4:12:51 AM UTC+4, R.I. Pienaar wrote:> > ----- Original Message ----- > > Could you get the versions of facter in > > /usr/lib/ruby/vendor_ruby/facter.rb and > > /usr/lib/vservers/*/usr/lib/ruby/1.8/facter.rb and see if they > > differ? > > > Not been following this thread but this kind of wrong facts was > previously observed under heavily loaded webrick based installs. > > What web server are you using? >Yes, I''m using WEBrick, but my setup is very far from heavy load. I have only 4 servers under Puppet control. -- 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/-/0lThruNGYFYJ. 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.