ReST input creation: Address already in use

(Gianluca Valentini) #1

I’m using Graylog OVA 2.4.3 and when I try to create Input using ReST, Graylog shows the created Inputs marked as Failed: The message that I see is: Address already in use.


Here the JSon about the related input:


"title": "test_6f1c06e2-e27c-4c41-a577-bd17f37c3547",

"global": true,

"name": "Beats",

"content_pack": "5bbb21bd1838ed2ce0d6524e",

"created_at": "2018-10-08T09:22:04.207Z",

"type": "",

"creator_user_id": "admin",

"attributes": {

"recv_buffer_size": 1048576,

"port": 12202,

"tls_key_file": "",

"tls_enable": false,

"tls_key_password": "",

"tcp_keepalive": false,

"tls_client_auth_cert_file": "",

"tls_client_auth": "disabled",

"override_source": "",

"bind_address": "",

"tls_cert_file": ""


"static_fields": {

"ENABLE_ENRICH": "false",

"entity_name": "NONE",

"tags": "test_6f1c06e2-e27c-4c41-a577-bd17f37c3547"


"node": null,

"id": "5bbb21bc9fb73040f9349195"

The port number is 12202

Executing netstat -plnt I can see the result below

All seems correct, but Graylog give me the error message.
Looking the log file we can see the stack trace:

2018-10-08_09:22:51.44381 ERROR [InputLauncher] The [] input with ID <5bbb21bc9fb73040f9349195> misfired. Reason: Address already in use.
2018-10-08_09:22:51.44430 org.graylog2.plugin.inputs.MisfireException: org.graylog2.plugin.inputs.MisfireException: Failed to bind to: /
2018-10-08_09:22:51.44485 at org.graylog2.plugin.inputs.MessageInput.launch( ~[graylog.jar:?]
2018-10-08_09:22:51.44569 at org.graylog2.shared.inputs.InputLauncher$ [graylog.jar:?]
2018-10-08_09:22:51.44616 at com.codahale.metrics.InstrumentedExecutorService$ [graylog.jar:?]
2018-10-08_09:22:51.44721 at java.util.concurrent.Executors$ [?:1.8.0_161]
2018-10-08_09:22:51.44763 at [?:1.8.0_161]
2018-10-08_09:22:51.44805 at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:1.8.0_161]
2018-10-08_09:22:51.44877 at java.util.concurrent.ThreadPoolExecutor$ [?:1.8.0_161]
2018-10-08_09:22:51.44965 at [?:1.8.0_161]
2018-10-08_09:22:51.45498 Caused by: org.graylog2.plugin.inputs.MisfireException: Failed to bind to: /
2018-10-08_09:22:51.45539 at org.graylog2.plugin.inputs.transports.NettyTransport.launch( ~[graylog.jar:?]
2018-10-08_09:22:51.45600 at org.graylog2.plugin.inputs.MessageInput.launch( ~[graylog.jar:?]
2018-10-08_09:22:51.45675 … 7 more
2018-10-08_09:22:51.45721 Caused by: Failed to bind to: /
2018-10-08_09:22:51.45793 at org.jboss.netty.bootstrap.ServerBootstrap.bind( ~[graylog.jar:?]
2018-10-08_09:22:51.46060 at org.graylog2.plugin.inputs.transports.NettyTransport.launch( ~[graylog.jar:?]
2018-10-08_09:22:51.46179 at org.graylog2.plugin.inputs.MessageInput.launch( ~[graylog.jar:?]
2018-10-08_09:22:51.46210 … 7 more
2018-10-08_09:22:51.46263 Caused by: Address already in use
2018-10-08_09:22:51.46438 at Method) ~[?:1.8.0_161]
2018-10-08_09:22:51.46507 at ~[?:1.8.0_161]
2018-10-08_09:22:51.46688 at ~[?:1.8.0_161]
2018-10-08_09:22:51.46744 at ~[?:1.8.0_161]
2018-10-08_09:22:51.46870 at ~[?:1.8.0_161]
2018-10-08_09:22:51.47187 at$ ~[graylog.jar:?]
2018-10-08_09:22:51.47258 at ~[graylog.jar:?]
2018-10-08_09:22:51.47336 at ~[graylog.jar:?]
2018-10-08_09:22:51.47365 at ~[graylog.jar:?]
2018-10-08_09:22:51.47417 at ~[graylog.jar:?]
2018-10-08_09:22:51.47495 at org.jboss.netty.util.internal.DeadLockProofWorker$ ~[graylog.jar:?]
2018-10-08_09:22:51.47566 … 3 more
2018-10-08_09:22:51.47672 INFO [InputStateListener] Input [Beats/5bbb21bc9fb73040f9349195] is now FAILED

If I restart Graylog the Input become valid, without changes!!
Is there something that I can do to fix this problem?

Why at the first time, Graylog say me that the input is not valid but after restarting the server, the input become good?


(Jan Doberstein) #2

Have you tried if that is happening with the latest stable release too?

(2.4.6 at time of writing)

(Gianluca Valentini) #3

Hi @jan
currently I cannot upgrade my Graylog env to the last version (2.4.6).
So I can not give you an answer

(Gianluca Valentini) #4

Any suggestions to understand what happened?

(Gianluca Valentini) #5

Hi @jan
I update the env to the latest version (v 2.4.6) and I have the same problem.

Do you have any suggestions?

(system) #6

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