Plesk Panel MU Update Notifications

[pleskpanel]

On one CentOS 6.5 Plesk 12.0.18 install (with all MUs applied) each time an admin logs in a notification is displayed ("Plesk was successfully updated. View detailed information on the updates.") and once a week the panel generates an email notification (Plesk panel updated successfully).

Other Plesk 12.0.18 servers that are set to automatically update aren't generating this email notification or displaying the "green" notification upon login to the Plesk Panel.

Is there a flag, tmp file, or a DB trigger that isn't being set properly to cause this?

 

[UFHH01]

Please try to fix that issue with:

/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base​

If this didn't help, please use the DailyMaintenance script ( => KB - article 114 979 <= ) :

/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f CheckForUpdates
or/and
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f InstallUpdates
or/and
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f UpgradePanel​

 

[pleskpanel]

Thanks for the tips - We ran the patch updates using /usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base but it didn't stop the panel from its daily "Plesk was successfully updated. View detailed information on the updates." display so we've gone ahead with the DailyMaintenance script using the flags that you noted and we'll see if this resolves it.

Regardless of the result, many thanks again UFHH01 for pointing us in the right direction!

 

[pleskpanel]

Following UFHH01's suggestion, we manually ran the DailyMaintenance script (running each time with a separate flag above) and since then we haven't had any errant Plesk panel notifications - Not entirely clear as to why it was updating properly but regardless, the running the DailyMaintenance script process manually once did the trick.