Hello,
When I try to access the Analyze APIs page from the gateway, I get the following message:
Kibana server is down. Please make sure that Kibana server is running or not
Do you have tracks?
thank you in advance
Please share errors from APIGatewayLog.log
Hello
It shows the following error trace
ERROR Helper - Error occured while loading configuration.
ERROR KibanaProxy -
This problem has occurred after restarting the Gateway
thanks in advance
That’s strange! can you quickly check below and verify if host and port are correct:
<SAG_Install_Directory>/profiles/IS_default/apigateway/config/uiconfiguration.properties
apigw.dashboard.url = http://<valid_hostname>:9405
apigw.es.url = http://<valid_hostname>:9240
Yes that’s what I have
I think I found the cause of the problem
the server is not listening on port 9405
Can you provide your os specs.
Stop API gateway completely and start it by doing this it will bring up the elastic search kibana at the same time. Simultaneously check the server logs and API gateway logs and see if any errors have been received.
I restarted the gateway, and still the problem
[
DEBUG KibanaProcessManager - start command [./kibana, -p, 9405, -e, http://:9240]
2018-07-11 10:45:58 DEBUG KibanaProcessManager - Executing : [./kibana, -p, 9405, -e, http://9240]
2018-07-11 10:46:39 DEBUG wire - http-outgoing-6 << “{“dashboardInstance”:“http://:9405”}”
2018-07-11 10:46:40 DEBUG PoolingHttpClientConnectionManager - Connection request: [route: {}->http://:9405][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
2018-07-11 10:46:40 DEBUG PoolingHttpClientConnectionManager - Connection leased: [id: 0][route: {}->http://:9405][total kept alive: 0; route allocated: 1 of 2; total allocated: 1 of 20]
2018-07-11 10:46:40 DEBUG MainClientExec - Opening connection {}->http://:9405
2018-07-11 10:46:40 DEBUG DefaultHttpClientConnectionOperator - /10.9.124.82:9405
2018-07-11 10:46:40 DEBUG PoolingHttpClientConnectionManager - Connection released: [id: 0][route: {}->http://9405][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
2018-07-11 10:46:40 ERROR KibanaProxy - Connect to :9405 [/10.9.124.82] failed: Connection refused (Connection refused)
2018-07-11 10:47:03 DEBUG wire - http-outgoing-16 << “{“dashboardInstance”:“http://:9405”}”
]
It’s good, I fixed the problem
The problem is related to a restart of the gateway done in root, of the blow of the files like that of the kibana.pid are in root, and another user can not erase them
Thank you @M@he$h
Makes sense, thanks for letting us know the root cause. It will definitely help other users here.
Hi guys,
So I’m also having “Kibana server is down. Please make sure whether Kibana server is running or not” problem.
and I checked the APIGateway.log and have
DEBUG PoolingHttpClientConnectionManager - Connection request: [route: {}->http://:9405][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
DEBUG PoolingHttpClientConnectionManager - Connection leased: [id: x][route: {}->http://:9405][total kept alive: 0; route allocated: 1 of 2; total allocated: 1 of 20]
DEBUG MainClientExec - Opening connection {}->http://:9405
DEBUG DefaultHttpClientConnectionOperator - Connecting to /:9405
DEBUG PoolingHttpClientConnectionManager - Connection released: [id: 8][route: {}->http://:9405][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
ERROR KibanaProxy - Connect to :9405 [/] failed: Connection refused (Connection refused)
DEBUG wire - http-outgoing-1195 << “{“dashboardInstance”:“http://:9405”}”
And checked the <SAG_Install_Directory>/profiles/IS_default/apigateway/config/uiconfiguration.properties
and I can’t see the “apigw.dashboard.url = http://<valid_hostname>:9405” in the setting.
I read the documentation of SAG and it was also talking about the same setting in the uiconfiguration.properties. Haven’t been able to setup kibana yet, so settings are at default.
Descided to restart API Gateway to see if kibana will still be down. server.log seems fine.
Kibana is up after the restart.
Checked APIGateway.log again and found this error trace.
2019-02-08 07:22:10 ERROR KibanaProxy - Error while processing the request
org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:356)
at org.apache.catalina.connector.OutputBuffer.flushByteBuffer(OutputBuffer.java:808)
at org.apache.catalina.connector.OutputBuffer.writeByte(OutputBuffer.java:428)
at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:80)
at com.softwareag.apigateway.ui.kibana.KibanaProxy.executeProxyRequest(KibanaProxy.java:194)
at com.softwareag.apigateway.ui.kibana.KibanaProxy.doPost(KibanaProxy.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
API GW version is 10.1, IS_10.1_Core_Fix6.
Hi Mark,
When there is an request to Kibana is in progress, if you either navigate out of analytics tab or if you apply a new filter when a previous request is in progress, you will see this ClientAbortException in the logs since the previous request is closed forcefully. Otherwise, these errors should not be visible in the logs.
Regards,
Dhivakar
Ohh, I see. Thank you for the fast response Dhivakar 