Step 1 - Identify Replaced Drive

1. Log in to your server and as root run the following command:
   
   # gmirror list
   
2. This will produce output similar to the following
   
   Geom name: gm0
   State: DEGRADED
   Components: 2
   Balance: round-robin
   Slice: 4096
   Flags: NONE
   GenID: 0
   SyncID: 3
   ID: 3594034660
   Providers:
   1. Name: mirror/gm0
      Mediasize: 159999999488 (149G)
      Sectorsize: 512
      Mode: r2w2e5
   Consumers:
   1. Name: ad4
      Mediasize: 160000000000 (149G)
      Sectorsize: 512
      Mode: r1w1e1
      State: ACTIVE
      Priority: 0
      Flags: DIRTY
      GenID: 0
      SyncID: 3
      ID: 4064102945
   

   In this example we can see the status of the mirror is degraded and the only active drive is 'ad4'.

3. To find out which drives are available and the corresponding device name run the atacontrol list command.
   # atacontrol list
   

   This will produce a list of drives with device names which are connected to your server.

   ATA channel 2:
       Master:  ad4 <WDC WD1602ABKS-18N8A0/02.03B04> SATA revision 2.x
       Slave:       no device present
   ATA channel 3:
       Master:  ad6 <WDC WD2502ABYS-02B7A0/02.03B03> SATA revision 2.x
       Slave:       no device present
   

   From this we can see that device '*ad6*' is the device name of the new drive we can use to rebuild the mirror. You should already be aware of the device name from alerts generated by your server when the drive failed; the replacement drive will show up with the same device name.

Step 2 - Rebuild Mirror

1. Now that we have verified device name of the new drive we can easily rebuild the array using the following commands:
   # gmirror forget gm0
   # gmirror insert gm0 <device>
   

   Where <device> is the device name of the new drive we determined above. In the example above <device> would be 'ad6'.

2. To verify the drive has been added to the mirror and the mirror is being rebuild run the '*gmirror list'* command.
   # gmirror list
   Geom name: gm0
   State: DEGRADED
   Components: 2
   Balance: round-robin
   Slice: 4096
   Flags: NONE
   GenID: 0
   SyncID: 3
   ID: 3594034660
   Providers:
   1. Name: mirror/gm0
      Mediasize: 159999999488 (149G)
      Sectorsize: 512
      Mode: r3w2e5
   Consumers:
   1. Name: ad4
      Mediasize: 160000000000 (149G)
      Sectorsize: 512
      Mode: r1w1e1
      State: ACTIVE
      Priority: 0
      Flags: NONE
      GenID: 0
      SyncID: 3
      ID: 4064102945
   2. Name: ad6
      Mediasize: 251059544064 (234G)
      Sectorsize: 512
      Mode: r1w1e1
      State: SYNCHRONIZING
      Priority: 0
      Flags: DIRTY, SYNCHRONIZING
      GenID: 0
      SyncID: 3
      Synchronized: 3%
      ID: 2247886846
   

   We can see here the new drive has been added and the mirror is being rebuilt (3% complete). Rebuild times can take anywhere from 20 minutes to a few hours depending on the size of the drives and the amount of application I/O on your system.
   
   The first few lines show that overall state of the mirror, once the state changes from 'DEGRADED' to 'COMPLETE' the rebuild is complete.
   

When attempting to use the IBM Remote Control feature of the RSA you receive a Java error preventing you from logging in.

Resolution

This issue is due to a bug with the RSA that only affects customers with the latests versions of Java greater than 1.6.0_11. The resolution is to downgrade your Java version to 1.6.0_11 or lower

Cause

The Virtuozzo Control Panel firewall and service features are based on the CentOS 5 template and as a result do not work correctly in other VPS Linux distributions such as Debian or Ubuntu..

Solution

There is no solution to this as these Control Panel tools will not work in non CentOS VPSs. You will need to use the command line tools to manage these components of your VPS.

When configuring your email application for email accounts you have created in the Messaging Administrator or in Plesk Control Panel, the following settings should be used:

POP3 / IMAP / SMTP Server Settings

Incoming POP Server	mail.<yourdomain>
Outgoing SMTP Server	mail.<yourdomain>
Login / Account Name	<youraddress>@<yourdomain>

Need help? View our helpful flash tutorials that guide you through the process of adding an email account for seven of the most common email applications. View the tutorials here

Important Information About Sending Email Through Net24

1. Because you will be connecting from an untrusted IP network it is necessary to enable SMTP Authentication in your email application. Alternatively you can also send mail using your ISP SMTP server which will not require authentication.
2. If you encounter problems connecting to our SMTP server your connection to our server may be blocked by your ISP. Many ISPs are blocking port 25 which is used to send email in an attempt to reduce the spread of viruses and the distribution of spam. In this situation please configure your email application to use the port 10025 for outgoing SMTP connections.

Accessing WebMail Services

You can access your email using any standard web browser by visiting webmail.<yourdomain.co.nz>

