Search configuration: Elasticsearch error

1,241 views
Skip to first unread message

prathmes...@gmail.com

unread,
Nov 14, 2014, 3:33:56 PM11/14/14
to ica-ato...@googlegroups.com
Hi,

 I'm trying to install a fresh install of an Atom 2.0 instance on my Development Server. I'm using the Git Method of Installation.

So when I reach the Search Configuration part on the Web Install, I get this Error "Elasticsearch Error". I tried the debug mode but I don't get any more descriptive error.

This are the credentials I'm filling in are,
  • Search host: localhost
  • Search port: 9200
  • Search index: atom

My elastic search is running fine on the Server when I checked. 

sudo /etc/init.d/elasticsearch status
* elasticsearch is running

There is another Atom2.1 instance running successfully on the same Server as this, will that search index have any conflict or anything to do with this.

I even tried entering a different search index: "atomdev" for this instance but still the same error.

Any help is appreciated !!

Best,

Prathmesh Mengane,
Database and CMS Developer,
Dumbarton Oaks.


Jesús García Crespo

unread,
Nov 14, 2014, 3:42:23 PM11/14/14
to ica-ato...@googlegroups.com
Hi Prathmesh,

If you are using ES 1.x please not that the startup process may take longer than usually. I've seen instances taking more than a minute to start up so that may be the reason why your AtoM is giving you that error.

You can verify the status manually by running: curl http://127.0.0.1:9200

Let us know how it goes!

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at http://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/094c08bc-8c75-497c-802d-3d86519fb3ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Jesús García Crespo,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | +1.604.527.2056

prathmes...@gmail.com

unread,
Nov 14, 2014, 4:05:46 PM11/14/14
to ica-ato...@googlegroups.com
Hi Jesus,

    Here's the O/P of the curl command;

curl http://127.0.0.1:9200
{
  "status" : 200,
  "name" : "Frog-Man",
  "version" : {
    "number" : "1.3.4",
    "build_hash" : "(some hash value ...)",
    "build_timestamp" : "2014-09-30T09:07:17Z",
    "build_snapshot" : false,
    "lucene_version" : "4.9"
  },
  "tagline" : "You Know, for Search"
}


Does that shed any light on the Issue ? I rebooted the Server and gave it some time but still the same Error.

Interestingly, in my other atom instance running on the same server when I run search:populate it works fine, so I'm assuming ElasticSearch is running fine ?

Best,
Prathmesh

Jesús García Crespo

unread,
Nov 15, 2014, 1:22:54 PM11/15/14
to ica-ato...@googlegroups.com
Yes, it looks like Elasticsearch is running properly.

I'd suggest to check the web server error log because it may have more details about the error.


For more options, visit https://groups.google.com/d/optout.

prathmes...@gmail.com

unread,
Nov 17, 2014, 2:49:44 PM11/17/14
to ica-ato...@googlegroups.com
Hey Jesus,

    So I checked my /var/log/apache2/error.log , and I think this is the Error it logged when I get the "ElasticSearch Error" on the front end during Search Configuration Step.

 "No connection information in your runtime configuration file for datasource [propel] "

Any insights ?

Thanks,
Prathmesh

Jesús García Crespo

unread,
Nov 17, 2014, 2:51:46 PM11/17/14
to ica-ato...@googlegroups.com
Hi Prathmesh,

Sorry, I don't think I can help. I'd suggest to restart the installation.


For more options, visit https://groups.google.com/d/optout.

prathmes...@gmail.com

unread,
Nov 18, 2014, 10:06:11 AM11/18/14
to ica-ato...@googlegroups.com
Hi Jesus,

  I've tried restarting the install from scratch several times but I always get stuck with this error at the same stage.

As you know, I am already running another Atom 2.1 instance on the same error which is running fine. ( I installed using tarball method)

I had couple of questions regarding elasticsearch configuration.

I wanted to know whether I need to enter different names for the elasticsearch "search index" on the config page. Meaning can the search index name for the already running 2.1 instance(which is by set to "atom") and the new instance I'm trying to create, can they be same ?

