Kaki Supper

= See the comparisons and Try the FREE Demo =

I’ve successfully upgraded my blog from old version WP 2.6.x to 2.8 today.  The following is the steps that i sorted out:

1. Log in “wp-admin” to disable all existing Plugins (Important step)
2. Backup the mySQL database
3. Rename the existing blog directory (Backup the source)
4. Recreate the blog directory & Install the new version WordPress (can be easily uses Cpanel Fantastico)
5. Rename the new “wp-content” directory
6. Replace it by Copy back the original “wp-content” directory from backup source
7. Restore/Import the mySQL database into the new DB (Normally Fantastico will auto create a new DB)
8. Browse “wp-admin”, the system will prompt to click a button for upgrading the blog DB
9. Log in “wp-admin” to check the contents & settings
10. Some older version Plugins might need to be remove or reinstall (Find the compatible version before activate)
11. Grant the write permission to the path:  wp-content/uploads/
12. Edit “wp-config.php” to delete “utf8” at DB_CHARSET  (To make the encoding loads well)

NOTE:  Always be reminded to keep a copy of full backup before make any changes.

This is a faster way to transfer/move a cpanel account from one server to another server:

Assumed the destination IP = xxx.xxx.xxx.xxx

1. SSH to Source server
2. /scripts/pkgacct
3. Once the backup complete, you will see “md5 checksum ok”
4. cd /home
5. scp -P cpmove-cpanelusername.tar.gz root@xxx.xxx.xxx.xxx:/home
6. Just follow the instruction, input the root password
7. Then wait for it to complete with 100%
8. Log in WHM of the Destination server, Restore Full Backup/cpmove
9. Enter the cpanel username to restore
10. At DNS zone editor, redirect the domains including Addons and parked domains’s IP from the Source server to Destination server IP

Sometimes spamd child process for a particular user can cause server high loads.  This is reported as a bug with spamassassin, refer to:

http://www.cpanelconfig.com/how-to/spamassasin-spamd-using-100-cpu/

To fix the issue on the cPanel servers, try run the following script as root:

/scripts/autorepair spamd_dbm_fix