Signals Screening Metastore does not start after a reboot

Sukesh Nischal

November 18, 2022 10:14
Updated

Date Posted: 2021-05-26
Product: TIBCO Spotfire®

Problem:

Signals Screening Metastore does not start after a reboot

Solution:

The Signals Screening metastore is located inside docker containers which run a MongoDB database. Prior to version 2.7.0 of Signals Screening, the docker containers would not automatically restart after the Linux system containing docker is rebooted.

To ensure that the docker images are always started after a reboot, the restart policy for the docker image must be set to "always". This can be done via the following command:

# docker update --restart always $(docker ps -qa)

To check if the restart policy has changed:

# docker inspect --format '{{.HostConfig.RestartPolicy.Name}}' $(docker ps -qa)
always
always

To check if the containers are currently running:

# docker ps -qa

If the docker images is not in status "Up",they can be started again with:

# docker start $(docker ps -qa)

Your Notifications (0)

Signals Screening Metastore does not start after a reboot

Comments

Your Notifications (0)

Related articles