Summary: facter 1.3.8 and puppet were working fine for me. facter 1.5 results in a series of " Timed out seeking value for ..." messages and make puppet unsusable. I revert to facter 1.3.8 and all works fine again. Details: Fresh install of RHEL 5.1 into a VMWare Server 1.0.6 guest. A clone of this guest was working fine with puppet (which rocks!) prior to the new version of facter. After installing the newest facter from RPMs... Installed: puppet.noarch 0:0.24.4-1.el5.selinux1 Dependency Installed: facter.noarch 0:1.5.0-2.el5 I get these errors and puppet is unusable... # puppetd --server erinbl14vm4 --waitforcert 60 --test Timed out seeking value for kernel Timed out seeking value for kernel Timed out seeking value for hostname Timed out seeking value for hostname Timed out seeking value for domain Timed out seeking value for domain Timed out seeking value for hostname info: Creating a new certificate request for .min.veritas.com info: Creating a new SSL key at /var/lib/puppet/ssl/ private_keys/.min.veritas.com.pem warning: peer certificate won''t be verified in this SSL session notice: No certificates; exiting Output of facter 1.5: # facter Timed out seeking value for kernel Timed out seeking value for kernel Timed out seeking value for kernel Timed out seeking value for kernel Timed out seeking value for kernel Timed out seeking value for kernel Timed out seeking value for kernel Timed out seeking value for kernel architecture => x86_64 domain => min.veritas.com facterversion => 1.5.0 fqdn => erinbl14vm2.min.veritas.com hardwareisa => x86_64 hardwaremodel => x86_64 hostname => erinbl14vm2 id => root interfaces => eth0,sit0,virbr0 ipaddress => 10.80.140.103 ipaddress_eth0 => 10.80.140.103 ipaddress_virbr0 => 192.168.122.1 kernel => Linux kernelrelease => 2.6.18-53.el5 lsbdistcodename => Tikanga lsbdistdescription => Red Hat Enterprise Linux Server release 5.1 (Tikanga) lsbdistid => RedHatEnterpriseServer lsbdistrelease => 5.1 lsbmajdistrelease => 5 lsbrelease => :core-3.1-amd64:core-3.1-ia32:core-3.1- noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch macaddress => 00:0C:29:87:45:B0 macaddress_eth0 => 00:0C:29:87:45:B0 macaddress_virbr0 => 00:00:00:00:00:00 memoryfree => 797.23 MB memorysize => 1003.11 MB netmask => 255.255.248.0 netmask_eth0 => 255.255.248.0 netmask_virbr0 => 255.255.255.0 operatingsystem => RedHat operatingsystemrelease => 5 ps => ps -ef puppetversion => 0.24.4 rubysitedir => /usr/lib/ruby/site_ruby/1.8 rubyversion => 1.8.5 sshdsakey => ... sshrsakey => ... swapfree => 509.87 MB swapsize => 509.87 MB uniqueid => 500a678c Output of facter when I revert to version 1.3.8: # facter --version 1.3.8 # facter architecture => x86_64 domain => min.veritas.com facterversion => 1.3.8 fqdn => erinbl14vm2.min.veritas.com hardwareisa => x86_64 hardwaremodel => x86_64 hostname => erinbl14vm2 id => root ipaddress => 10.80.140.103 ipaddress_eth0 => 10.80.140.103 ipaddress_virbr0 => 192.168.122.1 kernel => Linux kernelrelease => 2.6.18-53.el5 lsbdistcodename => Tikanga lsbdistdescription => Red Hat Enterprise Linux Server release 5.1 (Tikanga) lsbdistid => RedHatEnterpriseServer lsbdistrelease => 5.1 lsbrelease => :core-3.1-amd64:core-3.1-ia32:core-3.1- noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch macaddress => 00:0C:29:87:45:B0 macaddress_eth0 => 00:0C:29:87:45:B0 macaddress_virbr0 => 00:00:00:00:00:00 manufacturer => VMware, Inc. memoryfree => 797.68 MB memorysize => 1003.11 MB operatingsystem => RedHat operatingsystemrelease => 5 processor0 => Dual-Core AMD Opteron(tm) Processor 8218 processorcount => 1 productname => VMware Virtual Platform ps => ps -ef puppetversion => 0.24.4 rubysitedir => /usr/lib/ruby/site_ruby/1.8 rubyversion => 1.8.5 serialnumber => ... sshdsakey => ... sshrsakey => ... swapfree => 509.87 MB swapsize => 509.87 MB uniqueid => 500a678c -- Pete --~--~---------~--~----~------------~-------~--~----~ 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> Summary: > facter 1.3.8 and puppet were working fine for me. > facter 1.5 results in a series of " Timed out seeking value for ..." > messages and make puppet unsusable.there have been a bug report about that: http://reductivelabs.com/redmine/issues/show/1422 please fill your notes their. thanks. greets Pete --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Thanks Peter, it hadn''t occurred to me to check bug reports first.
As it turns out, facter 1.5 is just more sensitive to a VMWare guest with
clock problems than facter 1.3.8 is. The facter 1.5 problem goes away if I
follow the advice here to fix the clock problems:
http://kamilkisiel.blogspot.com/2008/01/vmware-linux-guest-clock.html
Specifically, I rebooted my RHEL 5.1 x86_64 kernel with the following
additional parameters:
clocksource=pit nosmp noapic nolapic
And now I get no "Timed out" messages from facter 1.5.
--
Pete
On 7/20/08, Peter Meier <peter.meier@immerda.ch>
wrote:>
>
> Hi
>
> > Summary:
> > facter 1.3.8 and puppet were working fine for me.
> > facter 1.5 results in a series of " Timed out seeking value for
..."
> > messages and make puppet unsusable.
>
> there have been a bug report about that:
> http://reductivelabs.com/redmine/issues/show/1422
>
> please fill your notes their. thanks.
>
> greets Pete
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
Hello I have this problem on Debian etch , the system is not a vmware guest . # lsb_release -a LSB Version: core-2.0-noarch:core-3.0-noarch:core-3.1- noarch:core-2.0-ia32:core-3.0-ia32:core-3.1-ia32 Distributor ID: Debian Description: Debian GNU/Linux 4.0 (etch) Release: 4.0 Codename: etch # facter Timed out seeking value for lsbdistid Timed out seeking value for lsbdistdescription Timed out seeking value for lsbrelease Timed out seeking value for lsbdistrelease Timed out seeking value for lsbdistrelease Timed out seeking value for lsbdistrelease Timed out seeking value for lsbdistid Timed out seeking value for lsbdistcodename architecture => i386 cfkey => MIIBCAKCAQEAvfUiuk+Zb1uVOx5ri/ 61SGs1A442+KyvPEDG4Rt4wxlZlZotDQsAz4ORs +gAK1NdOYqMe54R3dGrWrlv7ff0wyAK3xyYGv4G7nbhPi1+53kYYNhDZXBwLo1b5/ BBCKXtwGzi8FPzlB+FHxaCOwP7GT9GbV3K8YL8TeUfIisnDp2BBCHNQWIl8YJ1MzA +rgXyQqIrFbTtoNsSb08OCfkwhM6/ cuoMcTEt3cGvhiB2a5gpbzCB7z57OEwvGSjwQVsQhIfeDHlKfFpR +IKUSOLnGk9y1Vz7z7ULdq/H58xup7DcmCvLmDcWnJjkDz4tuqPvxu9S4FDs0rpv/ mJ3NT0dNwIBIw=facterversion => 1.5 ... On Aug 1, 4:45 am, "Pete TerMaat" <elk...@gmail.com> wrote:> Thanks Peter, it hadn''t occurred to me to check bug reports first. > > As it turns out, facter 1.5 is just more sensitive to a VMWare guest with > clock problems than facter 1.3.8 is. The facter 1.5 problem goes away if I > follow the advice here to fix the clock problems: > > http://kamilkisiel.blogspot.com/2008/01/vmware-linux-guest-clock.html > > Specifically, I rebooted my RHEL 5.1 x86_64 kernel with the following > additional parameters: > > clocksource=pit nosmp noapic nolapic > > And now I get no "Timed out" messages from facter 1.5. > > -- > Pete > > On 7/20/08, Peter Meier <peter.me...@immerda.ch> wrote: > > > > > Hi > > > > Summary: > > > facter 1.3.8 and puppet were working fine for me. > > > facter 1.5 results in a series of " Timed out seeking value for ..." > > > messages and make puppet unsusable. > > > there have been a bug report about that: > >http://reductivelabs.com/redmine/issues/show/1422 > > > please fill your notes their. thanks. > > > greets Pete > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Vincent wrote:> Hello > > I have this problem on Debian etch , the system is not a vmware > guest .It''s a known bug with 1.5.0. It''s fixed in 1.5.1. Regards James Turnbull - -- Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIv9En9hTGvAxC30ARAnE6AJ0TXOVPLje0mIdnW/2I4SCdvVVVhQCffRBE ainiHvqZnbfxoGddRUFM0Ew=mWII -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---