Can't run Graylog Service

Graylog Central (peer support)
1

Hello everyone, I am new to graylog and I intend to evaluate the tool, I just made an installation on an Ubuntu Server 18.04 following the installation steps of the site, but I can not start the graylog-server service, here I share the error logs

2019-09-17T15:00:05.820Z ERROR [CmdLineTool] Invalid configuration com.github.joschi.jadconfig.ValidationException: Couldn't run validator method at com.github.joschi.jadconfig.JadConfig.invokeValidatorMethods(JadConfig.java:227) ~[graylog.jar:?] at com.github.joschi.jadconfig.JadConfig.process(JadConfig.java:100) ~[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:178) [graylog.jar:?] at org.graylog2.bootstrap.Main.main(Main.java:50) [graylog.jar:?] Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_222] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_222] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_222] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_222] at com.github.joschi.jadconfig.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:53) ~[graylog.jar:?] at com.github.joschi.jadconfig.JadConfig.invokeValidatorMethods(JadConfig.java:221) ~[graylog.jar:?] ... 5 more Caused by: java.lang.RuntimeException: Could not parse URI. at org.graylog2.plugin.Tools.getUriWithScheme(Tools.java:541) ~[graylog.jar:?] at org.graylog2.plugin.Tools.lambda$normalizeURI$0(Tools.java:593) ~[graylog.jar:?] at java.util.Optional.map(Optional.java:215) ~[?:1.8.0_222] at org.graylog2.plugin.Tools.normalizeURI(Tools.java:593) ~[graylog.jar:?] at org.graylog2.configuration.HttpConfiguration.getHttpPublishUri(HttpConfiguration.java:118) ~[graylog.jar:?] at org.graylog2.configuration.HttpConfiguration.validateHttpPublishUriPathEndsWithSlash(HttpConfiguration.java:234) ~[graylog.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_222] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_222] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_222] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_222] at com.github.joschi.jadconfig.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:53) ~[graylog.jar:?] at com.github.joschi.jadconfig.JadConfig.invokeValidatorMethods(JadConfig.java:221) ~[graylog.jar:?] ... 5 more Caused by: java.net.URISyntaxException: Expected scheme-specific part at index 5: http: at java.net.URI$Parser.fail(URI.java:2848) ~[?:1.8.0_222] at java.net.URI$Parser.failExpecting(URI.java:2854) ~[?:1.8.0_222] at java.net.URI$Parser.parse(URI.java:3057) ~[?:1.8.0_222] at java.net.URI.(URI.java:673) ~[?:1.8.0_222] at org.graylog2.plugin.Tools.getUriWithScheme(Tools.java:539) ~[graylog.jar:?] at org.graylog2.plugin.Tools.lambda$normalizeURI$0(Tools.java:593) ~[graylog.jar:?] at java.util.Optional.map(Optional.java:215) ~[?:1.8.0_222] at org.graylog2.plugin.Tools.normalizeURI(Tools.java:593) ~[graylog.jar:?] at org.graylog2.configuration.HttpConfiguration.getHttpPublishUri(HttpConfiguration.java:118) ~[graylog.jar:?] at org.graylog2.configuration.HttpConfiguration.validateHttpPublishUriPathEndsWithSlash(HttpConfiguration.java:234) ~[graylog.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_222] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_222] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_222] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_222] at com.github.joschi.jadconfig.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:53) ~[graylog.jar:?] at com.github.joschi.jadconfig.JadConfig.invokeValidatorMethods(JadConfig.java:221) ~[graylog.jar:?] ... 5 more
2

The error indicates an issue with your HttpPublishUri which is a value set in your configuration file. Can you check HttpPublishUri for any typos and post the value you have set.

3

hi @jcspino

In fact, the problem was a bar in httpPublishUri, the service is already working fine. But I still cannot access via web from another computer (of the same network), I attach my configuration file

4

###############

HTTP settings

###############

HTTP bind address

The network interface used by the Graylog HTTP interface.

This network interface must be accessible by all Graylog nodes in the cluster and by all clients

using the Graylog web interface.

If the port is omitted, Graylog will use port 9000 by default.

Default: 127.0.0.1:9000

http_bind_address = 10.0.1.65:9000
#http_bind_address = [2001:db8::1]:9000

HTTP publish URI

The HTTP URI of this Graylog node which is used to communicate with the other Graylog nodes in the cluster and by all

clients using the Graylog web interface.

The URI will be published in the cluster discovery APIs, so that other Graylog nodes will be able to find and connect to this Graylog node.

This configuration setting has to be used if this Graylog node is available on another network interface than $http_bind_address,

for example if the machine has multiple network interfaces or is behind a NAT gateway.

If $http_bind_address contains a wildcard IPv4 address (0.0.0.0), the first non-loopback IPv4 address of this machine will be used.

This configuration setting must not contain a wildcard address!

Default: http://$http_bind_address/

http_publish_uri = http://10.0.1.65:9000

External Graylog URI

The public URI of Graylog which will be used by the Graylog web interface to communicate with the Graylog REST API.

The external Graylog URI usually has to be specified, if Graylog is running behind a reverse proxy or load-balancer

and it will be used to generate URLs addressing entities in the Graylog REST API (see $http_bind_address).

When using Graylog Collector, this URI will be used to receive heartbeat messages and must be accessible for all collectors.

This setting can be overriden on a per-request basis with the “X-Graylog-Server-URL” HTTP request header.

Default: $http_publish_uri

http_external_uri =$http_publish_uri/

Enable CORS headers for HTTP interface

This is necessary for JS-clients accessing the server directly.

If these are disabled, modern browsers will not be able to retrieve resources from the server.

This is enabled by default. Uncomment the next line to disable it.

http_enable_cors = true

Enable GZIP support for HTTP interface

This compresses API responses and therefore helps to reduce

overall round trip times. This is enabled by default. Uncomment the next line to disable it.

http_enable_gzip = true

The maximum size of the HTTP request headers in bytes.

http_max_header_size = 8192

The size of the thread pool used exclusively for serving the HTTP interface.

http_thread_pool_size = 16

################

HTTPS settings

################

Enable HTTPS support for the HTTP interface

This secures the communication with the HTTP interface with TLS to prevent request forgery and eavesdropping.

Default: false

http_enable_tls = false

The X.509 certificate chain file in PEM format to use for securing the HTTP interface.

#http_tls_cert_file = /path/to/graylog.crt

The PKCS#8 private key file in PEM format to use for securing the HTTP interface.

#http_tls_key_file = /path/to/graylog.key

The password to unlock the private key used for securing the HTTP interface.

#http_tls_key_password = secret

5

I already checked the logs in detail and the whole problem was that I had not configured the elasticsearch node correctly, thanks for the help

6

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