can't get new server hostname

[winsonlee]

i add 2 server into nls cluster, but can't see new server in "configure" and "admin --> system status"

[cdienger]

Were you logged into either of the new machines when you took the screenshot? Try logging in directly to one of the new machines and check the status.

Also check the /usr/local/nagioslogserver/var/cluster_hosts on all machines. It should contain the IPs or the resolvable names of each instance in the cluster.

Run this on one of the new servers to export a copy of the config and PM it to me:

Code: Select all

curl -XPOST http://localhost:9200/nagioslogserver/_export?path=/tmp/nagioslogserver.tar.gz

The file it creates and that we'd like to see is /tmp/nagioslogserver.tar.gz.

[winsonlee]

Because of the relationship between performance, We expand the cluster nodes to 8 nodes now
but still ca't see all new node.

and in "Configure" menu has a blank item, blank item will change after reflash screen.

[winsonlee]

Because of the relationship between performance, We expand the cluster nodes to 8 nodes now
but still ca't see all new node.

and in "Configure" menu has a blank item, blank item will change after reflash screen.

[cdienger]

A PM was sent yesterday with a steps try with the nodes in the cluster. Please test the same way with these additional nodes.

[winsonlee]

A PM was sent yesterday with a steps try with the nodes in the cluster. Please test the same way with these additional nodes.

all node in same subnet, no firewall between each node.

telnet test is ok.

[cdienger]

Please open a ticket for this so at https://support.nagios.com/tickets and we can look into this more with a remote. Please attach a profile from each system to the ticket after it is opened. A profile can be under Admin > System > System Status > Download System Profile or from the command line with:

Code: Select all

/usr/local/nagioslogserver/scripts/profile.sh

This will create /tmp/system-profile.tar.gz.

Note that this file can be very large and may not be able to be uploaded through the ticketing system. This is usually due to the logs in the Logstash and/or Elasticsearch directories found in it. If it is too large, please open the profile, extract these directories/files and send them separately.