thr3ads.net - Puppet users - Still having factsync trouble ... [Apr 2007]

If this information is useful, please help other people find it:
Share via:

Ben

2007-Apr-17 04:34 UTC

Still having factsync trouble ...

Some time ago i sent to the list a problem i was having with facts on 
fedora core 6 and wasn''t able to find a solution at that time, but with
the release of RHEL5 and CentOS 5 based on fc6 i have hit the problem again.

i have written several facts to collect information about a clients 
network and i am also using the vmware fact from the wiki.  i have 
separated my original fact into several smaller facts in an effort to 
find the fault.  i have been using these facts successfully on CentOS 4 
for months.

After the facts are run on a fc6, rhel5 or centos5 client puppet stops. 
i have added a ''puts'' at the end of each fact to show when
they are each
complete and the output shows that each fact is being executed to 
completion, note the "Finshed....." at the bottom of the output below.
puppet will sit indefinitely until interrupted with ctrl+c.

The facts work perfectly well on fc5 and centos4 clients.

I have tested i386 and x86_64 arch and both do the same, i have tested 
on vmware and physical and both do the same.  puppet does NOT stop when 
called with the "-o" (once) command line option, when using
"-o"
everything runs perfectly and to completion.

I have attached my facts and would appreciate if someone could test them 
and possibly shed some light on where puppet is stopping.  I find it 
really interesting that it runs fine when the "-o" (once) command line
option is specified.

below is the output from `puppetd --debug --factsync`

Ben

    # rm -rf /var/lib/puppet/facts/*   
    # puppetd --debug --trace --factsync
    /usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
    writable dir /home/INTERNAL, mode 041777
    /usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
    writable dir /home/INTERNAL, mode 041777
    /usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
    writable dir /home/INTERNAL, mode 041777
    /usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
    writable dir /home/INTERNAL, mode 041777
    /usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
    writable dir /home/INTERNAL, mode 041777
    debug: puppet: Setting vardir to ''/var/lib/puppet''
    debug: puppet: Setting logdir to ''/var/log/puppet''
    debug: puppet: Setting rundir to ''/var/run/puppet''
    debug: puppet: Setting ssldir to ''$vardir/ssl''
    debug: puppet: Setting report to ''true''
    debug: puppet: Setting autoflush to ''true''
    debug: puppetd: Setting classfile to ''$vardir/classes.txt''
    debug: puppetd: Setting localconfig to
