Hi there
I really appreciate you guys providing packages to install graylog, makes
things a lot easier.
But why do you not allow directory listing?
https://packages.graylog2.org/repo/packages/
Like many others our servers don't have internet access and we mirror all
needed repositories
This is our config, works really good.
server {
listen 80;
server_name _;
return 301 https://$host$request_uri;
}
server {
listen 443;
server_name _;
ssl on;
ssl_certificate /etc/pki/tls/certs/.pem;
ssl_certificate_key
Or can't we create and maintain extractors separately from inputs and later
associate them to multiple inputs of our choices? This way we can use an
extractor for multiple inputs of same type and we don't have to recreate
them when we destroy inputs.
I like this idea as well. That way
I’m trying to install Graylog2 and I’m getting the following error:
2014-11-19 15:39:41,282 ERROR: org.graylog2.Main - Graylog2 startup failed.
Exiting. Exception was:
java.lang.IllegalStateException: Expected to be healthy after starting. The
following services are not running:
Hi Jeff,
do you see any other Exceptions in the logs of Graylog2? Which version of
Graylog2 are you running and can it connect to the Elasticsearch cluster?
Best regards,
Jochen
Am Mittwoch, 19. November 2014 16:54:32 UTC+1 schrieb Jeff Schoolcraft:
I’m trying to install Graylog2 and I’m
Hi,
we also like this idea and I have opened an issue
at https://github.com/Graylog2/graylog2-server/issues/773 for this change.
Cheers,
Jochen
Am Mittwoch, 19. November 2014 14:34:57 UTC+1 schrieb Jeremy Farr:
Or can't we create and maintain extractors separately from inputs and
later
It was solved in the chat by the following:
elasticsearch_discovery_zen_ping_multicast_enabled = false
kroepke
elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300
kroepke
in graylog2.conf
kroepke
elasticsearch defaults to multicast discovery, which sometimes just doesn’t
work. a
