-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collectd fails to start when wsrepstats is enabled #757
Labels
bug
Something isn't working
Comments
|
Hi @steventwheeler. thanks for bringing this up. Are you able to provide a test that verifies this? Or can you test if it works for you when you correct the variable naming? |
|
@bastelfreak thanks for the quick response. I can confirm that it works with the configuration below. I will see if I can find some time today to write up a test. |
steventwheeler
added a commit
to steventwheeler/puppet-collectd
that referenced
this issue
Mar 2, 2018
Adds tests as requested in voxpupuli#757
|
@bastelfreak I have implemented a fix for this in #758. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
The collectd service fails to start.
What behaviour did you expect instead
The collectd service should start.
Output log
The strange thing is there are not 125+ lines in
/etc/collectd.d/mysql-mysql.conf, my guess is that collectd must concatenate all of the config files into on massive file when parsing. What I do notice is that the valuetrueis not included after theWsrepStatsStatsparameter. Also, this parameter appears to be misnamed, I believe it should beWsrepStats.Any additional information you'd like to impart
My best guess is that this is a problem with the ERB template. The case used for the variable's name is inconsistent on lines 22 and 23
@wsrepstatsvs@WsrepStatsrespectively.The text was updated successfully, but these errors were encountered: