After the OPMS is installed, the monit summary output may show an error in the bm_proxy process.
This is even if the process will be shown as running:
# ps -ef | grep browsermob-proxy
smartpop 232389 1 0 Mar09 ? 00:48:34 /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.282.b08-1.el7_9.x86_64/jre/bin/java -classpath :/opt/asm/browsermob-proxy/browsermob-proxy-2.0.1-SNAPSHOT-jar-with-dependencies.jar:/opt/asm/browsermob-proxy/etc -Dapp.name=browsermob-proxy -Dapp.pid=232389 -Dbasedir=/opt/asm/browsermob-proxy net.lightbody.bmp.proxy.Main --address 172.17.42.1 --port 9090 --proxyPortRange 9091-9591 --ttl 240
Release : 99.0
Component :
The monit checks for the existence of the process by looking for the pid in this file
/opt/asm/var/run/browsermob-proxy.pid
It can happen that the file is not created so the monit status will be inaccurate
Use this process to allow monit to reflect the correct status:
Find pid with this command:
ps aux | grep app.name=browsermob-proxy | grep -v grep | awk '{ print $2 }'
Kill process:
kill -9 <pid>
restart using monit:
monit restart bm_proxy
bm_proxy is used by full-page monitors and real-time browser monitor (rbtm) (Firefox)