• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Plesk 12.0.18 MU#60

Rate this MU

  • 5

    Votes: 2 40.0%
  • 4

    Votes: 0 0.0%
  • 3

    Votes: 1 20.0%
  • 2

    Votes: 1 20.0%
  • 1

    Votes: 1 20.0%

  • Total voters
    5

IgorG

Plesk addicted!
Plesk Certified Professional
Ladies and Gentlemen,

We have released new microupdate - http://kb.odin.com/en/126526
Please write in this sticky thread all problems with your Plesk servers which arose after applying this microupdate.
We also welcome the positive reviews :)

Several improvements were made in this microupdate. Please share your opinion how it was easy to get them.

Thanks.
 
Installing MU#60 yields some errors and does not resolve the issue with Imagick on CentOS 6.7:

Updating: plesk-wp-cli-0.18.0-15081116.noarch [1/2]
Cleanup: plesk-wp-cli [2/2]
Verify: 1/2: plesk-wp-cli.noarch 0:0.18.0-15081116 - u
Verify: 2/2: plesk-wp-cli.noarch 0:0.18.0-15021212 - ud
===> Cumulative APS controller upgrade (final stage) has been started.
===> Cumulative upgrade of APS controller (final stage) has been completed.
===> Cumulative Plesk upgrade (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade of Plesk (final stage) has been completed.
/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh: line 394: /etc/httpd/conf/httpd.conf.rpmnew
/etc/httpd/conf/httpd.conf.new: No such file or directory
cat: write error: Broken pipe
mv: target `/etc/httpd/conf/httpd.conf' is not a directory
/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh: line 394: /etc/httpd/conf/httpd.conf.rpmnew
/etc/httpd/conf/httpd.conf.new: No such file or directory
cat: write error: Broken pipe
mv: target `/etc/httpd/conf/httpd.conf' is not a directory
/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh: line 394: /etc/httpd/conf/httpd.conf.rpmnew
/etc/httpd/conf/httpd.conf.new: No such file or directory
cat: write error: Broken pipe
mv: target `/etc/httpd/conf/httpd.conf' is not a directory
/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh: line 394: /etc/httpd/conf/httpd.conf.rpmnew
/etc/httpd/conf/httpd.conf.new: No such file or directory
cat: write error: Broken pipe
mv: target `/etc/httpd/conf/httpd.conf' is not a directory
Stopping sw-cp-serverd: [ OK ]
Starting psa... Starting sw-engine-fpm: [ OK ]


CentOS 6.7 - PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/php/modules/imagick.so' - libMagickWand.so.2: cannot open shared object file: No such file or directory in Unknown on line 0
 
Hi Igor! Hope all is well. I have 5 Plesk servers and on one of my most important ones this update stopped php-fpm from working. Not sure why but about a minute after I got the email that the system had been updated last night all sites on this server stopped with the 502 bad gateway error. Any insight as to why this would have happened?? Anything I can check? All I had to do was service php-fpm restart and it now is answering but for now I have disabled auto updates so something like this doesn't happen again. Let me know if you have any ideas or if I can get you more information.

Thanks,

Tony
 
Another thing I just noticed. After last nights update I can no longer make any adjustments to fail2ban.

Unable to add some IP addresses to the list of trusted addresses: f2bmng failed: ERROR Found no accessible config files for 'filter.d/ssh' under /etc/fail2ban
ERROR No section: 'Definition'
ERROR No section: 'Definition'
ERROR Unable to read the filter
ERROR Errors in jail 'ssh'. Skipping...
ERROR Failed during configuration: 'NoneType' object has no attribute 'startswith'
ERROR:f2bmng:Command '['/usr/bin/fail2ban-client', 'reload']' returned non-zero exit status 255

Being that this is a production server it's not good... Any ideas would be appreciated.

Thanks,

Tony
 
Hi TonyI,

for a short and dirty resolution, I would suggest un- and re-installing Fail2Ban over the command line:

Make a backup:
mkdir /etc/fail2ban.backup && cp /etc/fail2ban /etc/fail2ban.backup
afterwards to remove Fail2Ban:
/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --remove-component fail2ban
afterwards to re-install Fail2Ban:
/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component fail2ban

You can then enable Fail2Ban quickly again with the desired jails and investigate your issue in your files inside the backup folder.
 
Unable to load dynamic library '/usr/lib64/php/modules/imagick.so' - libMagickWand.so.2

This from your system PHP.
You should install all system updates and update ImageMagick extension.

Or you can just use one of Plesk PHP:

#/opt/plesk/php/5.4/bin/php -m | grep magic
imagick
# /opt/plesk/php/5.5/bin/php -m | grep magic
imagick
# /opt/plesk/php/5.6/bin/php -m | grep magic
imagick
#
# /opt/plesk/php/5.6/bin/php -i | grep 'Warning'
# /opt/plesk/php/5.6/bin/php -v | grep 'Warning'
# /opt/plesk/php/5.5/bin/php -i | grep 'Warning'
# /opt/plesk/php/5.5/bin/php -v | grep 'Warning'
# /opt/plesk/php/5.4/bin/php -i | grep 'Warning'
# /opt/plesk/php/5.4/bin/php -v | grep 'Warning'
 
Thanks UFHH01. I will give that a try and let you guys know. Another thing I noticed since the update is this error in the backup manager.

Server settings are skipped from backup due to error: No semi-colon found after entity name [Ln: 28, Col: 373927334]

Nothing has changed w/ regards to the backups. Anyone ever seen this error? Any ideas?

Thanks,

Tony
 
Hiho,

i have followed the instructions with the Key file.
# wget http://autoinstall.plesk.com/plesk.gpg
# apt-key add plesk.gpg

This i have do before i start the update, but i become the same error messages since MU 49 or so.
W: GPG-Fehler: http://autoinstall.plesk.com trusty InRelease: Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 227C38D6AF741DEB
W: GPG-Fehler: http://autoinstall.plesk.com trusty InRelease: Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 227C38D6AF741DEB

My Server runs with Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-61-generic x86_64).

