# No\_shard\_available\_action\_exception

**URL:** <https://discuss.elastic.co/t/no-shard-available-action-exception/341883>\
**Category:** Elasticsearch\
**Created:** [August 29, 2023, 1:25pm UTC](https://discuss.elastic.co/t/no-shard-available-action-exception/341883 "2023-08-29T13:25:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nibort](https://avatars.discourse-cdn.com/v4/letter/n/9e8a1a/32.png) [@Nibort](https://discuss.elastic.co/u/Nibort)\
**Post date:** [August 29, 2023, 1:25pm UTC](https://discuss.elastic.co/t/no-shard-available-action-exception/341883/1 "2023-08-29T13:25:32Z")

</div>

Hello,  
I'm trying to send rsyslog with filebeat to my Elasticsearch cluster  
I've added the global path where logs are stored (/var/log/\*.log)

filebeat.yml

```auto
filebeat.inputs:
- type: log
  id: rsyslog
  paths:
    - /var/log/*.log

filebeat.config.modules:
  path: ${path.config}/modules.d/*.yml
  reload.enabled: true

# ======================= Elasticsearch template setting =======================
setup.template.settings:
  index.number_of_shards: 1

output.elasticsearch:
  hosts: ["https://my-ip:9200"]
  protocol: "https"
  username: "filebeat_writer"
  password: "${FB}"
  ssl:
    enabled: true
    certificate_authorities: ["/etc/filebeat/certs/transport-ca-fullchain.crt"]

setup.kibana:
  host: "my-kibana:443"
  protocol: "https"
  username: "filebeat_writer"
  password: "${FB}"
  ssl:
    enabled: true
    certificate_authorities: ["/etc/filebeat/certs/nginx-ca-fullchain.crt"]

```

I'm also sending other type of logs with filebeat but I don't get any error message and it's works fine.  
But for rsyslog configuration, when I'm going on dashboard, I have shards failed message :

```auto
{
  "took": 2,
  "timed_out": false,
  "_shards": {
    "total": 5,
    "successful": 4,
    "skipped": 2,
    "failed": 1,
    "failures": [
      {
        "shard": 0,
        "index": "filebeat-8.9.0",
        "node": null,
        "reason": {
          "type": "no_shard_available_action_exception",
          "reason": null
        }
      }
    ]
  },
  "hits": {
    "max_score": null,
    "hits": []
  }
}

```

I have recently updated my elastic/filebeat/kibana version from 8.9 to 8.9.1, so I think it might cause the problem, but can't fix it  
If anyone has the solution or can bring me help, I would appreciate it.

Rob

---

<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:** [September 26, 2023, 1:26pm UTC](https://discuss.elastic.co/t/no-shard-available-action-exception/341883/2 "2023-09-26T13:26:14Z")

</div>

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