[graylog2] Re: Incorrect Graylog Cluster details

2017-02-15 Thread Jochen Schalanda 
Hi Paweł,

please describe exactly what you did and which error messages you've seen. 
Additionally describe the current situation, the configuration of all 
Graylog nodes, and what problem you're trying to solve right now.

Cheers,
Jochen

On Wednesday, 15 February 2017 00:34:59 UTC+1, Paweł Karoluk wrote:
>
> Hi Jochen, You're right but there is another problem
> I have tried to enable rest_transport_uri with "public IP" but it couldn't 
> bind to Interface with port 9000 or 12900. I have SeLinux na IPtables 
> disabled so it's not a problem, maybe something else
>
> # netstat -tlpn | grep java
> tcp0  0 :::127.0.0.1:9000  :::*   
>   LISTEN  62396/java  
> tcp0  0 :::10.0.0.1:9200:::* 
> LISTEN  62396/java  
> tcp0  0 :::10.0.0.1:9300:::* 
> LISTEN  62396/java 
>
>
> My current config:
>
> rest_listen_uri = http://127.0.0.1:9000/api/
> rest_transport_uri = http://10.0.0.1:9000/api/
>
> web_listen_uri = http://127.0.0.1:9000/
> web_endpoint_uri = https://graylog1.local/api/
>
> HAproxy config:
> https://graylog1.local/ -> 127.0.0.1:9000
>
> I will appreciate any help
>
> Cheers!
>
>
> Hi, I have two node Graylog Cluster and as you can see there is some wrong 
>> with cluster config:
>>
>>
>> *GET /api/system/cluster/nodes*
>>
>> {
>> nodes: [
>> {
>> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
>> node_id: "5f596ebf-a988-4c08-858e-67d38a3e483b",
>> type: "server",
>> transport_address: "http://127.0.0.1:9000/api/;,
>> last_seen: "2017-02-10T00:45:30.000Z",
>> short_node_id: "5f596ebf",
>> hostname: "analog1.local",
>> is_master: true
>> },
>> {
>> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
>> node_id: "8be9e293-f60b-40c6-a0e6-8af6d617eb1a",
>> type: "server",
>> transport_address: "http://127.0.0.1:9000/api/;,
>> last_seen: "2017-02-10T00:45:30.000Z",
>> short_node_id: "8be9e293",
>> hostname: "analog2.local",
>> is_master: false
>> }
>> ],
>> total: 2
>> }
>>
>>
>> *GET /api/cluster*
>>
>> {
>> 5f596ebf-a988-4c08-858e-67d38a3e483b: {
>> facility: "graylog-server",
>> codename: "Smuttynose",
>> node_id: "5f596ebf-a988-4c08-858e-67d38a3e483b",
>> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
>> version: "2.1.3+040d371",
>> started_at: "2017-02-10T00:27:13.101Z",
>> hostname: "analog1.local",
>> lifecycle: "running",
>> lb_status: "alive",
>> timezone: "Europe/Warsaw",
>> operating_system: "Linux 2.6.32-642.13.1.el6.x86_64",
>> is_processing: true
>> },
>> 8be9e293-f60b-40c6-a0e6-8af6d617eb1a: {
>> facility: "graylog-server",
>> codename: "Smuttynose",
>> node_id: "5f596ebf-a988-4c08-858e-67d38a3e483b",
>> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
>> version: "2.1.3+040d371",
>> started_at: "2017-02-10T00:27:13.101Z",
>> hostname: "analog1.local",
>> lifecycle: "running",
>> lb_status: "alive",
>> timezone: "Europe/Warsaw",
>> operating_system: "Linux 2.6.32-642.13.1.el6.x86_64",
>> is_processing: true
>> }
>> }
>>
>>
>> In /api/cluster I supposed to get two different node_id and hostname, but 
>> hostnames are the same. As the result when I want to check the 
>> /system/nodes I got dubbed stats only of one host. The real HeapSize of 
>> analog2 is only 2GB (img: analog2-system-nodes 
>> ) not 4GB as analog1 - master node 
>> (img: analog1-system-nodes ).
>>
>>
>> MongoDB and ES Cluster are external and shared for both hosts.
>>
>>
>> Thanks Guys
>>
>>
>> Pawel
>>
>

-- 
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/889031aa-aa6a-479d-a8a0-b73f62219bd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Incorrect Graylog Cluster details

2017-02-14 Thread Paweł Karoluk 
Hi Jochen, You're right but there is another problem
I have tried to enable rest_transport_uri with "public IP" but it couldn't 
bind to Interface with port 9000 or 12900. I have SeLinux na IPtables 
disabled so it's not a problem, maybe something else

# netstat -tlpn | grep java
tcp0  0 :::127.0.0.1:9000  :::* 
LISTEN  62396/java  
tcp0  0 :::10.0.0.1:9200:::*   
  LISTEN  62396/java  
tcp0  0 :::10.0.0.1:9300:::*   
  LISTEN  62396/java 


My current config:

rest_listen_uri = http://127.0.0.1:9000/api/
rest_transport_uri = http://10.0.0.1:9000/api/

web_listen_uri = http://127.0.0.1:9000/
web_endpoint_uri = https://graylog1.local/api/

HAproxy config:
https://graylog1.local/ -> 127.0.0.1:9000

I will appreciate any help

Cheers!


