# Installation seems to hang **URL:** \ **Category:** Elasticsearch\ **Created:** [August 11, 2021, 8:16pm UTC](https://discuss.elastic.co/t/installation-seems-to-hang/281116 "2021-08-11T20:16:31Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![D-Groenewegen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/d-groenewegen/32/92874_2.png) [@D-Groenewegen](https://discuss.elastic.co/u/D-Groenewegen)\ **Post date:** [August 11, 2021, 8:16pm UTC](https://discuss.elastic.co/t/installation-seems-to-hang/281116/1 "2021-08-11T20:16:31Z")
Dear all, I hope you'll forgive me for my utter noobness. With the help of [Install Elasticsearch from archive on Linux or MacOS | Elasticsearch Guide [7.14] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/targz.html), I tried installing ES for Linux. When I got to step "Running Elasticsearch from the command line", typed `./bin/elasticsearch` and hit enter, the process began to hang indefinitely. Here are the final lines from my terminal: ```auto [2021-08-11T21:36:25,102][INFO][o.e.i.g.GeoIpDownloader] [plesk01.snel.com] geoip database [GeoLite2-City.mmdb] is up to date, updated timestamp [2021-08-11T21:36:25,218][INFO][o.e.i.g.GeoIpDownloader] [plesk01.snel.com] geoip database [GeoLite2-Country.mmdb] is up to date, updated timestamp [2021-08-11T21:36:27,099][INFO][o.e.i.g.DatabaseRegistry] [plesk01.snel.com] database file changed [/tmp/elasticsearch-8441497374832882486/geoip-databases/dc7GhAjvSIioe-Myj5Cn3Q/GeoLite2-City.mmdb], reload database... ``` What can I do? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [August 12, 2021, 7:05am UTC](https://discuss.elastic.co/t/installation-seems-to-hang/281116/2 "2021-08-12T07:05:24Z")
> [@D-Groenewegen](#): > > What can I do? Celebrate? Looks like Elasticsearch is up and running. From the page you linked: > By default, Elasticsearch runs in the foreground, prints its logs to the standard output ( `stdout` ), and can be stopped by pressing `Ctrl-C` . ---
**Author:** ![D-Groenewegen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/d-groenewegen/32/92874_2.png) [@D-Groenewegen](https://discuss.elastic.co/u/D-Groenewegen)\ **Post date:** [August 12, 2021, 7:58am UTC](https://discuss.elastic.co/t/installation-seems-to-hang/281116/3 "2021-08-12T07:58:31Z")
Thanks, haha, that's rather good news! Didn't I say "noobness" ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [August 19, 2021, 1:44pm UTC](https://discuss.elastic.co/t/installation-seems-to-hang/281116/4 "2021-08-19T13:44:33Z")
You're not the first to ask, and probably not the last. I opened a PR to clarify the docs in this area: > > > Users following the installation guide sometimes get stuck, reporting > that Elas…ticsearch has "hung" after running \`./bin/elasticsearch\` > because it doesn't exit, it just sits there in the foreground waiting > for something to happen. We do say that it "runs in the foreground" in > the docs but that's not clear enough, maybe folks expect it to declare > it started up successfully or to open a browser window for them or > something. > > This commit expands the docs to clarify what users should expect from > running Elasticsearch from the command line and what they should do > next. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [September 6, 2021, 11:12am UTC](https://discuss.elastic.co/t/installation-seems-to-hang/281116/5 "2021-09-06T11:12:31Z")
... and also this issue since these newly-introduced log messages are likely adding to the confusion: > > > Users sometimes get confused by how Elasticsearch logs a bunch of stuff at start…up and then simply stops, as if the process is blocked trying to do something. This is in general a tricky problem to solve, we're ready to receive HTTP requests well before the logging stops, but there's no well-defined endpoint to these log messages either. In the past it wasn't too bad, the last message would often be something positive-sounding like \`Cluster health status changed from \[YELLOW\] to \[GREEN\]\`, but in recent versions it seems that this is often the last log message: > > https://github.com/elastic/elasticsearch/blob/331a44ba425d9ae937a8f49a7f94d8d0a02f3b93/modules/ingest-geoip/src/main/java/org/elasticsearch/ingest/geoip/DatabaseRegistry.java#L311 > > This is \[apparently\](https://discuss.elastic.co/t/database-file-changed-error/281903) making the confusion much worse, it looks like we're stuck trying to reload a database file that changed. Could we improve the logging in this area to make it clearer that everything is fine and we're not stuck waiting for anything to complete? > > Relates https://github.com/elastic/elasticsearch/pull/76709 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 4, 2021, 11:13am UTC](https://discuss.elastic.co/t/installation-seems-to-hang/281116/6 "2021-10-04T11:13:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.