Resolving a token expiry issue
While creating a new media pod, token may expire, and installation of media server is not completed. The installation logs at /mnt/nblogs/setup-server.logs display an error on the respective media server.
EXIT STATUS 5934: The token has expired.
To resolve a token expiry issue
- Edit the environment server CR using the kubectl edit environment <environment-CR-name> -n <namespace> command.
- In the mediaServer section, reduce the replica count.
For example, if media pod with name xyz-media-2 has the token expired issue and the replica was originally 3, then change the replica count to 2. Save the changes. The extra pods are deleted and statefulset displays new replica count in ready state (2/2).
- Edit the media server CR using the kubectl edit MediaServer <mediaServer-CR-name> -n <namespace> command.
- Increase replica count to original replica count.
As given in the example, change the replica count to 3. This creates additional media pods and reissues the token for newly added media server.