''$vardir/localconfig''
    /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:229: warning: Insecure
    world writable dir /home/INTERNAL, mode 041777
    debug: /puppetconfig/puppet/File[/var/lib/puppet/plugins]:
    Autorequiring File[/var/lib/puppet]
    debug: /puppetconfig/puppetd/File[/var/lib/puppet/classes.txt]:
    Autorequiring File[/var/lib/puppet]
    debug: /puppetconfig/puppet/File[/var/lib/puppet/facts]:
    Autorequiring File[/var/lib/puppet]
    debug: /puppetconfig/puppet/File[/etc/puppet/namespaceauth.conf]:
    Autorequiring File[/etc/puppet]
    debug: /puppetconfig/puppet/File[/var/lib/puppet/state/graphs]:
    Autorequiring File[/var/lib/puppet/state]
    debug: /puppetconfig/puppetd/File[/var/log/puppet/puppetd.log]:
    Autorequiring File[/var/log/puppet]
    debug: /puppetconfig/puppet/File[/var/lib/puppet/state]:
    Autorequiring File[/var/lib/puppet]
    debug: /puppetconfig/puppetd/File[/var/log/puppet/http.log]:
    Autorequiring File[/var/log/puppet]
    debug: /puppetconfig/puppet/File[/var/lib/puppet/lib]: Autorequiring
    File[/var/lib/puppet]
    debug:
    /puppetconfig/puppetd/File[/var/lib/puppet/state/puppetdlock]:
    Autorequiring File[/var/lib/puppet/state]
    debug: /puppetconfig/puppet/File[/var/lib/puppet/state/state.yaml]:
    Autorequiring File[/var/lib/puppet/state]
    debug: /puppetconfig/puppet/File[/var/lib/puppet/templates]:
    Autorequiring File[/var/lib/puppet]
    debug: /puppetconfig/puppetd/File[/var/lib/puppet/localconfig]:
    Autorequiring File[/var/lib/puppet]
    debug: /puppetconfig/puppet/File[/var/lib/puppet/ssl]: Autorequiring
    File[/var/lib/puppet]
    debug: /puppetconfig/puppetd/File[/var/lib/puppet/localconfig]: File
    does not exist
    debug: /puppetconfig/puppetd/File[/var/lib/puppet/localconfig]:
    Changing owner,mode
    debug: /puppetconfig/puppetd/File[/var/lib/puppet/localconfig]: 2
    change(s)
    debug:
    /puppetconfig/puppetd/File[/var/lib/puppet/localconfig]/owner: File
    does not exist; cannot set owner
    debug: /puppetconfig/puppetd/File[/var/lib/puppet/localconfig]/mode:
    File does not exist; cannot set mode
    debug: /puppetconfig/puppetd/File[/var/log/puppet/http.log]: File
    does not exist
    debug: /puppetconfig/puppetd/File[/var/log/puppet/http.log]:
    Changing owner,mode
    debug: /puppetconfig/puppetd/File[/var/log/puppet/http.log]: 2 change(s)
    debug: /puppetconfig/puppetd/File[/var/log/puppet/http.log]/owner:
    File does not exist; cannot set owner
    debug: /puppetconfig/puppetd/File[/var/log/puppet/http.log]/mode:
    File does not exist; cannot set mode
    debug: /puppetconfig/puppet/File[/var/lib/puppet/state/state.yaml]:
    Changing mode
    debug: /puppetconfig/puppet/File[/var/lib/puppet/state/state.yaml]:
    1 change(s)
    debug:
    /puppetconfig/puppet/File[/var/lib/puppet/state/state.yaml]/mode:
    mode changed ''640'' to ''660''
    debug:
    /puppetconfig/puppetd/File[/var/lib/puppet/state/puppetdlock]: File
    does not exist
    debug: /puppetconfig/puppet/File[/etc/puppet/namespaceauth.conf]:
    File does not exist
    debug: /puppetconfig/puppetd/File[/var/log/puppet/puppetd.log]: File
    does not exist
    debug: /puppetconfig/puppetd/File[/var/log/puppet/puppetd.log]:
    Changing owner,mode
    debug: /puppetconfig/puppetd/File[/var/log/puppet/puppetd.log]: 2
    change(s)
    debug:
    /puppetconfig/puppetd/File[/var/log/puppet/puppetd.log]/owner: File
    does not exist; cannot set owner
    debug: /puppetconfig/puppetd/File[/var/log/puppet/puppetd.log]/mode:
    File does not exist; cannot set mode
    debug: /puppetconfig/puppet/File[/var/lib/puppet/plugins]: File does
    not exist
    debug: Finishing transaction 23456259974580 with 7 changes
    debug: Creating default schedules
    notice: Starting Puppet client version 0.22.3
    debug: Loaded state in 0.02 seconds
    debug: Puppet::Network::Client::File: defining fileserver.describe
    debug: Puppet::Network::Client::File: defining fileserver.list
    debug: Puppet::Network::Client::File: defining fileserver.retrieve
    info: Retrieving facts
    debug: Calling fileserver.list
    debug: Calling fileserver.describe
    debug: /fact_collector/File[/var/lib/puppet/facts]: Changing checksum
    debug: /fact_collector/File[/var/lib/puppet/facts]: 1 change(s)
    debug: /fact_collector/File[/var/lib/puppet/facts]/checksum: setting
    time (currently {time}Tue Apr 17 14:30:08 +1000 2007)
    debug: /fact_collector/File[/var/lib/puppet/facts]/checksum:
    Replacing /var/lib/puppet/facts checksum {time}Tue Apr 17 13:21:42
    +1000 2007 with {time}Tue Apr 17 14:30:08 +1000 2007
    notice: /fact_collector/File[/var/lib/puppet/facts]/checksum:
    checksum changed ''{time}Tue Apr 17 13:21:42 +1000 2007'' to
    ''{time}Tue Apr 17 14:30:08 +1000 2007''
    debug: Calling fileserver.list
    debug: /fact_collector/File[/var/lib/puppet/facts/home.rb]: File
    does not exist
    debug: Calling fileserver.describe
    debug: /fact_collector/File[/var/lib/puppet/facts/home.rb]: Changing
    ensure
    debug: /fact_collector/File[/var/lib/puppet/facts/home.rb]: 1 change(s)
    debug: /fact_collector/File[/var/lib/puppet/facts/home.rb]/ensure:
    setting file (currently absent)
    debug: Calling fileserver.retrieve
    notice: /fact_collector/File[/var/lib/puppet/facts/home.rb]/ensure:
    created
    debug: Calling fileserver.list
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-ipcalc.rb]: File
    does not exist
    debug: Calling fileserver.describe
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-ipcalc.rb]:
    Changing ensure
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-ipcalc.rb]: 1
    change(s)
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-ipcalc.rb]/ensure:
    setting file (currently absent)
    debug: Calling fileserver.retrieve
    notice:
    /fact_collector/File[/var/lib/puppet/facts/network-ipcalc.rb]/ensure:
    created
    debug: Calling fileserver.list
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-bootproto.rb]:
    File does not exist
    debug: Calling fileserver.describe
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-bootproto.rb]:
    Changing ensure
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-bootproto.rb]: 1
    change(s)
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-bootproto.rb]/ensure:
    setting file (currently absent)
    debug: Calling fileserver.retrieve
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-bootproto.rb]/checksum:
    Replacing /var/lib/puppet/facts/network-bootproto.rb checksum
    {md5}1bf408adeae82cf3a37250b18a81b5d8 with
    {md5}5175fb87cd8ee7946796667f8887a0fe
    notice:
    /fact_collector/File[/var/lib/puppet/facts/network-bootproto.rb]/ensure:
    created
    debug: Calling fileserver.list
    debug: /fact_collector/File[/var/lib/puppet/facts/network-count.rb]:
    File does not exist
    debug: Calling fileserver.describe
    debug: /fact_collector/File[/var/lib/puppet/facts/network-count.rb]:
    Changing ensure
    debug: /fact_collector/File[/var/lib/puppet/facts/network-count.rb]:
    1 change(s)
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-count.rb]/ensure:
    setting file (currently absent)
    debug: Calling fileserver.retrieve
    notice:
    /fact_collector/File[/var/lib/puppet/facts/network-count.rb]/ensure:
    created
    debug: Calling fileserver.list
    debug: /fact_collector/File[/var/lib/puppet/facts/vmware.rb]: File
    does not exist
    debug: Calling fileserver.describe
    debug: /fact_collector/File[/var/lib/puppet/facts/vmware.rb]:
    Changing ensure
    debug: /fact_collector/File[/var/lib/puppet/facts/vmware.rb]: 1
    change(s)
    debug: /fact_collector/File[/var/lib/puppet/facts/vmware.rb]/ensure:
    setting file (currently absent)
    debug: Calling fileserver.retrieve
    notice:
    /fact_collector/File[/var/lib/puppet/facts/vmware.rb]/ensure: created
    debug: Calling fileserver.list
    debug: /fact_collector/File[/var/lib/puppet/facts/network-mac.rb]:
    File does not exist
    debug: Calling fileserver.describe
    debug: /fact_collector/File[/var/lib/puppet/facts/network-mac.rb]:
    Changing ensure
    debug: /fact_collector/File[/var/lib/puppet/facts/network-mac.rb]: 1
    change(s)
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-mac.rb]/ensure:
    setting file (currently absent)
    debug: Calling fileserver.retrieve
    debug:
    /fact_collector/File[/var/lib/puppet/facts/network-mac.rb]/checksum:
    Replacing /var/lib/puppet/facts/network-mac.rb checksum
    {md5}7765e956ade7dbddf017ced0df3cadc4 with
    {md5}a001678ac29a8440fa24a01a585acd54
    notice:
    /fact_collector/File[/var/lib/puppet/facts/network-mac.rb]/ensure:
    created
    debug: Finishing transaction 23456258041000 with 7 changes
    info: Loading fact home
    Finished home.rb
    info: Loading fact vmware
    Finished vmware.rb
    info: Loading fact network-ipcalc
    Finished network-ipcalc.rb
    info: Loading fact network-count
    Finished network-count.rb
    info: Loading fact network-mac
    Finished network-mac.rb
    info: Loading fact network-bootproto
    Finished network-bootproto.rb








