E
eryan
Guest
Hi there!
PRODUCT: Plesk panel
VERSION: 10
OPERATING SYSTEM: Debian 5
ARCHITECTURE: x64
PROBLEM DESCRIPTION AND STEPS TO REPRODUCE:
Had a clean install of Plesk 10 working happily, with a couple of domains migrated in from a Plesk 9.5.3 box.
I clicked into the updates, selected 10.2.0 (I think) and it steamed ahead with updates (I was expecting to see some options to review before committing to updating the system).
It stopped, reporting some error which I failed to note.
Attempting to access the control panel through https://IP:8443/ now just shows a blank screen.
Attempting to restart psa show the following:
root:~# /etc/init.d/psa start
Starting psa... done
Starting xinetd service... done
Starting bind9 service... done
Starting mysql service... done
Starting postgresql service... not installed
Starting psa-spamassassin service... not installed
Plesk: Starting Mail Server... failed
Starting mail handlers tmpfs storage
Starting psa... done
Starting drwebd service... failed
I guess this suggests that the failed update broke some things.
Why does it start psa twice?
These two posts seemed relevant:
http://forum.parallels.com/showthread.php?t=106450
http://forum.parallels.com/showthread.php?t=105869
So, as suggested I tried
# /usr/local/psa/bootstrapper/pp10.9.0-bootstrapper/bootstrapper.sh repair
"Errors occured during quotacheck run.
Trying to check for quota support... Quota is not supported by your operating system.
Probably kernel has not compiled in quota support.
WARNING!
During the check for quota support found some problems
Continue..."
Wouldn't have thought the lack of quota support would have caused this, but then again.... ?
ACTUAL RESULT
Unusable control panel with domains down.
EXPECTED RESULT
Updated server.
Any ideas of where to start looking for clues?
Can I start the update process again manually from the command line indeed step back to pre-update?
Any suggestions appreciated.
PRODUCT: Plesk panel
VERSION: 10
OPERATING SYSTEM: Debian 5
ARCHITECTURE: x64
PROBLEM DESCRIPTION AND STEPS TO REPRODUCE:
Had a clean install of Plesk 10 working happily, with a couple of domains migrated in from a Plesk 9.5.3 box.
I clicked into the updates, selected 10.2.0 (I think) and it steamed ahead with updates (I was expecting to see some options to review before committing to updating the system).
It stopped, reporting some error which I failed to note.
Attempting to access the control panel through https://IP:8443/ now just shows a blank screen.
Attempting to restart psa show the following:
root:~# /etc/init.d/psa start
Starting psa... done
Starting xinetd service... done
Starting bind9 service... done
Starting mysql service... done
Starting postgresql service... not installed
Starting psa-spamassassin service... not installed
Plesk: Starting Mail Server... failed
Starting mail handlers tmpfs storage
Starting psa... done
Starting drwebd service... failed
I guess this suggests that the failed update broke some things.
Why does it start psa twice?
These two posts seemed relevant:
http://forum.parallels.com/showthread.php?t=106450
http://forum.parallels.com/showthread.php?t=105869
So, as suggested I tried
# /usr/local/psa/bootstrapper/pp10.9.0-bootstrapper/bootstrapper.sh repair
"Errors occured during quotacheck run.
Trying to check for quota support... Quota is not supported by your operating system.
Probably kernel has not compiled in quota support.
WARNING!
During the check for quota support found some problems
Continue..."
Wouldn't have thought the lack of quota support would have caused this, but then again.... ?
ACTUAL RESULT
Unusable control panel with domains down.
EXPECTED RESULT
Updated server.
Any ideas of where to start looking for clues?
Can I start the update process again manually from the command line indeed step back to pre-update?
Any suggestions appreciated.