Graylog will not start after upgrade to 2.3.0


(Beth) #1

I am trying to upgrade my Graylog from 2.2.0 to 2.3.0 on a Debian system. I am also upgrading from Elasticsearch 2.x to 5.x. I have a simple setup all on one server. I did the Elasticsearch upgrade to 5.x first, and it seems healthy. I then did the Graylog upgrade using the Debian package. I did not see upgrade errors, but Graylog will not start, and I don’t see much in the error logs. to the server.conf file, I added the elasticsearch_hosts parameter, and tried using both http://localhost:9200 and http://10.x.x.x:9200 but that did not help either. I made sure to remove all the deprecated settings for elasticsearch in the /etc/graylog/server/server.conf file, but that also did not help. My /var/log/graylog-server/server.log file shows the following when I try to start Graylog:

2017-10-09T15:59:24.778-07:00 INFO  [Version] HV000001: Hibernate Validator null
2017-10-09T15:59:40.385-07:00 INFO  [CmdLineTool] Loaded plugin: SyslogOutputPlugin 1.0.0 [com.wizecore.graylog2.plugin.SyslogOutput]
2017-10-09T15:59:40.387-07:00 INFO  [CmdLineTool] Loaded plugin: Aggregates 0.0.12 [org.graylog.plugins.aggregates.AggregatesPlugin]
2017-10-09T15:59:40.388-07:00 INFO  [CmdLineTool] Loaded plugin: Elastic Beats Input 2.3.1 [org.graylog.plugins.beats.BeatsInputPlugin]
2017-10-09T15:59:40.389-07:00 INFO  [CmdLineTool] Loaded plugin: Collector 2.3.1 [org.graylog.plugins.collector.CollectorPlugin]
2017-10-09T15:59:40.390-07:00 INFO  [CmdLineTool] Loaded plugin: Enterprise Integration Plugin 2.3.1 [org.graylog.plugins.enterprise_integration.EnterpriseIntegrationPlugin]
2017-10-09T15:59:40.391-07:00 INFO  [CmdLineTool] Loaded plugin: MapWidgetPlugin 2.3.1 [org.graylog.plugins.map.MapWidgetPlugin]
2017-10-09T15:59:40.400-07:00 INFO  [CmdLineTool] Loaded plugin: Pipeline Processor Plugin 2.3.1 [org.graylog.plugins.pipelineprocessor.ProcessorPlugin]
2017-10-09T15:59:40.401-07:00 INFO  [CmdLineTool] Loaded plugin: Anonymous Usage Statistics 2.3.1 [org.graylog.plugins.usagestatistics.UsageStatsPlugin]
2017-10-09T15:59:40.659-07:00 INFO  [CmdLineTool] Running with JVM arguments: -Xms1g -Xmx1g -XX:NewRatio=1 -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow -Dlog4j.configurationFile=file:///etc/graylog/server/log4j2.xml -Djava.library.path=/usr/share/graylog-server/lib/sigar -Dgraylog2.installation_source=deb
2017-10-09T15:59:40.922-07:00 INFO  [Version] HV000001: Hibernate Validator null

The log says “Running”, but when I do service graylog-server status, it shows failed:

Oct 09 16:00:57 dshsapoly808glq systemd[1]: Started A high performance web server and a reverse proxy server.
root@dshsapoly808glq:~# service graylog-server status
● graylog-server.service - Graylog server
   Loaded: loaded (/usr/lib/systemd/system/graylog-server.service; enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2017-10-09 16:02:59 PDT; 5s ago
     Docs: http://docs.graylog.org/
  Process: 5123 ExecStart=/usr/share/graylog-server/bin/graylog-server (code=exited, status=1/FAILURE)
 Main PID: 5123 (code=exited, status=1/FAILURE)

Oct 09 16:02:59 dshsapoly808glq systemd[1]: Unit graylog-server.service entered failed state.

I am stuck. Does anyone know how to get more detailed logging?

Beth


(Jochen) #2

You have to ensure that all 3rd party plugins from the plugin directory of your Graylog node are compatible with the version of Graylog you’re using.

For example the Aggregates plugin is not compatible with Graylog 2.3.x in the version you’re using.


(Beth) #3

Thank you SO much!! I removed the aggregates plugin and everything started up.


(system) #4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.