Cuando hago click en "index now" aparece este error: Couldn't index items. Check the logs for details.

Versiones instaladas:
Search API 8.x-1.3
Elasticsearch-connector 8.x-5.0-alpha1
Elasticsearch 2.4.0

Seleccioné la opción "Make this cluster default connection" como sugiere el issue #2713227 y sigue dando error

CommentFileSizeAuthor
#6 elasticsearch_connector-could_not_index_items-2906783-6-D8.patch593 bytesskek
#3 recent-log.png230.52 KBmariana.romaldi@unc.edu.ar
index-elasticsearch.png114.47 KBmariana.romaldi@unc.edu.ar
index_now.png163.16 KBmariana.romaldi@unc.edu.ar
search_api.png150.01 KBmariana.romaldi@unc.edu.ar
make-cluster-default.png193.31 KBmariana.romaldi@unc.edu.ar
elasticsearch-connector.png134.01 KBmariana.romaldi@unc.edu.ar

Comments

mariana.romaldi@unc.edu.ar created an issue. See original summary.

juampynr’s picture

juampynr commented
Status: Active » Postponed (maintainer needs more info)

@mariana.romaldi@unc.edu.ar: did you actually check the logs? Unless you have disabled dblog module, there should be further info of what is going on at Admin > Reports > Recent log messages.

mariana.romaldi@unc.edu.ar’s picture

mariana.romaldi@unc.edu.ar commented
StatusFileSize
new recent-log.png230.52 KB

thanks for answering @juampynr

log elasticsearch cluster

cat /var/log/elasticsearch/digesto.log

[2017-09-06 08:56:13,976][INFO ][cluster.metadata         ] [digesto] [elasticsearch_index_digesto_d8_normativa] creating index, cause [api], templates [], shards [5]/[1], mappings []
[2017-09-06 08:56:14,055][INFO ][cluster.metadata         ] [digesto] [elasticsearch_index_digesto_d8_normativa] create_mapping [normativa]
[2017-09-06 08:56:14,061][INFO ][cluster.routing.allocation] [digesto] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[elasticsearch_index_digesto_d8_normativa][4], [elasticsearch_index_digesto_d8_normativa][4]] ...]).
[2017-09-06 08:56:25,561][INFO ][cluster.metadata         ] [digesto] [elasticsearch_index_digesto_d8_normativa] creating index, cause [api], templates [], shards [5]/[1], mappings []
[2017-09-06 08:56:25,629][INFO ][cluster.metadata         ] [digesto] [elasticsearch_index_digesto_d8_normativa] create_mapping [normativa]
[2017-09-06 08:56:25,634][INFO ][cluster.routing.allocation] [digesto] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[elasticsearch_index_digesto_d8_normativa][4], [elasticsearch_index_digesto_d8_normativa][4]] ...]).

attachment screenshot of recent log

zulljin’s picture

zulljin commented

I had a similar problem, when I clicked 'Clear all indexed data' on page search index, I got this error: 

{
  "error": {
    "root_cause": [
      {
        "type": "invalid_index_name_exception",
        "reason": "Invalid index name [elasticsearch_index_ID_site_nodes], must be lowercase",
        "index_uuid": "_na_",
        "index": "elasticsearch_index_ID_site_nodes"
      }
    ],
    "type": "invalid_index_name_exception",
    "reason": "Invalid index name [elasticsearch_index_ID_site_nodes], must be lowercase",
    "index_uuid": "_na_",
    "index": "elasticsearch_index_ID_site_nodes"
  },
  "status": 400
}

My DB name - ID_site, when i changed to id_site, everything worked fine. If you have capital letters in your database name, simply change the name using lowercase letters.

zulljin’s picture

zulljin commented
Status: Postponed (maintainer needs more info) » Needs review
skek’s picture

skek commented
StatusFileSize
new elasticsearch_connector-could_not_index_items-2906783-6-D8.patch593 bytes

@Zulljin,

Thank you for the input.
Can you please apply the attached patch and check again?
It seems we need to lower case the index name because of Elasticsearch server requirement.

zulljin’s picture

zulljin commented
Status: Needs review » Fixed

skek
Yes, patch has fixed this issue, thanks.

skek’s picture

skek commented
Status: Fixed » Reviewed & tested by the community

@Zulljin,

We should mark the issues to RTBC when checked and confirm it is working.
We are marking it with Fixed, when it has been committed to the dev version.

@mariana.romaldi@unc.edu.ar
Most probably your problem is connected with Elasticsearch server version.
This module has been designed to work with 5.x for Elasticsearch server but you are running 2.
Can you please check it with 5.x?

  • skek authored 2007754 on 8.x-5.x 
    Issue #2906783 by skek, Zulljin, juampynr: Couldn't index items. Check...
skek’s picture

skek commented
Status: Reviewed & tested by the community » Fixed

@mariana.romaldi@unc.edu.ar please fill free to reopen it but I think the problem here is tightly connected with your Elasticsearch version.

zulljin’s picture

zulljin commented

skek,
Maybe necessary added logs in watchdog when happening this or similar errors? Because it is very difficult debugging without logs.

The logic is: get errors from ElasticSearch and add them to watchdog Drupal.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

andrezstar’s picture

andrezstar commented

Not working for me after applying the patch