Issue: unknown key [index.max_result_window] for create index

[Fernando Ramirez Llorens]

Hi everyone

I'm uploading from 2.9.2 to 2.10. I've uninstalled elasticsearch 6 and installed 7.10.2,

following the installation instructions in Atom documentation. Then, I uploaded Atom.

When I try to repopulate the elasticsearch index, I receive an "unknown key [index.max_result_window] for create index" error.

The whole message is:

Indices that will be created:
 - atom_aip
 - atom_term
 - atom_actor
 - atom_accession
 - atom_repository
 - atom_functionobject
 - atom_informationobject
Defining and populating indices...
  unknown key [index.max_result_window] for create index 

I've already tried deleting cache, downloading Atom tarball and reinstalling again, and, of course, restarting php and nginx.

I'm running Atom in Ubuntu server 24.04.

Any suggestions? Thanks in advance!

Fernando.

[Hans-Arno Mielsch]

Unfortunately not.

I've got the same issue with unknown key [analysis] :-(

Regards,

-Hans-Arno

[Dan Gillean]

Hi both, 

Just a guess, but: I wonder if perhaps your old index may still be around (or cached), causing the issue? Perhaps you can try manually deleting the index, restarting the ES service, clearing all caches, and then reindexing?

• curl -XDELETE 'localhost:9200/atom'
• sudo systemctl restart elasticsearch
• sudo systemctl restart php8.3-fpm
  
• php symfony cc
• php symfony search:populate

There are also a bunch of older ES troubleshooting suggestions on this thread; perhaps something there might spark additional ideas if the above doesn't work..

Dan Gillean, MAS, MLIS
Business & User Experience Analyst
Artefactual Systems, Inc.
604-527-2056

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.
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/4018a6c0-8e9c-4eea-ba2f-0d8d4794685fn%40googlegroups.com.

[Fernando Ramirez Llorens]

Hi Dan, thanks for your tip.

I asked chatGPT, who "fixed" search.yml, changing some lines in order to make it "compatible" with ES7. Whatever it did, it worked and index repopulated. I wanted to try your suggestion, so I brought back the original search.yml (whitout changes) and now it remains working (I ran search:populate again with original search.yml file). So, I can't try if curl command fixes the problem. Maybe Hans can try.

Dan, if you realize what's happening, please tell us.

Thanks,

Fernando,

To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZ%2BYMZAtjRG2NGYoS6EN94enxMHi0kvUxvKqU1_M48FR-w%40mail.gmail.com.

[Hans-Arno Mielsch]

Curl -XDELETE says there is no index.

and

~/atom$ php symfony search:status
Elasticsearch server information:
 - Version: 7.10.2
 - Host: localhost
 - Port: 9200
 - Index name: atom

Document indexing status:
 - Accession: 1/0
 - Actor: 1/1057

                                                      
  no such index [atom_qubitaip] [index: atom_qubitaip]  
                                                       
means "something was wrong in tools:install"???

Or should I create AIP - what is it?

Regards,

-Hans-Arno

[Dan Gillean]

Hans, 

Can you check the full version number listed in Admin > Settings? There should be the application number (i.e. 2.10) and then another number after a dash. This second number is the database schema version. I want to double-check if this is correct - for release 2.10, according to the release notes, it should be 193. 

If this number is NOT 193 for your installation, then we may have found the issue. This usually happens when a step of the upgrade process is accidentally skipped - usually either: 

• Dropping and then recreating the database BEFORE loading your previous sqldump (step 4 here), or
• Running the sql-upgrade task AFTER loading your data (this step in the docs)

So far that's the only other idea I have at present; if it's not that I will flag the AtoM Maintainers so they can review this thread. 

Cheers, 

Dan Gillean, MAS, MLIS
Business & User Experience Analyst
Artefactual Systems, Inc.
604-527-2056

he / him

To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/5f682ba2-213f-47d9-8681-3308dda9448fn%40googlegroups.com.

[Fernando Ramirez Llorens]

If it helps, in my case it doesn't show 193, but 197.

To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZL53%2Bhh7Hu4EjQ_zY4pyV9_--orrwSeBzPbX25%3DUJVW0A%40mail.gmail.com.

[Dan Gillean]

Hi Fernando, 

Ha! Welp, I checked with the Maintainers and it seems that the version was not updated on the release page - so in fact, schema version 197 is correct for the 2.10.0 release. 

Meaning as well that the issue is not caused by a database schema mismatch. 

Unfortunately I am out of suggestions for now! But I have let the Maintainers know about this issue, and will report back if they have further suggestions, etc. 

Dan Gillean, MAS, MLIS
Business & User Experience Analyst
Artefactual Systems, Inc.
604-527-2056

he / him

To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/CAP3LaMJ6c7E0XWGt4o5vKXU-%3DPH0JhzYe-Xh%3Dgc%3DXtXVv622Tw%40mail.gmail.com.

[Hans-Arno Mielsch]

In my AtoM instance the database schema was updated, too.

@Fernando: how did you ask Chat-GPT to repair?

Perhaps we can learn about the workaround here...

Regards,

-Hans-Arno

[Fernando Ramirez Llorens]

Hi Hans! I explained chatgpt the issue upgrading Atom, I told it about the upgrade from ES6 to ES7 and I showed it the error message. And it said that the problem lied in a change of sintaxis of the new version of ES, which (in its words) made search.yml outdated. It offered to rewrite search.yml to fit to ES new sintaxis.

As I said, it already solved the problem (so I could repoblate index), but then I tried the search.yml as delivered by Atom, and it worked fine to repoblate index again. So... its clear that original search.yml works, but the version of gpt fixes the problem that lies here.

I attach the gpt version of search.yml, so you can see (and try if you want, rename it in order to work).

To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/402e34c1-7ff0-4496-981c-f25f81cbc7adn%40googlegroups.com.

[Hans-Arno Mielsch]

Well, using this search.yml did not change anything, even deleting config/search.yml did not repair any error on my side.

I think I will remove elasticsearch and start from scratch :-(

Regards,

-Hans-Arno

[Hans-Arno Mielsch]

That was a bad idea: ElasticSearch won't start.

Status see attachment

:-((