Kibana service running but port 5601 not opened

Elastic Stack Kibana
1

I'm new to kibana and I'm facing a problem I'm following https://digitalave.github.io/spring/2020/01/15/Install-and-configre-wazuh-security-monitoring-and-detection-system.html tutorial to setup everything my kibana.yml looks like
server.port: 5601
server.host: "ip of my server"
elasticsearch.hosts: ["http://127.0.0.1:9200"]

netstat -natp | grep 560 returns nothing and port number 5601 is not opened.

systemctl status -l kibana.service return
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2020-03-12 16:44:41 EDT; 1s ago
Main PID: 15579 (node)
CGroup: /system.slice/kibana.service
└─15579 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml

Mar 12 16:44:41 Wazuh systemd[1]: kibana.service holdoff time over, scheduling restart.
Mar 12 16:44:41 Wazuh systemd[1]: Stopped Kibana.
Mar 12 16:44:41 Wazuh systemd[1]: Started Kibana.

2

Hello,

Are there any other Kibana logs in the logging destination or in systemd?

3

last 10 lines of /var/log/kibana/kibana.log
{"type":"log","@timestamp":"2020-03-13T06:45:33Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"Unable to revive connection: http://127.0.0.1:9200/"}
{"type":"log","@timestamp":"2020-03-13T06:45:33Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"No living connections"}
{"type":"log","@timestamp":"2020-03-13T06:45:36Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"Unable to revive connection: http://127.0.0.1:9200/"}
{"type":"log","@timestamp":"2020-03-13T06:45:36Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"No living connections"}
{"type":"log","@timestamp":"2020-03-13T06:45:38Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"Unable to revive connection: http://127.0.0.1:9200/"}
{"type":"log","@timestamp":"2020-03-13T06:45:38Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"No living connections"}
{"type":"log","@timestamp":"2020-03-13T06:45:41Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"Unable to revive connection: http://127.0.0.1:9200/"}
{"type":"log","@timestamp":"2020-03-13T06:45:41Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"No living connections"}
{"type":"log","@timestamp":"2020-03-13T06:45:43Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"Unable to revive connection: http://127.0.0.1:9200/"}
{"type":"log","@timestamp":"2020-03-13T06:45:43Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"No living connections"}

and
curl http://my_server_ip:9200 return
{
"name" : "node-1",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "N2USPGkIRei-hDSF4bfDyA",
"version" : {
"number" : "7.6.1",
"build_flavor" : "default",
"build_type" : "rpm",
"build_hash" : "aa751e09be0a5072e8570670309b1f12348f023b",
"build_date" : "2020-02-29T00:15:25.529771Z",
"build_snapshot" : false,
"lucene_version" : "8.4.0",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}

but curl http://127.0.0.1:9200 return
curl: (7) Failed connect to 127.0.0.1:9200; Connection refused

4

I managed to start port but now it says Kibana server is not ready yet.

5

If the port is open now, you can try restarting the server and the "Kibana Server is not ready" message will disappear in at most 1 minute after starting the server.

6

I had started it from last night but still gave same "Kibana server is not ready yet"

7

Is the elasticsearch.host set to my_server_ip:9200 or to 127.0.0.1:9200 in kibana.yml?

8

yea I changed elasticsearch.hosts: ["http://127.0.0.1:9200"] to elasticsearch.hosts: ["http://my_server_ip:9200"] and that's why kibana's port is open but now I'm facing the problem is "Kibana server is not ready yet" on kibana port 5601

my installed versions
wazuh manager - 3.11.4-1
filebeat - 7.6.1
elasticsearch - 7.6.1
kibana - 7.6.1
wazuh app for kibana - 3.11.4_7.6.1

9

Are you getting the same errors in the Kibana log now?

["warning","elasticsearch","admin"],"pid":16454,"message":"Unable to revive connection: http://127.0.0.1:9200/"}
{"type":"log","@timestamp":"2020-03-13T06:45:43Z","tags":["warning","elasticsearch","admin"],"pid":16454,"message":"No living connections"}

10

There is not any log file only two files in /var/log/kibana/ is kibana.stderr kibana.stdout

11

Anything in those files?

12

Nope both files are blank.
here is log while running kibana manually
[root@server bin]# ./kibana --allow-root
log [16:05:52.073] [info][plugins-service] Plugin "case" is disabled.
log [16:06:30.737] [info][plugins-system] Setting up [37] plugins: [taskMana ger,siem,licensing,infra,encryptedSavedObjects,code,usageCollection,metrics,canv as,timelion,features,security,apm_oss,translations,reporting,uiActions,data,navi gation,status_page,share,newsfeed,kibana_legacy,management,dev_tools,inspector,e xpressions,visualizations,embeddable,advancedUiActions,dashboard_embeddable_cont ainer,home,spaces,cloud,apm,graph,eui_utils,bfetch]
log [16:06:30.738] [info][plugins][taskManager] Setting up plugin
log [16:06:30.790] [info][plugins][siem] Setting up plugin
log [16:06:30.791] [info][licensing][plugins] Setting up plugin
log [16:06:30.794] [info][infra][plugins] Setting up plugin
log [16:06:30.794] [info][encryptedSavedObjects][plugins] Setting up plugin
log [16:06:30.795] [warning][config][encryptedSavedObjects][plugins] Generat ing a random key for xpack.encryptedSavedObjects.encryptionKey. To be able to de crypt encrypted saved objects attributes after restart, please set xpack.encrypt edSavedObjects.encryptionKey in kibana.yml
log [16:06:30.800] [info][code][plugins] Setting up plugin
log [16:06:30.801] [info][plugins][usageCollection] Setting up plugin
log [16:06:30.803] [info][metrics][plugins] Setting up plugin
log [16:06:30.804] [info][canvas][plugins] Setting up plugin
log [16:06:30.809] [info][plugins][timelion] Setting up plugin
log [16:06:30.810] [info][features][plugins] Setting up plugin
log [16:06:30.811] [info][plugins][security] Setting up plugin
log [16:06:30.812] [warning][config][plugins][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml
log [16:06:30.813] [warning][config][plugins][security] Session cookies will be transmitted over insecure connections. This is not recommended.
log [16:06:30.836] [info][apm_oss][plugins] Setting up plugin
log [16:06:30.837] [info][plugins][translations] Setting up plugin
log [16:06:30.837] [info][data][plugins] Setting up plugin
log [16:06:30.843] [info][plugins][share] Setting up plugin
log [16:06:30.844] [info][home][plugins] Setting up plugin
log [16:06:30.850] [info][plugins][spaces] Setting up plugin
log [16:06:30.876] [info][cloud][plugins] Setting up plugin
log [16:06:30.877] [info][apm][plugins] Setting up plugin
log [16:06:30.883] [info][graph][plugins] Setting up plugin
log [16:06:30.886] [info][bfetch][plugins] Setting up plugin
log [16:06:30.893] [info][savedobjects-service] Waiting until all Elasticsea rch nodes are compatible with Kibana before starting saved objects migrations...
log [16:06:30.929] [info][savedobjects-service] Starting saved objects migra tions
log [16:06:31.100] [info][plugins-system] Starting [22] plugins: [taskManage r,siem,licensing,infra,encryptedSavedObjects,code,usageCollection,metrics,canvas ,timelion,features,security,apm_oss,translations,data,share,home,spaces,cloud,ap m,graph,bfetch]
log [16:06:32.898] [info][optimize] Optimizing and caching bundles for core, graph, monitoring, space_selector, login, overwritten_session, logout, logged_o ut, ml, dashboardViewer, apm, maps, canvas, infra, siem, uptime, lens, wazuh, ki bana, stateSessionStorageRedirect, status_page and timelion. This may take a few minutes

13

Hi, Thank you for helping.
I managed to start everything perfectly.
The problem was elasticsearch service was not started now everything works perfectly.

14

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.