Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Database service is unhealthy after restart #1381
The database service starts only once just after rebuild and then database is unhealthy for all next starts in drupal7 recipe.
Tell us about your setup
Linux Mint 18.2
Server: Docker Engine - Community
Tell us about your
Very simple test site.
Tell us about the command you were running
Tell us about the error you got
Tell us more
The problem is probably related to drupal7 recipe. The drupal8 recipe works normally. I tested
This is part of log, maybe it helps.
@pirog I gladly helped.
The problem is dynamic and not all restarts failed. I tested these steps in sequence for simple D8 recipe:
@pirog It's hard to say, but unfortunately the problem seems to remain in RC3.
Step to reproduce:
Randomly in approx. 50 % of cases you will see:
That’s interesting. I’ve restarted maybe 30 times in a row and not seeing this.…
On Sat, Feb 2, 2019 at 6:22 PM Martin Klíma ***@***.***> wrote: @pirog <https://github.com/pirog> It's hard to say, but unfortunately the problem seems to remain in RC3. Step to reproduce: 1. Use simple drupal7 or drupal8 recipe without any specialities. 2. Use lando destroy -y; lando rebuild -y 3. And repeat several times command lando restart Randomly in approx. 50 % of cases you will see: Waiting until database service is ready... warn: Service database is unhealthy warn: Run "lando logs -s database" before BOOMSHAKALAKA!!! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1381 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAri0F8PRTGhNm4CLs1ohSIGBMeVBRlMks5vJh2ygaJpZM4aflY5> .
I continued with tests on another PC with Linux Mint and the pattern is unpredictible. 1 = OK, 0 = Fail. The 1st run is after
The message in log
is always occurs regardless of the result. The only difference I found in log is:
for started database and
for failed database.
There are also 2 opened issues look very similar to our problem on bitnami-docker-mysql: