Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

gNumskull's avatar

Installation Hangs

I'm following the https://laravel.com/docs/8.x/installation instructions under https://laravel.com/docs/8.x/installation#getting-started-on-macos. I'm using Mac OS 10.14.6

The first command:

curl -s "https://laravel.build/example-app" | bash

was successful. Then I ran

cd example-app && ./vendor/bin/sail up

which seems to hang with this output in the terminal

mysql_1         | 2021-06-06T00:12:09.459894Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.25'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
meilisearch_1   | [2021-06-06T01:11:35Z INFO  ureq::unit] sending request POST https://api.amplitude.com/httpapi
meilisearch_1   | [2021-06-06T01:11:36Z ERROR meilisearch::analytics] Unsuccessful call to Amplitude: too_many_requests
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
meilisearch_1   | [2021-06-06T02:11:33Z INFO  ureq::unit] sending request POST https://api.amplitude.com/httpapi
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events
mailhog_1       | [APIv1] KEEPALIVE /api/v1/events

This is my second attempt, after the first (which hanged in the same place), in Docker I ran: Reset to Factory Defaults and Clean / Purge data Then I restarted the installation process which still produces the hang detailed above.

At this point I am unable to install the easiest test project.

Any help would be appreciated.

0 likes
3 replies
rhand's avatar
rhand
Best Answer
Level 6

The MeiliSearch error does not seem to matter and the other output just seems like you started up Sail keeping feedback running in the terminal. Are you sure it is not running. Did you check for containers running using docker ps? Or did you check for all containers to see if any failed with docker ps -a?

1 like
gNumskull's avatar

Thanks @rhand It is running fine. I didn't realize it was a normal warning.

IMAGE                         COMMAND                  STATUS
mysql:8.0                     "docker-entrypoint.s…"   Up 11 hours (healthy)
selenium/standalone-chrome    "/opt/bin/entry_poin…"   Up 11 hours
mailhog/mailhog:latest        "MailHog"                Up 11 hours
redis:alpine                  "docker-entrypoint.s…"   Up 11 hours (healthy)
getmeili/meilisearch:latest   "tini -- /bin/sh -c …"   Up 11 hours
madsplattr's avatar

Thanks for all this. I was wondering if I had done something wrong, esp since it took a while to get sail up and running for me — because first I had to figure out how to turn off my already existing mysql and apache2 services that listened on the same ports that docker wanted to use.

Please or to participate in this conversation.