IP address conflict: address already in use by an active service

Problem

When a service is opened, modified, or closed, the task fails with an error:

Error: IP address '10.10.10.10' is already in use by an active service
(type: 'ip_on_active_item'; object: '213045'; value: ''; msg: 'IP address '10.10.10.10' is already in use by an active service')

Explanation:

• 10.10.10.10 — the virtual machine (VM) address that the system is trying to assign to the service, but detects that it is already in use;
• 213045 — the ID of the service that the address is currently assigned to;
• type: 'ip_on_active_item' — the error type. Indicates that the address is assigned to a service with the status Active.

The service cannot be opened or closed because BILLmanager considers the IP address to be in use. At the same time, in VMmanager the VM is already active or the address has already been released.

Cause

The IP address allocation logic in BILLmanager has been violated. The VM address was changed or deleted directly in the VMmanager platform. As a result, BILLmanager is unaware of the actual state of the address and continues to hold it for the previous service.

Diagnostics

To confirm the cause:

1. Get the ID of the service that the address is assigned to. To do this, take the value of the object field from the error text.
   

   Example

   (type: 'ip_on_active_item'; object: '213045'; value: ''; msg: 'IP address '10.10.10.10' is already in use by an active service')

   In this example, the service ID is 213045.

2. Check the IP address in the VMmanager interface via BILLmanager:

   1. In BILLmanager, select the required service in the Products/Services section.

   2. Open the menu and click Go. VMmanager opens.

   3. Make sure the VM does not have the conflicting IP address from the error text.
3. Check the service in BILLmanager:
   1. Select the required service.
   2. Click the IP addresses button in the top menu.
   3. Check the list of IP addresses. If the conflicting address is present, the system is holding it for the service even though it no longer belongs to it.
4. Check the IP address using the global search in BILLmanager. The system will show all services it is assigned to. The address must be assigned to only one service. If it is found on two or more — the conflict is confirmed.

If the address is absent in VMmanager but is assigned in BILLmanager to a service with the status Active — this confirms the problem. For more information about service statuses, see List of services.

Solution

To solve the problem, in BILLmanager delete the IP address of the conflicting service:

1. Go to the Products/Services section → select the service type.
2. Select the conflicting service with the ID from the error text.
3. Click the IP addresses button.
4. Select the IP address from the error text.
5. Click Delete.
6. Click Ok to confirm the deletion.
7. Make sure the address is free. To do this, use the global search in the platform to verify that the IP address is no longer assigned anywhere.

8. Restart the task:

   1. Go to the Tools → Tasks section.
   2. Select the required task.
   3. Click the Start button.
9. Check the service status. After the conflict is resolved, the platform synchronizes the statuses and completes the operation.