- Jun 1, 2020
chown graylog:graylog graylog.conf log4j2.xml, why graylog:graylog?
You don't need to do this; this is already set by the pkg install.
Modify the Elasticsearch configuration file (/etc/elasticsearch/elasticsearch.yml) and set the cluster name to graylog and uncomment action.auto_create_index: false to enable the action:
$ sudo vim /etc/elasticsearch/elasticsearch.yml
I suspect you've failed to set ownership of one or more of the directories you needed to specify in graylog.conf to the graylog user/group.Input 5f26b7aa1559cb6ab29aabd6 has failed to start on node 453fd7fc-0e3d-414d-aca0-c8496367d940 for this reason: »Permission denied
Unless you enabled TLS support in graylog.conf, I don't recommend you expose your graylog jail to the Internet like this. Run a VPN on your router, and access your graylog installation that way.I have all working, the only that seems not working is the oitside acces on the graylog webpage. I have a dns pointing to my graylog ip over 9000 port, and the fdqn resolving outside and inside, but only work inside the same lan, outside is blank page. I have a forward port on my router pointing to my freenas jail ip 192.168.0.98 on port 9000, but nothing, i only have 192.168.0.98:9000 on the bind_adress on configuration, i try all the others but then not working the internal webpage.
You might be waiting for a while, and any script I might do to install this isn't going to enable TLS. But you could put it behind a reverse proxy, and I'll have a script out within a couple of days on that subject--though if you use a router that has this capability (like pfSense or OPNsense), you might want to use that instead.uff to much for me, i wait for a Danb35 script ;-)
Since there is no such release, no, you didn't. You may have done it with 12.0 (which is still in beta), or with some flavor of 11.3 (which is an actual release). But if your jails are being corrupted, there's assuredly something going on not tied to installing this software. I'd encourage you to track that down in a separate thread (with way more details than, well, you've given in any post you've made in these forums).Yesterday I reinstall all, with 13.1 release