Hi Marius,
Thank you for your response, same think happend today after re-running the
image yesterday.
The error at graylog2.log - same error that I posted yesterday :
[2015-11-13 05:31:59,337][INFO ][cluster.service ] [Sack] added
Thank you for your reply. I gave Graylog write permissions on the folders
in that path and restarted the 'graylog-server' service, but nothing has
changed. I'm still getting the same error in the log. Do you have any
other suggestions?
On Saturday, September 5, 2015 at 4:25:39 AM UTC-4,
Hi,
ERROR: Unable to access file /data
>
>
Graylog needs write-access to the /data directory (also see
message_journal_dir,
https://github.com/Graylog2/graylog2-server/blob/1.1.6/misc/graylog2.conf#L254-L256).
You have to ensure that the Graylog system user is allowed to enter, read,
and
Does anyone have to answer ? How do I solve this elasticsearch problem ?
On Tuesday, March 17, 2015 at 8:36:23 PM UTC+2, Abdüllatif ERKAYA wrote:
I am getting 500 logs per second. It may have an impact ?
On Tuesday, March 17, 2015 at 3:12:37 PM UTC+2, Abdüllatif ERKAYA wrote:
I started
Wed, 18 Mar 2015 06:38:51 -0700 (PDT), Abdüllatif ERKAYA
aerka...@gmail.com :
Does anyone have to answer ? How do I solve this elasticsearch
problem ?
First you can be sure it's an elasticsearch problem. When you query the
ElasticSearch cluster, what's the status?
curl -XGET
Looks like Elasticsearch is not starting properly after the reboot. This
can be caused by several reasons. One is too few system resources, make
sure your vm has enough memory allocated. 3-4 Gb at least. Another would be
a wrong IP setup, please double check that you exactly followed these
steps:
I am getting 500 logs per second. It may have an impact ?
On Tuesday, March 17, 2015 at 3:12:37 PM UTC+2, Abdüllatif ERKAYA wrote:
I started from the beginning. i deployed it .
Allocated 8GB Memory and 8 core cpu.
IP Address: DHCP. I did not change.
I made the time- zone setting
and
I started from the beginning. i deployed it .
Allocated 8GB Memory and 8 core cpu.
IP Address: DHCP. I did not change.
I made the time- zone setting
and
graylog-ctl reconfigure
Login to web interface.
Add an syslog udp input.
Received logs.
After 2 hours,
I rebooted it.
same results.
Yes, i did.
On Monday, March 16, 2015 at 9:39:38 AM UTC+2, Marius Sturm wrote:
Hi Abdüllatif,
did you run graylog-ctl reconfigure after changing the IP?
On 15 March 2015 at 14:37, Abdüllatif ERKAYA aerk...@gmail.com
javascript: wrote:
root@graylog:~# graylog-ctl status
run:
Could you please check if there are any errors in
/var/log/graylog/server/current ? Also check if the server is restarting
constantly!
On 16 March 2015 at 15:21, Abdüllatif ERKAYA aerka...@gmail.com wrote:
Yes, i did.
On Monday, March 16, 2015 at 9:39:38 AM UTC+2, Marius Sturm wrote:
Hi
Hi Abdüllatif,
did you run graylog-ctl reconfigure after changing the IP?
On 15 March 2015 at 14:37, Abdüllatif ERKAYA aerka...@gmail.com wrote:
root@graylog:~# graylog-ctl status
run: elasticsearch: (pid 13318) 624s; run: log: (pid 982) 1695s
run: etcd: (pid 9648) 900s; run: log: (pid 985)
root@graylog:~# graylog-ctl status
run: elasticsearch: (pid 13318) 624s; run: log: (pid 982) 1695s
run: etcd: (pid 9648) 900s; run: log: (pid 985) 1695s
run: graylog-server: (pid 19409) 9s; run: log: (pid 974) 1695s
run: graylog-web: (pid 13400) 623s; run: log: (pid 986) 1695s
run: mongodb: (pid
12 matches
Mail list logo
