Build with -Pberkeley-elasticsearch,dist worked for me.

Build with -Pembedded-hbase-solr,dist does NOT work for me. It had issues
starting up Solr.
Had symtoms similar to ATLAS-800




From:   Nigel Jones <jon...@uk.ibm.com>
To:     dev@atlas.incubator.apache.org
Date:   28/06/16 06:35 PM
Subject:        quick_start.py : no server (connection refused)



There's been some changes to the atlas setup/build in recent months.

I just build trunk for the first time in a while, and ran quick_start
but the server clearly hasn't started

     }
   ]
}
Exception in thread "main"
com.sun.jersey.api.client.ClientHandlerException:
java.net.ConnectException: Connection refused
         at
com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle
(URLConnectionClientHandler.java:155)

Following a clean build, I built the distribution with
mvn clean package -Pdist,embedded-hbase-solr

previously I'd not used the embedded-hbase-solr, but from
InstallationSteps.html this now seems the preferred option.

I see relatively little in the quick start log:
2016-06-28 12:07:01,129 INFO  - [main:] ~ Looking for
atlas-application.properties in classpath (ApplicationProperties:73)
2016-06-28 12:07:01,133 INFO  - [main:] ~ Loading
atlas-application.properties from
file:/home/ibmcloud/build/atlas/20160628a/apache-atlas-0.8-incubating-SNAPSHOT/conf/atlas-application.properties

(ApplicationProperties:86)
2016-06-28 12:07:14,673 INFO  - [main:] ~ Client has only one service
URL, will use that for all actions: http://localhost:21000
(AtlasClient:248)
2016-06-28 12:07:15,256 WARN  - [main:] ~ Handled exception in calling
api api/atlas/types (AtlasClient:725)
com.sun.jersey.api.client.ClientHandlerException:
java.net.ConnectException: Connection refused
         at
com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle
(URLConnectionClientHandler.java:155)
         at
com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle
(HTTPBasicAuthFilter.java:105)


Any tips? I'm just going back to the code/scripts to figure out how it's
put together, but it may be I've missed some key step?

Note - no firewall running or apps on related ports. Centos 7.

Thanks
Nigel.



Reply via email to