Quantcast
Channel: Ask Puppet: Puppet DevOps Q&A Community - RSS feed
Viewing all articles
Browse latest Browse all 6104

gettextsetup warnings

$
0
0
After updating puppet from 4.10.5 to 4.10.6, and recently 4.10.7 my logs are swamped with warning messages about GettextSetup. For example:
Warning: GettextSetup is not available, skipping GettextSetup initialization for mysql_server.
Warning: GettextSetup is not available, skipping GettextSetup initialization for pkg_clean.
Warning: GettextSetup is not available, skipping GettextSetup initialization for openntpd.
Warning: GettextSetup is not available, skipping GettextSetup initialization for apache22.
Warning: GettextSetup is not available, skipping GettextSetup initialization for sudo.
Warning: GettextSetup is not available, skipping GettextSetup initialization for sshd.
Warning: GettextSetup is not available, skipping GettextSetup initialization for monit.
Warning: GettextSetup is not available, skipping GettextSetup initialization for smartmon.
Warning: GettextSetup is not available, skipping GettextSetup initialization for motd.
Warning: GettextSetup is not available, skipping GettextSetup initialization for accounts.
This goes on and on. For every module I get multiple warnings and for every agent run on every node. My question is two-fold: 1. How do I fix this? What needs to be configured/upgraded/installed/whatever to satisfy Puppet? 2. Failing to fix this, how do I disable this warning? My logs are now utterly useless because the warnings swamp everything. Currently running Puppet 4.10.7 on FreeBSD 10.3. The warning also shows up with Puppetserver 2.7.2. Installing the gettext and gettext-setup gem doesn't help.

Viewing all articles
Browse latest Browse all 6104

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>