Search results

Not humorous but a phrase - It's the very top link in the forum with 24K views!

Funny you should ask... Question - Try our new tool to upgrade your old MariaDB server from Plesk UI Make sure to take a full backup of your server before running that tool!

bump

So the database sounds like it's being stopped (but not gracefully) since you noted that you have to start the service up again and there are no logs about shutdown. Check the messages log and you might find that it's being sacrificed by the OOM killer.

This may not be an error caused by too many connections but rather a corrupt table or database causing the database service to restart. Check your database log and see if it's causing the entire database service to crash/restart frequently.

@Sebahat.hadzhi are you able to provide a more official confirmation as to the updated approach above? Additionally, are we correct in assuming that this precludes the use of older (PHP 7) versions?

Before you go through the effort of building the server, it's possible that this is still just a compromised site issue. Keep in mind that one tactic used by perpetrators today is to keep running a PHP file such that even when the file itself it deleted, it still executes, thereby "living" in...

The latest Plesk PHP package appears to include ImageMagick 3.8.0 for PHP 8.1-8.4 however there is a caveat and that is to use it, the EPEL one must be removed via yum. So running the following command should remove EPEL's ImageMagick: # yum remove ImageMagick Once the process is complete...

Username: TITLE ImageMagick 6.9.13-25 breaks PDF reading PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE AlmaLinux 9.5 (Teal Serval), Plesk Obsidian 18.0.68 Update #2 PROBLEM DESCRIPTION Latest release of ImageMagick 6.9.13-25 updated via YUM breaks PDF reading and returns an...

Plesk Obsidian 18.0.68 Update 2 rolling out today:

Quite slow on pushing out this rather critical issue; hopefully there is an update in very short order.

Did you add the additional FTP user via Plesk?

You're welcome! It's not directly a Plesk issue per say but they could add better support/documentation for handling CMS platforms on Nginx-only scenarios which would shortcut the aggravation that you went through. Sebahat's solution would work if requests were proxied to Apache while Mow...

A bit extreme but I can understand the sentiment and indeed with all of these constant license costs increases coupled with "you asked for it" (but really nobody asked for it) features, it would seem that PHP 8.4 could be shipped a little more expeditiously or at least open a transparent dialog...

If you're using Nginx-only (no proxying to Apache) then you'll likely want to use either the the single domain or all domain versions of this...

If that's the case, then it's likely an abusive or malicious bot/vulnerability sniffer that causes your memory usage to surge so much that OS invokes the OOM killer to avoid kernel panic so you might want to check access logs if you want to try and track it down. Almalinux 9 is solid and has a...

If the database (or more likely, a table within it) is corrupt or the service crashes during the dump process, that might result in odd behaviors so after checking the aforementioned path, try checking/optimizing the database, restart the database service, and check the database log to see if...

Your VPS doesn't have enough memory and the OOM killer selects the highest memory consuming process (which on your setup is invariably going to be MariaDB) to avoid a kernel panic state. If you can add more memory, that would help as more than likely you have a momentary increase in traffic...

That "InnoDB: Cannot allocate memory for the buffer pool" error usually indicates that there isn't enough free memory so one option is to restart your server with the allocation below as your cached memory might be taking up almost all of the free memory: If that fails, then check to ensure...

Those numbers are far too low - Trying clicking the "Revert All" button in your screenshot and then add these changes to the custom file in /etc/my.cnf.d/custom.cnf file before restarting MariaDB.