Closed ElZeeBee closed 7 years ago
@ElZeeBee What's in the logs of your Graylog node? http://docs.graylog.org/en/2.3/pages/configuration/file_location.html
According to the logs, the only issue is that Parameter password_secret should not be blank
. When I first upgraded from 2.2.x, the new config file was created with the new parameters as described in the upgrade guide in the documentation, but Graylog still seemed to work; I was able to bring up the web console and log in with the old config settings. Because of this, I didn't think to check the new config file.
I have added in password_secret
and root_password_sha2
and it seems to be working now. Interesting note: I checked the service before updating the new config file, and it seemed to be running.
Logs for reference:
2017-08-25T14:04:41.520-04:00 INFO [CmdLineTool] Loaded plugin: Collector 2.3.1 [org.graylog.plugins.collector.CollectorPlugin]
2017-08-25T14:04:41.520-04:00 INFO [CmdLineTool] Loaded plugin: Enterprise Integration Plugin 2.3.1 [org.graylog.plugins.enterprise_integration.EnterpriseIntegrationPlugin]
2017-08-25T14:04:41.521-04:00 INFO [CmdLineTool] Loaded plugin: MapWidgetPlugin 2.3.1 [org.graylog.plugins.map.MapWidgetPlugin]
2017-08-25T14:04:41.528-04:00 INFO [CmdLineTool] Loaded plugin: Pipeline Processor Plugin 2.3.1 [org.graylog.plugins.pipelineprocessor.ProcessorPlugin]
2017-08-25T14:04:41.528-04:00 INFO [CmdLineTool] Loaded plugin: Anonymous Usage Statistics 2.3.1 [org.graylog.plugins.usagestatistics.UsageStatsPlugin]
2017-08-25T14:04:41.541-04:00 ERROR [CmdLineTool] Invalid configuration
com.github.joschi.jadconfig.ValidationException: Parameter password_secret should not be blank
at com.github.joschi.jadconfig.validators.StringNotBlankValidator.validate(StringNotBlankValidator.java:25) ~[graylog.jar:?]
at com.github.joschi.jadconfig.validators.StringNotBlankValidator.validate(StringNotBlankValidator.java:11) ~[graylog.jar:?]
at com.github.joschi.jadconfig.JadConfig.validateParameter(JadConfig.java:215) ~[graylog.jar:?]
at com.github.joschi.jadconfig.JadConfig.processClassFields(JadConfig.java:148) ~[graylog.jar:?]
at com.github.joschi.jadconfig.JadConfig.process(JadConfig.java:99) ~[graylog.jar:?]
at org.graylog2.bootstrap.CmdLineTool.processConfiguration(CmdLineTool.java:351) [graylog.jar:?]
at org.graylog2.bootstrap.CmdLineTool.readConfiguration(CmdLineTool.java:344) [graylog.jar:?]
at org.graylog2.bootstrap.CmdLineTool.run(CmdLineTool.java:177) [graylog.jar:?]
at org.graylog2.bootstrap.Main.main(Main.java:44) [graylog.jar:?]
After updating to version 2.3.1, the Graylog service is failing to start (or it runs very briefly before failing).
journalctl
suggests this may be related to Collector Sidecar.Also posted to Graylog2/collector-sidecar#188
Expected Behavior
Graylog service should start and run as normal
Current Behavior
Graylog service fails to start (or runs briefly before failing).
journalctrl
reports:Steps to Reproduce (for bugs)
systemtl status graylog-server.service
Context
Your Environment
Collector Sidecar 0.1.4 Filebeat 5.5.1