Search results

FC5 is not officially supported so don't expect your problems to be solved soon. SWsoft has much more supported errors to solve.

Hmm, I don't recall many problems with the update from 7.5.3 to 7.5.4. I would do that first and then try to update to 8.0.0.

psadump has been replaced by pleskbackup see: http://download1.swsoft.com/Plesk/Plesk8.0/Doc/plesk-8-backup-restore-users-guide/index.htm

you need the updater3 to be able to update to v8. And updater3 is provided with the latest 7.5.4 build. You can download the updater from the website and update via the updater by SSH (does the same as via controlpanel)

I have only installed Plesk8 on FC4 and RHEL4. FC4 uses 5.x and RHEL4 uses 4.x

Freebsd might have a different path, check /etc/psa/psa.conf for the HTTPD_VHOSTS_D.

read all about it on http://www.openspf.org/ use their wizard to get the right DNS change make the DNS change in your server read the Pleskdocumentation about the other settings, they even give advice on what you should put there.

you can find this html file at /var/www/vhosts/default/htdocs/

don't worry. this is the standard way of memory usage on a linux machine.

you can't use a wildcard with the remove RPM option. find out what rpms are installed (e.g. rpm -qa|grep psa) and deinstall them with their fullname.

login with SSH go to /etc/ssh/ edit sshd_config find the line "Protocol 2" make sure it doesn't have "1" in it find the line "PermitRootLogin no" make sure it read "no" save the changes. BEFORE you restart SSH make sure you have a user you can login with and from which you can change to...

here it is the servername, the same name as when you run "hostname" on the prompt.

on RHEL4/Plesk8 the vhosts are declared in the following file: /etc/httpd/conf.d/zz010_psa_httpd.conf for domain specific confs check: /var/www/vhosts/domainname.com/conf/

or install manually the selinux-policy-targeted-sources rpm that match your selinux-policy-targeted rpm version.

check /tmp/autoinstall3.log and search for backlist. There are lines that tell you what rpms couldn't be resolved. Resolve them yourself and try the updater again.

IGNORE MY POST changing the PRODUCT_ROOT_D path is not as easy as changing the VHOST path.... :(

I see, it is not the temp directory but the install directory. Then I would edit /etc/psa/psa.conf and move PRODUCT_ROOT_D to a better path.

check /etc/psa/psa.conf for the install path.

do you also have selinux-policy-targeted-sources installed? This rpm is a new dependency, I guess if you install it manually the updater won't need to install selinux-policy-targeted .

let me try again :) the vault applications of these programs are not always up to date.