# Connection problem at the second login

**URL:** <https://discuss.elastic.co/t/connection-problem-at-the-second-login/309851>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [July 18, 2022, 7:14am UTC](https://discuss.elastic.co/t/connection-problem-at-the-second-login/309851 "2022-07-18T07:14:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tamir\_raviv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tamir_raviv/32/108429_2.png) [@tamir\_raviv](https://discuss.elastic.co/u/tamir_raviv)\
**Post date:** [July 18, 2022, 7:14am UTC](https://discuss.elastic.co/t/connection-problem-at-the-second-login/309851/1 "2022-07-18T07:14:24Z")

</div>

Hey. Running elasticsearch locally. Using elasticsearch-8.3.2 and kibana-8.3.2. I'm able to run everything smoothly the first time. After some timeout, when i'm not running anything, Kibana asking me to login again when entering the credentials again Kibana tells me i can't login.  
After shutting down both services and trying to run them again, i'm getting the following error from kibana:

`[ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. Request timed out`

only when i downloading or extracting the same folders again i'm able to start with a new password and credentials.  
can someone help me keep my session running, or at least been able to login again after shutting out?  
thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 18, 2022, 7:32am UTC](https://discuss.elastic.co/t/connection-problem-at-the-second-login/309851/2 "2022-07-18T07:32:03Z")

</div>

Welcome to our community! 😃

What do the Elasticsearch logs show?

---

<div class="post-metadata">

**Author:** ![tamir\_raviv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tamir_raviv/32/108429_2.png) [@tamir\_raviv](https://discuss.elastic.co/u/tamir_raviv)\
**Post date:** [July 18, 2022, 7:52am UTC](https://discuss.elastic.co/t/connection-problem-at-the-second-login/309851/3 "2022-07-18T07:52:15Z")

</div>

Thanks @warkolm Elastic logs gives me the following error. the last few logs lines:  
[

```auto
2022-07-18T10:45:13,797][INFO][o.e.x.s.a.Realms] [tamirs-MacBook-Pro.local] license mode is [basic], currently licensed security realms are [reserved/reserved,file/default_file,native/default_native]
[2022-07-18T10:45:13,801][INFO][o.e.g.GatewayService] [tamirs-MacBook-Pro.local] recovered [15] indices into cluster_state
[2022-07-18T10:45:13,952][ERROR][o.e.i.g.GeoIpDownloader] [tamirs-MacBook-Pro.local] exception during geoip databases update
org.elasticsearch.ElasticsearchException: not all primary shards of [.geoip_databases] index are active
	at org.elasticsearch.ingest.geoip.GeoIpDownloader.updateDatabases(GeoIpDownloader.java:134) ~[ingest-geoip-8.3.2.jar:8.3.2]
	at org.elasticsearch.ingest.geoip.GeoIpDownloader.runDownloader(GeoIpDownloader.java:274) [ingest-geoip-8.3.2.jar:8.3.2]
	at org.elasticsearch.ingest.geoip.GeoIpDownloaderTaskExecutor.nodeOperation(GeoIpDownloaderTaskExecutor.java:102) [ingest-geoip-8.3.2.jar:8.3.2]
	at org.elasticsearch.ingest.geoip.GeoIpDownloaderTaskExecutor.nodeOperation(GeoIpDownloaderTaskExecutor.java:48) [ingest-geoip-8.3.2.jar:8.3.2]
	at org.elasticsearch.persistent.NodePersistentTasksExecutor$1.doRun(NodePersistentTasksExecutor.java:42) [elasticsearch-8.3.2.jar:?]
	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:769) [elasticsearch-8.3.2.jar:?]
	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26) [elasticsearch-8.3.2.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
	at java.lang.Thread.run(Thread.java:833) [?:?]
[2022-07-18T10:45:20,771][INFO][o.e.i.g.DatabaseNodeService] [tamirs-MacBook-Pro.local] successfully loaded geoip database file [GeoLite2-Country.mmdb]
[2022-07-18T10:45:22,147][INFO][o.e.i.g.DatabaseNodeService] [tamirs-MacBook-Pro.local] successfully loaded geoip database file [GeoLite2-ASN.mmdb]
[2022-07-18T10:45:22,873][INFO][o.e.c.r.a.AllocationService] [tamirs-MacBook-Pro.local] current.health="YELLOW" message="Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana-event-log-8.3.2-000001][0], [.ds-ilm-history-5-2022.07.17-000001][0]]])." previous.health="RED" reason="shards started [[.kibana-event-log-8.3.2-000001][0], [.ds-ilm-history-5-2022.07.17-000001][0]]"
[2022-07-18T10:45:24,106][INFO][o.e.i.g.DatabaseNodeService] [tamirs-MacBook-Pro.local] successfully loaded geoip database file [GeoLite2-City.mmdb]

```

---

<div class="post-metadata">

**Author:** ![tamir\_raviv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tamir_raviv/32/108429_2.png) [@tamir\_raviv](https://discuss.elastic.co/u/tamir_raviv)\
**Post date:** [July 18, 2022, 8:51am UTC](https://discuss.elastic.co/t/connection-problem-at-the-second-login/309851/4 "2022-07-18T08:51:22Z")

</div>

@warkolm trying to resolve the error in elasticearch by adding the line:  
`ingest.geoip.downloader.enabled: false`  
to the elasticsearch.yml file.  
it changed the elasticsearch logs but i'm still getting the same error in kibana.  
the new elasticsearch logs:

```auto
[2022-07-18T11:44:24,314][INFO][o.e.x.s.a.Realms] [tamirs-MacBook-Pro.local] license mode is [basic], currently licensed security realms are [reserved/reserved,file/default_file,native/default_native]
[2022-07-18T11:44:24,317][INFO][o.e.g.GatewayService] [tamirs-MacBook-Pro.local] recovered [15] indices into cluster_state
[2022-07-18T11:44:24,479][INFO][o.e.c.m.MetadataDeleteIndexService] [tamirs-MacBook-Pro.local] [.geoip_databases/NjfOut3sQ6u_8VPvVDeeAA] deleting index
[2022-07-18T11:44:28,744][INFO][o.e.c.r.a.AllocationService] [tamirs-MacBook-Pro.local] current.health="YELLOW" message="Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana-event-log-8.3.2-000001][0]]])." previous.health="RED" reason="shards started [[.kibana-event-log-8.3.2-000001][0]]"

```

tried to generate new passwords both for kibana end elasticsearch with the following lines in the command:

- bin/elasticsearch-reset-password -u kibana\_system --auto
- bin/elasticsearch-reset-password -u elastic

and receiving the error:  
`ERROR: Failed to determine the health of the cluster. `  
not sure if it's related

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 15, 2022, 8:51am UTC](https://discuss.elastic.co/t/connection-problem-at-the-second-login/309851/5 "2022-08-15T08:51:50Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
