WARN [ProxiedResource] Unable to call http

Graylog Central (peer support)
1

Hi All,

i am receiving the below Error Message while accessing the Graylog
I am not using any SSL and have disabled the SSL conf on the Graylog server.conf file.

Graylog-Error
Graylog-Error.jpg1819×719 453 KB

2

Error LOG-

WARN  [ProxiedResource] Unable to call http://:9000/api/system/metrics/multiple on node <f2f3f21c-ed04-4005-8ad5-c17fd7f443fd>
java.net.SocketTimeoutException: connect timed out
        at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_171]
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_171]
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_171]
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_171]
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_171]
        at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_171]
        at okhttp3.internal.platform.Platform.connectSocket(Platform.java:125) ~[graylog.jar:?]
        at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:238) ~[graylog.jar:?]
        at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:158) ~[graylog.jar:?]
        at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:256) ~[graylog.jar:?]
        at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:134) ~[graylog.jar:?]
        at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:113) ~[graylog.jar:?]
        at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42) ~[graylog.jar:?]
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[graylog.jar:?]
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) ~[graylog.jar:?]
        at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93) ~[graylog.jar:?]
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[graylog.jar:?]
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) ~[graylog.jar:?]
        at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) ~[graylog.jar:?]
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[graylog.jar:?]
        at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:125) ~[graylog.jar:?]
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[graylog.jar:?]
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) ~[graylog.jar:?]
        at org.graylog2.rest.RemoteInterfaceProvider.lambda$get$0(RemoteInterfaceProvider.java:59) ~[graylog.jar:?]
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[graylog.jar:?]
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) ~[graylog.jar:?]
        at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200) ~[graylog.jar:?]
        at okhttp3.RealCall.execute(RealCall.java:77) ~[graylog.jar:?]
        at retrofit2.OkHttpCall.execute(OkHttpCall.java:180) ~[graylog.jar:?]
3

The URI in this message is broken. Have you redacted the hostname or is this the original log message?

4

http://(i have removed the url while pasting log here):9000/api/system/

5

What’s the output of the following command on the machine running Graylog?

# curl -i 'http://<URL-from-your-logs>:9000/api/?pretty=true'
6

Hi @jochen,

I’m having the exact same issue as @harishpal2090. I ran the curl command like you asked. Here is the output of mine:

curl -i ‘http://10.12.14.156:9000/api/?pretty=true’

HTTP/1.1 200 OK
X-Graylog-Node-ID: 477c437a-3e95-4ad7-b961-9a46b743d1cc
X-UA-Compatible: IE=edge
Content-Type: text/html
Date: Tue, 10 Jul 2018 12:11:01 GMT
Content-Length: 1640

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=“X-UA-Compatible” content=“IE=edge”>
<meta name=“robots” content=“noindex, nofollow”>
<meta charset=“UTF-8”>
<title>Graylog Web Interface</title>
<link rel=“shortcut icon” href=“/assets/favicon.png”>

</head>
<body>
<script src=“/config.js”></script>

<script src=“/assets/vendor.552834c48b86209e305c.js”></script>

<script src=“/assets/polyfill.d62de657b1bfcd25ec80.js”></script>

<script src=“/assets/plugin/org.graylog.plugins.threatintel.ThreatIntelPlugin/plugin.org.graylog.plugins.threatintel.ThreatIntelPlugin.81cab787bad4ca22b96f.js”></script>

<script src=“/assets/plugin/org.graylog.plugins.pipelineprocessor.ProcessorPlugin/plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.8c9a4458c39fe3208ae2.js”></script>

<script src=“/assets/plugin/org.graylog.plugins.map.MapWidgetPlugin/plugin.org.graylog.plugins.map.MapWidgetPlugin.049919e74da17267e882.js”></script>

<script src=“/assets/plugin/org.graylog.plugins.enterprise_integration.EnterpriseIntegrationPlugin/plugin.org.graylog.plugins.enterprise_integration.EnterpriseIntegrationPlugin.cb7b290aaf58d8948b4c.js”></script>

<script src=“/assets/plugin/org.graylog.plugins.collector.CollectorPlugin/plugin.org.graylog.plugins.collector.CollectorPlugin.bf8b7a7e9309b0148f8d.js”></script>

<script src=“/assets/plugin/org.graylog.aws.plugin.AWSPlugin/plugin.org.graylog.aws.plugin.AWSPlugin.b2ad019c873d95bc5ea9.js”></script>

<script src=“/assets/app.d62de657b1bfcd25ec80.js”></script>

</body>
</html>

Please let me know if I can be of any more help.

Thanks

7

My issue got resolved- here is the summary-
i have setup the garylog in Azure instance- and accessing it via Azure public IP/Public DNS Name
My Web URI have put the Azure Public DNS name and in NSG i am allowing same public IP address.
After that it start working-- Still im not sure how it has fixed but it is working now and i can see the node now.

1 Like
8

Either you haven’t used the URI from the error message in your Graylog node’s logs or you’ve misconfigured your Graylog node (rest_listen_uri, web_listen_uri, web_endpoint_uri; see http://docs.graylog.org/en/2.4/pages/configuration/web_interface.html for details).

9

The output of the above curl command that jochen requested to run should provide output similar to the below.

$ curl -i 'http://172.16.1.34:9000/api/?pretty=true'
HTTP/1.1 200 OK
X-Graylog-Node-ID: b5b4a120-f9ce-4106-b178-f2c229797a76
X-Runtime-Microseconds: 592
Content-Type: application/json
Date: Wed, 11 Jul 2018 08:11:56 GMT
Content-Length: 253

{
  "cluster_id" : "c2e6c51a-2e7a-4e34-ae5e-ae5ac6ebc872",
  "node_id" : "b5b4a120-f9ce-4106-b178-f2c229797a76",
  "version" : "2.4.5+8e18e6a",
  "tagline" : "Manage your logs in the dark and have lasers going and make it look like you're from space!"
}
10

Just for your FYI
my elasticsearch conf are- below
elasticsearch_analyzer = standard
output_batch_size = 500
output_flush_interval = 1
output_fault_count_threshold = 5
output_fault_penalty_seconds = 30

check yours ?
file Path- /etc/elasticsearch/elasticsearch.yaml

11

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