Graylog stopped working Indice blocked

Continuing the discussion from Indices blocked:

Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question.
Don’t forget to select tags to help index your topic!

1. Describe your incident:

2. Describe your environment:

  • OS Information: Ubuntu server 22.05:

  • Package 5.1.6

  • Service logs, configurations, and environment variables:
    I have graylog 5. and noticed that it stopped working saying that Elastick search is out of space yet I have 400 G?b available in my HyperV Machine

Indices blocked (triggered 12 hours ago)

7 indices are blocked.

  • juniper345_20: index.blocks.read_only_allow_delete
  • srx345_49: index.blocks.read_only_allow_delete
  • gl-failures_0: index.blocks.read_only_allow_delete
  • srx1500_25: index.blocks.read_only_allow_delete
  • gl-events_0: index.blocks.read_only_allow_delete
  • graylog_0: index.blocks.read_only_allow_delete
  • gl-system-events_0: index.blocks.read_only_allow_delete

3. What steps have you already taken to try and solve the problem?

Elasticsearch nodes disk usage above flood stage watermark (triggered 12 hours ago)

Elasticsearch nodes disk usage above high watermark (triggered a day ago)

4. How can the community help?
I have deleted all the .gz files in both elasticsearch and graylogs logs and rebooted and still am having the same issue. No data since October 7 th

Helpful Posting Tips: Tips for Posting Questions that Get Answers [Hold down CTRL and link on link to open tips documents in a separate tab]

You will need to drill down into how ES is allocating space to figure out why you keep exceeding the watermark.

Please refer to these docs:

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