Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Amabari server not starting after system reboot.

avatar
New Member

Hi,

I have setup HDP 2.4.2 cluster using Amabri automated install. I have just one machine. On this I have installed the ambari-agent as well. All was working fine, just high RAM consumption. So, I manually stopped all the services from Ambari UI and then rebooted the machine.

Now when I try to start the ambari server, I get the foll error on the screen:

Waiting for server start....................
ERROR: Exiting with exit code -1. 
REASON: Ambari Server java process died with exitcode 255. Check /var/log/ambari-server/ambari-server.out for more information.

and inside the ambari-server.log file, I have the following msgs:

07 Mar 2017 12:43:09,823  INFO [main] ViewRegistry:1566 - View deployed: SLIDER{2.0.0}.
07 Mar 2017 12:43:09,828  INFO [main] ViewRegistry:1538 - Reading view archive /var/lib/ambari-server/resources/views/tez-view-2.2.2.0.460.jar.
07 Mar 2017 12:43:10,005  INFO [main] ViewRegistry:1598 - Auto creating instance of view TEZ for cluster winnow.
07 Mar 2017 12:43:10,005  INFO [main] ViewRegistry:1566 - View deployed: TEZ{0.7.0.2.3.4.0-460}.
07 Mar 2017 12:43:10,006  INFO [main] HeartbeatProcessor:154 - **** Starting heartbeats processing threads ****
07 Mar 2017 12:43:10,007  INFO [main] AmbariServer:449 - ********** Started Heartbeat handler **********
07 Mar 2017 12:43:10,008  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:157 - Heartbeat lost from host hdp.com
07 Mar 2017 12:43:10,008 ERROR [main] AmbariServer:844 - Failed to run the Ambari Server
java.lang.NumberFormatException: For input string: "900000000000000"  
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)  
at java.lang.Integer.parseInt(Integer.java:583)  
at java.lang.Integer.parseInt(Integer.java:615)  
at org.apache.ambari.server.configuration.Configuration.getConnectionMaxIdleTime(Configuration.java:1570)  
at org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:502)  
at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:842)

Not sure what's wrong here!

Thanks

1 ACCEPTED SOLUTION

avatar
Master Mentor

@Devpriyo Bhattacharya

Edit the "/etc/ambari-server/conf/ambari.properties" file and lower the value as following. (You seem to have defined too large value there "900000000000000")

server.connection.max.idle.millis=900000

.

The default value can be seen (as '900000') in the Ambari code base as following:

https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/con...

.

That seems to be causing the following error:

ERROR [main] AmbariServer:844 - Failed to run the Ambari Server java.lang.NumberFormatException: For input string: "900000000000000"  
   at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)  

View solution in original post

2 REPLIES 2

avatar
Master Mentor

@Devpriyo Bhattacharya

Edit the "/etc/ambari-server/conf/ambari.properties" file and lower the value as following. (You seem to have defined too large value there "900000000000000")

server.connection.max.idle.millis=900000

.

The default value can be seen (as '900000') in the Ambari code base as following:

https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/con...

.

That seems to be causing the following error:

ERROR [main] AmbariServer:844 - Failed to run the Ambari Server java.lang.NumberFormatException: For input string: "900000000000000"  
   at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)  

avatar
New Member

Thanks a ton @Jay SenSharma. The problem was that I was not able to locate the ambari.properties file. First ambari install. Well, as suggested, I changed the value and now its working.