[Puppet Users] puppetdb v7 test: no such file to load -- puppet/util/puppetdb

2020-12-08 Thread comport3
Whilst trying to test a new Puppet v7.0.0 master (which is OK) and PuppetDB, I get the following on PuppetDB: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Internal Server Error: org.jruby.exceptions.LoadError: (LoadError) no such file to load --

Re: [Puppet Users] Windows exec resource cannot find command error

2020-12-08 Thread Michael Watters
Probably need to quote the executable due to spaces: exec { '"c:/program files/telegraf/telegraf.exe" --service install': Looks like that worked. Thanks for the help. On Tuesday, December 8, 2020 at 1:58:12 PM UTC-5 Josh Cooper wrote: > On Tue, Dec 8, 2020 at 10:37 AM Michael Watters wrote:

Re: [Puppet Users] Windows exec resource cannot find command error

2020-12-08 Thread Josh Cooper
On Tue, Dec 8, 2020 at 10:37 AM Michael Watters wrote: > Here is the exact error message. > > Info: /Stage[main]/Dart::Abstract::Windows_node/File[c:/program > files/telegraf/telegraf.conf]: Scheduling refresh of Exec[c:/program > files/telegraf/telegraf.exe --service install] > Error: Could not

Re: [Puppet Users] Windows exec resource cannot find command error

2020-12-08 Thread Michael Watters
Here is the exact error message. Info: /Stage[main]/Dart::Abstract::Windows_node/File[c:/program files/telegraf/telegraf.conf]: Scheduling refresh of Exec[c:/program files/telegraf/telegraf.exe --service install] Error: Could not find command 'c:/program' Error:

Re: [Puppet Users] Windows exec resource cannot find command error

2020-12-08 Thread Michael Watters
I tried that as well and it simply results in an error stating "Could not find command: c:/program". On Monday, December 7, 2020 at 2:06:53 PM UTC-5 Martin Alfke wrote: > Have you tried using the full path to the executable? > > exec { 'c:/program files/telegraf/telegraf.exe --service install'

Re: [Puppet Users] Could not retrieve local facts: can't create Thread: Resource temporarily unavailable

2020-12-08 Thread Helmut Schneider
Am 08.12.2020 um 14:45 schrieb Helmut Schneider: 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

Re: [Puppet Users] Could not retrieve local facts: can't create Thread: Resource temporarily unavailable

2020-12-08 Thread Helmut Schneider
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

Re: [Puppet Users] Could not retrieve local facts: can't create Thread: Resource temporarily unavailable

2020-12-08 Thread bogdan...@puppet.com
Managed to reproduce the problem by limiting the number of threads to 200 on Ubuntu 18.04 echo 200 > /proc/sys/kernel/threads-max root@raw-drawl:~# facter Traceback (most recent call last): 14: from /opt/puppetlabs/puppet/bin/facter:10:in `' 13: from

Re: [Puppet Users] Could not retrieve local facts: can't create Thread: Resource temporarily unavailable

2020-12-08 Thread Bogdan Irimie
Hi Helmut, 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? Please try to run

[Puppet Users] Could not retrieve local facts: can't create Thread: Resource temporarily unavailable

2020-12-08 Thread Helmut Schneider
Hi, after update of puppet-agent on Ubuntu I get the following error: Debug: Facter: Query is operatingsystem Debug: Facter: Checking query tokens operatingsystem Debug: Facter: List of resolvable facts: [#@fact_class=Facts::Linux::Os::Name, @filter_tokens=[], @user_query="operatingsystem",