*2016-05-12 14:19:48.000*
May 12 15:19:48 localhost sshd[25142]: pam_unix(sshd:auth): authentication
failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.30.4.10 user=root
*2016-05-12 14:03:12.000*
May 12 15:03:12 localhost sshd[24470]: pam_unix(sshd:auth): authentication
failure; logname=
Hello,
I have installed graylog 2.0 on centos6
I have acces to the web interface.
Nevertheless I have the folowing issue:
1=> When makjing a search , I have got a prompt telling "...service
unvailable, we are experiencing problem connecting to http://10.X.X.X:12900
curl -XGET
Hi guys,
Could someone help me on this subject please?
regards.
Le lundi 9 mai 2016 15:16:05 UTC+2, kaiser a écrit :
>
> Hello,
>
> Is there some documents talking about how to install graylog multi nodes,
> how to install load balancer, what to replicate,
> which log to put in which node,
Hi Jochen!!,
The AWS plugin is not reading any logs, though it is reaching to the AWS
cloudtrail successfully. I am sharing the payload sample and the
configuration I have done in both Graylog and AWS. Please tell me if any
thing wrong I have done doing it.
this is one of the value that
Hi Everyone!!,
The plugin is still not reading the
On Friday, 6 May 2016 16:32:38 UTC+5:30, Anant Sawant wrote:
>
> Hi Everyone!!,
>
> I went through the documentation for setting up the Cloudtrail plugin for
> US-WEST-1, but I am getting the following error.
> I have done all the AWS
Hi Jochen,
I hv gone through doc but getting this error
[2016-05-12T01:16:48-07:00] FATAL: Can not reach master server, make sure
127.0.0.1 is reachable and 'etcd' service is running properly.
Recipe
Hi team,
I am trying to upgrade graylog from 1.3 to 2.0 version
but facing some issues Please help me in this
*ERROR*
[2016-05-12T01:16:48-07:00] FATAL: Can not reach master server, make sure
127.0.0.1 is reachable and 'etcd' service is running properly.
Hi gang,
I'm running into a strange problem where my graylog nodes are complaining
about not being able to find their meta info:
2016-05-12T11:50:09.691-07:00 WARN [NodePingThread] Did not find meta info
of this node. Re-registering.
2016-05-12T11:50:12.878-07:00 WARN [NodePingThread]
I just setup my first Graylog server. After getting the config files right
(or what I think is right) I'm able to log into the web interface. The
problem is that when I select System/Nodes -> Nodes, I get this error:
(You caused a org.graylog2.restclient.lib.APIException. API call failed GET
Is it possible to use kibana with graylog2 ??
If yes then which version i need to choose for kibana and graylog2.
--
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
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=256m; support was removed in 8.0
Play server process ID is 23707
[debug] application - Loading timeout value into cache from configuration
for key DEFAULT: Not configured, falling back to default.
[debug] application -
root@raju-test-ES:~# netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN
1048/sshd
tcp0
I now have both servers using the same mongo, and as far as I can tell
everything works. But I'm back to the same problem with an admin logged
into the slave having the ability to accidentally or intentionally delete
indices. The reader account is pretty much useless. I realize it's
possible
I'm having a similar issue. I have things to a point where neither instance
sees more than one "node". Both are seeing the elasticsearch indicies (one
local, one not). The master node seems mostly operational. I set up a
"slave" node for only one reason. The Graylog user levels made it
Hi Jochen,
I managed to access graylog web interface.
Nevertheless I obtain graylog interface with empty inputs, empty streams,
empty dashboard.
I have followed the instructions on elasticsearch website and the graylog
documentation ...
--
You received this message because you are
15 matches
Mail list logo
