Depoly Graylog on GKE

Graylog Central (peer support)
1

Hello,

I’m having a hard time deploying Graylog on Google Kubernetes Engine, I’m using this configuration https://github.com/aliasmee/kubernetes-graylog-cluster with some minor modifications. My Graylog server is up but show this error in the interface:

Error message
    Request has been terminated
    Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.
Original Request
    GET http://ES_IP:12900/system/sessions
Status code
    undefined
Full error message
    Error: Request has been terminated
    Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.

Graylog logs show nothing in particular other than this:

org.graylog.plugins.threatintel.tools.AdapterDisabledException: Spamhaus service is disabled, not starting (E)DROP adapter. To enable it please go to System / Configurations.
    at org.graylog.plugins.threatintel.adapters.spamhaus.SpamhausEDROPDataAdapter.doStart(SpamhausEDROPDataAdapter.java:68) ~[?:?]
    at org.graylog2.plugin.lookup.LookupDataAdapter.startUp(LookupDataAdapter.java:59) [graylog.jar:?]
    at com.google.common.util.concurrent.AbstractIdleService$DelegateService$1.run(AbstractIdleService.java:62) [graylog.jar:?]
    at com.google.common.util.concurrent.Callables$4.run(Callables.java:119) [graylog.jar:?]
    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]

but at the end :

2019-01-16 13:35:00,255 INFO : org.graylog2.bootstrap.ServerBootstrap - Graylog server up and running.

Elastic search health check is green, no issues in ES nor Mongo logs. I suspect a problem with the connection to Elastic Search though.

I’m posting this on StackOverflow here:

Any ideas are welcome.
Thanks !

2

without knowing how you configured your Graylog exactly I guess nobody can help. You should check web_listen_uri and rest_listen_uri that your browser is able to communicate with the Graylog API.

3

That’s what I’m having on the browser:

05
Screenshot 2019-01-16 at 15.40.05.jpg1413×724 217 KB

4

yes - your browser is not able to reach 10.63.240.12 on port 12900. But your browser need to be able to connect to the Graylog API.

Please read the comments in the configuration for rest_transport_uri and web_endpoint_uri ( http://docs.graylog.org/en/2.5/pages/configuration/server.conf.html#web )

5

It seems Graylog is reachable but not its API.
Use the browser developper console to confirm that.
As Jan said tou should check rest_transport_uri.

6

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