millions-hydrogen-95879
04/19/2023, 6:48 AMUnable to run quickstart - the following issues were detected:
- elasticsearch-setup exited with an error
- datahub-gms is still starting
- elasticsearch is running by not yet healthy
- datahub-upgrade is still runninglively-cat-88289
04/19/2023, 6:48 AMlimited-refrigerator-50812
04/19/2023, 12:07 PMexport DOCKER_DEFAULT_PLATFORM=linux/amd64
Then, when I run quickstart, the images will start but they get stuck in some infinite loop. So I manually stop and start them again. If this happens for you as well you could try to stop and start them in this order (and check the logs to see if they work).
First check that these images are working:
Mysql + Zookeeper —> Broker —> Schemaregistry —> Elasticsearch —> Elasticsearchsetup
These generally just work for me. However, it is possible to that Elasticsearch gets stuck.
GMS The GMS relies on the previous images, and when it starts up, it checks if it can connect to their ports. Check the logs to see if these connections are made succesfully and if not, restart those images untill they do. Even if the GMS connects succesfully to all the ports. I often have to restart the container two or three times until it finishes and exposes the 8080 port. You can check wether GMS is up and running by pinging http://localhost:8080/config. Afterwards, you can start the upgrade, actions and frontend containers. Again, if they get stuck, just keep rebooting them.
``millions-hydrogen-95879
04/20/2023, 5:38 AM05:34:11 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.astonishing-answer-96712
04/20/2023, 9:00 PM