_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users

Ben

2007-Apr-17 05:03 UTC

head link

Re: Still having factsync trouble ...

Ben wrote:>
> The facts work perfectly well on fc5 and centos4 clients.
>i just retested the facts on fc5 and it does not work.  puppet on fc5 
behaves exactly the same as fc6.

i have also tested all the facts on fc6 and centos5 using facter by itself.

    # cp -f /var/lib/puppet/facts/* ~/lib/ruby/facter/
    # RUBYLIB=~/lib/ruby facter

they all work.

Ben

Ben

2007-Apr-17 05:37 UTC

head link

Re: Still having factsync trouble ...

Ben wrote:> Some time ago i sent to the list a problem i was having with facts on 
> fedora core 6 and wasn''t able to find a solution at that time, but
> with the release of RHEL5 and CentOS 5 based on fc6 i have hit the 
> problem again.
>
> i have written several facts to collect information about a clients 
> network and i am also using the vmware fact from the wiki.  i have 
> separated my original fact into several smaller facts in an effort to 
> find the fault.  i have been using these facts successfully on CentOS 
> 4 for months.
>
> After the facts are run on a fc6, rhel5 or centos5 client puppet 
> stops. i have added a ''puts'' at the end of each fact to
show when they
> are each complete and the output shows that each fact is being 
> executed to completion, note the "Finshed....." at the bottom of
the
> output below.  puppet will sit indefinitely until interrupted with 
> ctrl+c.
>
> The facts work perfectly well on fc5 and centos4 clients.
>
> I have tested i386 and x86_64 arch and both do the same, i have tested 
> on vmware and physical and both do the same.  puppet does NOT stop 
> when called with the "-o" (once) command line option, when using
"-o"
> everything runs perfectly and to completion.
>
> I have attached my facts and would appreciate if someone could test 
> them and possibly shed some light on where puppet is stopping.  I find 
> it really interesting that it runs fine when the "-o" (once)
command
> line option is specified.
>
during subsequent runs, i.e. after the first download of the facts, the 
facts are loaded early on, see the output below, and puppet continues 
after that up until it runs the facts a second time.

