Tổng hợp các lổi "Unable to Start Container, Service Container..."

Tổng hợp các lổi Unable to Start Container, Service Container...

I> Lổi can't start Container 101

1. Errors

While starting one of the Container on Windows Node it shown following Error.

C:>vzctl start 101

  Failed to start Virtual Private Server ’101′. Error invoking external utility:

 ERROR:Virtuozzo API function call ‘VZVolumeMount’ failed err = 183
 ERROR:Virtuozzo API function call ‘dq_mount’ failed

 ERROR:Cannot set disk quota for container 101
  

The issue is that Virtuzzso is not able to determine which filesize is correct. It first looks at the file size from the primary *.efd file and also the quota limit that is set in the quotalimit for the VEID. However at times if the *.efd is changed the quotalimit at times will not and vice versa. So far I’ve only ever noticed it in Virtuzzso 3.5.1, but it could also occur in 4.0.


2. Cach xu ly:

Cach 1:
C:>vzcfgt get 101 GUID

{7EAE4A3A-8A27-480C-BEFF-4DA8B90B5FFF}

Or you can open E:/vz/conf/101.conf and look for Following

GUID=”{7EAE4A3A-8A27-480C-BEFF-4DA8B90B5FFF}”

Once you find GUID execute following command to unmount the Container

C:>vzdskctl umount {7EAE4A3A-8A27-480C-BEFF-4DA8B90B5FFF}
SUCCESS

Now, try to start the container
C:>vzctl start 101

Starting container …
Container is mounted
Container was started

C:>vzlist 101

VEID NPROC STATUS IP_ADDR HOSTNAME
101 37 running xxx.xxx.xxx.xx TEST-EITWEB


Cach 2:


The issue is that Virtuzzso is not able to determine which filesize is correct. It first looks at the file size from the primary *.efd file and also the quota limit that is set in the quotalimit for the VEID. However at times if the *.efd is changed the quotalimit at times will not and vice versa. So far I’ve only ever noticed it in Virtuzzso 3.5.1, but it could also occur in 4.0.

The fix is to manually set a quotalimit to the veid. To do this you will need to drop down to a command line. Once you do that you will need to force the change as I’ve done in the example;


Xem: c:\vz\conf\101.conf

copy va paste len sau trong CMD (thay doi lai thong tin cho phu hop voi container cua ban)


C:\vzquota setlimit 101 -B 5684930 –-drive C:\



II> Lổi can't start container 1 (Service container is out of disk space)

C:\Users\Administrator>vzctl mount 1
Virtuozzo API function call 'fsresizer_resize' failed : attempting repair disk
Virtuozzo API function call 'fsresizer_resize' failed
Virtuozzo API function call 'resize' failed
Cannot set disk quota for container 1

C:\Users\Administrator>vzctl start 1
Starting container ...
Virtuozzo API function call 'fsresizer_resize' failed : attempting repair disk
Virtuozzo API function call 'fsresizer_resize' failed
Virtuozzo API function call 'resize' failed
Cannot set disk quota for container 1
Cannot mount disk for container 1

truy cập vào E:\vz\private\1 xem kích thước file: root.efd

truy cập vào E:\vz\Conf\1.conf xem (DiskQuota="5240007168")

giá trị Diskquota phải lớn hơn kích thước file: root.efd (nếu bạn thấy phần "DiskQuota" nhỏ hơn kích thước file: root.efd thì bạn hãy tăng giá trị "DiskQuota" lên)

Tiếp theo bạn sử dụng các lệnh sau để start lại container

C:\Users\Administrator>vzctl mount 1
WARNING: (E:\vz\Private\1\root.efd, {8c6ca97e-4632-4fbe-a5e5-1afe7461d161}) shar
ing violation, trying nonpaged mount
Container is mounted

C:\Users\Administrator>vzctl start 1
Starting container ...
ERROR: Creating port mapping for IP address 123.30.110.4 on port 80 failed. Err
or=10013
ERROR: Port mapping for CT 1 failed. Port 80 is busy for IP address 123.30.110.
4. Ignored.
ERROR: Creating port mapping for IP address 127.0.0.1 on port 80 failed. Error=
10013
ERROR: Port mapping for CT 1 failed. Port 80 is busy for IP address 127.0.0.1.
Ignored.
ERROR: Creating port mapping for IP address 192.168.165.27 on port 80 failed. E
rror=10013
ERROR: Port mapping for CT 1 failed. Port 80 is busy for IP address 192.168.165
.27. Ignored.
ERROR: Creating port mapping for IP address 127.0.0.1 on port 80 failed. Error=
10013
ERROR: Port mapping for CT 1 failed. Port 80 is busy for IP address 127.0.0.1.
Ignored.
Container is mounted
Container was started

C:\Users\Administrator>

III>VZ quota error: lstat (No such file or directory)



If you attempt to start a container after a hardware node crash, you may see an error like this:


Starting Container ...
vzquota : (warning) Incorrect quota shutdown for id 101, recalculating disk usage
vzquota : (error) quota check : lstat `somefile.ext': No such file or directory


Running vzquota on failed for Container 101 [1]


This means that the container’s quota system is crashed. You can restart it simply switching the quota off and on:

vzquota off 101
vzquota on 101

The container should now start up properly.


Restart lai Hardware Node if container can't start.


Nguon: Tonghop