• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue help! plesk 12.5 to onyx failed due to out of memory

geegee

New Pleskian
today i ran the upgrade to onyx but it failed.

the log file show stuff like:

Running Transaction Check
Error in PREIN scriptlet in rpm package psa-mod_proxy-2.4.6-centos7.16102516.x86_64
Non-fatal POSTIN scriptlet failure in rpm package plesk-platform-runtime-1.0.1-centos7.892097.16021112.x86_64
Non-fatal POSTIN scriptlet failure in rpm package plesk-rdbmspp-2.0.1-centos7.735641.16021112.x86_64
Non-fatal POSTIN scriptlet failure in rpm package plesk-dovecot-pigeonhole-0.4.16-centos7.16112221.x86_64
Non-fatal POSTIN scriptlet failure in rpm package bitstream-vera-fonts-1.10-7.noarch
Non-fatal POSTIN scriptlet failure in rpm package 1:fail2ban-0.9.2-centos7.16102516.noarch
Non-fatal POSTIN scriptlet failure in rpm package log4cplus-1.1.3-0.4.rc3.el7.x86_64
Error in PREIN scriptlet in rpm package plesk-lmlib-0.2.3-centos7.825.16102518.x86_64
Non-fatal POSTIN scriptlet failure in rpm package libaps-1.0.8-centos7.798670.16071418.x86_64
Non-fatal POSTIN scriptlet failure in rpm package sw-engine-2.20.2-centos7.201612081611.x86_64
Non-fatal POSTIN scriptlet failure in rpm package libbsd-0.6.0-3.el7.x86_64
Non-fatal POSTIN scriptlet failure in rpm package libopendkim-2.11.0-0.1.el7.x86_64
Error in PREIN scriptlet in rpm package sw-cp-server-2.3.0-centos7.16072714.x86_64
Error in PREIN scriptlet in rpm package plesk-base-17.0.17-cos7.build1700161028.14.x86_64
Non-fatal POSTIN scriptlet failure in rpm package psa-pylibplesk-17.0.17-cos7.build1700161208.17.x86_64
Non-fatal POSTIN scriptlet failure in rpm package psa-vhost-17.0.17-cos7.build1700161026.16.noarch
Non-fatal POSTIN scriptlet failure in rpm package psa-libpam-plesk-17.0.17-cos7.build1700161028.14.x86_64
Non-fatal <unknown> scriptlet failure in rpm package psa-libpam-plesk-17.0.17-cos7.build1700161028.14.x86_64
Error in PREIN scriptlet in rpm package psa-phpmyadmin-4.6.6-cos7.build1700170125.17.noarch
Error in PREIN scriptlet in rpm package psa-proftpd-1.3.5b-cos7.build1700161026.16.x86_64
Updating: plesk-dovecot-core-2.2.26.0-centos7.16120817.x86_64 [1/121]
Updating: plesk-release-17.0.17-cos7.build1700161028.14.x86_64 [2/121]
Updating: psa-17.0.17-cos7.build1700161028.14.x86_64 [3/121]
Installing: sw-librrd-1.6.0.1-centos7.16112417.x86_64 [4/121]
error: Couldn't fork %pre(psa-mod_proxy-2.4.6-centos7.16102516.x86_64): Cannot allocate memory

and a lot mre of those "Cannot allocate memory"

i guess my plesk is now in a half upgraded state.

how can i rerun the upgrade... how can i make sure it wont run out of memory?
 
I suggest that you first look into the process list, which processes are consuming your RAM. If they are not vitally important for either Plesk, mail or web, maybe you can stop them before you start the upgrade. Stop or kill the processes so that you have enough RAM available for Plesk.

Afterwards, start the upgrade again, e.g. via console:

1) Pre-upgrade check:
# wget http://autoinstall.plesk.com/PSA_17.5.3/examiners/panel_preupgrade_checker.php
# /usr/local/psa/admin/bin/php panel_preupgrade_checker.php

2) Upgrade:
# wget https://installer.plesk.com/plesk-installer
# chmod +x plesk-installer
# ./plesk-installer --debug
 
i fear that will not work because the plesk instalation thinks it is already updated to the new version.

the installation does not detect the out of memory problems and not executed preinit scripts and all that stuff.
 
Do you fear it or have you tried it?

If Plesk was upgraded, but is not working, you can try
# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation -y
 
Back
Top