Solution

1. Reconfigure the email distribution settings and restart the mstr_srv pod.
   ADDITIONAL INFORMATION:

   Ignore the following warning message:

   Maximum number of semaphore arrays 128 is low.
2. If the issue is not resolved, complete the following steps to capture debug information and share this information with the Avaya support team:
   1. Log in to the Cluster Control Manager (CCM) console as the customer user.
   2. To switch to the root user, type su and press Enter.
   3. Use the following command to edit the configmap:
      ADDITIONAL INFORMATION: k edit cm -n mstr srv-configmap

      Use i for insert mode.
   4. Use the following command to update the property UPD_DEBUG from False to True:
      ADDITIONAL INFORMATION: UPD_DEBUG: "false" →  UPD_DEBUG: "true"
   5. Note the podname for use in future sessions using the following command:
      ADDITIONAL INFORMATION: export mstrsrvpod=$(k get pods -n mstr -o custom-columns=":metadata.name" | grep mstr-srv)
   6. Restart the mstr_srv pod using the following command:
      ADDITIONAL INFORMATION: k delete pods -n mstr $mstrsrvpod
   7. Note the new podname for use in future sessions using the following command:
      ADDITIONAL INFORMATION: export mstrsrvpod=$(k get pods -n mstr -o custom-columns=":metadata.name" | grep mstr-srv)
   8. Save a copy of the configmap using the following command:
      ADDITIONAL INFORMATION: mkdir /var/avaya/artifactCache/mstr/$mstrsrvpod/
k get cm -n mstr srv-configmap -o yaml > /var/avaya/artifactCache/mstr/$mstrsrvpod/srv-configmap.txt
   9. Copy the mstr_srv log directory to CCM after two to three minutes using the following command:
      ADDITIONAL INFORMATION: export mstrsrvpod=$(k get pods -n mstr -o custom-columns=":metadata.name" | grep mstr-srv)
k cp -n mstr $mstrsrvpod:/mnt/log/mstr/ /var/avaya/artifactCache/mstr/$mstrsrvpod/
   10. Ensure that the logs and configmap are available, and then turn off debug.