Jochen, thanks again. I did as suggested, then checked the status and etcd was down. I deleted /var/opt/graylog/data/etcd/* and executed graylog-ctl reconfigure and etcd status is just fine now.
I still however see: *Elasticsearch cluster is yellow.* Shards: 4 active, 0 initializing, 0 relocating, 4 unassigned, Is that something I should worry about it appears it's normal behaviour based on the documentation http://docs.graylog.org/en/2.1/pages/configuration/elasticsearch.html states: *With only one Elasticsearch node, the cluster state cannot become green because shard replicas cannot be assigned.* One last question, how can I prevent running out of space. As I noticed on the blog, 2.2 should come with some improvements in this area, but what is the proper procedure for now. As I understand it, the server should automatically delete older data, when the disk starts feeling up? On Thursday, January 5, 2017 at 3:35:26 PM UTC+1, Jochen Schalanda wrote: > Hi, > > On Thursday, 5 January 2017 13:10:57 UTC+1, cyph...@gmail.com wrote: >> >> May I delete the disk journal now and how? >> > > You can simply empty the journal directory while Graylog is not running, > see http://docs.graylog.org/en/2.1/pages/configuration/file_location.html > for the specific path for your installation. > > Cheers, > Jochen > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/15897859-5d97-4505-bbf9-06f153fafca2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
