How to forcibly restart MID Server that went down by SSH?

[Sato3]

Hi, All.

I'm looking for a command that uses SSH to forcibly restart a MID Server that went down for some reason and put it in the Up state.

I'm not very familiar with MID Server, but is it possible to run it using REST API etc.?

I hope someone will contribute to me.

Thank you.

[Rahul Priyadars]

what is the Unix OS flavor you have for ur your Mid Server?

on Unix Box GREP the Mid Server Daemon and see what is its Start Path?

ps -ef | grep -i mid

Let me know this first.

Regards

RP

[Sato3]

Hi, @Rahul Priyadarshy 

The Unix OS flavor is Centos. I am using it via Docker.

>>>on Unix Box GREP the Mid Server Daemon and see what is its Start Path?

postscript : 

Correct, yes, confirm.

Eventually, the Down state of the target MID Server process should be forcibly restarted.

Best regards

[Rahul Priyadars · Accepted solution]

Good to know that You are using - Containerized Mid Server.

So when POD is up means mid-server is also up.

Ur Problem Statement is - How to restart container + Mid server ?

have a look

docker stop <container_id>This command shuts down the containerized MID Server.

docker start <container_id>This command starts a containerized MID Server if it is stopped.

docker restart <container_id>This command shuts down a MID Server and restarts it.

Regards

RP

[Sato3]

Hi, @Rahul Priyadarshy 

Yes, it works fine, thank you. Finally, if you want to restart the process from Linux server via MID Server, you can restart it by using the [./start.sh] command as answered in the above comment.

Do you agree with the recognition?

Also, this command is going to call and execute Flow Action (the restart command is entered as an argument) from Flow of Flow Designer, but if there are barriers that may occur at that time, etc.

I hope you can tell me.

Then I want to close this thread.

Thanks for your cooperation.

Best regards

[Rahul Priyadars]

Only barrier i can think of is Connectivity Lost between Flow and the host then execution will fail.

if connectivity is established for remote command execute then it should run (unless User access is not revoked).

In case of any error you can try and catch it in exception handling section and grab it  (email/write in some logs table etc )as per your needs. 

Hope this helps,

Regards

RP