# Can't run Graylog Service **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [September 17, 2019, 3:31pm UTC](https://community.graylog.org/t/cant-run-graylog-service/11992 "2019-09-17T15:31:45Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![aleff616](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@aleff616](https://community.graylog.org/u/aleff616)\ **Post date:** [September 17, 2019, 3:31pm UTC](https://community.graylog.org/t/cant-run-graylog-service/11992/1 "2019-09-17T15:31:46Z")
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 ---
**Author:** ![jcspino](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jcspino/32/1461_2.png) [@jcspino](https://community.graylog.org/u/jcspino)\ **Post date:** [September 17, 2019, 4:49pm UTC](https://community.graylog.org/t/cant-run-graylog-service/11992/2 "2019-09-17T16:49:25Z")
> [@aleff616](#): > > org.graylog2.configuration.HttpConfiguration.validateHttpPublishUriPathEndsWithSlash 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. ---
**Author:** ![aleff616](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@aleff616](https://community.graylog.org/u/aleff616)\ **Post date:** [September 18, 2019, 2:58pm UTC](https://community.graylog.org/t/cant-run-graylog-service/11992/3 "2019-09-18T14:58:21Z")
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 ---
**Author:** ![aleff616](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@aleff616](https://community.graylog.org/u/aleff616)\ **Post date:** [September 18, 2019, 3:00pm UTC](https://community.graylog.org/t/cant-run-graylog-service/11992/4 "2019-09-18T15:00:50Z")
############### # 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](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 ---
**Author:** ![aleff616](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@aleff616](https://community.graylog.org/u/aleff616)\ **Post date:** [September 18, 2019, 6:41pm UTC](https://community.graylog.org/t/cant-run-graylog-service/11992/5 "2019-09-18T18:41:42Z")
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 ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [October 2, 2019, 6:41pm UTC](https://community.graylog.org/t/cant-run-graylog-service/11992/6 "2019-10-02T18:41:43Z")
Closed on October 2, 2019, 6:41pm UTC This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.