All works very well, its only the error message.
What can i do to solve this?
 
Hi Igor,

still getting Update Errors on multiple Plesk Servers when they try to update to Centos 6.7 ... latest MU #60 is installed
Error:
Code:
--> Running transaction check
---> Package ImageMagick.x86_64 0:6.5.4.7-7.el6_5 will be updated
--> Processing Dependency: libMagickCore.so.2()(64bit) for package: psiconv-0.9.8-5.el6.x86_64
---> Package libwmf.x86_64 0:0.2.8.4-23.el6 will be installed
---> Package vim-filesystem.x86_64 2:7.4.629-5.el6 will be installed
--> Finished Dependency Resolution
Error: Package: psiconv-0.9.8-5.el6.x86_64 (@epel)
           Requires: libMagickCore.so.2()(64bit)
           Removing: ImageMagick-6.5.4.7-7.el6_5.x86_64 (@updates)
               libMagickCore.so.2()(64bit)
           Updated By: ImageMagick-6.7.2.7-2.el6.x86_64 (base)
               Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

and on another Plesk Server:

Code:
--> Running transaction check
---> Package ImageMagick.x86_64 0:6.5.4.7-7.el6_5 will be updated
--> Processing Dependency: libMagickCore.so.2()(64bit) for package: php-pecl-imagick-2.2.2-4.el6.x86_64
--> Processing Dependency: libMagickWand.so.2()(64bit) for package: php-pecl-imagick-2.2.2-4.el6.x86_64
---> Package libwmf.x86_64 0:0.2.8.4-23.el6 will be installed
---> Package vim-filesystem.x86_64 2:7.4.629-5.el6 will be installed
--> Finished Dependency Resolution
Error: Package: php-pecl-imagick-2.2.2-4.el6.x86_64 (@epel)
           Requires: libMagickCore.so.2()(64bit)
           Removing: ImageMagick-6.5.4.7-7.el6_5.x86_64 (@updates)
               libMagickCore.so.2()(64bit)
           Updated By: ImageMagick-6.7.2.7-2.el6.x86_64 (base)
               Not found
Error: Package: php-pecl-imagick-2.2.2-4.el6.x86_64 (@epel)
           Requires: libMagickWand.so.2()(64bit)
           Removing: ImageMagick-6.5.4.7-7.el6_5.x86_64 (@updates)
               libMagickWand.so.2()(64bit)
           Updated By: ImageMagick-6.7.2.7-2.el6.x86_64 (base)
               Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Any ideas on this?

