Kibana and elasticsearch failing to start

everything was working fine until I changed the IP for my virtual machine, when I tried to open the localhost it was saying kibana server is not ready yet, after that I tried some solutions but ended up facing this frustrating error

systemctl status kibana            
× kibana.service - Kibana
     Loaded: loaded (/usr/lib/systemd/system/kibana.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2024-04-18 11:29:15 EDT; 1min 44s ago
   Duration: 2.247s
       Docs: https://www.elastic.co
    Process: 42443 ExecStart=/usr/share/kibana/bin/kibana (code=exited, status=1/FAILURE)
   Main PID: 42443 (code=exited, status=1/FAILURE)
        CPU: 2.898s

Apr 18 11:29:15 kali-purple systemd[1]: kibana.service: Scheduled restart job, restart counter is at 3.
Apr 18 11:29:15 kali-purple systemd[1]: kibana.service: Start request repeated too quickly.
Apr 18 11:29:15 kali-purple systemd[1]: kibana.service: Failed with result 'exit-code'.
Apr 18 11:29:15 kali-purple systemd[1]: Failed to start kibana.service - Kibana.
Apr 18 11:29:15 kali-purple systemd[1]: kibana.service: Consumed 2.898s CPU time, 70.8M memory peak, 0B memory swap peak.
                                                                                                                                                                                                                                           
┌──(root㉿kali-purple)-[~]
└─# systemctl status kibana
× kibana.service - Kibana
     Loaded: loaded (/usr/lib/systemd/system/kibana.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2024-04-18 11:29:15 EDT; 8min ago
   Duration: 2.247s
       Docs: https://www.elastic.co
    Process: 42443 ExecStart=/usr/share/kibana/bin/kibana (code=exited, status=1/FAILURE)
   Main PID: 42443 (code=exited, status=1/FAILURE)
        CPU: 2.898s

Apr 18 11:29:15 kali-purple systemd[1]: kibana.service: Scheduled restart job, restart counter is at 3.
Apr 18 11:29:15 kali-purple systemd[1]: kibana.service: Start request repeated too quickly.
Apr 18 11:29:15 kali-purple systemd[1]: kibana.service: Failed with result 'exit-code'.
Apr 18 11:29:15 kali-purple systemd[1]: Failed to start kibana.service - Kibana.
Apr 18 11:29:15 kali-purple systemd[1]: kibana.service: Consumed 2.898s CPU time, 70.8M memory peak, 0B memory swap peak.
                                                                                                                                                                                                                                           
┌──(root㉿kali-purple)-[~]
└─# systemctl status elasticsearch
× elasticsearch.service - Elasticsearch
     Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2024-04-18 11:30:27 EDT; 7min ago
       Docs: https://www.elastic.co
    Process: 42839 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
   Main PID: 42839 (code=exited, status=1/FAILURE)
        CPU: 1min 14.597s

Apr 18 11:29:52 kali-purple systemd[1]: Starting elasticsearch.service - Elasticsearch...
Apr 18 11:29:56 kali-purple systemd-entrypoint[42839]: Apr 18, 2024 11:29:56 AM sun.util.locale.provider.LocaleProviderAdapter <clinit>
Apr 18 11:29:56 kali-purple systemd-entrypoint[42839]: WARNING: COMPAT locale provider will be removed in a future release
Apr 18 11:30:26 kali-purple systemd-entrypoint[42839]: ERROR: Elasticsearch did not exit normally - check the logs at /var/log/elasticsearch/elasticsearch.log
Apr 18 11:30:27 kali-purple systemd-entrypoint[42839]: ERROR: Elasticsearch died while starting up, with exit code 1
Apr 18 11:30:27 kali-purple systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Apr 18 11:30:27 kali-purple systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Apr 18 11:30:27 kali-purple systemd[1]: Failed to start elasticsearch.service - Elasticsearch.
Apr 18 11:30:27 kali-purple systemd[1]: elasticsearch.service: Consumed 1min 14.597s CPU time.

Did you check your elasticsearch logs? Kibana can't start without a functioning Elasticsearch cluster in the first place.

This seem to be a duplicate from your other post.

As mentioned, you are having systemd errors, you need to look in the system log for the reason why systemd cannot start your services.

Not sure where it is in Kali, but look for /var/log/messages or /var/log/syslog.

Try to start the services again and look on the system logs for fresh logs mentioned elasticsearch and kibana.

thank you I got it working