OEM 24ai: Start OMS Failed With Error "Status:API Gateway start Failed/Timed Out"
(Doc ID 3046789.1)
Last updated on JANUARY 07, 2025
Applies to:
Enterprise Manager Base Platform - Version 24.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Start OMS Failed With Error "Status:API Gateway start Failed/Timed Out"
<gc_inst>/em/EMGC_OMS1/sysman/log/emctl.log
2024-09-10 01:47:25,132 [Thread-7] INFO commands.BaseCommand - <OUT>Tue Sep 10 01:47:25 UTC 2024 INFO: Loading Gateway properties file <gc_inst>/em/apigateway_inst/apigateway.properties
2024-09-10 01:47:25,175 [Thread-7] INFO commands.BaseCommand - <OUT>Tue Sep 10 01:47:25 UTC 2024 INFO: Log File : <gc_inst>/em/apigateway_inst/logs/application.log
2024-09-10 01:47:25,181 [Thread-7] INFO commands.BaseCommand - <OUT>Tue Sep 10 01:47:25 UTC 2024 INFO: Executing: <EXT_OMS_HOME>/oracle_common/jdk/bin/java -Doracle.jdbc.autoCommitSpecCompliant=false -Djava.security.egd=file:///dev/urandom -Xmx512M -XX:+UseG1GC -XX:ErrorFile=<gc_inst>/em/apigateway_inst/logs/HS_ERR_PID%p.log -Xloggc:<gc_inst>/em/apigateway_inst/logs/gc.log -XX:-OmitStackTraceInFastThrow -jar <EXT_OMS_HOME>/apigateway/lib/em-platform-apigway-api-24.1.0.0.0.jar server <EXT_OMS_HOME>/apigateway/conf/server-config/em.conf
2024-09-10 01:47:25,186 [Thread-7] INFO commands.BaseCommand - <OUT>Tue Sep 10 01:47:25 UTC 2024 INFO: Executing command rm -f <gc_inst>/em/apigateway_inst/start.txt
2024-09-10 01:47:25,210 [Thread-7] INFO commands.BaseCommand - <OUT>Tue Sep 10 01:47:25 UTC 2024 INFO: API Gateway start in progress ...
2024-09-10 01:47:27,282 [Thread-7] INFO commands.BaseCommand - <OUT>Tue Sep 10 01:47:27 UTC 2024 INFO: API Gateway start in progress ...
20
2024-09-10 01:29:26,254 [Thread-7] INFO commands.BaseCommand - <OUT>Tue Sep 10 01:29:26 UTC 2024 INFO: API Gateway start in progress ...
2024-09-10 01:29:28,396 [Thread-7] INFO commands.BaseCommand - <OUT>Tue Sep 10 01:29:28 UTC 2024 ERROR: Status:API Gateway start Failed/Timed Out
2024-09-10 01:29:28,407 [main] INFO commands.StartCommand - startGwExitCode=1
2024-09-10 01:29:28,407 [main] ERROR commands.BaseCommand - WebTier Could Not Be Started.
2024-09-10 01:29:28,407 [main] ERROR wls.OMSController - OMSController failed for start oms
2024-09-10 01:29:28,407 [main] ERROR wls.OMSController - OMSController Error: WebTier Could Not Be Started.
java.lang.Exception: WebTier Could Not Be Started.
<gc_inst>/em/apigateway_inst/logs/application.log
java.lang.RuntimeException: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:7788
at org.eclipse.jetty.setuid.SetUIDListener.lifeCycleStarting(SetUIDListener.java:229)
at org.eclipse.jetty.util.component.AbstractLifeCycle.setStarting(AbstractLifeCycle.java:205)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
at io.dropwizard.cli.ServerCommand.run(ServerCommand.java:52)
at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:68)
at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:98)
at io.dropwizard.cli.Cli.run(Cli.java:78)
at io.dropwizard.Application.run(Application.java:94)
at com.oracle.sysman.platform.apigway.EmPlatformApigwayApi.main(EmPlatformApigwayApi.java:362)
Caused by: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:7788
at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)
at org.eclipse.jetty.setuid.SetUIDListener.lifeCycleStarting(SetUIDListener.java:216)
... 8 common frames omitted
Caused by: java.net.BindException: Address already in use
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |