Am 08.12.2020 um 13:15 schrieb Bogdan Irimie:
Facter 4 resolves each fact on a separate thread, this can lead to a
high number of threads being created. Can you please provide the output
of `cat /proc/sys/kernel/threads-max` on the system where you see this
issue? Does this happen at every run or sporadically?
helmut@h2873756:~$ cat /proc/sys/kernel/threads-max
3090194
helmut@h2873756:~$
Every time I run puppet.
Please try to run facter from the cli and let me know if you have any
issues.
helmut@h2873756:~$ facter
Traceback (most recent call last):
14: from /opt/puppetlabs/puppet/bin/facter:10:in `<main>'
13: from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/cli/cli_launcher.rb:23:in
`start'
12: from
/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/base.rb:485:in
`start'
11: from
/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor.rb:392:in
`dispatch'
10: from
/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in
`invoke_command'
9: from
/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/command.rb:27:in
`run'
8: from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/cli/cli.rb:114:in
`query'
7: from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:390:in
`to_user_output'
6: from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact_manager.rb:25:in
`resolve_facts'
5: from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:15:in
`resolve_facts'
4: from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:62:in
`start_threads'
3: from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:62:in
`map'
2: from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:63:in
`block in start_threads'
1: from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:63:in
`new'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:63:in
`initialize': can't create Thread: Resource temporarily unavailable
(ThreadError)
helmut@h2873756:~$
You can disable parallel fact resolution with facter.conf
(https://puppet.com/docs/facter/3.11/configuring_facter.html
<https://puppet.com/docs/facter/3.11/configuring_facter.html>) by adding
global : {
sequential: true
}
That helps, yes.
The system is a VM on OpenVZ. Other machines on Hyper-V and VMWare are
not affected.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/rqo01m%2415p%241%40ciao.gmane.io.
