I need to evaluate in all linux (RHE 5,6,7,8) the status of the “resilient” service.
All the queries give me wrong data:
Q: service "resilient.service"
A: “resilient.service” “resilient.sh” “Stopped”
Q: exists running service "resilient"
A: False
When I do a “systemctl status resilient”:
systemctl status resilient
● resilient.service - Resilient Service application
Loaded: loaded (/usr/lib/systemd/system/resilient.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2022-05-28 19:27:52 -03; 1 month 28 days ago
Process: 12907 ExecStart=/usr/share/co3/bin/resilient.sh start (code=exited, status=0/SUCCESS)
Partners, any suggestions?
You may want to try something like:
exists names whose (it contains “resilient”) of processes
Let me know if that works!
1 Like
I had already tried this and the same thing happens to me, it returns False
Q: exists names whose (it contains “resilient”) of processes
A: False
T: 35947
When you do a ps, how does the resilient process present itself?
Excuse me, I did not understand the query… could it be this?
[root@serverres bin]# ps
PID TTY TIME CMD
26990 pts/0 00:00:00 sudo
27016 pts/0 00:00:00 su
27017 pts/0 00:00:00 bash
32647 pts/0 00:00:00 ps
Ah ok. So to get this you will need to run the following command:
ps auxw | grep -e resilient
This is results:
[root@serverres ~]# ps auxw | grep -e resilient
resadmin 4277 0.3 0.0 1110024 53980 ? Sl 10:48 1:10 /opt/app-root/bin/python3.9 /opt/app-root/bin/resilient-circuits run
resadmin 6143 0.4 0.0 1110476 57252 ? Sl May27 411:45 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
resadmin 6914 0.4 0.0 1104116 44336 ? Sl May27 400:08 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
resadmin 7198 0.4 0.0 1124888 53164 ? Sl May27 399:19 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
resadmin 7331 0.4 0.0 1104104 46176 ? Sl May27 404:46 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
resadmin 7688 0.4 0.0 1106328 42380 ? Sl May27 404:38 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
resadmin 7722 0.4 0.1 1169288 80676 ? Sl May27 437:04 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
root 8925 0.0 0.0 10756 224 ? Ss May27 0:00 resilient-messaging -procname resilient-messaging -cp /usr/share/java/resilient/resilient-messaging.jar -java-home /usr/lib/jvm/ibm-jdk-8 -user res-messaging -outfile /var/log/resilient-messaging/resilient-messaging.out -errfile /var/log/resilient-messaging/resilient-messaging.err -pidfile /var/run/resilient-messaging.pid -keepstdin -wait 120 -Djava.awt.headless=true -Dco3.log.dir=/var/log/resilient-messaging -Dlogback.configurationFile=/usr/share/res-messaging/logback-messaging.xml com.resilient.messaging.MessagingServerDaemon
res-mes+ 8926 0.3 0.4 2261780 309940 ? SLl May27 298:20 resilient-messaging -procname resilient-messaging -cp /usr/share/java/resilient/resilient-messaging.jar -java-home /usr/lib/jvm/ibm-jdk-8 -user res-messaging -outfile /var/log/resilient-messaging/resilient-messaging.out -errfile /var/log/resilient-messaging/resilient-messaging.err -pidfile /var/run/resilient-messaging.pid -keepstdin -wait 120 -Djava.awt.headless=true -Dco3.log.dir=/var/log/resilient-messaging -Dlogback.configurationFile=/usr/share/res-messaging/logback-messaging.xml com.resilient.messaging.MessagingServerDaemon
res-app+ 10172 0.6 0.3 2760204 260760 ? SLl May27 591:42 /usr/lib/jvm/ibm-jdk-8/bin/java -Xmx1024M -Djava.awt.headless=true -Dmanager.log.dir=/var/log/resilient-app-manager -jar /usr/share/java/resilient/resilient-app-manager.jar
root 10272 0.0 0.0 10756 236 ? Ss May27 0:00 resilient-email -procname resilient-email -cp /usr/share/java/resilient/resilient-email.jar -java-home /usr/lib/jvm/ibm-jdk-8 -user res-email -outfile /var/log/resilient-email/resilient-email.out -errfile /var/log/resilient-email/resilient-email.err -pidfile /var/run/resilient-email.pid -keepstdin -wait 120 -Djava.awt.headless=true -Dco3.log.dir=/var/log/resilient-email -Xmx1024m com.resilient.email.EmailServerDaemon
res-ema+ 10273 1.2 3.7 4936484 2445888 ? SLl May27 1141:17 resilient-email -procname resilient-email -cp /usr/share/java/resilient/resilient-email.jar -java-home /usr/lib/jvm/ibm-jdk-8 -user res-email -outfile /var/log/resilient-email/resilient-email.out -errfile /var/log/resilient-email/resilient-email.err -pidfile /var/run/resilient-email.pid -keepstdin -wait 120 -Djava.awt.headless=true -Dco3.log.dir=/var/log/resilient-email -Xmx1024m com.resilient.email.EmailServerDaemon
resadmin 11793 0.3 0.0 1115096 55288 ? Sl Jun15 200:47 /opt/app-root/bin/python3.9 /opt/app-root/bin/resilient-circuits run
root 12619 0.0 0.0 10756 228 ? Ss May28 0:00 resilient-scripting -procname resilient-scripting -cp /usr/share/java/resilient/resilient-scripting.jar -java-home /usr/lib/jvm/ibm-jdk-8 -user res-scripting -outfile /var/log/resilient-scripting/resilient-scripting.out -errfile /var/log/resilient-scripting/resilient-scripting.err -pidfile /var/run/resilient-scripting.pid -keepstdin -wait 120 -Djava.security.manager=com.resilient.scripting.security.ResilientSecurityManager -javaagent:/usr/share/java/resilient/resilient-scripting-agent.jar -Djava.awt.headless=true -Dco3.log.dir=/var/log/resilient-scripting -Dlogback.configurationFile=/usr/share/res-scripting/logback-scripting.xml com.resilient.scripting.ScriptingServerDaemon
res-scr+ 12620 3.4 1.2 2577680 846300 ? SLl May28 2964:08 resilient-scripting -procname resilient-scripting -cp /usr/share/java/resilient/resilient-scripting.jar -java-home /usr/lib/jvm/ibm-jdk-8 -user res-scripting -outfile /var/log/resilient-scripting/resilient-scripting.out -errfile /var/log/resilient-scripting/resilient-scripting.err -pidfile /var/run/resilient-scripting.pid -keepstdin -wait 120 -Djava.security.manager=com.resilient.scripting.security.ResilientSecurityManager -javaagent:/usr/share/java resilient/resilient-scripting-agent.jar -Djava.awt.headless=true -Dco3.log.dir=/var/log/resilient-scripting -Dlogback.configurationFile=/usr/share/res-scripting/logback-scripting.xml com.resilient.scripting.ScriptingServerDaemon
root 12935 0.0 0.0 10756 240 ? Ss May28 0:00 resilient -procname resilient -home /usr/lib/jvm/ibm-jdk-8 -classpath /usr/share/resilient-tomcat/bin/bootstrap.jar:/usr/share/resilient-tomcat/bin/tomcat-juli.jar -outfile /usr/share/co3/logs/catalina.out -errfile /usr/share/co3/logs/catalina.err -pidfile /var/run/resilient.pid -cwd /usr/share/co3 -user co3 -Dcatalina.home=/usr/share/resilient-tomcat -Dcatalina.base=/usr/share/co3 -Dorg.jboss.logging.provider=slf4j -Dlogback.configurationFile=/usr/share/co3/conf/logback.xml -Djava.awt.headless=true -Dco3.log.dir=/usr/share/co3/logs -Dcom.atomikos.icatch.file=/usr/share/co3/conf/jta.properties -Xmx32904m -Xms16452m -Xdump:directory=/usr/share/co3/logs/dumps -Djavax.servlet.request.encoding=UTF-8 -Dfile.encoding=UTF-8 -Dorg.quartz.properties=/usr/share/co3/conf/quartz.properties -Dcom.co3.web.rest.restTraceLoggingFilter.config=/usr/share/co3/conf/restTraceLoggingFilter.properties org.apache.catalina.startup.Bootstrap
co3 12936 4.9 13.9 36301440 9199688 ? SLl May28 4271:48 resilient -procname resilient -home /usr/lib/jvm/ibm-jdk-8 -classpath /usr/share/resilient-tomcat/bin/bootstrap.jar:/usr/share/resilient-tomcat/bin/tomcat-juli.jar -outfile /usr/share/co3/logs/catalina.out -errfile /usr/share/co3/logs/catalina.err -pidfile /var/run/resilient.pid -cwd /usr/share/co3 -user co3 -Dcatalina.home=/usr/share/resilient-tomcat -Dcatalina.base=/usr/share/co3 -Dorg.jboss.logging.provider=slf4j -Dlogback.configurationFile=/usr/share/co3/conf/logback.xml -Djava.awt.headless=true -Dco3.log.dir=/usr/share/co3/logs -Dcom.atomikos.icatch.file=/usr/share/co3/conf/jta.properties -Xmx32904m -Xms16452m -Xdump:directory=/usr/share/co3/logs/dumps -Djavax.servlet.request.encoding=UTF-8 -Dfile.encoding=UTF-8 -Dorg.quartz.properties=/usr/share/co3/conf/quartz.properties -Dcom.co3.web.rest.restTraceLoggingFilter.config=/usr/share/co3/conf/restTraceLoggingFilter.properties org.apache.catalina.startup.Bootstrap
resadmin 14548 0.4 0.0 1104100 44216 ? Sl May28 396:22 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
resadmin 16053 0.4 0.2 1147920 146840 ? Sl May28 413:38 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
resadmin 16613 0.8 0.1 1165160 76180 ? Sl Jul18 107:30 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
resadmin 16853 0.3 0.0 1110268 49176 ? Sl Jul18 46:00 /opt/app-root/bin/python3.9 /opt/app-root/bin/resilient-circuits run
resadmin 17191 0.3 0.1 1120160 70772 ? Sl Jul18 46:48 /opt/app-root/bin/python3.9 /opt/app-root/bin/resilient-circuits run
root 18948 0.0 0.0 112816 984 pts/0 S+ 16:22 0:00 grep --color=auto -e resilient
resadmin 24980 0.8 0.0 1113412 47856 ? Sl 14:29 0:57 /opt/app-root/bin/python3.6 /opt/app-root/bin/resilient-circuits run
resadmin 30853 0.3 0.0 1190064 53180 ? Sl Jul26 5:30 /opt/app-root/bin/python3.9 /opt/app-root/bin/resilient-circuits run
So it looks like when the resilient service starts, it spawns a number of different processes. I am going to send you a DM to discuss this further.
-Matt
Matt, the same happens with another service for example “nfs”.