You may choose between two webmail interfaces, Webmail Standard Edition and Webmail Corporate Edition. Standard Edition provides a fast non-graphical interface to your email and Corporate Edition is designed to provide the same familiar interface as your standard desktop email client.

TLS/SSL Connections

Net24 supports TLS/SSL security, which provides secure transport of user credentials and messages over the Internet. If you wish to use TLS/SSL we recommend you use the official name of systems to avoid certificate errors.

The official hostname for POP/IMAP/SMTP is: MP.MAIL.ISX.NET.NZ.

DNS Settings

If a 3rd party is managing the DNS services for your domain name, please ensure the following zone records are created:

  domain.co.nz. IN MX 10 mx.mail.isx.net.nz.
  mail.domain.co.nz. IN CNAME mp.mail.isx.net.nz.
  webmail.domain.co.nz IN CNAME wm.mail.isx.net.nz.
  manager.domain.co.nz IN CNAME manager.isx.net.nz.

Cause

The RSA Remote Console uses UDP to transfer screen information to the client. If you are behind a firewall these packets may be blocked.

Resolution

Open up access on your firewall to allow the required UDP packets to reach your client machine. The table below shows the ports and protocols used for remote console access.

Protocol	Source Address	Source Port	Destination Address	Destination Port
UDP	<RSA IP Address>	2000	<Client Computer Accessing RSA>	> 1024

When you use the Remote Supervisor Adapter's Remote Console, key presses are repeated multiple times on the server making it difficult or impossible to use.

Cause

This problem can occur if you are using the Remote Supervisor Adapter's Remote Console over a slow connection.

Resolution

Disable the key repeat function in the Operating System. For Windows follow the instructions below:

1. Run '*Start > Programs > Accessories > Accessibility > Accessibility Wizard*'.
2. Navigate your way through the wizard until you reach the page that contains the option '*I have difficulty using the keyboard or mouse*' and then check this option.
3. On the BounceKeys page select '*Yes*'.
4. The keystroke repeat rate of 0.50 seconds should be sufficient to resolve the issue.

• What is the maximum message size I can receive or send?
• How many recipients can I send to in one message?

Custom error pages allow you to show a customised page for all web server errors, but most commonly, 404 Not Found and 500 Internal Errors. This allows you to show a more user friendly or branded page when a page is not found or in the event of 500 Internal Errors, capture or notify the webmaster so that the errors can be corrected.

This article will show you how to enable custom error pages in Plesk under Unix. There is a different method for Windows hosted accounts. See How To Enable Custom Error Pages In Plesk - Windows

Methods For Enabling Custom Error Pages

There are two methods for using custom error pages for Unix hosted accounts.

If you only wish to modify the default HTML error pages follow the first method using Plesk. If you wish to redirect common error pages to a PHP page you will need to use the second method which uses a .htaccess file.

Enabling Custom Error Pages in Plesk - Unix

1. Turn on support for custom errors documents in Plesk
   1. Once logged into Plesk, click on your domain name and then click the Setup icon.
   2. Select the Custom Error Documents check box.
   3. Click OK
2. Login via FTP and edit the custom HTML error pages within the /error_docs directory

Enabling Custom Error Pages With a .htaccess File

Create a .htaccess file with a text editor and for each error you want to redirect, add the following directive to the .htaccess file:

ErrorDocument 000 /path/to/file

where 000 is the error number e.g. 400, 404, 500) and /path/to/file is the location of your new error document. For example, if you have created an error page at http://www.example.com/errors/404.php then set the path as /errors/404.php

Example:

ErrorDocument 404 /errors/404.php

Do this for each custom error document, example:

ErrorDocument 400 /errors/bad-request.php
ErrorDocument 401 /errors/unauthorised.php
ErrorDocument 403 /errors/forbidden.php

Save and upload the .htaccess file to the document root of your site or to any folders where you need to change the default document that is loaded when the folder is accessed.

While attempting to restore your database using MyLittle Backup you receive the following error:

The media set has 2 media families but only 1 are provided. All members must be provided.

Cause

This error is due to your backup being divided into more than one part at the time of creating your initial backup file. The backup will need to be repeated so that it is contained in one file only.

In the example screenshot below you will see that there are two paths listed for the backup destination, which will create a backup over two files.

Resolution

Remove one path from the backup destination so that only one .bak file is created and then restore this file using MyLittleBackup.

When connecting to IIS7 using FTP you get the following error.

530 Valid Hostname is expected

Reason

When you set up name-based FTP services IIS7 wants the sitename defined with the username so that IIS7 can associate the username with the site they wish to log in to.

Solution A

If you want more than one FTP site on your VPS you will need to :

Configure all FTP clients such that :
Host: Mysite.com
User: Mysite.com|Username

Note the "|" that seperates the Sitename and the Username.

Solution B

If you only have one FTP site remove the "Host Name" defined in the "Bindings" property of the FTP site.