User Tools

Site Tools


duplicate_server_entries_in_controller

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
duplicate_server_entries_in_controller [2020/10/08 21:46] – external edit 127.0.0.1duplicate_server_entries_in_controller [2023/03/09 22:35] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Duplicate Server Entries in Controller ====== ====== Duplicate Server Entries in Controller ======
 <color #db5f0b>May 2017</color> <color #db5f0b>May 2017</color>
 +\\ 
 +<color #ff7f27>Updated Oct 2021</color>
 \\  \\ 
 \\  \\ 
Line 26: Line 28:
     ipaddress=ipaddress of the controller     ipaddress=ipaddress of the controller
     servername=the name of the failed server listed in controller     servername=the name of the failed server listed in controller
 +
 +For orchestrated deployments, this will not work, you have to use the following:
 +\\ 
 +\\ 
 +Login to the node with MDT installed (normally the first HA node)
 +\\ 
 +\\ 
 +Execute the following:
 +    kubectl -n mediakind get pods (to find exact name of unified-ui pod)
 +We are looking for the name of the unified-ui pod.
 +\\ 
 +\\ 
 +On my test system it was called unified-ui-576c87cbbd-vd42h. Your system will be different.
 +\\ 
 +\\ 
 +Now execute the following, using your unified-ui name to edit the pod, ui is the name of the internal pod.
 +\\ 
 +\\ 
 +    kubectl -n mediakind exec -it unified-ui-576c87cbbd-vd42h -c ui /bin/sh
 +\\ 
 +\\ 
 +Execute the following to list the servers:
 +\\ 
 +\\ 
 +    curl api-gateway:8080/api/servers
 +Now you can delete the server using the following:
 \\  \\ 
 \\  \\ 
 +    curl -X DELETE api-gateway:8080/api/servers/sky-01
  
 +(replace sky-01 with the server name you wish to delete)
duplicate_server_entries_in_controller.1602189988.txt.gz · Last modified: 2023/03/09 22:35 (external edit)