Hi Jochen,
I am bit confused while sending logs in to graylog server. I have graylog
configured on X server , while I want to send logs from Y server into
graylog.
1) DO we need to configure syslog file in graylog server ("X") too ??? or
else only installation of agent (graylog-collector)
The public ip is from my Graylog machine. I'm trying to test this on a
single AWS instance. The only way i can successfully log into the Web UI
is by defining the public ip there (rest_transport_uri = ) . This allows
me to log on, but than i get the below exception in the logs which
Hello,
We, at OVH are very fond of Graylog and want to support it.
If you want to try it, we invite you to our lab, right here:
https://www.runabove.com/paas-logs.xml
https://community.runabove.com/kb/en/logs/quick-start.html
The full documentation of the platform is available here :
Group,
I've been running a setup as a testbed for a couple of months (OVA of
1.2.2) that blew up rather spectacularly a couple of weeks ago. It ran out
of disk space, unallocated shards, This:
https://t37.net/how-to-fix-your-elasticsearch-cluster-stuck-in-initializing-shards-mode.html
Hi Arie,
make sure to read the upgrade notes for Graylog 2.0.0-beta.1 at
https://github.com/Graylog2/graylog2-server/blob/2.0.0-beta.1/UPGRADING.asciidoc#upgrading
Cheers,
Jochen
On Thursday, 24 March 2016 22:53:24 UTC+1, Arie wrote:
>
> Super,
>
> Are there some guidelines on upgrading from
Hi,
I am attempting to intergate openldap into Graylog 1.33. I am new to
ldap search strings and in my attempt to connect the two I caused an issue.
I see the following error in my server log:
2016-03-23T17:01:56.141-04:00 ERROR [LdapSettingsServiceImpl] Graylog does
not yet support
Dear Jochen,
Thanks for your information!!!
On Wednesday, March 23, 2016 at 6:29:54 PM UTC+7, Jochen Schalanda wrote:
>
> Hi Scarlet,
>
> those messages are usually caused by clients (i. e. web browsers) whose
> session timed out (thus the 401 HTTP response status) but still have a tab
> with
