Welcome to gitblit Discussions!

[gitblit]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[krishnatejasanam]

Hi Gitblit Community,

I hope you are doing well.

I have configured a Gitblit server on Windows Server 2022, and my requirement is to keep the Gitblit service running continuously, 24×7×365.

However, the service stops unexpectedly after running for a few days, even though I have configured the Recovery settings in Windows Services to restart the service, including a delayed restart. For some reason, the recovery mechanism does not seem to work as expected.

Interestingly, I have configured the same setup on Windows Server 2016, where the service recovery settings work as expected without any issues.

Could you please suggest a way to troubleshoot and resolve this issue on Windows Server 2022? Are there any recommended configurations or alternative approaches to ensure that the Gitblit service runs continuously, other than scheduling a Windows Task to monitor and restart the service?

Any suggestions or guidance would be greatly appreciated.

Thanks and regards,
Krishna Teja Sanam

[jcasale]

Hi,
Can you describe how the service runs (what is the binary path and what context does it run under) and how you configured the service recovery settings?

You mention "stops unexpectedly after running for a few days" but to be clear, after a few days does it:

• Stop from a running state? What is the exit code?
• Does it fail to start after being restarted?
• Do you have the GitBlit log enabled? What does it say before it fails?