Service Restart Method for the Wedora Cloud

Posted 2020-09-02

Supplement

Service Restart Method

Mysql

Stop:

#service mysqld stop

Start:

#service mysqld start

mongo

Stop:

#ps -ef|grep mongo

#kill -9 {PID}

 

Start:

#/usr/local/mongodb/bin/mongod --config /usr/local/mongodb/mongodb.conf--auth

#ps -ef|grep mongo

 

#tail -f /usr/local/mongodb/data/logs/mongodb.log

Msgbus

Restart:

#ps -ef|grep msbgus

#kill -9 {PID}

#kill -9 {PID}

#cd /usr/local/wedora/msgbus

#ps -ef|grep msgbus

#nohup ./msgbus_start.sh 2> /dev/null 2>&1 &

 

#tail -f /usr/local/wedora/msgbus/log/hd.log

 

 

 

Tomcat

Stop:

#ps -ef|grep tomcat7

#Kill -9 {PID}

Start:

#cd /usr/local/wedora/tomcat7/bin/

View:

#ps -ef|grep tomcat

Start:

#./startup.sh

#ps -ef|grep tomcat

#cd/usr/local/wedora/tomcat7/logs

#tail -f /usr/local/wedora/tomcat7/logs/app.log

 

 

ibserver

Stop:

#ps -ef|grep ibserver

#cd /usr/local/wedora/ibserver/

#./shutdown.sh

#ps -ef|grep ibserver

 

( The PID is change from 31853 to 62702, i.e. ibserver service is restart)

 

Start:

#./startup.sh

 

(Automatic input log information, by Ctrl+C to exit)

#ps -ef|grep ibserver

(The python ibserver.py service is started)

 

 

wmmp

Stop:

#ps –ef|grep wmmp

#kill -9 {PID1} **(As show in figure, kill the 33895 script process)

#kiil -9 {PID2} **(Then kill the 33881 wmmp service)

#ps -ef|grep wmmp

(The wmmp1_startup.sh and wmmp1 fep -n fep.wmmp1 processes don‘t exit, mean wmmp service is stopped)

Start:

#cd /usr/local/wedora/wmmp1/

#nohup ./wmmp1_startup.sh 2> /dev/null 2>&1 &

#ps -ef|grep wmmp

(wmmp1_startup.sh(PID=55038) and wmmp1 fep -n fep.wmmp1(PID=55059) processes start, mean the wmmp service is started)

 

Log: (you can check the log to validate after the restart service)

#cd /usr/local/wedora/wmmp1/log/

#tail -f hd.log