vmkfstools -X new_sizevmfs_name:disk_name

cpanelguide.net/addon.php

Basically it allows you to run mutiple websites off your single account/domain name. Brilliant idea, if it was done properly. When you add an Addon Domain, it creates a folder in your main sites public_html folder, typically its name is that of your domain name. Lets just say that my customer has two domain names, the main one bob.com and an additional one jill.com

The customer creates jill.com as an Addon Domain, all is swell. Until they find out they can access the addon domain at “jill.com” and “bob.com/jill.com”. Why is this bad? Well google will see it as duplicate conent and your site will either never get indexed or have funky SEO results.

How do you fix it? Change the root directory to not be placed inside the public_html folder and viola, no duplicate content. Also make sure to edit the subdomain to forward to the correct URL as well or more duplicate content will exist.

“[ERROR] The Client Access server role is already installed on this computer.”

For each rolle that I had installed on said server. I didn’t know why it was doing this. I suspected that ESXi left some reminents of the Exchange Install and that VMWare ESXi Snapshots weren’t really “Snapshots”. So I did a full re-install and still was receiving the above message.

I think starting doing some research and found out that there is Active Directory information that states what roles a server has, and the setup checks this before installing. All I had to do was delete this information. Here is the steps, that I found on the web.

1. Click Start, point to Programs, point to Windows 2000 Support
Tools, point to Tools, and then click ADSI Edit.
2. Expand each of the following items:
Configuration Container
CN=3DConfiguration, DC=3DDomain_Name,DC=3Dcom
CN=3DServices
CN=3DMicrosoft Exchange
CN=3DYour_Organization_Name
CN=3DAdministrative Groups
CN=3DYour_Administrative_Group_Name_Or_Exchange5.5_Site_Name
CN=3DServers

Note In this procedure, Domain_Name is a placeholder for the name of
your domain, Your_Organization_Name is a placeholder for the name of
your organization, and
Your_Administrative_Group_Name_Or_Exchange5.5_Site_Name is a
placeholder for the name of your administrative group or Exchange 5.5
site.
3. Right-click the Exchange 2003 server object, and then click
Delete.
4. Click Yes in every adsiedit dialog box that prompts you to confirm
the deletion.

Once I completed this, I was able to install Exchange 2007 again. I had to process this on the Domain Controller which is a separate machine.

Once you have SSH access, you just need to create a Virtual Machine Directory in your DataStore which should be located in “/vmfs/volumes/datastore1/”. Type the following.

mkdir /vmfs/volumes/datastore1/NewVM

You will then need to run the “vmkfstools” to clone the Virtual Machine.

/vmfs/volumes/4991bc35-5ced5b0c-a99e-00221953f98d # /sbin/vmkfstools -i /vmfs/volumes/datastore1/exch01/exch01.vmdk /vmfs/volumes/datastore1/newvmware/newvmware.vmdk
Destination disk format: VMFS thick
Cloning disk ‘/vmfs/volumes/datastore1/exch01/exch01.vmdk’…
Clone: 100% done.
/vmfs/volumes/4991bc35-5ced5b0c-a99e-00221953f98d #

The Virtual Machine should now be cloned.

Some may ask how you now create a new Virtual Machine based on this clone. You simply do the following.

1. Make a new VM on this server
2. Choose ‘Custom’ and when you get to the ‘Select a Disk’ portion of creation you will browse the datastore and select this newly renamed vmdk file.

Viola! Done!

I was trying to get access to VMWare ESXi as this is the only way to access the images for each Virtual Machine as snapshots seem to have messed up an Exchange install. I will go into more depth below. But first, the following steps are required to open up SSH access to your ESXi Machine.

ESXi 3.5 does ship with the ability to run SSH, but this is disabled by default (and is not supported). If you just need to access the console of ESXi, then you only need to perform steps 1 – 3.

1) At the console of the ESXi host, press ALT-F1 to access the console window.
2) Enter unsupported in the console and then press Enter. You will not see the text you type in.
3) If you typed in unsupported correctly, you will see the Tech Support Mode warning and a password prompt. Enter the password for the root login.
4) You should then see the prompt of ~ #. Edit the file inetd.conf (enter the command vi /etc/inetd.conf).
5) Find the line that begins with #ssh and remove the #. Then save the file. If you’re new to using vi, then move the cursor down to #ssh line and then press the Insert key. Move the cursor over one space and then hit backspace to delete the #. Then press ESC and type in :wq to save the file and exit vi. If you make a mistake, you can press the ESC key and then type it :q! to quit vi without saving the file.
6) Once you’ve closed the vi editor, run the command /sbin/services.sh restart to restart the management services. You’ll now be able to connect to the ESXi host with a SSH client.

Update for ESXi 3.5 Update 2 – With Update 2 the service.sh command no longer restarts the inetd process which enables SSH access. You can either restart your host or run ps | grep inetd to determine the process ID for the inetd process. The output of the command will be something like 1299 1299 busybox      inetd, and the process ID is 1299. Then run kill -HUP <process_id> (kill -HUP 1299 in this example) and you’ll then be able to access the host via SSH.

Credit to the above steps go out to vm-help.com and you can read the above steps and comments on thier site.

The main reason why I required this, is the snapshots provided with VMWare work great. But I had to re-install exchange becuase of a configuration change that couldn’t be reversed. I had created a Active Directory Child Domain on an existing Domain, and then had setup Exchange 2007. But in the long run, this wasn’t required, instead I wanted to use our existing Domain. Removing the new Child Domain and deleting the Domain Controller/Demoting woudl have caused issues with Exchange.

So I decided to use ESXi Snapshot Manager to revert back to when I created a Snapshot after install Windows Server 2003, as it was a clean install. Once I did then and then went on to install Exchange again. Exchange Setup had complained that the server’s role was already installed and setup. Which was not the case, so I don’t know what really happened, either way. I’m going to make backups through SSH from now on.

www.darcynorman.net/2007/05/15/how-to-migrate-from-drupal-5-to-wordpress-2/

At the moment I have posts and permalinks working. So I didn’t take a big SEO hit. I am now working on comments. I won’t be migrating the categories over, I’m going to create new categories and go through my articles and re-tag and categorize them.

Cheers!

(4)Interrupted system call: FastCGI: comm with server “php-fastcgi.fcgi” aborted: select() failed

After doing some reasearch I stumbled upon the following patch.

groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/3de22bc415d3da02?pli=1

Will test this out and see if it has resolved some of the problems.
*UPDATE* The following Debian Lenny and Etch packages complied by a non Debian Package Maintainer are available.

isp-control.net/forum/thread-5462.html

Upgrading libapache2-mod-fastcgi from 2.4.6 to 2.4.7 seems to have rectified the issue.

Cheers!

*UPDATE*  Heres the link to the FastCGI developers site talking about the bug. www.fastcgi.com/archives/fastcgi-developers/2009-January/000156.html