Graylog startup failed - JerseyService FAILED

Since the update to Graylog 5.0.6 the Graylog Service on one of two nodes is toggling, that means starting and stopping again with the following error message:

2023-04-14T14:37:07.045+02:00 ERROR [ServerBootstrap] Graylog startup failed. Exiting. Exception was:
java.lang.IllegalStateException: Expected to be healthy after starting. The following services are not running: {FAILED=[JerseyService [FAILED]]}
at$ServiceManagerState.checkHealthy( ~[graylog.jar:?]
at$ServiceManagerState.awaitHealthy( ~[graylog.jar:?]
at ~[graylog.jar:?]
at org.graylog2.bootstrap.ServerBootstrap.startCommand( [graylog.jar:?]
at org.graylog2.bootstrap.CmdLineTool.doRun( [graylog.jar:?]
at [graylog.jar:?]
at org.graylog2.bootstrap.Main.main( [graylog.jar:?]
Suppressed:$FailedService: JerseyService [FAILED]
Caused by: Cannot assign requested address
at Method) ~[?:?]
at Source) ~[?:?]
at Source) ~[?:?]
at Source) ~[?:?]
at Source) ~[?:?]
at org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler.bindToChannelAndAddress( ~[graylog.jar:?]
at org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler.bind( ~[graylog.jar:?]
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind( ~[graylog.jar:?]
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind( ~[graylog.jar:?]
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind( ~[graylog.jar:?]
at org.glassfish.grizzly.http.server.NetworkListener.start( ~[graylog.jar:?]
at org.glassfish.grizzly.http.server.HttpServer.start( ~[graylog.jar:?]
at org.graylog2.shared.initializers.JerseyService.startUpApi( ~[graylog.jar:?]
at org.graylog2.shared.initializers.JerseyService.startUp( ~[graylog.jar:?]
at$DelegateService$ ~[graylog.jar:?]
at$ ~[graylog.jar:?]
at Source) ~[?:?]
2023-04-14T14:37:07.055+02:00 INFO [Server] SIGNAL received. Shutting down.

May be not the update to Graylog 5.0.6 (from 5.0.5) ist the problem, rather a background update of the SLES 15 to level SLES15 SP5 which was done by the “provider”.

There is a two node Opensearch cluster running in the background (2.5.0).

The strange thing is, that one node (master) runs fine, and the other one (not master) has the mentioned problem.

Does anyone know waht to do or check?


Dietmar Schurr

Hey Dietmar!

The error is resulting from the Graylog server failing to bind to a port for the HTTP interface. The most common error would be that there is already something running on port 9000. Can you make sure that no other process is occupying that port?

The port seems to be unoccupied.
netstat -tulpen | grep 9000
gives no result.

I checked meanwhile SELinux, seems to be disabled.

Thanks in advance for your help.

Dietmar Schurr


in fact there was the value for http_bind_address in the server.conf wrong.

Once I fixed it, the problem was gone.

Thanks for your help.


Dietmar Schurr

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