Elastic did not load properly

[TheGrandMaster01]

Issue with Kibana/Elastic. Elastic did not load properly. Check the server output for more information.

⚠️ Basic support information (commands are expected to run as root)

We happily take the time to improve T-Pot and take care of things, but we need you to take the time to create an issue that provides us with all the information we need.

• What OS are you T-Pot running on? Debian 12 - VirtualBox

• What is the version of the OS lsb_release -a and uname -a? Linux debian 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux

• What T-Pot version are you currently using (only T-Pot 24.04.x is currently supported)? 24.04

• What architecture are you running on (i.e. hardware, cloud, VM, etc.)? VirtualBox

• Review the ~/install_tpot.log, attach the log and highlight the errors. tpotinit.log

• How long has your installation been running? For more than 3 weeks

• Did you install upgrades, packages or use the update script? No

• Did you modify any scripts or configs? If yes, please attach the changes. No

• Please provide a screenshot of htop and docker stats.

• How much free disk space is available (df -h)?

• What is the current container status (dps)?

• On Linux: What is the status of the T-Pot service (systemctl status tpot)?

• What ports are being occupied? Stop T-Pot systemctl stop tpot and run grc netstat -tulpen

[t3chn0m4g3]

The setup is not really recommended. Based on the screenshots you seem to be running a desktop environment. This might lead to standby issues with ES being unable to close indices correctly and thus being unable to recover them correctly. You can use Elasticvue to further investigate the issue and simply delete indices that are defective, however you will most likely run into the same issues as long you are a using a desktop environment. Also docker logs elasticsearch -f will provide you with error logs regarding ES.

[TheGrandMaster01]

Error response from daemon: No such container: elasticsearch

Alright, so what do you recommend then, physical install?

[t3chn0m4g3]

Based on the screenshots the container is up at some point, then you need to run the logging. Otherwise follow the ReadMe to the recommended installation.

Physical install will make no difference, if you keep using a desktop environment the error will probably continue.