You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by Nigel Jones <jo...@uk.ibm.com> on 2016/06/28 13:04:07 UTC
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.
Re: quick_start.py : no server (connection refused)
Posted by Shwetha Shivalingamurthy <ss...@hortonworks.com>.
I use embedded-hbase-solr for local testing , you have to run
conf/atlas-env.sh before starting atlas. This works for me on mac laptop
Because of licensing issues, BerkelyDB jar is not packaged anymore in any
of the profiles. So, even if you build with BerkelyDB profile, you have to
copy the BerkelyDB jar manually and its documented in
InstallationSteps.twiki. BerkelyDB profile works as well after copying the
jar
Regards,
Shwetha
On 28/06/16, 8:58 PM, "Nigel Jones" <jo...@uk.ibm.com> wrote:
>
>> Just to share experience: I generally use the default profile -Pdist to
>>build the atlas binary. This points to an external instance of Hbase and
>>Solr.
>>
>> This ³external² instance is just another process that runs on the same
>>machine (my Mac OS X laptop). I use Hbase 1.1.2 and Solr 5.5.1 (until
>>recently - I was using Solr 5.2.1). These two require Zookeeper to be
>>running. I generally just use the Zookeeper that comes with Kafka 0.10.
>>I use Kafka 0.10 if I need to test with external Kafka, but mostly just
>>default to the embedded one.
>
>> Possibly Linux is behaving differently with Solr etc. Any information /
>>fixes you can provide about the issue you are facing with Solr / Hbase
>>will help set this up correctly for other platforms as well.
>
>Thanks - not tried external yet .. (in part as this particular system [a
>CentOS cloud vm] doesn't [yet] have standalone hbase/solr]).
>
>
>The BerkelyDB version did start up ok & quick start runs successfully
>
>I'll go back to the others later to raise any required defects/changes
>
>Nigel.
>
>
Re: quick_start.py : no server (connection refused)
Posted by Nigel Jones <jo...@uk.ibm.com>.
> Just to share experience: I generally use the default profile -Pdist to build the atlas binary. This points to an external instance of Hbase and Solr.
>
> This \u201cexternal\u201d instance is just another process that runs on the same machine (my Mac OS X laptop). I use Hbase 1.1.2 and Solr 5.5.1 (until recently - I was using Solr 5.2.1). These two require Zookeeper to be running. I generally just use the Zookeeper that comes with Kafka 0.10. I use Kafka 0.10 if I need to test with external Kafka, but mostly just default to the embedded one.
> Possibly Linux is behaving differently with Solr etc. Any information / fixes you can provide about the issue you are facing with Solr / Hbase will help set this up correctly for other platforms as well.
Thanks - not tried external yet .. (in part as this particular system [a
CentOS cloud vm] doesn't [yet] have standalone hbase/solr]).
The BerkelyDB version did start up ok & quick start runs successfully
I'll go back to the others later to raise any required defects/changes
Nigel.
Re: quick_start.py : no server (connection refused)
Posted by Hemanth Yamijala <hy...@hortonworks.com>.
Folks,
Just to share experience: I generally use the default profile -Pdist to build the atlas binary. This points to an external instance of Hbase and Solr.
This “external” instance is just another process that runs on the same machine (my Mac OS X laptop). I use Hbase 1.1.2 and Solr 5.5.1 (until recently - I was using Solr 5.2.1). These two require Zookeeper to be running. I generally just use the Zookeeper that comes with Kafka 0.10. I use Kafka 0.10 if I need to test with external Kafka, but mostly just default to the embedded one.
In Atlas conf, I setup the following properties
atlas.graph.storage.hostname
atlas.graph.index.search.solr.zookeeper-url
atlas.audit.hbase.zookeeper.quorum
I also need to create Solr indexes using a script like this:
$ cat ~/projects/hwx/atlas/docs/solr-index-create.sh
#!/bin/sh
ATLAS_HOME=/Users/hyamijala/software/atlas/apache-atlas-0.7-incubating-SNAPSHOT
bin/solr create -c vertex_index -d $ATLAS_HOME/conf/solr -shards 1 -replicationFactor 1
bin/solr create -c edge_index -d $ATLAS_HOME/conf/solr -shards 1 -replicationFactor 1
bin/solr create -c fulltext_index -d $ATLAS_HOME/conf/solr -shards 1 -replicationFactor 1
Generally, with this things have always worked for me. All this is documented in the InstallationSteps.twiki file to the best of my knowledge (This can be published once the release is done - until then, please refer to the source version)
Possibly Linux is behaving differently with Solr etc. Any information / fixes you can provide about the issue you are facing with Solr / Hbase will help set this up correctly for other platforms as well.
Thanks
hemanth
On 6/28/16, 7:16 PM, "Nigel Jones" <jo...@uk.ibm.com> wrote:
>On 28/06/2016 14:12, Venkata R Madugundu wrote:
>> 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
>
>Thanks Venkata, will try that too and either add notes to the existing
>jira or open a new one.
>
>As it stands currently it seems my server fails to start properly with:
>
>Exception in thread "main" java.lang.ExceptionInInitializerError
> at
>org.apache.atlas.repository.graph.DeleteHandler.<clinit>(DeleteHandler.java:50)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:195)
> at
>org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
>org.apache.atlas.RepositoryMetadataModule.getDeleteHandlerImpl(RepositoryMetadataModule.java:148)
> at
>org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:95)
> at
>com.google.inject.AbstractModule.configure(AbstractModule.java:62)
>
>
>.. (full log in defect as needed)
>
>the cuase being some issue with the back end store .. so I'll take a
>little look at hbase too.
>
>
>
Re: quick_start.py : no server (connection refused)
Posted by Nigel Jones <jo...@uk.ibm.com>.
On 28/06/2016 14:12, Venkata R Madugundu wrote:
> 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
Thanks Venkata, will try that too and either add notes to the existing
jira or open a new one.
As it stands currently it seems my server fails to start properly with:
Exception in thread "main" java.lang.ExceptionInInitializerError
at
org.apache.atlas.repository.graph.DeleteHandler.<clinit>(DeleteHandler.java:50)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:195)
at
org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
at
org.apache.atlas.RepositoryMetadataModule.getDeleteHandlerImpl(RepositoryMetadataModule.java:148)
at
org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:95)
at
com.google.inject.AbstractModule.configure(AbstractModule.java:62)
.. (full log in defect as needed)
the cuase being some issue with the back end store .. so I'll take a
little look at hbase too.
Re: quick_start.py : no server (connection refused)
Posted by Venkata R Madugundu <ve...@in.ibm.com>.
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 <jo...@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.