Hello,
Today I tried to connect to graylog-web - but got information that “Server currently unavailable”.
Checked both graylog-server, elasticsearch processes both are active - only graylog-web has active (exited) status. Elasticsearch cluster has a green status, all server logs seems to be fine (no warnings/errors etc.).
About 5 days ago I’ve upgraded Debian from 8 to 9 (Stretch) - but after update it worked well. Graylog/elasticsearch configuration hasn’t changed. Graylog version: 2.2.3.
I also checked JS console in browser and there are bunch of errors:
Blockquote
plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:55:21724
“There was an error fetching a resource: Bad request.” Additional information: Not available plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:1:2865
Unhandled rejection t@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:1:2765
value/this.request<@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:1:4230
r@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:57:8699
[22]</n.exports/o.prototype._settlePromiseFromHandler@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:56:13906
[22]</n.exports/o.prototype._settlePromise@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:56:14709
[22]</n.exports/o.prototype._settlePromise0@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:56:15410
[22]</n.exports/o.prototype._settlePromises@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:56:16629
[2]</i.prototype._drainQueue@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:55:2807
[2]</i.prototype._drainQueues@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:55:2865
i/this.drainQueues@http://SERVERNAME:9000/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.0cbe11128085ed745b77.js:55:1001
u@http://SERVERNAME:9000/assets/polyfill.35e28e4da7743596569a.js:2:23694
j/<@http://SERVERNAME:9000/assets/polyfill.35e28e4da7743596569a.js:2:23816
a@http://SERVERNAME:9000/assets/polyfill.35e28e4da7743596569a.js:1:23019
PS. The strange thing about this is that Graylog displays “Server currently unavailable” in Firefox only (checked on 2 PC’s, also cleared the browser cache), but in Chrome it works well… (browsers were not updated within 2 weeks).