[jira] [Commented] (AMBARI-23346) Ambari server start exits with non zero

2018-04-06 Thread Aravindan Vijayan (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-23346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428936#comment-16428936
 ] 

Aravindan Vijayan commented on AMBARI-23346:


[~ste...@apache.org] Ambari Server does not bring in aws-shaded-sdk or hadoop 
JARs. But, the problem could likely be the time taken for the servlet to scan 
the jar. I will take a look if we can exclude specific JARs from being scanned. 

> 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: 2h 10m
>  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)


[jira] [Commented] (AMBARI-23346) Ambari server start exits with non zero

2018-03-26 Thread Steve Loughran (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-23346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


[jira] [Commented] (AMBARI-23346) Ambari server start exits with non zero

2018-03-26 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-23346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414158#comment-16414158
 ] 

Hudson commented on AMBARI-23346:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8912 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8912/])
AMBARI-23346 : Ambari server start exits with non zero. (avijayan: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9aa2c6bd36b64be3168aed5824441d61f628eb54])
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py


> 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)


[jira] [Commented] (AMBARI-23346) Ambari server start exits with non zero

2018-03-23 Thread Aravindan Vijayan (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-23346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411592#comment-16411592
 ] 

Aravindan Vijayan commented on AMBARI-23346:


*Analysis*

No single point of slowness seen in the Ambari Server startup. It took about 1 
min for the UI to be accessible while the startup script fails at 50 seconds.

Some high latency actions (~5 seconds)

{code}
14 Mar 2018 19:53:59,447  INFO [main] ViewExtractor:94 - Extracting files from 
ambari-admin-2.7.0.0.143.jar.
14 Mar 2018 19:54:04,452  INFO [main] AmbariServer:214 - Found 
org/apache/ambari/server/controller/AmbariServer.class class in 
file:/usr/lib/ambari-server
/ambari-server-2.7.0.0.143.jar!/org/apache/ambari/server/controller/AmbariServer.class
{code}

{code}
14 Mar 2018 19:54:12,459  INFO [main] AuditLoggerModule:82 - Binding audit 
event creator class 
org.apache.ambari.server.audit.request.eventcreator.ViewPrivilegeEventCreator
14 Mar 2018 19:54:17,270  INFO [main] HostRoleCommandDAO:275 - Host role 
command status summary cache enabled !
{code}

{code}
14 Mar 2018 19:54:22,875  INFO [pool-4-thread-1] 
AbstractPoolBackedDataSource:212 - Initializing c3p0 pool... 
14 Mar 2018 19:54:26,354  INFO [pool-4-thread-1] 
AmbariLdapConfigurationProvider:103 - Loaded LDAP configuration instance: [ {} ]
{code}

{code}
14 Mar 2018 19:54:40,485  INFO [main] StackContext:222 - Loaded all VDF in 
5530ms
{code}

{code}
14 Mar 2018 19:54:58,374  INFO [main] ViewExtractor:94 - Extracting files from 
hive-jdbc-2.7.0.0.143.jar.
14 Mar 2018 19:55:01,602  INFO [main] ViewRegistry:1898 - setting up logging 
for view HIVE{1.5.0} as per property file view.log4j.properties
{code}

And some VDF related exceptions like
{code}
14 Mar 2018 19:58:58,612  WARN [Stack Version Loading Thread] 
RepoVdfCallable:142 - Could not load version definition for HDP-3.0 identified 
by http://s3.
amazonaws.com/dev.hortonworks.com/HDP/ubuntu12/3.x/BUILDS/2.6.0.0-598/HDP-2.6.0.0-598.xml.
 http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu12/3.x/BU
ILDS/2.6.0.0-598/HDP-2.6.0.0-598.xml
java.io.FileNotFoundException: 
http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu12/3.x/BUILDS/2.6.0.0-598/HDP-2.6.0.0-598.xml
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
at java.net.URL.openStream(URL.java:1045)
at 
org.apache.ambari.server.state.repository.VersionDefinitionXml.load(VersionDefinitionXml.java:543)
at 
org.apache.ambari.server.state.stack.RepoVdfCallable.timedVDFLoad(RepoVdfCallable.java:154)
at 
org.apache.ambari.server.state.stack.RepoVdfCallable.mergeDefinitions(RepoVdfCallable.java:136)
at 
org.apache.ambari.server.state.stack.RepoVdfCallable.call(RepoVdfCallable.java:79)
at 
org.apache.ambari.server.state.stack.RepoVdfCallable.call(RepoVdfCallable.java:41)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}

The number of jars in /usr/lib/ambari-server/ have increased from 144 (2.6.2) 
to 172 (2.7.0).

The number of classes loaded during server start has increased from 11681 to 
15814. That is about a 35% jump.

*Fix*
Increasing the timeout to 90 seconds to make sure start command does not fail 
on slower systems. 

> 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
> Fix For: 2.7.0
>
>
> 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
>