Open B3K7 opened 2 years ago
user@host # curl -X GET "localhost:9200/_cluster/health?pretty" { "cluster_name" : "graylog", "status" : "green", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 12, "active_shards" : 12, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 0, "active_shards_percent_as_number" : 100.0 }
user@host # curl -XGET 'http://localhost:9200/_cat/health?pretty' 1668178556 14:55:56 graylog green 1 1 12 12 0 0 0 0 - 100.0%
user@host # curl -XGET 'http://127.0.0.1:9200/_cluster/health?level=indices' {"cluster_name":"graylog","status":"green","timed_out":false,"number_of_nodes":1,"number_of_data_nodes":1,"active_primary_shards":12,"active_shards":12,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":0,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":100.0,"indices":{"gl-events_0":{"status":"green","number_of_shards":4,"number_of_replicas":0,"active_primary_shards":4,"active_shards":4,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":0},"graylog_0":{"status":"green","number_of_shards":4,"number_of_replicas":0,"active_primary_shards":4,"active_shards":4,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":0},"gl-system-events_0":{"status":"green","number_of_shards":4,"number_of_replicas":0,"active_primary_shards":4,"active_shards":4,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":0}}}
Uninstalled graylog-server Installed graylog-enterprise
Issue resolved.
Issue resolved
It is recommended that Graylog improve the quality of licensing related errors.
Dennis Oelkers Recommend changing this case from a bug to an issue. (Or closing - your call.)
@B3K7 Can you provide us with some details? Was this a new installation of Graylog 5.0.0-beta, or did you update from an earlier version? (Notice: 5.0 is not stable yet) If you updated from an earlier version, which version did you update from, and did you use Enterprise and a valid license in your old setup?
Thank you!
Hi Bernd
To the best of my knowledge, my machine was running 4.3 Graylog Open with the Enterprise Plugin and a valid 2GB free License Key - prior to upgrade. (The website seems to have changed so the terminology may not be 100% correct.) Brent
On Mon, Nov 14, 2022, 5:54 a.m. Bernd Ahlers @.***> wrote:
@B3K7 https://github.com/B3K7 Can you provide us with some details? Was this a new installation of Graylog 5.0.0-beta, or did you update from an earlier version? (Notice: 5.0 is not stable yet) If you updated from an earlier version, which version did you update from, and did you use Enterprise and a valid license in your old setup?
Thank you!
— Reply to this email directly, view it on GitHub https://github.com/Graylog2/graylog2-server/issues/13948#issuecomment-1313473918, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS36C3IBIKG23LZAED4EKJDWIIK7VANCNFSM6AAAAAAR5U6YEQ . You are receiving this because you were mentioned.Message ID: @.***>
Graylog is stuck in a loop.
Elasticsearch cluster Could not retrieve Elasticsearch cluster health. Fetching Elasticsearch cluster health failed: There was an error fetching a resource: Internal Server Error. Additional information: Couldn't read Elasticsearch cluster health
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
1. 2. 3. 4.
Context
Your Environment
Graylog Version: graylog2 stable 5.0
Java Version: openjdk 17 stable
Elasticsearch Version: elastic oss-7.x stable main
MongoDB Version: mongodb-org/5.0 main
Operating System: Debian bullseye
Browser version: firefox latest