Plesk stops working after upgrade, help please

General Discussion of atomic repo and development projects.

Ask for help here with anything else not covered by other forums.
xbaez

Plesk stops working after upgrade, help please

Unread post by xbaez »

The autoinstaller for plesk has never worked, so I tried this site:
the following packages were updated:

psa-bu-7.5.1-rhel3.build75041216.14
psa-api-cli-7.5.1-rhel3.build75041216.14
psa-locale-base-en-US-7.5.1-rhel3.build75041216.14
psa-api-common-7.5.1-rhel3.build75041216.14
psa-key-7.5-rhel3.build75041216.14

Check this error when I try to start plesk
# service psa start
===> Reading /etc/psa/psa.conf ...
service imap does not support chkconfig
PHP Warning: Unable to define user id for "psaadm": Success in Unknown on line 0
PHP Fatal error: Unable to start psasem module in Unknown on line 0
/usr/local/psa/admin/bin/httpsdctl start: httpd could not be started


Any suggestions Sam?
xbaez

The worst thing is...

Unread post by xbaez »

that I can't uninstall the psa-api-rpc file package:

yum remove psa-api-rpc
Gathering header information file(s) from server(s)
Server: Atomic Rocket Turtle - 3ES - Atomic PSA-Compatible RPMS
Server: Atomic Rocket Turtle - 3ES - SW-Soft PSA 7.1 RPMS
Server: Atomic Rocket Turtle - 3ES - SW-Soft PSA 7.5 RPMS
Server: Atomic Rocket Turtle - 3ES - OS Update RPMS mirror
Finding updated packages
Downloading needed headers
Resolving dependencies
Dependencies resolved
I will do the following:
[erase: psa-api-rpc 1.3.2-3.1.i586]
Is this ok [y/N]: y
Downloading Packages
Running test transaction:
Test transaction complete, Success!
PHP Warning: Unable to define user id for "psaadm": Success in Unknown on line 0
PHP Fatal error: Unable to start psasem module in Unknown on line 0
error: %preun(psa-api-rpc-1.3.2-3.1) scriptlet failed, exit status 254
Erased: psa-api-rpc 1.3.2-3.1.i586
[/i]
scott
Atomicorp Staff - Site Admin
Atomicorp Staff - Site Admin
Posts: 8355
Joined: Wed Dec 31, 1969 8:00 pm
Location: earth
Contact:

Unread post by scott »

thats a pretty wierd error there, Ive never seen that before. What happened when you tried to install with the autoinstaller
Post Reply