Search results

Can you explain why Plesk actually did the MariaDB upgrade, even when system updates are deactivated? Does Plesk ignore these settings for some mandatory packages?

Autoinstaller did indeed the upgrade, despite auto updates are off (see attached image). Why is that? [2019-11-06 03:06:24.080488] Following bootstrapper packages will be installed: (empty) [2019-11-06 03:06:24.080506] ---------------- [2019-11-06 03:06:24.080519] Getting packages to...

How to prevent Plesk from doing this upgrade? We have this in our config, this does not prevent Plesk from updating MariaDB this night on several nodes: [updates] systemUpdatesTool = on

The problem reappeared this night. How to fix that?

Plesk or the WP Toolkit created these files exactly at 0:00 and did not remove them afterwards, so this seems to be Plesk update issue.

See Issue - WordPress Toolkit update disaster - you have to delete the .maintenance file and it should work again.

We had the same issue on some of our servers. You have to delete the file named ".maintenance" in the webroot to resolve this. Plesk should look into this asap, this is a very important issue as it breaks customers websites.

Yes, would be very good to have an option to disable this (for us) useless tool! Thanks!

IMHO this is definitly not a feauture, but a serious bug in one of your scripts. Please consider to open a bug report for this.

--------------------------------------------------------------- PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE - Plesk Onyx, CentOS 7, 64 Bit PROBLEM DESCRIPTION - The cron /etc/cron.hourly/plesk-php-cleanuper script does not respect session.gc_maxlifetime settings from Plesk PHP versions in...

You're welcome! Good news ;-)

Ok, added - please contact me directly to get the servers IP. Don't want to post it on this public forums. Thanks.

No problem, please send us your SSH PubKey to support {at} robhost.de

Any ETA for the next MU #14 with the fix included, finally?

Problem still exists in repo. Why does this fix take so long? It prevents whole system from updating, which is a major security issue. Does Plesk QA not test against EPEL (which is a standard repo for RHEL and CentOS imho).

Thanks, worked, finally. Can you guys from "PLESK" explain what exactly took 4 month to solve this?

Hi dash, here comes the info: # host autoinstall.plesk.com autoinstall.plesk.com is an alias for ec.geo.odin.net. ec.geo.odin.net is an alias for wpc.051C.thetacdn.net. wpc.051C.thetacdn.net is an alias for gp1.wpc.v2cdn.net. gp1.wpc.v2cdn.net has address 93.184.221.133...

You can move the /etc/yum.repos.d/pplesk-php5.3.repo to another directory and then do the update as an interim solution. But surely Odin has to fix the repo and the mirror sync asap.

Yep, really annoying :(

Problem still persists for "plesk-php53" repo. Odin, can you please fix this? This lasts since almost 2 month and is very poor from your support. At the moment this annoying repofail blocks CentOS 7.2 update on hundreds of hosts here.