ATLAS Metadata Server fails to start on HDP 2.6

[#1]

I have a clean install of HDP 2.6 but the Atlas Metadata Server has failed to start. The dependent services (Hbase, Kafka and Ambari Infra) are all started. Please find the error message below;

Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py", line 259, in <module>
    MetadataServer().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 314, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py", line 117, in start
    not_if=no_op_test
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__
    self.env.run()
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run
    self.run_action(resource, action)
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action
    provider_action()
  File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 262, in action_run
    tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, in inner
    result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in checked_call
    tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in _call_wrapper
    result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in _call
    raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'source /usr/hdp/current/atlas-server/conf/atlas-env.sh ; /usr/hdp/current/atlas-server/bin/atlas_start.py' returned 255. Exception: [Errno 2] No such file or directory 
Traceback (most recent call last):
  File "/usr/hdp/current/atlas-server/bin/atlas_start.py", line 149, in <module>
    returncode = main()
  File "/usr/hdp/current/atlas-server/bin/atlas_start.py", line 73, in main
    mc.expandWebApp(atlas_home)
  File "/usr/hdp/2.6.0.3-8/atlas/bin/atlas_config.py", line 143, in expandWebApp
    jar(atlasWarPath)
  File "/usr/hdp/2.6.0.3-8/atlas/bin/atlas_config.py", line 196, in jar
    process = runProcess(commandline)
  File "/usr/hdp/2.6.0.3-8/atlas/bin/atlas_config.py", line 232, in runProcess
    p = subprocess.Popen(commandline, stdout=stdoutFile, stderr=stderrFile, shell=shell)
  File "/usr/lib64/python2.6/subprocess.py", line 642, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.6/subprocess.py", line 1238, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

[#2]

@Joshua Adeleke, could you confirm if the following files exist in your cluster:

/usr/hdp/current/atlas-server/conf/atlas-env.sh

/usr/hdp/current/atlas-server/bin/atlas_start.py

The error mentions about file/directory not found. If the files exists, could you share the atlas logs here from /var/log/atlas/application.log.

[#3]

@Sarath Subramanian The atlas-env.sh and atlas_start.py files exist but there is no log generated.

[#4]

@Sarath Subramanian

I experience the same problem. The above mentioned files exist. The contents of the Atlas .err file in the log directory has the following content:

-------------

log4j:WARN Continuable parsing error 37 and column 14

log4j:WARN The content of element type "appender" must match "(errorHandler?,param*,r

ollingPolicy?,triggeringPolicy?,connectionSource?,layout?,filter*,appender-ref*)".

log4j:WARN No such property [maxFileSize] in org.apache.log4j.DailyRollingFileAppende

r.

log4j:WARN No such property [maxFileSize] in org.apache.log4j.DailyRollingFileAppende

r.

---------------

[#5]

Hi ,

The files you mentioned are not available on the node on which the atlas has been installed. Can you please suggest. 

[#6]

I know this is an old question, but someone may benefit from my answer. The problem is that the atlas.war file did not extract properly.

Fix it like this:

ls /usr/hdp/current/atlas-server/server/webapp/atlas

If the war did not get extracted properly, you will see no files in this directory. If that's the case, do this:

su - atlas
cd /usr/hdp/current/atlas-server/server/webapp/atlas
jar xvf ../atlas.jar

Now you can start Atlas.

[#7]

In addition to the fix from james.jones, you may also need to manually work around the bug AMBARI-18368, whose detailed instructions are here:

https://issues.apache.org/jira/browse/AMBARI-18368

[#8]

@William Lu

Thanks!

[#9]

the command is

jar xvf ../atlas.war