Hi, I have two node Graylog Cluster and as you can see there is some wrong 
> with cluster config:
>
>
> *GET /api/system/cluster/nodes*
>
> {
> nodes: [
> {
> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
> node_id: "5f596ebf-a988-4c08-858e-67d38a3e483b",
> type: "server",
> transport_address: "http://127.0.0.1:9000/api/;,
> last_seen: "2017-02-10T00:45:30.000Z",
> short_node_id: "5f596ebf",
> hostname: "analog1.local",
> is_master: true
> },
> {
> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
> node_id: "8be9e293-f60b-40c6-a0e6-8af6d617eb1a",
> type: "server",
> transport_address: "http://127.0.0.1:9000/api/;,
> last_seen: "2017-02-10T00:45:30.000Z",
> short_node_id: "8be9e293",
> hostname: "analog2.local",
> is_master: false
> }
> ],
> total: 2
> }
>
>
> *GET /api/cluster*
>
> {
> 5f596ebf-a988-4c08-858e-67d38a3e483b: {
> facility: "graylog-server",
> codename: "Smuttynose",
> node_id: "5f596ebf-a988-4c08-858e-67d38a3e483b",
> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
> version: "2.1.3+040d371",
> started_at: "2017-02-10T00:27:13.101Z",
> hostname: "analog1.local",
> lifecycle: "running",
> lb_status: "alive",
> timezone: "Europe/Warsaw",
> operating_system: "Linux 2.6.32-642.13.1.el6.x86_64",
> is_processing: true
> },
> 8be9e293-f60b-40c6-a0e6-8af6d617eb1a: {
> facility: "graylog-server",
> codename: "Smuttynose",
> node_id: "5f596ebf-a988-4c08-858e-67d38a3e483b",
> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
> version: "2.1.3+040d371",
> started_at: "2017-02-10T00:27:13.101Z",
> hostname: "analog1.local",
> lifecycle: "running",
> lb_status: "alive",
> timezone: "Europe/Warsaw",
> operating_system: "Linux 2.6.32-642.13.1.el6.x86_64",
> is_processing: true
> }
> }
>
>
> In /api/cluster I supposed to get two different node_id and hostname, but 
> hostnames are the same. As the result when I want to check the 
> /system/nodes I got dubbed stats only of one host. The real HeapSize of 
> analog2 is only 2GB (img: analog2-system-nodes 
> ) not 4GB as analog1 - master node 
> (img: analog1-system-nodes ).
>
>
> MongoDB and ES Cluster are external and shared for both hosts.
>
>
> Thanks Guys
>
>
> Pawel
>

-- 
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/e73fcf7f-68bf-4c4b-a4f3-5649af8adfd7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Incorrect Graylog Cluster details

2017-02-13 Thread Jochen Schalanda 
Hi Paweł,

as a matter of fact, everything is correct, except for your configuration.

The transport_address attribute in the output of GET 
/api/system/cluster/nodes shows, that both nodes are using 
http://127.0.0.1:9000/api/ as their transport address.
This address can be configured with the rest_transport_uri setting 

 
and has to be the public URI of the Graylog REST API of each Graylog node. 
It's being used by every Graylog node to communicate with other Graylog 
nodes.

tl;dr: Set rest_transport_uri on each Graylog node to a URI which can be 
accessed by all the other Graylog nodes.

Cheers,
Jochen

On Monday, 13 February 2017 19:51:02 UTC+1, Paweł Karoluk wrote:
>
> Hi, I have two node Graylog Cluster and as you can see there is some wrong 
> with cluster config:
>
>
> *GET /api/system/cluster/nodes*
>
> {
> nodes: [
> {
> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
> node_id: "5f596ebf-a988-4c08-858e-67d38a3e483b",
> type: "server",
> transport_address: "http://127.0.0.1:9000/api/;,
> last_seen: "2017-02-10T00:45:30.000Z",
> short_node_id: "5f596ebf",
> hostname: "analog1.local",
> is_master: true
> },
> {
> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
> node_id: "8be9e293-f60b-40c6-a0e6-8af6d617eb1a",
> type: "server",
> transport_address: "http://127.0.0.1:9000/api/;,
> last_seen: "2017-02-10T00:45:30.000Z",
> short_node_id: "8be9e293",
> hostname: "analog2.local",
> is_master: false
> }
> ],
> total: 2
> }
>
>
> *GET /api/cluster*
>
> {
> 5f596ebf-a988-4c08-858e-67d38a3e483b: {
> facility: "graylog-server",
> codename: "Smuttynose",
> node_id: "5f596ebf-a988-4c08-858e-67d38a3e483b",
> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
> version: "2.1.3+040d371",
> started_at: "2017-02-10T00:27:13.101Z",
> hostname: "analog1.local",
> lifecycle: "running",
> lb_status: "alive",
> timezone: "Europe/Warsaw",
> operating_system: "Linux 2.6.32-642.13.1.el6.x86_64",
> is_processing: true
> },
> 8be9e293-f60b-40c6-a0e6-8af6d617eb1a: {
> facility: "graylog-server",
> codename: "Smuttynose",
> node_id: "5f596ebf-a988-4c08-858e-67d38a3e483b",
> cluster_id: "6701202c-a9fe-42d2-8d5a-015acf66fbfa",
> version: "2.1.3+040d371",
> started_at: "2017-02-10T00:27:13.101Z",
> hostname: "analog1.local",
> lifecycle: "running",
> lb_status: "alive",
> timezone: "Europe/Warsaw",
> operating_system: "Linux 2.6.32-642.13.1.el6.x86_64",
> is_processing: true
> }
> }
>
>
> In /api/cluster I supposed to get two different node_id and hostname, but 
> hostnames are the same. As the result when I want to check the 
> /system/nodes I got dubbed stats only of one host. The real HeapSize of 
> analog2 is only 2GB (img: analog2-system-nodes 
> ) not 4GB as analog1 - master node 
> (img: analog1-system-nodes ).
>
>
> MongoDB and ES Cluster are external and shared for both hosts.
>
>
> Thanks Guys
>
>
> Pawel
>

-- 
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/6a85729a-f686-4b3c-b239-d43500d897d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.