Thank you for helping. I needed to refresh my mind and restart diagnostic from the start.
I created a different thread about Scheduled Monitoring.
I agree what you said about those “light” instances and I don’t complain when once in a while I have to restart Webmin on one of the working instances (note that the hosted Tiki/MariaDB is published 24/7).
Trying to details the diagnostic, the instances were all installed following this exact procedure : Tiki Wiki CMS installation on Amazon Lightsail instance with Debian11, MariaDB, Git and Virtualmin/Webmin control panel
The one in Paris, Zone A (eu-west-3a) was Debian10 and had the issue that started this thread.
A few days I create a new instance (delete the previous one) with Debian11 and have the exact same issues:
- MariaDB shutdown regularly
- I can’t set up a Scheduled Monitoring
Comparing with a working server.
Working server:
System Information
|Operating system|Debian Linux 10|
|Webmin version|1.994|Usermin version|1.840|
|Virtualmin version|7.1-1|Authentic theme version|19.93.1|
- Apache Webserver
- PHP-FPM 7.3.33 Server (off)
- PHP-FPM 7.4.30 Server
- PHP-FPM 8.0.23 Server (off)
- PHP-FPM 8.1.10 Server (off)
- BIND DNS Server
- SSH Server
- MariaDB Database Server
This server is located in South America and up 99.9% of the time.
Server with the issue;
System Information
|Operating system|Debian Linux 11|
|Webmin version|2.001|Usermin version|1.860|
|Virtualmin version|7.2-1|Authentic theme version|20.01.1:5|
- Apache Webserver
- PHP-FPM 7.4.30 Server
- BIND DNS Server
- Postfix Mail Server
- Dovecot IMAP / POP3 Server (off)
- SSH Server
- MariaDB Database Server
Note; I see I have to update the working server but I keep it that way as long as I didn’t solve the issue.