Is there any other port I can use for elasticsearch other than 9200 ( does it conflict if another instance is already using that port) ?

Best,
Prathmesh

Jesús García Crespo

unread,
Nov 18, 2014, 12:13:39 PM11/18/14
to ica-ato...@googlegroups.com
Hi Prathmesh,

On Tue, Nov 18, 2014 at 7:06 AM, <prathmes...@gmail.com> wrote:
I wanted to know whether I need to enter different names for the elasticsearch "search index" on the config page. Meaning can the search index name for the already running 2.1 instance(which is by set to "atom") and the new instance I'm trying to create, can they be same ?

I believe that you can reuse an existing index but it will be flushed during the installation process, with the risk of losing all the data in your index. If you have two instances they should have their own indexes. 
 
Is there any other port I can use for elasticsearch other than 9200 ( does it conflict if another instance is already using that port) ?

Hey, that's two questions in one! :) If you really need to have two Elasticsearch services running in the same machine I guess the easiest is to having them listening on different IPs, but yes you can also change the ports. All that can be configured in a file called elasticsearch.yml (under /etc), for example the http module has its own settings, you want to take a look to http.port, http.host, etc... http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-http.html

If you really need both ES 0.9 and ES 1.x I feel it's going to be easier to have them deployed in two different machines. You may need some more hardware but you'll definitely save time trying to have two ES instances coexisting.

fatima ezzahra maida

unread,
Apr 8, 2015, 6:52:22 AM4/8/15
to ica-ato...@googlegroups.com
hi i m lost here, please can you help me
when i arrived to search configuration i found this problem

  • Can't connect to the server (Failed to connect to localhost port 9200: Connection refused).
what should i do

Jesús García Crespo

unread,
Apr 8, 2015, 11:40:52 AM4/8/15
to ica-ato...@googlegroups.com
Hi Fatima,

Have you installed Elasticsearch? It's one of the dependencies of AtoM. The installation instructions can be found at: https://www.accesstomemory.org/en/docs/2.1/admin-manual/installation/linux/#elasticsearch

If you are running the Elasticsearch service in a different host, the installer lets you define the address. Also, make sure that the traffic is not being blocked by any firewall in your local network.

Don't hesitate to ask us more questions!

On Wed, Apr 8, 2015 at 3:52 AM, fatima ezzahra maida <fatimaezz...@gmail.com> wrote:
  • Can't connect to the server (Failed to connect to localhost port 9200: Connection refused). 

moi moi

unread,
Nov 3, 2020, 3:22:12 AM11/3/20
to AtoM Users
Bonjour, 
svp comment installer elastisearch sur windows?
est ce possible de nous expliquer la relation ou plutot l'installation de ica-atom , elastisearch et wampserver et le tout sur windows
merci d'avance

bien cordialement
moussaoui

Dan Gillean

unread,
Nov 3, 2020, 10:03:23 AM11/3/20
to ICA-AtoM Users
Salut moussaoui, 

I have replied to you in one of your other threads (here), but for anyone else who finds this in the future, I will add further information. 

AtoM is developed, tested, and deployed in production on an open source stack - specifically, we develop against Linux Ubuntu as the base operating system. We recommend that if you want to install AtoM on a Windows server, you proceed via virtualization, running AtoM via a production-ready virtual appliance. Please see:
However, note as well that previous users in our forum have shared their own tips and suggestions for getting AtoM working via XAMPP, WAMP, etc. We do NOT test these instructions, and will therefore be limited in the support that we can offer in this forum, but hopefully other users will be able to offer you suggestions! 

Posts that mention WAMP:
Posts that are labelled "Windows":
If you are looking for a test environment installed on a local Windows computer, I would suggest checking out the Vagrant box we maintain, instead of trying to do a full install inside of WAMP, which can be very complicated because WAMP does not always enable all the necessary PHP extensions. Some more information on using our Vagrant box:
Please note that the AtoM Vagrant box is intended for local development and testing - it is *not* scaled to be used as a production instance! 

Regards, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory
he / him


--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages