I think we need to start a thread where everybody can post what by his or her opinion needs to be done to a WBL after you bought it. I configured 5 WBLs so far and I am facing to configure 10 more today; I imagine RackShack's techs do 10 times that, so this thread can be useful for them as well.
OK, things you may want to do:
1) Check date & time. On quite a few machines I had the date was set to Jul 2001! You can set the new date & time while in super-user mode:
CODE
[admin@plesk admin]$ date
Sat Jul 28 09:10:33 EDT 2001
[admin@plesk admin]$ su
Password:
[root@plesk admin]# date -s "Fri Nov 30 05:36:30 CST 2001"
Fri Nov 30 06:36:30 EST 2001
You can use your time zone when setting the time, the system will correctly adjust the time to machine's time zone.
(Of course you can do the same thing with Plesk. Go to Server/System/System Time. The only disadvantage of doing it from Plesk you can't be sure what time zone your server is in).
2) Install/upgrade openssh. If you are going to continue to use shell, install openssh-server (and upgrade openssh-clients to the latest version). By default openssh-server is not installed:
CODE
[root@plesk admin]# rpm -qa | grep -i ssh
openssh-clients-2.5.2p2-5
openssh-2.5.2p2-5
[root@plesk admin]# rpm -e openssh-clients
[root@plesk admin]# rpm -U [url]http://customer.saburovo.com/openssh-2.9p2-8.7.i386.rpm[/url]
[root@plesk admin]# rpm -U [url]http://customer.saburovo.com/openssh-clients-2.9p2-8.7.i386.rpm[/url]
[root@plesk admin]# rpm -U [url]http://customer.saburovo.com/openssh-server-2.9p2-8.7.i386.rpm[/url]
rpm -e openssh-clients is needed to remove openssh-clients installation, otherwise openssh will not upgrade to the latest version because of dependency of openssh-clients on the older version (and you can't upgrade openssh-client before upgrading openssh itself).
After that I had to reboot to make openssh-server work, simple
/etc/init.d/xinetd restart did not do the trick. Once this is done, you can login to your server with ssh instead of telnet.
3) Change server hostname. First with
hostname command check what hostname you have:
CODE
[admin@plesk admin]$ hostname
plesk.rackshack.net
If this is not the name you wish to have, you can change it. There are reports that using
hostname command to change the name creates problems with Plesk:
forum.rackshack.net/showthread.php?threadid=1496
What I did and it worked with Plesk, I just used
/sbin/linuxconf to change the server's name. Go to 'client tasks', then 'host name and IP network devices', then 'host name + domain' and type your desired host name there. Accept the changes, exit from linuxconf, then reboot with
/sbin/reboot.
If you don't have linuxconf, you can install it by executing
rpm -U http://customer.saburovo.com/linuxconf-1.2...4r2-10.i386.rpm as root (su).
Jonathan reports that in his case he also had to change /etc/hosts file to make Apache work with new hostname:
forum.rackshack.net/showthread.php?postid=9504#post9504
4) Upgrade Plesk installation. The list of what's new/fixed in the latest Plesk patch is too long to put here, you can check for yourself:
download1.plesk.com/psa2/build011011.15/psa_v2.0.0_build011011.15_os_RedHat_7.x_i686_patch.txt
Before upgrading, go to Server/System/Statistics and check what version of Plesk you have.
psa_v2.0.0_build010911.01_os_RedHat 7.x means you have Build 010911.01 and the latest one from Plesk is Build 011011.15. You can upgrade from shell:
CODE
[admin@plesk admin]$ wget [url]http://download1.plesk.com/psa2/build011011.15/psa_v2.0.0_build011011.15_os_RedHat_7.x_i686_patch.sh.gz[/url]
[admin@plesk admin]$ gunzip psa_v2.0.0_build011011.15_os_RedHat_7.x_i686_patch.sh.gz
[admin@plesk admin]$ su
Password:
[root@plesk admin]# sh psa_v2.0.0_build011011.15_os_RedHat_7.x_i686_patch.sh
Use it on your own risk! I upgraded 5 servers so far (2 Intels and 3 AMDs), it worked, but I can't guarantee it works for you.
Added on Dec 10: Plesk came with another patch, which fixes security issues with phpMyAdmin. You can install it only after you installed the previous one:
CODE
[admin@customer19 admin]$ wget [url]http://download1.plesk.com/psa2/distribs/psa_v2.0.1_build011129.20_os_RedHat_7.1_i686_patch.tar[/url]
[admin@customer19 admin]$ tar xf psa_v2.0.1_build011129.20_os_RedHat_7.1_i686_patch.tar
[admin@customer19 admin]$ su
Password:
[root@customer19 admin]# sh psa_v2.0.1_build011129.21_os_RedHat_7.1_i686_patch.sh
5) Check/set IP for name-based hosting. Of 15 Plesk servers I have 3 had IP for name-based hosting set incorrectly. As you can see from this post (
forum.rackshack.net/showthread.php?threadid=1353) this is quite common problem.
To correct it please follow the steps suggested in Plesk
documentation, page 171: run
/usr/local/psa/bin/reconfigurator.sh as root (su) from shell, anwer 'Y' to the first question, enter your e-mail address and then just press
to choose defaults for the next questions.
6) Switch off portmap. You may want to switch off portmap as suggested here by winston: forum.rackshack.net/showthread.php?threadid=1526:CODE
[root@plesk admin]# /sbin/service portmap status
portmap (pid 6867) is running...
[root@plesk admin]# /sbin/service portmap stop
Stopping portmapper: [ OK ]
That's it from my side so far; I'll be interested to hear what other people do with WBLs before putting them into production environment.