-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Platform.sh recipe, MariaDB 10.5 unavailable when connecting #63
Comments
I'm seeing the same issue on Ubuntu 20.04 so it's not just a Mac centric issue. |
Sounds like the P.sh team thinks this container should be working; I'll test it out and report back. |
I just tried with Lando 3.5.1 with one of our existing sites using mariadb 10.5 and got the same error as before. |
Yeah, tested using the examples running edge Lando from source (as well as edge P.sh plugin) and no joy.
Returns: When I run
|
...updating that I tried this using the example that Jan was using, still same error. |
We want to make sure this isn't an M1 Mac specific problem, so @labboy0276 is going to try on his Linux machine. Please let us know your steps/errors you receive in detail! |
@reynoldsalec I am not seeing the same on Ubuntu (PopOS) 20.04. Everything seems to work ok: I used your example here: https://github.com/reynoldsalec/platformsh-63 Did a
Then ran the DB commands:
|
Hmm, booting up the example on my Intel Mac I seem to get the same "Can't connect" error. Seeing if @gilzow or Chad might be able to test this out on their machines to see if there is an OS-specificity. |
I too am on macOS (11.6.1). Cloned the same repo: https://github.com/reynoldsalec/platformsh-63
Output from
|
In the same test repo, if I change the version of mariadb to 10.4 and |
Using my own platform.sh sites and a copy of the platformsh-63 repo, no joy on Ubuntu 20.04. Same failure with being unable to connect to mariadb 10.5. |
Same problem here. But even switching back to 10.4 and doing lando destroy && lando rebuild && land start did not fix it. I am on an 2018 Intel Mac with Monterey. Lando Version 3.6.2 |
That's interesting. It should get you back to a stable, working set-up. If you're completely stuck, and in an unworking state, you might try > lando stop && lando destroy -y && lando poweroff
<snip>
> docker system prune -a
> lando start |
Running into the same issue with my Mac (OS: Monterey Intel), downgrading mariadb to 10.4 fixed the issue and I was able to build my site. With the same codebase I can build on my desktop at home (Ubuntu 20.04) with no issue and mariadb 10.5 |
Also confirming this is still an issue on intel Mac 11.6.5, lando v3.6.4 running platformsh recipe with mariadb 10.5 Normally going back to mariadb 10.4 worked. But, today it did not. Team members running ubuntu say the 10.5 service works for them. Willing to help track down this issue or test a solution |
I was hoping this was related to issue #163 , but I still had the db issues using mariadb 10.5 with the stable tag. downgrading to 10.4 along with wiping ~/.lando/composer/projectname, ~/.lando/config/projectname and ~/.lando/cache/projectname got me working again. |
I created an similar issue in 2020 (#44) I confirm that I still have this issue with Ubuntu. On the other hand, I have the complete opposite solution that @philltran gave . My project was using mariadb 10.4, after updating the .platform/services.yaml to upgrade to 10.5, the problem was gone. For Ubuntu 20 |
Tl;DR - changing database service from
mariadb:10.4
tomariadb:10.5
causes the database service to be unaccessible:ERROR 2002 (HY000): Can't connect to MySQL server on 'db' (115)
. Changing the db service back to 10.4 and rebuilding allows the db service to be available again.Lando version: 3.3.2
OS version: macOS 11.6
Contents of .lando.yml
Using the default Platform.sh WordPress composer template.
Contents of
/.platform/services.yml
:Contents of
.platform.app.yml
Tell us about the command you were running
After bringing up lando (
lando start
) and attempting to access the database (lando database
), causes the errorERROR 2002 (HY000): Can't connect to MySQL server on 'db' (115)
. Changing the version back to 10.4 and rebuilding (vialando rebuild
) allows the db service to be available again.Info from
lando info
:Similar if not identical issue to #61
The text was updated successfully, but these errors were encountered: