TimT
October 9, 2017, 2:33pm
1
HI all,
Came across this issue today:
Both kibana and elastic are installed on same server and firewall ports have been opened.
I have tried using both ip and server name in the config files and re-installing the elastic search service (after deletion). (I uninstalled services and then removed services from registry)
I have installed this successfully on our test system with no issue and followed the same process for the production server.
I have also tried the following:
I can run http://servername:9200 and this tries to download the json file as i'd expect.
Have checked similar post, but none of the suggestions have so far worked. Any where I should be looking for more clues/information as to the issue.
Thanks.
TimT
October 9, 2017, 2:37pm
2
Kibana yml is as follows:
Kibana is served by a back end server. This setting specifies the port to use.
server.port: 5601
Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
The default is 'localhost', which usually means remote machines will not be able to connect.
To allow connections from remote users, set this parameter to a non-loopback address.
server.host: "C1RP0010PRAPP01"
Enables you to specify a path to mount Kibana at if you are running behind a proxy. This only affects
the URLs generated by Kibana, your proxy is expected to remove the basePath value before forwarding requests
to Kibana. This setting cannot end in a slash.
#server .basePath: ""
The maximum payload size in bytes for incoming server requests.
#server .maxPayloadBytes: 1048576
The Kibana server's name. This is used for display purposes.
#server.name : "your-hostname"
The URL of the Elasticsearch instance to use for all your queries.
elasticsearch.url: "http://C1RP0010PRAPP01:9200 "
When this setting's value is true Kibana uses the hostname specified in the server.host
setting. When the value of this setting is false, Kibana uses the hostname of the host
that connects to this Kibana instance.
#elasticsearch .preserveHost: true
Kibana uses an index in Elasticsearch to store saved searches, visualizations and
dashboards. Kibana creates a new index if the index doesn't already exist.
#kibana .index: ".kibana"
The default application to load.
#kibana .defaultAppId: "discover"
If your Elasticsearch is protected with basic authentication, these settings provide
the username and password that the Kibana server uses to perform maintenance on the Kibana
index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
is proxied through the Kibana server.
#elasticsearch .username: "user"#elasticsearch .password: "pass"
Paths to the PEM-format SSL certificate and SSL key files, respectively. These
files enable SSL for outgoing requests from the Kibana server to the browser.
#server .ssl.cert: /path/to/your/server.crt#server .ssl.key: /path/to/your/server.key
Optional settings that provide the paths to the PEM-format SSL certificate and key files.
These files validate that your Elasticsearch backend uses the same key files.
#elasticsearch .ssl.cert: /path/to/your/client.crt#elasticsearch .ssl.key: /path/to/your/client.key
Optional setting that enables you to specify a path to the PEM file for the certificate
authority for your Elasticsearch instance.
#elasticsearch.ssl.ca : /path/to/your/CA.pem
To disregard the validity of SSL certificates, change this setting's value to false.
#elasticsearch .ssl.verify: true
Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of
the elasticsearch.requestTimeout setting.
#elasticsearch .pingTimeout: 1500
Time in milliseconds to wait for responses from the back end or Elasticsearch. This value
must be a positive integer.
#elasticsearch .requestTimeout: 30000
List of Kibana client-side headers to send to Elasticsearch. To send no client-side
headers, set this value to [] (an empty list).
#elasticsearch .requestHeadersWhitelist: [ authorization ]
Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten
by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.
#elasticsearch .customHeaders: {}
Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
#elasticsearch .shardTimeout: 0
Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch .startupTimeout: 5000
Specifies the path where Kibana creates the process ID file.
#pid .file: /var/run/kibana.pid
Enables you specify a file where Kibana stores log output.
#logging .dest: stdout
Set the value of this setting to true to suppress all logging output.
#logging .silent: false
Set the value of this setting to true to suppress all logging output other than error messages.
#logging .quiet: false
Set the value of this setting to true to log all events, including system usage information
and all requests.
#logging .verbose: false
Set the interval in milliseconds to sample system and process performance
metrics. Minimum is 100ms. Defaults to 5000.
#ops .interval: 5000
TimT
October 9, 2017, 2:38pm
3
Elastiscsearch.ynl is:
======================== Elasticsearch Configuration =========================
NOTE: Elasticsearch comes with reasonable defaults for most settings.
Before you set out to tweak and tune the configuration, make sure you
understand what are you trying to accomplish and the consequences.
The primary way of configuring a node is via this file. This template lists
the most important settings you may want to configure for a production cluster.
Please consult the documentation for further information on configuration options:
---------------------------------- Cluster -----------------------------------
Use a descriptive name for your cluster:
cluster.name : Production1
------------------------------------ Node ------------------------------------
Use a descriptive name for the node:
#node.name : node-1
Add custom attributes to the node:
#node .attr.rack: r1
----------------------------------- Paths ------------------------------------
Path to directory where to store the data (separate multiple locations by comma):
#path .data: /path/to/data
Path to log files:
#path .logs: /path/to/logs
----------------------------------- Memory -----------------------------------
Lock the memory on startup:
#bootstrap .memory_lock: true
Make sure that the heap size is set to about half the memory available
on the system and that the owner of the process is allowed to use this
limit.
Elasticsearch performs poorly when the system is swapping the memory.
---------------------------------- Network -----------------------------------
Set the bind address to a specific IP (IPv4 or IPv6):
network.host: C1RP0010PRAPP01
Set a custom port for HTTP:
http.port: 9200
For more information, consult the network module documentation.
--------------------------------- Discovery ----------------------------------
Pass an initial list of hosts to perform discovery when new node is started:
The default list of hosts is ["127.0.0.1", "[::1]"]
#discovery .zen.ping.unicast.hosts: ["host1", "host2"]
Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#discovery .zen.minimum_master_nodes: 3
For more information, consult the zen discovery module documentation.
---------------------------------- Gateway -----------------------------------
Block initial recovery after a full cluster restart until N nodes are started:
#gateway .recover_after_nodes: 3
For more information, consult the gateway module documentation.
---------------------------------- Various -----------------------------------
Require explicit names when deleting indices:
#action .destructive_requires_name: true
What does the cluster stats API show?
warkolm
October 10, 2017, 12:25am
5
Also can you reformat your posts and use the </> (code) formatting on the configs, it's really hard to read as is
system
November 7, 2017, 12:26am
6
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
