Search results

Please provide your Plesk and Docker extension versions.

Sure. We actually use the upstream MariaDB packages for this feature. They are not modified in any way by Plesk (and Plesk doesn't interfere with mariadb-check on the service startup), so you should follow MariaDB Community Bug Reports and Feature Requests to report such bugs into the upstream.

Since MariaDB developers didn't manage to properly fix this issue on their side, we've implemented a workaround on our side. It was just released with Plesk 18.0.63.4. We've added an additional check for kernel version to avoid the issue since Plesk 18.0.61.4. So, all in all, it should be safe...

Please be advised that we've identified a couple of issues with the latest MariaDB 10.11.8 release. So you might want to hold off MariaDB upgrades until further notice to ensure the upgrade process is smooth and doesn't require manual intervention. The first is issue is only on Debian-based...

Should be resolved now. Thank you for reporting this issue!

Looks like a specific CDN endpoint (79.127.235.6) issue. Will reply here once it's addressed.

System package update-notifier-common post-install script failed due to a Python module absence. Try running: sudo apt-get --reinstall install python3-debian Alternatively, you may try removing update-notifier-common and packages that depend on it, if you don't need them (be careful, though).

This could've happened during a short window as a result of package updates being uploaded and cached by CDN. In case you're still experiencing issues, please notify us.

As long as it doesn't pull in other Plesk packages (other than the listed ones) and no sites use it, it's fine. It would just effectively result in the corresponding Plesk component being uninstalled. I recommend the following sequence of commands (verify that expected packages are being...

Should be OK. But you're free to update to point releases in whatever method is convenient for you.

That's expected, since the distribution is not available at the download site. This implies you have issues with the system repositories as well. Try running yum update php-\* and seeing if it errors out. In general, if you're absolutely sure you're not using the OS vendor PHP anywhere, you may...

In general you should be able to update from the default source. Try running plesk installer --source http://autoinstall.plesk.com Please also show the output of rpm -q psa

plesk sbin (internal utilities) and plesk bin (public CLI) are different. As I said before, just raise the limits according to your new needs.

Obviously, the same goes for removing arbitrary files.

Please do not use commands in the plesk sbin family, unless directed by the official documentation or staff. These are internal commands. Using them directly may result in unexpected changes or damage to your system. If you want to raise the messages limit for a specific object (mail, domain...

Probably there are issues on your system with the filesystem or SELinux.

@Darren Debono , @ext_jmontalvo , thank you for bringing this to our attention. The fix will be released with Plesk 18.0.60.

MariaDB developers may have changed their maintainer identification. Could you execute the following commands and paste the output here? This will help identify the root cause. for f in /usr/bin/mysql /usr/sbin/mysqld; do dpkg-query -W -f '${Maintainer}' "`dpkg -S "$f" | cut -d: -f1`"; echo...

I saw such error messages on older OSes when there are issues with certain DB table files (basically corrupted). Check the MariaDB logs (e.g. /var/log/mariadb/mariadb.log). You'll probably see something like: Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB...

Either you've already fixed your configuration or the problem is in a completely different place. I suggest either retrying installation or addressing support.