Fix setting for max_procs
#50
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After updating this module to version 0.8.0, I ran into the following error: ``` Error: Could not start Service[filebeat]: Execution of '/etc/init.d/filebeat start' returned 1: Exiting: error unpacking config data: can not convert 'string' into 'int' accessing 'max_procs' (source:'/etc/filebeat/filebeat.yml') ...fail! Error: /Stage[main]/Filebeat::Service/Service[filebeat]/ensure: change from stopped to running failed: Could not start Service[filebeat]: Execution of '/etc/init.d/filebeat start' returned 1: Exiting: error unpacking config data: can not convert 'string' into 'int' accessing 'max_procs' (source:'/etc/filebeat/filebeat.yml') ...fail! ``` Basically, the problem is that `/etc/filebeat/filebeat.yml` contained the following: ``` max_procs: undef ```
|
Thanks for this. I pushed this to the forge as v0.8.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After updating this module to version 0.8.0, I ran into the following error:
Basically, the problem is that
/etc/filebeat/filebeat.ymlcontained the following: