Octopus Server - service won't start

Legacy Uncategorised
1

We’ve been running Octopus for a couple of weeks now without problems, but after a scheduled server restart this weekend, the Octopus Server service won’t come back up.
You can start it manually from Services, but it crashes when we try to access the admin-interface.

The Octopus logs themselves show nothing at all, but in the event log, there are two associated errors:

Application Error:

Faulting application name: Octopus.Server.exe, version: 2.6.4.951, time stamp: 0x5507bc85
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532954fb
Exception code: 0xe0434352
Fault offset: 0x0000000000005bf8
Faulting process id: 0xff4
Faulting application start time: 0x01d080d2879eae0b
Faulting application path: C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: c8acc2ef-ecc5-11e4-80c7-005056a25fe0
Faulting package full name:
Faulting package-relative application ID:

And .NET Runtime:

Application: Octopus.Server.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
Stack:
at Octopus.Shared.Startup.WindowsServiceAdapter.RunService()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

2

Hi Jorgen,

Thanks for reaching out. I am sorry to say that this is a known issue that causes crashes. It is strictly related to RavenDB and its one of the main reasons why we are leaving this DB technology on 3.0 and moving to SQL. That being said some customers have found changing the following will help http://docs.octopusdeploy.com/display/OD/Switch+from+single-threaded+workstation+GC+to+concurrent+server+GC

Apologies for the trouble this issue is causing you.

Dalmiro

3

Hi Dalmiro,

Thanks for the quick reply - I tried the suggestions in your link, but it didn’t help.
However, there’s a difference in the stack trace of our error vs the error reported in your link - our exception doesn’t occur in a Raven library.
Also, we are unable to start Octopus AT ALL - this crash happens whenever we try starting the service - whereas the Raven issue seems to happen sporadically.
Are you sure our issue has the same cause?

BR/Jørgen

4

It seems that this problem was caused by the user configured to run the service having insufficient rights - probably someone at IT removed admin-rights from the user, though they admit to nothing…

5

Hi Jorgen,

Thanks for the update

Dalmiro