search cancel

jarvis services appear to start, but fail within a few seconds

book

Article ID: 203539

calendar_today

Updated On:

Products

CA Virtual Privilege Manager CA Privileged Identity Management Endpoint (PIM)

Issue/Introduction

jarvis services appear to start, but fail within a few seconds.

systemctl status ca_* shows them in red/failed status, even though they show as active (running).

Environment

Release : 14.0

Component : JASPERSOFT REPORTS FOR PAM SERVER CONTROL

Resolution

Jarvis services need to be started in a specific order:

ca_elasticsearch
ca_zookeeper
ca_kafka
ca_schema-registry
ca_indexer-ingest
ca_indexer-update
ca_verifier-ingest
ca_verifier-update
ca_esutils ca_tomcat

It is also a good idea to wait a few seconds after each service is started to give them time to start properly.

Additional Information

See the attached jarvisctl.sh.tar which contains jarvisctl.sh. This script starts (and stops, and give the status of) the jarvis services in the correct order, waiting 10 seconds between each one.

Attachments

1605667947703__jarvisctl.sh.tar get_app