APIGateway 10.3 -- Connection refused error in APIGateway log during server restart

Hello,

We are getting below errors during server restart:

APIGateway Log:

2020-04-05 00:31:26 ERROR ISConfiguration - Attempt to login with technical user failed: javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused: connect
java.io.IOException: javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused: connect

The server is in cluster and it has 3 nodes. The error occurred only during restart of any/all nodes. We don’t see any issue/impact or such errors after server restart completes. Customer wants to understand regarding such behavior. Please refer server log of same time stamp.

Server Log:

2020-04-05 00:30:20 AEDT [ISS.0028.0012I] WmAPIGateway: Startup service (apigateway:startup)
2020-04-05 00:30:20 AEDT [YAI.0300.0001I] [default][ServerName] Gateway Logger successfully registered and initialized.
2020-04-05 00:30:20 AEDT [YAI.0300.0109I] [default][ServerName] Setting watt properties.
2020-04-05 00:30:20 AEDT [YAI.0300.0105I] [default][ServerName] Starting ElasticSearch. API Gateway will wait for 300 seconds for ElasticSearch availability
2020-04-05 00:30:53 AEDT [YAI.0300.0099I] [default][ServerName] ElasticSearch started at http://qwswmagwas001.lfxau.linfox.com:9240 in 32 seconds.
2020-04-05 00:31:01 AEDT [YAI.0300.8888I] [default][ServerName] Trace: Properties loaded from config.properties
2020-04-05 00:31:01 AEDT [YAI.0300.8887I] [default][ServerName] Debug: creating rest client
2020-04-05 00:31:01 AEDT [YAI.0300.8887I] [default][ServerName] Debug: Rest Client Created
2020-04-05 00:31:02 AEDT [YAI.0300.0139I] [default][ServerName] Elasticsearch is not ready to serve the requests.
2020-04-05 00:31:03 AEDT [YAI.0300.8887I] [default][ServerName] Debug: Elastic Search cluster status is - yellow
2020-04-05 00:31:03 AEDT [YAI.0300.0138I] [default][ServerName] Elasticsearch is ready to serve the requests.
2020-04-05 00:31:03 AEDT [YAI.0300.8887I] [default][ServerName] Debug: Elasticsearch client Version - 5.6.4
2020-04-05 00:31:04 AEDT [YAI.0300.0117I] [default][ServerName] WS-Stack repository located at
2020-04-05 00:31:04 AEDT [YAI.0300.0118I] [default][ServerName] WS-Stack configuration file located:
2020-04-05 00:31:10 AEDT [YAI.0012.0001I] [default][ServerName] Initializing GatewayEhCacheManager
2020-04-05 00:31:10 AEDT [YAI.0012.0003I] [default][ServerName] APIGateway is having bigmemory license and its clustered.
2020-04-05 00:31:27 AEDT [YAI.0012.0006I] [default][ServerName] Creating new cache for CONFIGURATIONS(SMALL_UNBOUNDED)
2020-04-05 00:31:28 AEDT [YAI.0205.0500I] [default][ServerName] Audit sender startup
2020-04-05 00:31:30 AEDT [YAI.0300.0202I] [default][ServerName] No mediator migration file found: packages/WmAPIGateway/bin/migrate/mediator/pg-config.properties.
2020-04-05 00:31:30 AEDT [YAI.0300.0202I] [default][ServerName] No mediator migration file found: packages/WmAPIGateway/bin/migrate/mediator/serviceConfig.xml.
2020-04-05 00:31:32 AEDT [YAI.0300.0075I] [default][ServerName] Loaded Kibana objects successfully to datastore.
2020-04-05 00:31:32 AEDT [YAI.0300.0133I] [default][ServerName] Asset cache is already present in type configurations for index gateway_default
2020-04-05 00:31:32 AEDT [YAI.0300.8889W] [default][ServerName] /_ingest/pipeline/common_log_pipeline Not exists {1}
2020-04-05 00:31:32 AEDT [YAI.0300.0133I] [default][ServerName] Asset GlobalLogInvocationPolicy is already present in type policy for index gateway_default
2020-04-05 00:31:32 AEDT [YAI.0300.0133I] [default][ServerName] Asset GlobalLogInvocationPolicyAction is already present in type policyactions for index gateway_default

Could you please advise.

Hi,

The error log you see in APIGateway.log is because the UI is not able to connect to API Gateway server. When the server is up, those errors will be disappeared. This is usual and not an issue.

Thanks,
Clench