Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mirth service is not getting restarted #6163

Closed
Shahabuddin222 opened this issue Apr 16, 2024 · 4 comments
Closed

Mirth service is not getting restarted #6163

Shahabuddin222 opened this issue Apr 16, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@Shahabuddin222
Copy link

Shahabuddin222 commented Apr 16, 2024

Mirth service is not getting restarted if we use Recovery option which is present under Windows Services under Recovery tab.
There is any alternative thing to restart if the service is getting stopped for some issue
Screenshot 2024-04-16 145607

@Shahabuddin222 Shahabuddin222 added the bug Something isn't working label Apr 16, 2024
@Shahabuddin222
Copy link
Author

Anyone here who can help me out

@pacmano1
Copy link
Collaborator

Why is the service getting stopped to begin with?

What does the mirth log file say when it stops unexpectedly?

Mirth almost never stops on its own, it is extremely reliable.

In fact it is so reliable, I've never had to rely on the operating system to restart it.

@ab-mg-23
Copy link

Restart Actions only happen:

If this member is TRUE and the service has configured failure actions, the failure actions are queued if the service process terminates without reporting a status of SERVICE_STOPPED or if it enters the SERVICE_STOPPED state but the dwWin32ExitCode member of the SERVICE_STATUS structure is not ERROR_SUCCESS (0).

If something on the system is using the WinService API or sc.exe to stop the Mirth Service, that's WAD. If you need to find out what/whom is making the service stop that way, you can configure Windows Auditing on Audit Handle Manipulation and Audit Other Object Access Events - Success. However, doing so will generate a large number of entries so you should only enable it for as long as you need to find the culprit.

@pacmano1
Copy link
Collaborator

Moving to discussions until this is a confirmed issue.

@pacmano1 pacmano1 converted this issue into discussion #6175 Apr 18, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants