NetBackup messaging queue broker take more time to start
This issue is due to service taking more time to start.
To resolve this issue, perform the following steps
- Exec into the respective Primary Server pod using the following command:
kubectl exec -it <pod-name> -n <namespace> -- /bin/bash
- Check the nbmqbroker service logs which are in
/usr/openv/mqbroker/logs/folder.If the value of checking service start status count: is more than the 75 then nbmqbroker would take more time to start.
- Stop the nbmqbroker service using the following command:
/usr/openv/mqbroker/bin/nbmqbroker stop
- Open the
/usr/openv/mqbroker/bin/nbmqbrokerfile. - Increase the value of total_time and sleep_duration and save the file.
- Start the mqbroker service using the following command:
/usr/openv/mqbroker/bin/nbmqbroker start
If the Primary Server pod gets restarted then the user must perform the same above steps to increase the values of total_time and sleep_duration, as these values will not get persisted after pod restart.