so puppet is stopping after the second time the facts are run.

just something i noticed.

Ben

Ben

2007-Apr-17 07:18 UTC

head link

Re: Still having factsync trouble ...

Ben wrote:> Ben wrote:
>   
>> After the facts are run on a fc6, rhel5 or centos5 client puppet 
>> stops. i have added a ''puts'' at the end of each fact
to show when they
>> are each complete and the output shows that each fact is being 
>> executed to completion, note the "Finshed....." at the bottom
of the
>> output below.  puppet will sit indefinitely until interrupted with 
>> ctrl+c.
>>     
I have narrowed the problem down to a loop in the file 
"/usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb" at line
29.

            Facter.each { |name,fact|
                if down
                    facts[name] = fact.to_s.downcase
                else
                    facts[name] = fact.to_s
                end
            }

This loop is never exiting, it stops part way through the processing of 
the facts.

Ben

Ben

2007-Apr-17 08:18 UTC

head link

Re: Still having factsync trouble ...

Ben wrote:> Ben wrote:
>   
>> Ben wrote:
>>   
>>     
>>> After the facts are run on a fc6, rhel5 or centos5 client puppet 
>>> stops. i have added a ''puts'' at the end of each
fact to show when they
>>> are each complete and the output shows that each fact is being 
>>> executed to completion, note the "Finshed....." at the
bottom of the
>>> output below.  puppet will sit indefinitely until interrupted with 
>>> ctrl+c.
>>>     It appears the following line in network-mac.rb causes a problem when 
the facts are called in puppet.

    IO.readlines("/sys/class/net/" + i.chomp +
"/address")[0].chomp

the adjusted fact appear to work on fc6 and centos5.

i have attached the modified fact.

