[jira] [Commented] (ATLAS-3670) Server appears to start, but connections fail with 503

2022-03-07 Thread Gary J. (Jira)
[ https://issues.apache.org/jira/browse/ATLAS-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502342#comment-17502342 ] Gary J. commented on ATLAS-3670: - Have you been able to resolve this?  I've run into the same issue with

[jira] [Created] (ATLAS-3670) Server appears to start, but connections fail with 503

2020-03-19 Thread majiangping (Jira)
majiangping created ATLAS-3670: -- Summary: Server appears to start, but connections fail with 503 Key: ATLAS-3670 URL: https://issues.apache.org/jira/browse/ATLAS-3670 Project: Atlas Issue

Re: Server appears to start, but connections fail with 503

2018-02-14 Thread Ernie Ostic
Thanks for the pointer. lots of errors there. Hard to say exactly which is the key error, but all seem to be related to JanusGraph. Ernie Ernie Ostic Worldwide Technical Sales InfoSphere Information Server IBM Analytics Cell: (617) 331 8238

Re: Server appears to start, but connections fail with 503

2018-02-14 Thread David Aspegren
HI Ernie, what is the error you are gettin in the in the .out log file? Regards, David 2018-02-14 15:57 GMT+01:00 Ernie Ostic : > Setting the variables in advance "helped", and they show up now, in the > start console > > configured for local hbase. > hbase started. >

Re: Server appears to start, but connections fail with 503

2018-02-14 Thread Ernie Ostic
Setting the variables in advance "helped", and they show up now, in the start console 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

Re: Server appears to start, but connections fail with 503

2018-02-14 Thread Graham Wallis
Hi Ernie As Peter says in his email, there are a couple of environment variables needed: I build the same as you, i.e.: mvn clean install -DskipTests -Pdist,embedded-hbase-solr Then I do the following (I am on Windows): set MANAGE_LOCAL_HBASE=true set MANAGE_LOCAL_SOLR=true set

Re: Server appears to start, but connections fail with 503

2018-02-14 Thread Peter Gergo Barna
Hi David, # I think these are the env variables: export MANAGE_LOCAL_HBASE=true export MANAGE_LOCAL_SOLR=true # Here is a script that builds and starts Atlas locally from source, it was posted to this mailing list earlier. BRANCH=0.8-incubating ATLAS_SOURCE_DIR=/tmp/atlas-source

Re: Server appears to start, but connections fail with 503

2018-02-14 Thread David Aspegren
Hi, I have the same issue. Where are those environment variables for embedded hbase described? regards, David 2018-02-14 14:32 GMT+01:00 Ernie Ostic : > Thanks David... > > build string I am using is: *mvn clean -DskipTests package > -Pdist,embedded-hbase-solr* > > Will

Re: Server appears to start, but connections fail with 503

2018-02-14 Thread Ernie Ostic
Thanks David... build string I am using is: mvn clean -DskipTests package -Pdist,embedded-hbase-solr Will check again the environment variablesthx. Ernie Ernie Ostic Worldwide Technical Sales InfoSphere Information Server IBM Analytics Cell: (617) 331 8238

Re: Server appears to start, but connections fail with 503

2018-02-14 Thread David Radley
Hi Ernie, There are 2 ways to build and run Atlas currently: - external Hbase and Solr and ZK - embedded HBase Solr and ZK I am not sure which one you are trying. Sharing your build string would be helpful. If you are using the embedded HBase option then you need to specify

Re: Server appears to start, but connections fail with 503

2018-02-14 Thread Nixon Rodrigues
Ernie, Look in logs/application.log for exact issue Atlas is facing with. How did you build Atlas? Nixon On Feb 14, 2018 5:22 PM, "Ernie Ostic" wrote: Hi all... Using "master", the build appears to be successful, and the server is properly listening on port 21000, but

Server appears to start, but connections fail with 503

2018-02-14 Thread Ernie Ostic
Hi all... Using "master", the build appears to be successful, and the server is properly listening on port 21000, but quick start or even direct access fails with 503. Any suggestions on where to look? Thanks! Ernie $ bin/quick_start.py log4j:WARN No such property [maxFileSize] in