Automated ISPConfig Installation with older MariaDB and without Antivirus and Spamfilter

Dear all
How can I install ISPConfig with MariaDB 10.5.15 and without Antivirus and Spamfilter. I want to use this method because I will install ISPConfig on low RAM server and one of my web app have problem with stable version of mariadb 10.6.7. It freezes when query some tables and use 100% CPU on mariadb process. It works well with MariaDB one version below (10.5.15).

I prefer automate installation on following link: https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/

 

1. How low is your ram that installing and running Antivirus and Spamfilter will cause you problems? ISPConfig server normally can work fine with 2GB ram.
2. Why is that web app of yours requires lower version of mariadb? It doesn't make sense to me but I think you may try mysql instead of mariadb but I am not so sure whether the web app of yours will work with it though. Or separate that web app to another server.

Anyway, for your request, I guess you can simply run the ISPConfig Auto Installer, uninstall the software that you do not want, install software that you want, then run ISPConfig force update, BUT I am not sure ISPConfig will work if no AV is installed.

 

On low RAM system, make a big swap, so database does get to out-of-memory situation. Maybe your web app would work even with newer mariadb with enough memory space?
If I were you, rather that downgrading mariadb I would find out why the web app fails and fix the problem.

 

really not possible to run mail server without spamfilter? Can I at least exclude ClamAV (--no-clamav)?
For MariaDB problem, I will start a new discussion specifically on the problem after I find out how to exclude AntiVirus from the ISPConfig auto installation. It simply use 100% CPU on mariadb process when the App retrive data from some tables so I have to kill the process each time it happen. Normally, it should take only 1 second to complete (MariaDB 10.5.15 or lower)

 

You have not said how much RAM and swap that host has.

 

So I have to use auto install script then remove ClamAV afterwards because there is no option to exclude ClamAV in the first place and spam filter is required for mail to work, right? ClamAV is memory hungry process. Without it, all others process should use around 400MB. They should run well on 1GB RAM. Is there any proper ClamAV removal procedure after ISPConfig auto installation?

 

I used auto install script to install ISPConfig then run "apt autoremove clamav-freshclam" and free up a lot of memory. I have everything installed except ClamAV and RAM usage is only around 500MB. I will test further to see if something break. I noticed that MariaDB version is 10.3.34. Why does auto install script pull such an old version? Why not v10.5.15 or v10.6.7?

 

No, default MariaDB version for Ubuntu 20.04 is 10.6.7

 

How do you know that? Are you referring to mariadb site or Ubuntu 20.04 package?

 

I want to use Mariadb 10.5.15 so I added repository of this version to apt source and started ISPConfig auto install script and I got error message "UPDATE mysql.user SET Password=PASSWORD('diejdJidfjudkfdjkfkKhjdkjfkd') WHERE User='root'; failed". I think in version 10.5. There is no mysql.user anymore. Instead, it's replaced with mysql.global_priv. Can I get around this error?

 

That is not correct. The default version of MariaDB on Ubuntu 20.04.5 is 10.3. We can upgrade to 10.4+ here.

 

In short you cannot (unless you know how to resolve all the errors yourself) because ISPConfig only supports default version that is bundled with your OS.

 

Thanks for the confirmation @ahrasis. This is important. @till mentioned in a thread a long time ago that support for MariaDB 10.4+ was planned for ISPConfig v3.2+. But that hasn't happened yet for many valid reasons. As you said, since 10.4 is not bundled with Ubuntu 20, we should not use 10.4+ on this platform. Since ISPConfig isn't certified for Ubuntu 22 yet, that means MariaDB 10.3 is the one and only DB for 3.2 at this time and we're locked to Ubuntu 20 until further notice. I've been looking closely at these details, considering benefits of upgrades to the database or phpMyAdmin, etc. But with a better understanding of these dependencies, I'm completely comfortable to continue using the ISPConfig environment exactly as defined, with 3.2.x on Ubuntu 20 with MariaDB 10.3 until we can move forward to Ubuntu 22+.

This is mostly for anyone else who stumbles on this thread, as I have many times while researching.