-
Notifications
You must be signed in to change notification settings - Fork 548
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
GitHub Actions: ubuntu: focal mariadb10.3 not starting. #1184
Comments
I was able to run MariaDB server 10.2, 10.3, 10.4, 10.5 on GitHub Actions using MariaDB's official container. https://mariadb.com/kb/en/installing-and-using-mariadb-via-docker/ For MariaDB server 10.0, 10.1 right now I see some error. But maybe I can fix it. The question is which MariaDB client libraries we use for the MariaDB case. |
Now I was able to run MariaDB server 10.0, 10.2, 10.3, 10.4, 10.5 on GitHub Actions using MariaDB's official container on my testing repository. Here is the log. I will prepare to send PR to update MariaDB cases on this repository's GitHub Actions. |
This ticket is to manage the issue on the GitHub Actions: Ubuntu focal (20.04) mariadb (>= 10.3) case.
Today I debugged this environment. the CI result with debugging code, the working branch on my repo.
Right now I see the mariadb-server simply does not start correctly. It's not related to SSL.
Does anyone succeeded to install and start MariaDB server >= 10.3 on Ubuntu focal?
So far I saw some issues, and here is my working log as a reference.
Working log.
apparmor issue
I saw this error log by
journalctl
on the CI environment.It seems that when the called apparmor's profile for the mysqld (that is MySQL, not MariaDB) is enabled, then the mariadb-server is installed, this error happens. The solution is after disabling or removing the profile or removing, installing the mariadb-server.
Here is the detail.
https://mariadb.com/kb/en/the-community-mariadb-troubles-only-running-after-reboot-times-out-when-try/
Warning: Could not increase number of max_open_files ...
I am not sure this is the direct cause of the error.
https://mariadb.com/kb/en/could-not-increase-number-of-max_open_files-to-more-than-1024-request-1835/
It seems the warning is disappeared after that.
The mariadb server still does not start
But the mariadb server still does not start.
The text was updated successfully, but these errors were encountered: