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...@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+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
