Some types of DCImanager failures can be resolved by restarting the platform. For example, if there are problems with networks or Docker containers, or automatic platform update does not start, etc. The restart order depends on whether the location is configured on the same server as the platform or on a separate one.
Location on the same server as the platform
To restart DCImanager 6:
- Connect to the server with the platform via SSH.
-
Restart the platform:
dci restart
-
If the BMC proxy module is enabled on the location, restart the ipmi_proxy_service:
docker-compose -f /opt/ispsystem/ipmi_proxy_service/etc/docker/ipmi_proxy_v2.yml restart
-
Restart the location:
docker-compose -f /opt/ispsystem/dci/etc/location.yaml restart
Location on a separate server
To restart DCImanager 6:
- Connect to the server with the platform and the location server via SSH.
-
Run the commands:
-
On the server with the platform, restart the platform:
dci restart
-
On the location server, run:
-
Restart the ipmi_proxy_service if the BMC proxy module is enabled:
docker-compose -f /opt/ispsystem/ipmi_proxy_service/etc/docker/ipmi_proxy_v2.yml restart
-
Restart the location:
docker-compose -f /opt/ispsystem/dci/etc/location.yaml restart
-
-