BDA Mammoth Upgrade Fails at Step 10 with: service odi-agent start' returned 1 on Node 4 (Doc ID 1616674.1)

Last updated on JANUARY 23, 2014

Applies to:

Big Data Appliance Integrated Software - Version 2.2.0 and later
Linux x86-64

Symptoms

The Mammoth upgrade (./mammoth -p) fails at Step 10 with below error indicating a problem with ODI on Node 4.  Where Node 4 is the service location of the ODI Agent in Oracle Big Data Appliance V2 releases. (See Oracle Big Data Appliance Software / Service Roles Layout on V2.2.* / V2.3.1 (Doc ID 1575442.1)).

...
Error: [12865] (//bdanode04.example.com//Stage[main]/Odi::Odisetup/Service[odi-agent]/ensure) change from stopped to running failed: Could not start Service[odi-agent]: Execution of '/sbin/service odi-agent start' returned 1: at /opt/oracle/BDAMammoth/puppet/modules/odi/manifests/odisetup.pp:300.
...
ERROR Puppet script had errors.
ERROR unable to continue with install until errors are fixed #Step 10#
INFO Time spent in step 10 InstallBDASoftware is *** seconds

 

The puppet agent log files at: /opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-bdanode4-<timestamp>.log also show the error:

Jan 23 12:49:00 bdanode01 puppet-master[12865]: (//bdanode04.example.com//Stage[main]/Odi::Odisetup/Service[odi-agent]/ensure) change from stopped to running failed: Could not start Service[odi-agent]: Execution of '/sbin/service odi-agent start' returned 1:  at /opt/oracle/BDAMammoth/puppet/modules/odi/manifests/odisetup.pp:300


The /var/log/odi_agent.log on Node 4 of the cluster shows:

...
ODI-1441: Unable to connect to the master repository at JBDC URL=jdbc:oracle:thin:@localhost:1521:ORA111 with USER=USER_NAME.
...

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms