Re: [graylog2] Graylog stopped working

Hi, thanks for everything all, clear. Cheers! On Friday, January 6, 2017 at 1:50:54 PM UTC+1, Jochen Schalanda wrote: > Hi, > > On Friday, 6 January 2017 05:00:52 UTC+1, cyph...@gmail.com wrote: >> >> One last question, how can I prevent running out of space. >> > > The simple (and correct)

Re: [graylog2] Graylog stopped working

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

Re: [graylog2] Graylog stopped working

Hello, after deleting the notification for "*Elasticsearch cluster unhealthy (RED) (triggered 6 days ago)"* and rebooting the server I didn't get notified of this problem again. I still see: *Elasticsearch clusterThe possible Elasticsearch cluster states and more related information is

Re: [graylog2] Graylog stopped working

Jochen, thank you, I looked at the following logs: root@graylog:/var/log/graylog/elasticsearch# nano current GNU nano 2.2.6 File: current 2017-01-02_09:16:55.57535 [2017-01-02 10:16:55,574][INFO ][node ]

Re: [graylog2] Graylog stopped working

Jochen, thank you, I looked at the following logs: root@graylog:/var/log/graylog/elasticsearch# nano current GNU nano 2.2.6 File: current 2017-01-02_09:16:55.57535 [2017-01-02 10:16:55,574][INFO ][node ]

Re: [graylog2] Graylog stopped working

Thank you again, we're almost there: df -m Filesystem 1M-blocks Used Available Use% Mounted on udev1495 1 1495 1% /dev tmpfs300 1 300 1% /run /dev/dm-0 15282 4902 9582 34% / none 1 0 1 0%

Re: [graylog2] Graylog stopped working

Thank you Edmundo. It appears we ran out of space. df -h Filesystem Size Used Avail Use% Mounted on udev1.5G 4.0K 1.5G 1% /dev tmpfs 300M 388K 300M 1% /run /dev/dm-015G 15G 0 100% / none4.0K 0 4.0K 0% /sys/fs/cgroup none

[graylog2] Graylog stopped working

We've been using Graylog OVA 2.1 for a while now, but it stopped working all of the sudden. We're getting: Server currently unavailable We are experiencing problems connecting to the Graylog server running on https://graylog:443/api. Please verify that the server is healthy and working

[graylog2] Re: No space, manually deleted indexes

Thank you very, very much! All is good. Dne sreda, 23. november 2016 16.32.56 UTC+1 je oseba Sypris napisala: > > Try removing the entire nodes directory and restarting Elasticsearch. ES > should rebuild the nodes directory. > > On Wednesday, November 23, 2016 at 4:17:11 AM UTC-6,

[graylog2] No space, manually deleted indexes

We're using 2.1 OVA and ran out of space. Due to a lack of knowledge all the index directories under /var/opt/graylog/data/elasticsearch/graylog/nodes/0/indices/graylog_0 were deleted. We now only have _state in there, before there were three directories 0, 1 & 3. We can't go to

Re: [graylog2] Nessus vulnerability scanner and Graylog

Thank you Marius, I implemented the suggestions listed under: http://docs.graylog.org/en/2.0/pages/configuration/graylog_ctl.html#production-readiness apart from: "Seperate the box network-wise from the outside, otherwise Elasticsearch can be reached by anyone". I'd like to limit access to

[graylog2] Re: Enable HTTPS for web interface, Server currently unavailable

Dne sobota, 21. maj 2016 09.47.41 UTC+2 je oseba cyph...@gmail.com napisala: > > I performed sudo graylog-ctl enforce-ssl and then reconfigure on a 2.0 > OVA and am now getting Server currently unavailable: We are experiencing > problems connecting to the Graylog server running on

[graylog2] Enable HTTPS for web interface, Server currently unavailable

I performed sudo graylog-ctl enforce-ssl and then reconfigure on a 2.0 OVA and am now getting Server currently unavailable: We are experiencing problems connecting to the Graylog server running on http://x.x.x.x:12900/. Please verify that the server is healthy and working correctly. How can I

[graylog2] EventID 4720 not on Graylog

I've been testing Windows Event Forwarding and then sending the events using nxlog to Graylog. It works very well, but I'm not seeing EventID:4720 in Graylog. It appears under Forwarded Events, but I'm not sure if nxlog or Graylog is to blame, and where/how to even begin to troubleshoot. All

[graylog2] Re: Message truncated, WEF, nxlog, Graylog

Hello, thank you so much for this, changing the System Locale and this was just what was needed. Dne sobota, 30. april 2016 13.35.32 UTC+2 je oseba Jochen Schalanda napisala: > Hi, > > that might be caused by a setting in nxlog. See the description of the > ShortMessageLength directive in >

[graylog2] Message truncated, WEF, nxlog, Graylog

I'm using Windows Event Forwarding (WEF) to collect the events on one server and then forward then using nxlog to Graylog. The default input, extractors are used but the problem is the messages are truncated (I'm not seing the data that is needed):