Recent content by Franco

Hi all, I wanted to provide some sort of a conclusion on this issue : after various attempts described here and more, the best progress was obtained by disabling firewalld (while keeping the Plesk firewall. I think I could have made the opposite choice too). It was difficult to believe, but...

Thanks. I found out that I am already running NetworkManager and that disabling/stopping network-scripts won't affect my system. It only gives those errors when checking the network.service status. I guess I would need some clean-up along the way, but things look ok for now.

Hello, I am running almalinux 8.10 with Plesk 18.00.66 (the latest, I believe) and I observe the following errors at boot: network[870]: Bringing up interface eno16780032: network[1050]: Error: Connection activation failed: No suitable device found for this connect> network[870]: [FAILED]...

Thank you all, I'll think about migrating to something else. In any case a dedicated server is way an overkill. The current host has told me they guarantee the 8GB 100%, no matter what. Besides, I checked with the online mySQL calculator and with current settings (i.e., 2GB...

@trialotto the settings suggested for the DB were implemented a few days ago, but MariaDB crashes when reaching 25%+ of the 8GB available, i.e., when it gets to 2GB or so. I had a very very stable VPS with CentOS for years and with more websites and traffic than today. No issues whatsoever...

And here we go again, less than 2 days later MariaDB issues its OOM: Jan 6 06:09:10 vps kernel: mariadbd invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=-900 Jan 6 06:09:10 vps kernel: CPU: 2 PID: 493772 Comm: mariadbd Kdump: loaded Not tainted...

I was able to set the innodb parameters only after having rolled back vm.overcommit_memory to 0. Soon after the mariaDB changes the memory situation is: MiB Mem : 7665.7 total, 2131.7 free, 1833.2 used, 3700.8 buff/cache MiB Swap: 2048.0 total, 1937.8 free, 110.2 used. 5033.2...

I tried but the result is the database fails to start (cannot allocate memory): Jan 3 09:37:45 vps systemd[1]: Starting MariaDB 10.6.18 database server... Jan 3 09:37:45 vps mariadbd[3540]: 2025-01-03 9:37:45 0 [Note] Starting MariaDB 10.6.18-MariaDB source revision...

in my /etc/my.cnf it says it will include all files under /etc/my.cnf.d directory but it is followed by an include for /etc/db-performance.cnf. I then edited that file with your suggested values but the database crashes. I rolled it back and it works again (i.e., badly). I then looked at the...

I have created the file according to your instructions and restarted MariaDB; however, when I want to read the variables they are unchanged. Besides, my attempt via the Plesk db command line does not work either: MariaDB [psa]> set global innodb_buffer_pool_size = 2147483648; Query OK, 0 rows...

Hi, thank you for you suggestion, which I implemented. Unfortunately I still see some OOM messages in website logs and, more worrying: vps mariadbd[3640]: 2025-01-02 17:45:16 36 [Warning] Aborted connection 36 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (Out of...

Hello, I had a very stable system with CentOs 8, but since I have migrated to Almalinux 8 I have had several crashes (average 1-2/month) with php-fpm (8.3) trying to kill itself with OOM signals. I then followed some advice to set vm.overcommit_memory = 2 and a couple of other minor changes...

Hi, I guess KlausZ is talking about "yum updates": I observe the same situation and only today I got something to update, namely the kernel, MariaDB and python or something. After, say a month or so, whilst on CentOS updates were rather frequent.

In the end I succeeded by using the command "export LEAPP_OVL_SIZE=4096" before the script execution. At the end of the conversion, though, the apache/nginx configuration files contained errors (ex: Error: New configuration files for the Apache web server were not created due to the errors in...

Sorry, more readable Filesystem Type 1K-blocks Used Available Use% Mounted on devtmpfs devtmpfs 3983000 0 3983000 0% /dev tmpfs tmpfs 3994788 0 3994788 0% /dev/shm tmpfs tmpfs 3994788...