Uploaded image for project: 'Facter'
  1. Facter
  2. FACT-2898

Could not retrieve local facts: can't create Thread: Resource temporarily unavailable

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: FACT 4.0.47
    • Component/s: None
    • Environment:
    • Template:
    • Team:
      Night's Watch
    • Sub-team:
    • Story Points:
      2
    • Sprint:
      ghost-9.12
    • Method Found:
      Needs Assessment
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Fixed Error: Could not retrieve local facts: can't create Thread: Resource temporarily unavailable error thrown on systems where the file descriptor limit was low
    • QA Risk Assessment:
      Needs Assessment

      Description

      after update of puppet-agent to v7 on Ubuntu I get the following error:

      Debug: Facter: Query is operatingsystem
      Debug: Facter: Checking query tokens operatingsystem
      Debug: Facter: List of resolvable facts: 
      [#<Facter::SearchedFact:0x000055f89f7fb640 @name="operatingsystem", 
      @fact_class=Facts::Linux::Os::Name, @filter_tokens=[], 
      @user_query="operatingsystem", @type=:legacy, @file=nil>]
      Debug: Facter: Resolving fact in parallel
      Debug: Facter: Loading external facts
      Debug: Facter: User query is: []
      Debug: Facter: Resolving fact in parallel
      Error: Could not retrieve local facts: can't create Thread: Resource 
      temporarily unavailable
      Error: Failed to apply catalog: Could not retrieve local facts: can't 
      create Thread: Resource temporarily unavailable
      Debug: Resolving service 'report' using Puppet::HTTP::Resolver::Settings
      

       

      Moreover facts do not resolve properly:

      helmut@h2873756:~$ facter ipaddress
       
      helmut@h2873756:~$ facter networking.primary
       
      helmut@h2873756:~$ facter networking | grep primary
       primary => "aPublicIP"
      helmut@h2873756:~$ facter networking.interfaces
       
      helmut@h2873756:~$ facter networking | grep -A100 interfaces
       interfaces => {
       lo => {
       bindings => [
       {
       ip => "10.0.124.17",
       ip6 => "fe80::cc7a:d052:3220:e442",
       mac => "",
       mtu => 1500,
       netmask => "255.255.255.255",
       netmask6 => "ffff:ffff:ffff:ffff::",
       network => "10.0.124.17",
       network6 => "fe80::",
       scope6 => "link"
       },
       venet0 => {
       bindings => [
       {
       address => "127.0.0.1",
       netmask => "255.255.255.255",
       network => "127.0.0.1"
       },
       {
       address => "aPublicIP",
       netmask => "255.255.255.255",
       network => "aPublicIP"
       }
       ],
       bindings6 => [
       {
       address => "::2",
       netmask => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
       network => "::2"
       },
       {
       address => "aPublicIP",
       netmask => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
       network => "aPublicIP"
       }
       ],
       ip => "aPublicIP",
       ip6 => "::2",
       mac => "",
       mtu => 1500,
       netmask => "255.255.255.255",
       netmask6 => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
       network => "aPublicIP",
       network6 => "::2",
       scope6 => "compat,global"
       }
       },
       primary => "aPublicIP"
      }
      helmut@h2873756:~$ facter networking.hostname
      h2873756
      helmut@h2873756:~$
       
      helmut@h2873756:~$ facter -v
      4.0.46
      helmut@h2873756:~$
      

       

      Rolling back puppet-agent to v6 resolves the issue:

      helmut@h2873756:~$ facter ipaddress
      aPublicIP
      helmut@h2873756:~$ facter networking.primary
      venet0
      helmut@h2873756:~$
       
      helmut@h2873756:~$ facter -v
      3.14.14 (commit e36657bea27254f003c8fc71d8ef57454db643e2)
      helmut@h2873756:~$
      

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            Helmut Helmut Ritter
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support