i would appreciate any feedback.

Ben




_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users

Luke Kanies

2007-Apr-17 19:15 UTC

head link

Re: Still having factsync trouble ...

On Apr 17, 2007, at 3:18 AM, Ben wrote:> It appears the following line in network-mac.rb causes a problem  
> when the facts are called in puppet.
>
>    IO.readlines("/sys/class/net/" + i.chomp +
"/address")[0].chomp
>
> the adjusted fact appear to work on fc6 and centos5.
Wow, I''m glad you tracked that down.

I remember trying to reproduce the issues you were having and I never  
could.

I don''t understand why you''d get a hang with that code, but
I''m glad
you were able to fix it.

  --
  Today at work an ethernet switch decided to take the ''N'' out
of NVRAM
                  -- Richard Letts
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com

Ben

2007-Apr-18 00:09 UTC

head link

Re: Still having factsync trouble ...

Luke Kanies wrote:> On Apr 17, 2007, at 3:18 AM, Ben wrote:
>   
>> It appears the following line in network-mac.rb causes a problem  
>> when the facts are called in puppet.
>>
>>    IO.readlines("/sys/class/net/" + i.chomp +
"/address")[0].chomp
>>
>> the adjusted fact appear to work on fc6 and centos5.
>>     
>
> Wow, I''m glad you tracked that down.
>
> I remember trying to reproduce the issues you were having and I never  
> could.
>
> I don''t understand why you''d get a hang with that code,
but I''m glad
> you were able to fix itLuke,

i am glad to have found the cause also, but i find it very odd that the 
code works with facter itself but not puppet.

to debug this problem i split the facts into individual files but now i 
have the problem with all my clients still having the original fact, the 
factsync does not purge the deleted facts.  How can i purge the removed 
facts without visiting each client?

    network.rb

split to

    network-bootproto.rb
    network-count.rb
    network-ipcalc.rb
    network-mac.rb

i have added a purge arg to the self.download function in 
"/puppet/network/client/master.rb" but it doesn''t remove the
offending
files.  Any pointers?

    if args[:purge]
        Puppet.notice "Setting download purge: %s" % args[:purge]
        hash[:purge] = args[:purge]
    end

PS. Thanks for the good project and even more for the great support and 
involvement by yourself.  It makes a huge difference to a project when 
the leader/owner is so involved.

Ben

Luke Kanies

2007-Apr-18 21:11 UTC

head link

Re: Still having factsync trouble ...

On Apr 17, 2007, at 7:09 PM, Ben wrote:> Luke,
>
> i am glad to have found the cause also, but i find it very odd that  
> the
> code works with facter itself but not puppet.
I, also, find it odd.
> to debug this problem i split the facts into individual files but  
> now i
> have the problem with all my clients still having the original  
> fact, the
> factsync does not purge the deleted facts.  How can i purge the  
> removed
> facts without visiting each client?
>
>     network.rb
>
> split to
>
>     network-bootproto.rb
>     network-count.rb
>     network-ipcalc.rb
>     network-mac.rb
>
> i have added a purge arg to the self.download function in
> "/puppet/network/client/master.rb" but it doesn''t remove
the offending
> files.  Any pointers?
>
>     if args[:purge]
>         Puppet.notice "Setting download purge: %s" % args[:purge]
>         hash[:purge] = args[:purge]
>     end
It looks like this is a bug.  It''s been filed (was that you?).
> PS. Thanks for the good project and even more for the great support  
> and
> involvement by yourself.  It makes a huge difference to a project when
> the leader/owner is so involved.
Glad to hear it; thanks.

  --
  At my lemonade stand I used to give the first glass away free and  
charge
  five dollars for the second glass. The refill contained the antidote.
      -- Emo Phillips
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com

Maybe Matching Threads

Search for more apparently analagous threads

Puppet users - Apr 2007 - Still having factsync trouble ...

Still having factsync trouble ...

Re: Still having factsync trouble ...

Re: Still having factsync trouble ...

Re: Still having factsync trouble ...

Re: Still having factsync trouble ...

Re: Still having factsync trouble ...

Re: Still having factsync trouble ...

Re: Still having factsync trouble ...

Maybe Matching Threads