Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not to able access Atlas GUI with localhost:/21000 - Error The connection was reset. #1

Closed
SalmaSattar opened this issue Dec 6, 2019 · 9 comments

Comments

@SalmaSattar
Copy link

Hi,

I am running the docker you created on Ubuntu 18.04. Docker run command is successful.
when I connect localhost:/2100.

I get an error message The connection was reset.

Are there any other steps I need to follow to access Apache Atlas UI?

There is an environment variables list. Do I need to configure them?

Any inputs would be helpful.

@Smarker
Copy link

Smarker commented Dec 10, 2019

@SalmaSattar Hey I had a similar issue with not being able to connect to the Atlas UI. What worked for me was that I had to clear my browsing data from chrome in my case. Then when I went to localhost:21000 I saw the UI. Additionally you can try visiting http://localhost:21000/login.jsp and use username admin password admin.

Also, I noticed sometimes the UI would take as much as 10 mins to get set up. So maybe give it a bit more time?

I didn't need to do any other steps, since my JAVA_HOME was already set.

@sudhikul
Copy link

sudhikul commented Jan 8, 2020

Hi @Smarker ,

I am using the same docker image and till 2 days back, I was able to login to http://localhost:21000/login.jsp without any issues.

However, today, I am facing the same issue. I tried cleaning up the Docker containers/images, rebuilding the docker image and using the Docker run command mentioned by sburns.

I even cleared chrome browsing data. I am still facing the same issue.

Can you please let me know what could be the issue?

Thanks and Regards,
Sudhindra

@sburn
Copy link
Owner

sburn commented Jan 9, 2020

@sudhikul @SalmaSattar If Atlas UI is inaccessible, probably it could not start. Check logs.

@diego-gv
Copy link

diego-gv commented Jan 13, 2020

@sudhikul @SalmaSattar If Atlas UI is inaccessible, probably it could not start. Check logs.

@sburn I have the same problem. I have tried to deploy it as you indicate in the repository and when looking at the logs it freeze up trying to start atlas:

$ docker logs -f atlas 
configured for local hbase.
hbase started.
configured for local solr.
solr started.
setting up solr collections...
starting atlas on host localhost
starting atlas on port 21000

I know it's very little information, but any ideas?

Thanks and regards


EDIT: For some reason, Atlas has ended up running smoothly after a long wait without showing anything in the log.

@sburn
Copy link
Owner

sburn commented Jan 15, 2020

@SalmaSattar @sudhikul @diego-gv
I've fixed startup script interactivity, now you will see in container log either Web-UI started or not:

$ docker logs -f atlas 

starting atlas on host localhost
starting atlas on port 21000
..................
Apache Atlas Server started!
Running atlas with PID 717...

Please, update your Docker image. Also, take into account that at fist run Atlas initialize internal schemas and startup may take up to 10 mins depending on host machine performance.

If the problem still exists on your side, check the application.log:
docker exec -it atlas tail -f /opt/apache-atlas-2.0.0/logs/application.log

@sburn sburn pinned this issue Jan 15, 2020
@diego-gv
Copy link

@sburn OK! Thank you for all! 👍

@sburn
Copy link
Owner

sburn commented Jan 16, 2020 via email

@sburn sburn closed this as completed Jan 20, 2020
@playhere
Copy link

playhere commented Apr 11, 2021

same problem still with me.
docker logs -f atlas looks alright

configured for local hbase. hbase started. configured for local solr. solr started. setting up solr collections... starting atlas on host localhost starting atlas on port 21000

after i checked the /opt/apache-atlas-2.1.0/logs/application.log, it warns

java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716) at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361) at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)

any ideas?

@bitodt
Copy link

bitodt commented May 20, 2021

same problem still with me.
docker logs -f atlas looks alright

configured for local hbase. hbase started. configured for local solr. solr started. setting up solr collections... starting atlas on host localhost starting atlas on port 21000

after i checked the /opt/apache-atlas-2.1.0/logs/application.log, it warns

java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716) at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361) at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)

any ideas?

If you're running it with volume mounts, try without them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants