Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Atlas Metadata Server error HTTP 503 response from http://localhost:21000/api/atlas/admin/status in 0.000s (HTTP Error 503: Service Unavailable)

Solved Go to solution

Atlas Metadata Server error HTTP 503 response from http://localhost:21000/api/atlas/admin/status in 0.000s (HTTP Error 503: Service Unavailable)

Guru

When I upgraded hdp from 2.5.3 to 2.6.0.3 then I am getting following warning in Ambari:

HTTP 503 response from http://localhost:21000/api/atlas/admin/status in 0.000s (HTTP Error 503: Service Unavailable)

Also following error in application.log file

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Menlo} span.s1 {font-variant-ligatures: no-common-ligatures} span.s2 {font-variant-ligatures: no-common-ligatures; background-color: #e6e600}

2017-05-12 00:06:43,877 INFO - [qtp2050835901-1065 - 0d5633f1-091f-47ac-949e-ed1f3583122e:] ~ Audit: UNKNOWN/127.0.0.1-127.0.0.1 performed request GET http://localhost:21000/api/atlas/admin/status (127.0.0.1) at time 2017-05-12T04:06Z (AUDIT:104)

2017-05-12 00:07:44,005 INFO - [qtp2050835901-1066 - 329b25a9-f9c9-4142-ae11-42f9faed4e7b:] ~ Audit: UNKNOWN/127.0.0.1 performed request GET http://localhost:21000/api/atlas/admin/status (127.0.0.1) at time 2017-05-12T04:07Z (AuditFilter:91)

2017-05-12 00:07:44,006 INFO - [qtp2050835901-1066 - 329b25a9-f9c9-4142-ae11-42f9faed4e7b:] ~ Audit: UNKNOWN/127.0.0.1-127.0.0.1 performed request GET http://localhost:21000/api/atlas/admin/status (127.0.0.1) at time 2017-05-12T04:07Z (AUDIT:104)

2017-05-12 00:08:43,872 INFO - [qtp2050835901-1066 - 2e95c961-12cc-4353-a360-32c1f40f6678:] ~ Audit: UNKNOWN/127.0.0.1 performed request GET http://localhost:21000/api/atlas/admin/status (127.0.0.1) at time 2017-05-12T04:08Z (AuditFilter:91)

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Atlas Metadata Server error HTTP 503 response from http://localhost:21000/api/atlas/admin/status in 0.000s (HTTP Error 503: Service Unavailable)

Expert Contributor

@Saurabh

Can you attach atlas application.log file.

View solution in original post

5 REPLIES 5
Highlighted

Re: Atlas Metadata Server error HTTP 503 response from http://localhost:21000/api/atlas/admin/status in 0.000s (HTTP Error 503: Service Unavailable)

Super Mentor

@Saurabh

Please check if your Atlas Service is running fine on port 21000 on localhost?

# netstat -tnlpa | grep  21000

.

Also do you see any ERROR/ Warning on atlas log?

# less /var/log/atlas/atlas.20170419-185147.err
# less /var/log/atlas/atlas.20170419-185147.out 

.

Highlighted

Re: Atlas Metadata Server error HTTP 503 response from http://localhost:21000/api/atlas/admin/status in 0.000s (HTTP Error 503: Service Unavailable)

Guru

I see following logs in those files.

netstat -tnlpa | grep 21000

(No info could be read for "-p": geteuid()=4569 but you should be root.)

tcp 0 0 0.0.0.0:21000 0.0.0.0:* LISTEN -

cat atlas.20170512-081144.out

{metadata.broker.list=<server>:6667, request.timeout.ms=30000, client.id=atlas, security.protocol=PLAINTEXT}

cat atlas.20170512-081144.err

log4j:WARN Continuable parsing error 37 and column 14

log4j:WARN The content of element type "appender" must match "(errorHandler?,param*,rollingPolicy?,triggeringPolicy?,connectionSource?,layout?,filter*,appender-ref*)".

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

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

Highlighted

Re: Atlas Metadata Server error HTTP 503 response from http://localhost:21000/api/atlas/admin/status in 0.000s (HTTP Error 503: Service Unavailable)

Expert Contributor

@Saurabh

Can you attach atlas application.log file.

View solution in original post

Highlighted

Re: Atlas Metadata Server error HTTP 503 response from http://localhost:21000/api/atlas/admin/status in 0.000s (HTTP Error 503: Service Unavailable)

Guru

Hello @Nixon Rodrigues,

I checked application.log and found following error

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private org.apache.atlas.web.dao.UserDao org.apache.atlas.web.service.UserService.userDao; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userDao': Invocation of init method failed; nested exception is java.lang.RuntimeException: org.apache.atlas.AtlasException: /usr/hdp/current/atlas-server/conf/users-credentials.properties not found in file system or as class loader resource

and /usr/hdp/current/atlas-server/conf/policy-store.txt not found in file system or as class loader resource.

So actually these files were not present, I don't know whether its a behavior of Atlas that we manually have to create them and update accordingly or it was just specific to my env due to some issue.

But once I have created and updated these two files then atlas started working.

Highlighted

Re: Atlas Metadata Server error HTTP 503 response from http://localhost:21000/api/atlas/admin/status in 0.000s (HTTP Error 503: Service Unavailable)

Expert Contributor

@Saurabh, these two files are needed by Atlas for authentication. I think files were not copied to atlas conf properly when you upgrade HDP.

Don't have an account?
Coming from Hortonworks? Activate your account here