Search results

Same result following a successful upgrade to 18.0.29 #1.

Peter, thank you for sharing that as it confirms our conclusion as well! We were seeing the same behavior (micro-updates installed automatically but "number jumps" from 28 to 29 are manual) but as the new semi-major versioning system is still relatively new, there isn't much official...

The 18.0.29 update is still reported by Plesk but without manually initiating it, when will it kick off automatically?

Here are the results with Plesk 18.0.28 v3 still reporting a Postfix component update: # plesk installer --select-release-current --reinstall-patch --upgrade-installed-component WARNING: Ignored deprecated parameter in Plesk Installer's configuration file: 'SOURCE_TYPE' = 'plesk' WARNING...

This may not be a Plesk issue so to start, you could check your sending IP against a blacklist tool such as MX Lookup Tool - Check your DNS MX Records online - MxToolbox and then extend it to an SPF check with the sending IP to validate it.

On CentOS Linux 7.8.2003 (Core) running Plesk Obsidian Version 18.0.28 Update #3, we've been seeing the following: We dutifully hit Continue and while the process completes as follows, Plesk continues to show "Component updates are available" - Installation started in background Loaded...

Thank you - To clarify, is there a delay or a throttled delivery of when the major updates are actually applied? All of our server panels show the 18.0.29 release as ready to install but none of attempted to actually install it automatically.

With Plesk Obsidian, should automatic updates be expected for larger version upgrades such as 18.0.28 Update #3 to 18.0.29 or do larger version jumps need to be manually initiated? If it is expected to be automatic, which of these little fellas would be responsible for enabling that...

Another consideration might be to use the Linux screen command to account for unforeseen drops in Internet connectivity.

What kind of disk space was available at restart?

Yes, many mirrors were very slow to pick it up so either it was a question of waiting a week or manually updating the package.

‪CentOS Linux 7.7.1908 Version 17.8.11 Update #85 No CloudLinux Plesk Onyx for Linux returns this error for Yum and Plesk update commands: 403 packages excluded due to repository priority protections Exception: Failed to solve dependencies: plesk-php56-imagick-3.1.2-centos7.20042209.x86_64...

Are you able to share your solution?

Are you taking advantage of OPcache? OPcache can behave strangely with inefficient or error-ridden code which in some scenarios could possibly negate its benefits.

Thank you for your follow-up! Here are the answers to your questions: - PHP errors using the Plesk PHP 7.2 handler were written to the site's error log and not the /var/log/plesk-php73-fpm/ error file - "Add PHP 7.3 handler support via Plesk GUI" (this refers to adding the PHP 7.3 handler via...

here are some examples of code that was previously only written to the site's PHP error log and is now being written to the handler's log instead:

TITLE: Plesk Onyx 17.8 PHP 7.3 Handler Logs All Levels to Syslog PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: 17.8.11 Update #71, CentOS Linux 7.7.1908 PROBLEM DESCRIPTION: Following addition of the Plesk PHP 7.3.10 handler version via the Plesk components tool, all PHP errors that use it...

Indeed, same issues here on the same OS/Plesk versions!

While a recent upgrade of ten servers went off without a hitch, it's still a good idea to take a snapshot or backup image of those servers and kick off the process after work hours to help minimize any potential downtime should you run into an issue that's not quick or easy to recover from.

Not a bug