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)
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) answer is: Monitor your disk space usage and send
a notification if you start running out of disk space.
Also
see
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
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
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
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 ]
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 ]
Hi,
you first have to fix the cluster health state of your Elasticsearch
cluster before you should even think about deleting the Graylog disk
journal.
Check the Elasticsearch logs for corresponding
hints:
http://docs.graylog.org/en/2.1/pages/configuration/file_location.html#omnibus-package
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%
This documentation page covers how to extend the disk space in the OVA:
http://docs.graylog.org/en/2.1/pages/configuration/graylog_ctl.html#extend-disk-space
Please note that Graylog's journal is sometimes corrupted when it ran out of
disk space. In that case you may need to delete the journal
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
Hello,
I would start by looking into your logs in /var/log/graylog, specially those in
the "server" folder, which may give you some errors to start debugging the
issue.
Hope that helps.
Regards,
Edmundo
> On 27 Dec 2016, at 20:55, cypher...@gmail.com wrote:
>
> We've been using Graylog OVA
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
13 matches
Mail list logo
