VDSmanager:Troubleshooting

From ISPWiki

This section provides troubleshooting information for users who are having trouble using and administering VDSmanager.

Contents 1 Internal error "bad VDS ID" 2 Why does traffic usage in ISPmanager and VDSmanager differ? 3 How do I restore disk quota? 4 What is the CPU limit? 5 Calculating traffic in VDSmanager 6 Statistics in VDSmanager is not collected 7 Disk space usage 8 I have deleted the admin user in VDSmanager. What should I do? 9 Transferring a VPS from one disk to another 10 VPS is run and stopped simultaneously (XEN virtualization) 11 Calculating traffic in ISPmanager 12 Unable to create the 8th VPS under Xen 3 13 The pvtdisk directory not found

Internal error "bad VDS ID"

Defining the problem.

When creating a VPS running Centos, the «Internal error bad VDS ID <ID>» error is returned.

Solution. This error may occur, if there exists a directory, which name corresponds to the ID you are creating in в /vz/root/.

Why does traffic usage in ISPmanager and VDSmanager differ?

See: Calculating traffic in VDSmanager and Traffic in ISPmanager

How do I restore disk quota?

Such situation may occur if the mv command was used to transfer a VPS. In order to resolve the problem, follow the instructions below:

• Run vdisk alloc /vs/disk2/192.168.10.1. You will see something like this:

 quota file '/vs/disk2/quota.vds'
 alloc vid 188

• Use the command below to specify the vid for the server's files:

 find /vs/disk2/192.168.10.1 -exec vdisk set{}VID \;

What is the CPU limit?

This is the maximum number of seconds that is used by the central processing unit while executing various processes.

Calculating traffic in VDSmanager

This is total traffic usage (including both incoming and outgoing traffic) collected in VDSmanager. This figure will be used for counting traffic in the billing.

Statistics in VDSmanager is not collected

Locate the following line in the crontab -u root -l command output:

 1 3 * * *     /usr/local/ispmgr/sbin/vdsmoncalc

and make sure that the vdsmon process is up and running.
If not, run it with the following command:

 /usr/local/ispmgr/sbin/vdsmon

Disk space usage

1. To calculate the size of directories, go to VDSmanager -> Main-> Private files (VDS owner) -> Calculate the content of the directory.
2. Enable Logs rotation.
3. If the active log rotation does not work, and the log files continue enlarging, you need to change the hard links (they might have been damaged, as the user deleted the logs).

To do that, use a the domain user privileges to enter the "Logs" module and then exit. ISPmanager -> WWW domains (ISPmanager)-> Select a domain -> "Switch to User panel" -> "World Wide Web" -> WWW logs (User)
More information about logs rotation can be found here.

I have deleted the admin user in VDSmanager. What should I do?

Go to /usr/local/ispmgr/etc/vdsmgr.conf to change the hash in the User admin line into the hash of the password that you can locate in /etc/master.passwd

Transferring a VPS from one disk to another

This information applies to FreeBSD 6.

1. Stop the VPS
2. Create a directory for this VPS on the second disk
3. Allocate a new vid (vdctl alloc /vs/disk2/192.168.10.1) to this VPS
4. Move the files using tar
5. Change the path to the private disk in the VDSmanager configuration file into a new one.
6. Restart VDSmanager (killall vdsmgr)
7. Start the VPS
8. Delete the directory on the first disk.

Use the following commands to transfer a VPS under FreeBSD 8:

mkdir 192.168.10.10.test
vdisk alloc 192.168.10.10.test
vdisk quota 192.168.10.10.test 1000000 4096000
vdisk copypub 192.168.10.10.test /vs/pub/FreeBSD-8-minimal
vdisk copyvds 192.168.10.10 /vs/disk/192.168.10.10.test

In this case you transfer the VPS from /vs/disk/192.168.10.10 to /vs/disk/192.168.10.10.test. Follow the same procedure when transferring to another disk.

VPS is run and stopped simultaneously (XEN virtualization)

In the table you will see both the icon indicating that the VPS is active, and the icon indicating that the VPS was suspended by the administrator. This problem may be caused by the absence of the /etc/xen/auto directory that contains simlinks that are used to define whether a certain VPS was stopped or not.

See also How to restore disk quota?.

Calculating traffic in ISPmanager

WWW-traffic is counted by the mod_ispmgr module. Mail, ftp, etc., traffic is calculated according to the records in their logs. Nginx, MySQL, in case of replication or external usage, ssh and DNS are not counted at all.

Unable to create the 8th VPS under Xen 3

Run out of the loop devices; you need to enlarge their number by specifying correct debian-way into /etc/modprobe.d/xen

options loop max_loop=256

and reboot the server.

The pvtdisk directory not found

Specify PrivateDiskDir /xen/image into vdsmgr.conf