This message was deleted.
# puppet
s
This message was deleted.
t
If --debug and --trace does not give you a hint which fact fails, you must check all facts manually. Check each file in /opt/puppetlabs/puppet/cache/lib/facter and /opt/puppetlabs/puppet/cache/lib/facts.d. This is the location of the pluginsync. Remove all facts and add them one-by-one. When you get no output from facter you have found the broken one.
l
Thank you! I will try that. I hope it is just a custom fact, so i can fix that without a PR on a project xD
It is kinda sad that facter isn't able to give me any error output and handle the situation without becoming dead
@tuxmea Thanks again, that was surprisingly easy. It is the kmod fact. Sadly, not one of our custom facts.
t
you can disable fact collection of specific facts in facter.conf https://www.puppet.com/docs/puppet/7/configuring_facter.html
🦜 1
l
I am currently debugging that fact and it seems like the problem happens when it tries to read from
/sys/module/kvm_intel/parameters/eptad
People who come after me and have the same problem: I created an issue on github https://github.com/voxpupuli/puppet-kmod/issues/96
e
Late to the party, but wanna ask: how did you get process state? I'm asking because, in
ps o stat
, state "D" doesn't mean dead, but in I/O wait. Which would be the natural state when retrieving facts.