Search results

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.

Please compare and show the output of: # yum info MariaDB-server # yum info --disableexcludes=all MariaDB-server

grep -r exclude /etc/yum* should show you. Unless this is due to DNF module exclusions (which I don't believe it is).

Remove the exclude from your DNF configuration. Yes.

Yes, currently it's not supported for Mailman. There's a chance it won't be supported for Mailman 2 at all.

dkimpy

ARC signing is enabled by default. So this effectively does nothing out of the box. Can be disabled via plesk bin settings -s mail_arc_sign=false plus repair mail.

At this time - no. However, "Allow signing outgoing mail" should be enabled.

Please run the following command and paste it's entire output here: bash -x /usr/lib/plesk-9.0/mariadb_repo_setup --mariadb-server-version mariadb-10.11 --skip-maxscale --skip-check-installed