Octopus crashing

Starting with version: 2.5.4.280 we’ve had a few crashes and another occurred last night with the latest version. See below for details. Any ideas? Anyone else having this issue?

Faulting application name: Octopus.Server.exe, version: 2.5.5.318, time stamp: 0x53d5c78b
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532954fb
Exception code: 0xe0434352
Fault offset: 0x0000000000005bf8
Faulting process id: 0x1164
Faulting application start time: 0x01cfac8697e5eefc
Faulting application path: C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 5bb9c135-1af8-11e4-80bc-00155df90f3f
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: Octopus.Server.exe, version: 2.5.4.280, time stamp: 0x53cc6dec
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532954fb
Exception code: 0xc0000005
Fault offset: 0x00000000000038d2
Faulting process id: 0x3ac
Faulting application start time: 0x01cfaa703af03de6
Faulting application path: C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 75f8cd48-1834-11e4-80bc-00155df90f3f
Faulting package full name:
Faulting package-relative application ID:

Hi - thank you very much for the detailed report.

We believe we’ve tracked this one down, and have posted an updated build 2.5.6 at http://octopusdeploy.com/downloads to address the issue. Please let me know if you hit any further problems at all.

Best regards,
Nick

I’m having issues even after upgrading to 2.5.6.356. See http://help.octopusdeploy.com/discussions/problems/23424-octopus-server-consuming-100-memory-and-dashboard-never-renders

1 Like

I have had two crashes of the primary Windows service OctopusDeploy over the last two weeks on 2.5.8.447. I can’t find anything that jumps out in the logs other than some failed messages. Is this still being looked into?

Faulting application name: Octopus.Server.exe, version: 2.5.8.447, time stamp: 0x53fd1df5
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eebf2e
Exception code: 0xe0434352
Fault offset: 0x000000000000606c
Faulting process id: 0x23bc
Faulting application start time: 0x01cfe02eaad25051
Faulting application path: C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: c74e5202-4f25-11e4-80c8-000d3a100795

Hi Jason,

The over-all reason for the crash is still being looked into, but we have a current work around that is explained a little here:

We also suggest updating to 2.5.10 as soon as is possible.

Vanessa

I applied the work-around but had another crash today.

already existed so was removed from the config file under the runtime element as suggested by step 5.

Faulting application name: Octopus.Server.exe, version: 2.5.8.447, time stamp: 0x53fd1df5
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eebf2e
Exception code: 0xe0434352
Fault offset: 0x000000000000606c
Faulting process id: 0x54c
Faulting application start time: 0x01cfeaff206d3602
Faulting application path: C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 75c11b19-5abe-11e4-80c9-000d3a100795

Hi Jason,

Are you in a position to upgrade to 2.5.11? Quite a few different issues around the crash were also updated, so please let me know if this is possible, and we will go from there.
The crash data from 2.5.8 did not help to pinpoint the issue, so extra information will not help here.

Vanessa

I’m getting the same crash after upgrading to 2.5.11.614

Faulting application name: Octopus.Server.exe, version: 2.5.11.614, time stamp: 0x5448f3da
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eebf2e
Exception code: 0xe0434352
Fault offset: 0x000000000000606c
Faulting process id: 0xb90
Faulting application start time: 0x01cfefb34976df1e
Faulting application path: C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: b8123c9d-5ba6-11e4-80d2-00155d47e0f0
Faulting package full name:
Faulting package-relative application ID:

Given Arri’s response, is there any other information we can provide to get this tracked down? We can surely schedule an upgrade but that doesn’t appear to be the fix.

Reverting back to v2.5.8.447 resolved my issues. Prior to that I tried all of the documented settings ‘hacks’ to no avail.

Hi Arri and Jason,

Yeah nearly everything we have implemented and suggest are hacks because we have just not found the root source. And do note that for some customers upgrading, or applying the GC change or both have stopped the crashing. But it won’t account for all environments.

Currently we are writing up some documentation about how to turn on crash logging so we can give this out and get some more data to try in a(nother) effort to find this.
I am going to post it here and create a new post also to try and allow us to gather the data we need to (hopefully) track this down.
We have spent days on trying to get to the bottom of this with crash dumps we have previously gotten, and know it’s still an issue, hopefully a flood of more data might help.

Vanessa

Hello everyone tracking this thread and anyone new stumbling upon it.

To resolve this issue we are asking that anybody who’s Octopus Server is still crashing after upgrading to 2.5.11 and changing the GC settings (http://docs.octopusdeploy.com/display/OD/Switch+from+single-threaded+workstation+GC+to+concurrent+server+GC) to please use the following documentation and turn on crash dump logging.
http://docs.octopusdeploy.com/display/OD/Capture+a+crash+dump

Once you have your file, please name it to represent your company and upload it to the following location. https://file.ac/cMkQMTlkzkY/
If you can also email support at octopusdeploy dot com and notify us of the file you have uploaded and identify who you are this will help us.

Thanks! We do not require any extra information, just at this point the crash dump logs will be all that might finally help us to get the data we need.

Vanessa

So I enabled the crash dump and upgraded again to 2.5.11.614. This time I’m not experiencing any crashing. It would happen within a few mins, right now I’ve been running fine for 4+ hours.

One key difference is this time I put the server into maintenance mode prior to installing the upgrade. Previously when I upgraded and experienced issues, I did not enable maintenance mode.

Hi Arri,

Thanks for this extra information, it might help someone else also! Do let me know if your situation changes.

Vanessa

Thanks. It seems I’m out of the woods for now.

I was able to upgrade to 2.6.1.796 after deleting RavenDB indexes. Unfortunately, OctopusDeploy seems to crash more for me now. I have another private thread for this issue but wanted to relay that I am crashing on 2.6.1.796.