[graylog2] Re: fresh install of graylog 2.1.2 -> can't get it running

2017-02-13 Thread Denny Gebel
Thanks Jochen!

I switched the puppet-config for 
"elasticsearch_discovery_zen_ping_unicast_hosts" from Array to String.

Denny

Am Montag, 13. Februar 2017 10:42:40 UTC+1 schrieb Jochen Schalanda:
>
> Hi Denny,
>
> it looks like the elasticsearch_discovery_zen_ping_unicast_hosts setting 
> is wrong. Please refer to 
> http://docs.graylog.org/en/2.2/pages/configuration/elasticsearch.html#network-setup
>  
> for details.
>
> Cheers,
> Jochen
>
> On Monday, 13 February 2017 10:23:18 UTC+1, Denny Gebel wrote:
>>
>> Hi Grayloggers,
>>
>> I have a working 1.3.4 multi-server setup which needs to be upgraded.
>>
>> I've installed a new test environment with graylog 2.1.2 on CentOS 7 (no 
>> firewall enabled, selinux off):
>>
>> 3 VMs with Graylog (2.1.2) and MongoDB (2.6.12) + 3 VMs ES (2.4.4).
>> ES-Cluster is running fine, as well as the MongoDB-Replicaset.
>>
>> Configuration of Graylog is done via Graylog-Puppet-Module.
>>
>> The generated config file looks like this:
>> # WARNING: Maintained by Puppet, manual changes will be lost!
>>
>> allow_highlighting = true
>> allow_leading_wildcard_searches = true
>> content_packs_dir = /usr/share/graylog-server/contentpacks
>> elasticsearch_cluster_name = graylogcluster
>> elasticsearch_discovery_zen_ping_unicast_hosts = 
>> ["graylog-elasticsearch01.my.domain:9300", 
>> "graylog-elasticsearch02.my.domain:9300", 
>> "graylog-elasticsearch03.my.domain:9300"]
>> elasticsearch_index_prefix = graylog
>> elasticsearch_max_number_of_indices = 30
>> elasticsearch_max_time_per_index = 1d
>> elasticsearch_replicas = 1
>> elasticsearch_shards = 4
>> is_master = true
>> message_journal_dir = /var/lib/graylog-server/journal
>> mongodb_uri = 
>> mongodb://graylog:secretp...@graylog01.my.domain:27017,graylog02.my.domain:27017,graylog03.my.domain:27017/graylog
>> node_id_file = /etc/graylog/server/node-id
>> password_secret = supersecretpass
>> plugin_dir = /usr/share/graylog-server/plugin
>> rest_listen_uri = http://172.16.0.93:9000/api/
>> rest_transport_uri = http://172.16.0.93:9000/api/
>> retention_strategy = delete
>> root_password_sha2 = supersecretrootpass
>> root_timezone = Europe/Berlin
>> root_username = admin
>> rotation_strategy = time
>> web_enable = true
>> web_listen_uri = http://172.16.0.93:9000/
>>
>> Problem is: There's no web interface listening on port 9000 - which I 
>> would expect.
>>
>> Is there anything I missed? The log file (attached) doesn't show any 
>> error or something :/
>>
>> Thanks for your help.
>>
>> Denny
>>
>

-- 
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 email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/83004cc3-6cb3-4e05-9953-7ce29e1643b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: fresh install of graylog 2.1.2 -> can't get it running

2017-02-13 Thread Jochen Schalanda
Hi Denny,

it looks like the elasticsearch_discovery_zen_ping_unicast_hosts setting is 
wrong. Please refer 
to 
http://docs.graylog.org/en/2.2/pages/configuration/elasticsearch.html#network-setup
 
for details.

Cheers,
Jochen

On Monday, 13 February 2017 10:23:18 UTC+1, Denny Gebel wrote:
>
> Hi Grayloggers,
>
> I have a working 1.3.4 multi-server setup which needs to be upgraded.
>
> I've installed a new test environment with graylog 2.1.2 on CentOS 7 (no 
> firewall enabled, selinux off):
>
> 3 VMs with Graylog (2.1.2) and MongoDB (2.6.12) + 3 VMs ES (2.4.4).
> ES-Cluster is running fine, as well as the MongoDB-Replicaset.
>
> Configuration of Graylog is done via Graylog-Puppet-Module.
>
> The generated config file looks like this:
> # WARNING: Maintained by Puppet, manual changes will be lost!
>
> allow_highlighting = true
> allow_leading_wildcard_searches = true
> content_packs_dir = /usr/share/graylog-server/contentpacks
> elasticsearch_cluster_name = graylogcluster
> elasticsearch_discovery_zen_ping_unicast_hosts = 
> ["graylog-elasticsearch01.my.domain:9300", 
> "graylog-elasticsearch02.my.domain:9300", 
> "graylog-elasticsearch03.my.domain:9300"]
> elasticsearch_index_prefix = graylog
> elasticsearch_max_number_of_indices = 30
> elasticsearch_max_time_per_index = 1d
> elasticsearch_replicas = 1
> elasticsearch_shards = 4
> is_master = true
> message_journal_dir = /var/lib/graylog-server/journal
> mongodb_uri = 
> mongodb://graylog:secretp...@graylog01.my.domain:27017,graylog02.my.domain:27017,graylog03.my.domain:27017/graylog
> node_id_file = /etc/graylog/server/node-id
> password_secret = supersecretpass
> plugin_dir = /usr/share/graylog-server/plugin
> rest_listen_uri = http://172.16.0.93:9000/api/
> rest_transport_uri = http://172.16.0.93:9000/api/
> retention_strategy = delete
> root_password_sha2 = supersecretrootpass
> root_timezone = Europe/Berlin
> root_username = admin
> rotation_strategy = time
> web_enable = true
> web_listen_uri = http://172.16.0.93:9000/
>
> Problem is: There's no web interface listening on port 9000 - which I 
> would expect.
>
> Is there anything I missed? The log file (attached) doesn't show any error 
> or something :/
>
> Thanks for your help.
>
> Denny
>

-- 
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 email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/221dd34e-38f4-45c8-b519-5e11fbb26f3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.