Please forgive me that this is a long post but I reckoned more info would help explain the problem.
I have just installed VM on a clean install of Alma 8.6. During the wizard I get an error about Mariadb not being installed. I had no option at that time other than to cancel the wizard and come back to it later.
I had a look about and then recheck configuration I get the following:
MariaDB does not appear to be installed and running on your system, or has not yet been set up properly in Webmin’s MariaDB Database module. If your system does not use MariaDB, it should be disabled in Virtualmin’s module configuration page.
When I go to the first issue " that it has not yet been set up properly in Webmin’s MariaDB Database module it takes me to Mariadb server page in Webmin.
I then get The MariaDB startup script /etc/rc.d/init.d/mysqld was not found on your system. Maybe MariaDB is not installed, or your module configuration is incorrect.
The package can be automatically installed by Webmin using YUM. I try installing through Webmin and then I get the message:
Last metadata expiration check: 0:38:15 ago on Tue May 24 18:17:14 2022.
Error:
Problem 1: problem with installed package mariadb-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
package mariadb-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64 conflicts with mysql provided by mysql-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64
package mysql-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64 conflicts with mariadb provided by mariadb-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
conflicting requests
Problem 2: problem with installed package mariadb-server-utils-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
package mariadb-server-utils-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64 conflicts with mysql-server provided by mysql-server-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64
conflicting requests
Problem 3: problem with installed package mariadb-devel-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
package mariadb-devel-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64 conflicts with mysql-devel provided by mysql-devel-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64
package mysql-devel-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64 conflicts with mariadb-devel provided by mariadb-devel-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
conflicting requests
(try to add ‘–allowerasing’ to command line to replace conflicting packages or ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)
… install failed!
When I click the link to I get the following message:
Last metadata expiration check: 0:26:35 ago on Tue May 24 18:17:14 2022.
Error:
Problem 1: problem with installed package mariadb-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
package mariadb-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64 conflicts with mysql provided by mysql-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64
package mysql-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64 conflicts with mariadb provided by mariadb-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
conflicting requests
Problem 2: problem with installed package mariadb-server-utils-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
package mariadb-server-utils-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64 conflicts with mysql-server provided by mysql-server-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64
conflicting requests
Problem 3: problem with installed package mariadb-devel-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
package mariadb-devel-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64 conflicts with mysql-devel provided by mysql-devel-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64
package mysql-devel-8.0.26-1.module_el8.4.0+2532+b8928c02.x86_64 conflicts with mariadb-devel provided by mariadb-devel-3:10.3.32-2.module_el8.6.0+2867+72759d2f.x86_64
conflicting requests
(try to add ‘–allowerasing’ to command line to replace conflicting packages or ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)
On the features and plug ins page, Mariadb is ticked and MySQL is not on there.
I hope this makes some sense but if you need more info please let me know what you need and what I need to do.
I used the development script you gave me a link to in a previous thread.
BUT it was a converted OS so that’s obviously my problem. I just wanted to play about with Rocky for a couple of hours on the new server before converting to Alma. I’ve got the option to mount an Alma ISO so I’ll do that and if I still run into problems I’ll come back here.
I can assure you that installing using development version of install script (using my latest PR) works just fine with AlmaLinux.
Although, @Joe hasn’t upgraded Virtualin-Config package yet, where Webalizer must be disabled upon configuration is run. Because Webalizer is no longer installed but enabled it will throw an error upon config check, unless it’s manually disabled in Features and Plugins page.
I went back and installed Alma from scratch, clean drive and all fine.
Start the install of VM and all is well until I reach the MariaDB database size page in the wizard. It gives me this error message: Warning! MariaDB could not be started with the new configuration :
sh: /etc/rc.d/init.d/mysqld: No such file or directory
The old configuration has been restored.
I’m a bit confused and have looked but can’t find the answer here.
This seems like either: Our configuration is wrong, or the OS is being detected as a generic Linux. It shouldn’t be looking for an old initscript…it’s been years since that was a correct path. (I think it’s the latter. We don’t have this problem on CentOS 8. But, I also haven’t seen it on Alma or Rocky in my testing.)
We need to see /etc/redhat-release
And what OS is showing as being detected by Webmin?
I have now tried a clean install of Rocky 8.6 and it worked flawlessly so tried Alma again and that just gave me the same error messages.
So some difference between Alma and Rocky 8.6 causing this.
You’ve also got PostgreSQL installed here. This isn’t a fresh minimal installation. Seems to have MySQL preinstalled.
I’m not sure how to deal with that…replacing packages via dependencies in a yum group is quirky. We’d have to add a bunch of mess to remove any extras before starting installing our stuff.
What’s the source of your install? I guess it’s an OS image at a hosting provider?
So is it the case that it is not possible to install Vm on Alma 8.6 without these errors? Do Rocky and Alma have significant differences that result in these problems? I mean I am left with a working Vm on Rocky and I’m quite happy with that.
I installed both Alma and Rocky with minimal versions through my host, Hetzner, and I’m not sure if they are changed by them. Is that a possibility?
I don’t know. I haven’t had time to look to see what is going on. It looks like MySQL is somehow preinstalled (and postgresql, too!) on the screenshots posted above. So…something is unusual here. I’d be surprised if a minimal install includes either, must less both, preinstalled. That’d be nuts. So, maybe something else is going on, but I can’t guess what. I’ll have to look into it.
I am surprised they are behaving differently. I would expect Rocky and Alma to be very, very, similar…since both are supposed to be RHEL-compatible rebuilds. And, we should be treating them identically in our installer. Same repos, same packages, same configuration changes. But, this is kinda independent of any of that, though…having extra databases installed doesn’t make much sense.
I just tried again with a no extra software installed. I checked if mysql was not installed. Ran the script and mysql-sql was installed after running the script but not before, so something is installing mysql. Using dnf -list I see mysql but its not showing up in webmin Software Packages search. Weird stuff.
