• 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!
  • 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.

Upgraded to 7.5 now plesk does not work

T

tundra96

Guest
I ran the upgrade to 7.5 and this happened at the end:

Trying to stop MySQL server...
WARNING!
During the stop found some small problems(see log file: /tmp/psa_7.5.0_RedHat_9_build75041208.19_upgrade.log)

Continue...


ERROR while trying to stop
Check the error reason(see log file: /tmp/psa_7.5.0_RedHat_9_build75041208.19_upgrade.log), fix and try again

Aborting...

error: %pre(psa-7.5.0-rh9.build75041208.19) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping psa-7.5.0-rh9.build75041208.19
Generate public/private keys pair for server ...
domain_bu: Server's keys pair already exists
domain_bu: Server's keys pair already exists
Server keys generating done
===> Reading /etc/tomcat4/tomcat4.conf ...
===> Updating /etc/psa/psa.conf...
===> Reading /etc/psa/psa.conf ...

<html>
<head> <title>Key Error</title>
<body bgcolor='#ffffff'>
<script> <!--
alert('The key that you are using is invalid for the product version you are running.\nTo purchase a new key go to the Plesk Online Store at www.sw-soft.com or contact\nsales@sw-soft.com.');
//--> </script>
</body> </html>
error: %post(psa-api-rpc-1.3.2-3) scriptlet failed, exit status 255
===> Reading /etc/psa/psa.conf ...
/usr/local/psa/admin/bin/httpsdctl stop: httpd stopped
Stopping Plesk: [ OK ]
uninstall_post.sh

----- end of output -----
===> Autoinstaller: stopped logging at Tue Dec 14 10:04:21 2004

***** end of log file *****



15minuteservers tried to add the new key but they get this error:

user psaadm not found
user psaadm not found


My question is how do I fix this without having to re-image the server ?
 
I had this same problem. Download the rpm version, and install both of the rpms related to the key within the base directory. I had some other issues as well with the database, so I ended up nixing it, and reinstalling it (I don't use 3.23, I use Arts...which I believe are at 4.22).

I ran into the problem with psaadm as well...I believe what I ended up doing was telling it to install the rpm instead of -Uvh, and it ended up creating the psaadm group...and also ended up actually doing an upgrade instead of a reinstall, so I was happy!
 
You must log in or register to reply here.

Similar threads

P
Resolved Upgrade Mariadb 10.3 to 10.6 completes but trying to start MariaDB fails with error "systemctl status mariadb.service" and "journalctl -xe"
Replies
13
Views
3K
PeterK900
P
L
Question Plesk with Mailman3 and Hyperkitty / nginx
Replies
0
Views
644
Larian
L
A
Question Upgrade Almalinux 8 to 9 with Plesk installed
Replies
6
Views
4K
Sebahat.hadzhi
Sebahat.hadzhi
nethubonline
Issue poppassd.socket error when fresh install Plesk
Replies
3
Views
947
AlmaWalters
A
M
Issue Plesk Update 18.0.34 to 18.0.57 Database 'psa' not found
Replies
10
Views
3K
musa.sc
M
Back
Top