Thank you
Andreas Schnederle-Wagner
 
Well... I'll add my error problems into this thing too. After restoring a backup made prior to the update, I still encounter some odd httpd issue regarding vhosts, even after attempting a repair.

Code:
[[email protected]] /usr/local/psa/bin #> /usr/local/psa/bin/repair --run
-- Restoring DNS server configuration... started.
      ns239754.ip-192-99-160.net: Ok
      msrv.ca: Ok
      webmail.msrv.ca: Ok
      maos.ca: Ok
      files.maos.ca: Ok
      doremi-fansubs.com: Ok
      rctgamer3.doremi-fansubs.com: Ok
      pocketloli.com: Ok
      reader.pocketloli.com: Ok
      lolibrigadescans.com: Ok
      pizzicatomusic.ca: Ok
      hodge-mma.ca: Ok
      ns239754.ip-192-99-160.net: Ok
      srv1.msrv.ca: Ok
      onetimescans.com: Ok
      hotchocolatescans.com: Ok
-- Restoring DNS server configuration... done: Ok
-- Restoring mail server configuration... started.
==> Checking for: mailsrv_conf_init... ok
==> Checking for: mail_handlers_init... ok
==> Checking for: mailsrv_entities_dump... ok
==> Checking for: mail_admin_aliases... ok
==> Checking for: mail_auth_dump... ok
==> Checking for: mailman_lists_dump... ok
==> Checking for: mail_kav8_restore... ok
==> Checking for: mail_responder_restore... ok
==> Checking for: mail_imap_restore... ok
==> Checking for: mail_spam_restore... ok
==> Checking for: mail_grey_restore... ok
==> Checking for: mail_mailbox_restore... ok
==> Checking for: mail_spf_restore... ok
==> Checking for: mail_dk_restore... ok
==> Checking for: mail_drweb_restore... ok
==> Checking for: mail_outgoing_restore... fail
==> Checking for: mail_transport_restore... ok
Errors occured in mail restore procedure
Some utilities have exited with errors:
  /usr/lib64/plesk-9.0/remote_mail_restore/mail_outgoing_restore
-- Restoring mail server configuration... done: Error
-- Restoring web server configuration... started.
Execution failed.
Command: httpdmng
Arguments: Array
(
    [0] => --reconfigure-domains
    [1] => doremi-fansubs.com,files.maos.ca,hodge-mma.ca,hotchocolatescans.com,lolibrigadescans.com,maos.ca,msrv.ca,ns239754.ip-192-99-160.net,onetimescans.com,pizzicatomusic.ca,pocketloli.com,rctgamer3.doremi-fansubs.com,reader.pocketloli.com,webmail.msrv.ca
)

Details: [2015-08-17 08:43:08] ERR [util_exec] proc_close() failed
[2015-08-17 08:43:10] ERR [panel] Apache config (14398153820.56312900) generation failed: Template_Exception: Can not restart web server: Service /etc/init.d/httpd failed to start
Service /etc/init.d/httpd failed to start

file: /usr/local/psa/admin/plib/Service/Driver/Web/Server/Apache.php
line: 104
code: 0
Can not restart web server: Service /etc/init.d/httpd failed to start
Service /etc/init.d/httpd failed to start


-- Restoring web server configuration... done: Error
FAILED: Failed to fully restore the configuration files.
 
Hi mike_art03a,

please consider to add the ouput of

/etc/init.d/httpd restart

... and consider adding your used operating systen, when reporting issues or asking for suggestions and resolutions.


Please consider as well to use a bootstrapper repair with the command:

/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair

... because this will result in a detailed report in the depending repair - log, which you might post for further investigations.


Please bookmark as well:


... so you can add error - logs and possible depending configuration files for your issue.
 
Howdy UFHH01, I'm running CentOS 6.7, but I just did a full erase and reinstall. So no issues at the moment...

EDIT: Found out what my issue was, Atomic PHP Panda was breaking something apparently. So I removed it and regenerated the vhost files and now it works.
 
Last edited:
Back
Top