Answered

Executions not being picked up by Linux Server

Hello, I am seeing that our executions are not being picked up by our Linux Server; PROOF and all the VMs are currently up, please see screenshot of activemq. please advise what troublehooting actions our OPS group need to do. Thanks

 

 

0
5 comments
Avatar
Rex Feizi

It appears that the worker service is dead. Could you please as your IT to check? They have to do the following command and please send us the output. 

sudo docker ps -a 

 

 

0
Comment actions Permalink
Avatar
Akinpelumia

I will check now

 

0
Comment actions Permalink
Avatar
Akinpelumia

please see output below...

[root@era-iss-33-nprd docker]# docker ps -a

CONTAINER ID   IMAGE                                                              COMMAND                  CREATED      STATUS                            PORTS                                                                                     NAMES

ee69e3753ad8   connector-nexus.subject-7.com:443/s7/grail:0.12.0.20               "/bin/sh -c './start…"   2 days ago   Up 6 seconds (health: starting)   0.0.0.0:8083->8080/tcp                                                                    grail

cd4301db1363   connector-nexus.subject-7.com:443/s7/centos/pg-backup-12.1:0.1.0   "/home/subject7/back…"   2 days ago   Up 2 days (healthy)                                                                                                         postgres-backup

22ebdd737f2b   connector-nexus.subject-7.com:443/s7/proof-worker:9.5.7.2500       "/bin/sh -c './start…"   4 days ago   Exited (1) 2 days ago                                                                                                       worker

b09c94886b66   connector-nexus.subject-7.com:443/s7/ml-worker-svc:1.0.6.3         "/bin/sh -c './start…"   4 days ago   Up 5 hours (unhealthy)            8080/tcp                                                                                  ml-worker

e6a321cd4a35   connector-nexus.subject-7.com:443/s7/proof:9.5.7.2500              "./start_proof.sh"       4 days ago   Up 2 days (healthy)               8009/tcp, 0.0.0.0:8080->8080/tcp                                                          proof

c7a055571ea3   connector-nexus.subject-7.com:443/s7/hera-service:1.2.12.2         "/bin/sh -c './start…"   4 days ago   Up 2 days (healthy)               0.0.0.0:7000->8080/tcp                                                                    hera

e50089a40ee2   connector-nexus.subject-7.com:443/s7/activemq:5.17.0-11.0.14       "/bin/sh -c 'bin/act…"   4 days ago   Up 2 days (healthy)               0.0.0.0:8161->8161/tcp, 1100-1101/tcp, 0.0.0.0:61616->61616/tcp, 0.0.0.0:1101->1099/tcp   activemq

fc6efb7a5b34   connector-nexus.subject-7.com:443/s7/configserver:0.0.11.36        "/bin/sh -c './start…"   4 days ago   Up 2 days (healthy)               0.0.0.0:8888->8080/tcp

0
Comment actions Permalink
Avatar
Akinpelumia

Update -

the status queue is piling up, please help

0
Comment actions Permalink
Avatar
Rex Feizi

After a quick call, it was determined that the issue was an ungraceful shutdown of the docker containers. eRA has many integrations, and also jobs in the queue which makes it even more vital to have a graceful shutdown. As a result proof database was locked, this means there is a record in the table databasechangeloglock. We stopped the proof container and we remove the record in the table and restarted the proof container. 

0
Comment actions Permalink

Please sign in to leave a comment.