[
https://issues.apache.org/jira/browse/AMBARI-23346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414287#comment-16414287
]
Steve Loughran commented on AMBARI-23346:
-----------------------------------------
There's been issues in the past with the servlet introspection slowing things
down as JARs are scanned for them; the aws-shaded-sdk and any shaded hadoop
SDKs being risk points. Is that likely here? And if so, any way to tell the
JSP/servlet 3.0 code to not scan specific jars?
> Ambari server start exits with non zero
> ---------------------------------------
>
> Key: AMBARI-23346
> URL: https://issues.apache.org/jira/browse/AMBARI-23346
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> On slower machines, ambari server (2.7.0) start command fails because the web
> UI availability check times out at 50 seconds.
> {code}
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server
> start............................................................
> DB configs consistency check: no errors and warnings were found.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> failed and return code :1
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
