• Welcome to the SIMP documentation!
  • 1. Quick Start
  • 2. Changelogs
  • 3. Getting Started
  • 4. User Guide
  • 5. Contributing to SIMP
  • 6. Security Concept of Operations
  • 7. Security Control Mapping
  • 8. Vulnerability Supplement
  • 9. Help
    • Help
    • 9.1. Frequently Asked Questions
      • 9.1.1. SIMP Version Guide
      • 9.1.2. What is the Password Complexity for SIMP?
      • 9.1.3. How can the root user login
      • 9.1.4. Meltdown and Spectre
      • 9.1.5. Why aren’t audit logs being forwarded to syslog?
      • 9.1.6. Puppet-Related Issues
        • 9.1.6.1. Running Puppet Agent in Debug Mode Crashes
        • 9.1.6.2. When Should I Run puppet generate types?
      • 9.1.7. Why does SIMP use rsync?
      • 9.1.8. How to recover from SELINUX policy failure
      • 9.1.9. YUM Repo Issues
    • 9.2. Public Resources
    • 9.3. Commercial Resources
  • 10. License
  • 11. Contact
  • 12. Glossary of Terms
 
SIMP
  • Docs »
  • 9. Help »
  • 9.1. Frequently Asked Questions »
  • 9.1.6. Puppet-Related Issues
  • View page source

9.1.6. Puppet-Related Issues¶

9.1.6.1. Running Puppet Agent in Debug Mode Crashes¶

The FACT-1732 bug, present in some versions of Facter 3, can cause facter to crash when attempting to print Bignum level numbers.

Note

On a 64-bit system, a Bignum value is (2**62) or higher

This will affect runs of puppet agent -t --debug as well as facter -p.

It is highly likely that you will have one of these values from the shmall fact provided by the simplib module.

9.1.6.2. When Should I Run puppet generate types?¶

The puppet generate types command was added to help solve the SERVER-94 puppet environment isolation issue by caching custom type definitions in each environment.

SIMP has a Puppet class called pupmod::master::generate_types, which is enabled by default, and uses incron to automatically run puppet generate types in the following cases:

  • The puppet or puppetserver binaries have been updated.
  • A new environment is added to the system.

You will need to run puppet generate types manually if the following occurs:

  • A new module is added to your environment that includes custom types.
  • An existing custom type has its code modified.

Note

Versions 7.6.0 through 7.7.1 of SIMP’s pupmod Puppet module tried to include all of the cases above to ensure that users did not need to manually adjust any aspects of their systems. However, this proved to potentially add too much load to the system in certain situations and was reduced to the current functionality.

If you are using r10k then you can add a postrun snippet to run puppet generate types on the modified environments.

Next Previous

© Copyright 2019, THE SIMP TEAM.

Built with Sphinx using a theme provided by Read the Docs.