SYMPTOMS
Start of the service container fails with the following error:Creating port mapping for IP address 192.168.34.16 on port 80 failed.
Error=10013 Port mapping creation for VE 1 FAILED
Creating port mapping for IP address 127.0.0.1 on port 80 failed.
Error=10013 Port mapping creation for VE 1 FAILED
Unable to create port mappings for VE adapter 'venet0' (VE=1)
Setting up adapter failed, Err=0x00000057 (Container 1,netif0)
Failed to initialize network for container 1
CAUSE
The reason of the problem is that port mapping is not created for Parallels Infrastructure Manager because some application occupies port 80.More often there are IIS services running on Hardware Node that prevent to configure port mapping properly.RESOLUTION
To fix the issue it’s necessary to stop and disable IIS services or any other services or applications which is listening on 80, 4643 ports on the node.Then restart the service container.If IIS services are used and cannot be disabled on the node it’s necessary to change port mapping settings in the service container conf file:
1. Open vz\conf\1.conf file
2. Change 443 and 80 ports to free one
3. Save 1.conf file
4. Start the service container
For example, original record of the port mapping in 1.conf file:
PortMapping="TCP:22-22;TCP:4643-4643;TCP:4646-4646;TCP:8443-8443;TCP:443-4643;TCP:80-4642"
Port mapping is reconfigured here:
PortMapping="TCP:22-22;TCP:4643-4643;TCP:4646-4646;TCP:8443-8443;TCP:8843-4643;TCP:8888-4642"
Note that PIM and PPP will be accessable on ports 8843 or 8888 in this case (http:\\ip_of_the_node:8888).
Keywords: service container port mapping redirect