My Oracle Support Banner

Step 8 (StartHadoopServices) Of Mammoth Installation Fails Because NameNodes Fail to Start with "java.lang.illegalArgumentException: The value of property bind.address must not be null" (Doc ID 2490013.1)

Last updated on APRIL 25, 2020

Applies to:

Oracle Big Data Cloud Machine - Version N/A and later
Linux x86-64

Symptoms

Step 8 (StartHadoopServices) of Mammoth installation fails as below. Note that the Host Inspector reports all nodes in good health.

Error [3873]: (//bdanode03//Stage[main]/Hadoop::Startsvc2/Exec[setup_scm]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm_<##>.out returned 1 instead of one of [0]


Additional Information:

1. /opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm_<##>.out on Node 3 reports that the HDFS service fails to start.

....
Command 123 finished after 25 secondsOperation failedResult Message is: "Failed to start the HDFS service".
Operation failed
Result Message is: "Failed to start the HDFS service",
...


2. The HDFS service does not start because the NameNodes do not start. The NameNode logs shows that the NameNodes fails to start with "java.lang.illegalArgumentException: The value of property bind.address must not be null".

...
Starting Web-server for hdfs at: http://host.domain:50070
INFO Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Sl4jLog
INFO AuthenticationFilter Unable to initialize FileSignerSecretProvider, failing back to use random secrets.
INFO HttpRequestLog Http request log for http.requests.namenode is not defined
INFO Httpserver2 Added global filter 'safety' (class=org.apache.hadoop.http.HttpServer2$QuotingInputFilter)
ERROR Namenode
Failed to start NameNode
java.lang.illegalArgumentException: The value of property bind.address must not be null

...

3. The JournalNode logs shows that the JournalNodes also fail to start with "java.lang.illegalArgumentException: The value of property bind.address must not be null".

...
INFO org.apache.hadoop.http.HttpRequestLog: Http request log for http.requests.journal is not defined
INFO org.apache.hadoop.http.HttpServer2: Added global filter 'safety; (class=org.apache.hadoop.http.HttpServer2$QuotingInputFilter)
ERROR org.apache.hadoop.hdfs.qjournal.server.JournalNode: Failed to start Journalnode.
java.lang.illegalArgumentException: The value of property bind.address must not be null
...


4. Investigating the "0.0.0.0" IP address further with "nslookup 0.0.0.0" shows that expected information is not returned.

"nslookup 0.0.0.0" incorrectly reports output like: 

 

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
 Problem Cause
 Additional Checks
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.