• 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

Error on update to 11.0.9 #35

ip00

Basic Pleskian
I have tried patching Plesk Panel 11.0.9 with updated #35 but got errors. Plesk Panel went unresponsive but after restart it was up and running again.

Whole Installation log is attached, short version:

===> Preparing upgrade
Stopping psa... done
psa is stopped
Stopping psa... done
===> Cumulative database upgrade has been started
===> Upgrade completed.
Traceback (most recent call last):
File "/usr/local/psa/bin/yum_install", line 194, in <module>
main()
File "/usr/local/psa/bin/yum_install", line 189, in main
installer.perform(to_install, opts.remove)
File "/usr/local/psa/bin/yum_install", line 149, in perform
raise Exception("Scriptlet or other non-fatal errors occurred during transaction.")
Exception: Scriptlet or other non-fatal errors occurred during transaction.
~emptyError: Failed to run the Yum utility.
The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please, contact product technical support.

Why did this happen and what steps should we take now?
 

Attachments

  • parallels-installation-log.txt
    5.8 KB · Views: 7
Update #35 doesnot response

When I tried to update #35 in plesk 11.09 I see a message for wait and no more. Now when I go to update option I get a blank page and the page doesnot load, it stay loading without any message or notice.
And I see in psa ax several proc,s

/usr/bin/sw-engine-cgi -c /usr/local/psa/admin/conf/php.ini -d auto_prepend_file=auth.php3 -u psaadm

Where is the fix?
Thanks
 
Need help, please

After tring access update page I found this lines in autoinstaller3.log


Parallels Installer 3.12.1 (built on 2012-07-03 11:48 svn rev. 311941) started at (timezone CET) Mon Feb 4 12:07:58 2013
Command line arguments: /usr/local/psa/admin/bin/autoinstaller --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch current,release,stable --web-interface --with-ssl --disable-browser

SourceUrl: original source url is http://autoinstall.plesk.com/
SourceUrl: fixed url is http://autoinstall.plesk.com/
Try to find rcfile...
Autoinstaller rcfile not found.
Read component settings from /root/.autoinstaller/options.ini
DEBUG: web server PID: 18496
Error: Can't start build-in web-server
Not all packages were installed.
Please try installing packages again later.
Please resolve this issue and try installing the packages again.
If you cannot resolve the issue on your own, contact product technical support for assistance.

I suspect "Can't start build-in web server" is the key... but I don't know how fixit

Thanks
 
EOL - means End Of Live

The only Question is: Who ...
Who has reached EOL ?
plesk or parallels ...

11.0.9 #35 is absolutely destroying all machines, its like sitting on a time bomb you are not able to do anything.
We are working on Centos 6.3

for me its the same like 'death of ensim' ....
 
After tring access update page I found this lines in autoinstaller3.log


Parallels Installer 3.12.1 (built on 2012-07-03 11:48 svn rev. 311941) started at (timezone CET) Mon Feb 4 12:07:58 2013
Command line arguments: /usr/local/psa/admin/bin/autoinstaller --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch current,release,stable --web-interface --with-ssl --disable-browser

SourceUrl: original source url is http://autoinstall.plesk.com/
SourceUrl: fixed url is http://autoinstall.plesk.com/
Try to find rcfile...
Autoinstaller rcfile not found.
Read component settings from /root/.autoinstaller/options.ini
DEBUG: web server PID: 18496
Error: Can't start build-in web-server
Not all packages were installed.
Please try installing packages again later.
Please resolve this issue and try installing the packages again.
If you cannot resolve the issue on your own, contact product technical support for assistance.

I suspect "Can't start build-in web server" is the key... but I don't know how fixit

Thanks

Do you have any additional details from autoinstaller log?
Have you tried manually stop/start sw-cp-server and apache services?
 
I'm silly!!!

I've just fixed the problem. When I saw the error message in log file (/tmp/autoinstaller3.log) , I noticed that the PID mentioned in this message didn't exist, so I look in the ps command result, and ... oh!!! there was an autoinstaller process frozen. I kill him and the error dissapeared.

Thanks
 
Back
Top