Select your space You can change your space at anytime{ No spaces match search criteria }

Hi team,

I am using elk 7.x and i am getting a strange error that "No spaces match search criteria".I am getting this error cople of times.my kibana was working till yesterday but when i try to open i getting the above error.also all the visualizations and dashboards will be gone if i restart the kibana after that it will work fine couple of more day again same issue will arrive.
I didn't find any kibana logs also,i am attaching the screenshopt of what i am getting can anyone help me out this why it is happening?

thanks in advance

Team can anyone help out on this I am not getting why i got this error

2 Likes

Im seeing this as well.

1 Like

Hi Team, even I'm also started facing the same problem from past 5 days.
Everyday I will get that error and I need to restart kibana, but it's a very serious problem because I'm loosing all the imported data sources, visualizations and dashboards.
Can anyone please help on this ?

I am also facing same problem from past 4 days

When I restart kibana then it deletes all my existing indexes as well! and it has automatically created some random indexes (more then 40).

It happens every day for me! I have tried to re install the but inspite of it issue is not resolved!

please help! it causes data loss.

Try to create the API by calling the API.

https://www.elastic.co/guide/en/kibana/master/spaces-api-post.html

Thanks for the quick response kwonghung.
Yesterday morning I have tried the same way, instead of using the default space I have created my own space and created dashboard in that space.
But, today morning again it has started showing the same error.

same for me! I followed the steps for create space ! Today Again I am getting same error!

Yes, still the issue is not resolved. I'm facing the same error.

@Gopi_mdvk have you got any solution??

because of it we are getting data lost! and also it creates random indexes.

screenshot-64.225.47.149_5601-2020.07.27-10_43_28

Same here, what is strange:
1 - I only have this since 2 days
2 - I have downgrade to version 7.7.0 and this morning ... the problem is back
3 - I never got such issue previously, then this Friday this problem occur for the first time
4 - A clean reinstall does not help
5 - I have shutdown kibana & logstash, after a few hours Elastic is down again!

So, it is definitively an Elastic issue !

It looks like I've been hacked, I don't understand how it is possible! Mainly because for weeks I got no issue, here I can reproduce it several times per day!

What is strange too, is that a lot of peoples have the same issue at the same time (approx) !

Also, see my ES log, does someone is trying to DELETE my index, who/how ?

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:00,332Z", "level": "INFO", "component": "o.e.c.m.MetadataDeleteIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[posts_index/jcIQ4K29SqO0HIGjMt1H7g] deleting index", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:01,007Z", "level": "INFO", "component": "o.e.c.m.MetadataDeleteIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[stores_index/2oPaTL4kTVGwCf1tTDWguw] deleting index", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:01,749Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[5ak89j8y6x-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:02,966Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[ogredkdgmp-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:03,885Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[gxz37yiwye-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:05,033Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[efyt9ormp0-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:05,870Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[p2fzz423np-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:07,256Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[s3tax1unzj-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:08,037Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[7p4y6snup2-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:08,793Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[z18fz1chwp-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:09,547Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[ahdpzjoeas-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

[5va5w ](https://swarmpit.socloze.com/#/tasks/5va5wgbuj58h806g5t7d5q4kp?log=1) {"type": "server", "timestamp": "2020-07-27T08:56:10,344Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "docker-cluster-es01", "node.name": "es01", "message": "[41jkjkgb60-meow] creating index, cause [api], templates [], shards [1]/[1], mappings []", "cluster.uuid": "WKZ_vTKIQ4GkIPn1KIx7Gw", "node.id": "T1w-1R6LRoqnVfbnF67z-Q" }

Here is the reason:

1 Like

@ClubberLang Hi,
Did u find any solution for this?
How to secure our database?

Looks like the issue is resolved, can anyone please confirm the same ?
I can able to see the kibana home page, without restarting the kibana service..

@charan_syba Hi charan,
I think it is not resolved yet, today morning i have faced the same issue.
I restarted the server and i lost all my indexes again.

@Krishna_Sai_Nag_G Hi Krishna,
ooh ok, actually every day morning If I hit the url ip:5601 it will redirect to No Space error page and then I need to restart the server then only I will get the home page after hitting url ip:5601, but today I haven't restarted the server and I can able to get the home page.
So, I thought somehow they have resolved the issue..

@charan_syba Yeah charan, but i have faced the same issue on today morning. Is there any way to secure our database?

@Krishna_Sai_Nag_G Securing database I'm not sure, but the only solution right now is not exposing the application in public domain, like making the instance private or something like that..

@Krishna_Sai_Nag_G , yes securing the application work.

1 - now Kibana is only accessible internaly
2 - Elastic has been secure with basic auth

No issues until now.

@ClubberLang @charan_syba ok i will look into this, thank u.