Skip to content
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

Server crashes when log flush fails #4975

Closed
tothegills opened this issue Oct 12, 2018 · 3 comments

Comments

@tothegills
Copy link

commented Oct 12, 2018

The bug

Server crashes during deployment with error:

Exception Info: System.ObjectDisposedException
   at System.Threading.TimerQueueTimer.Change(UInt32, UInt32)
   at System.Threading.Timer.Change(System.TimeSpan, System.TimeSpan)
   at Octopus.Server.Orchestration.Logging.ServerLogWriter.Flush()
   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.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Links

https://secure.helpscout.net/conversation/682969480

@hnrkndrssn

This comment has been minimized.

Copy link

commented Oct 16, 2018

@tothegills tothegills closed this Oct 19, 2018
@octoreleasebot octoreleasebot added this to the 2018.8.12 milestone Oct 19, 2018
@octoreleasebot

This comment has been minimized.

Copy link

commented Oct 19, 2018

Release Note: Fixed a rare crash that occurred when attempting to write log files

@lock

This comment has been minimized.

Copy link

commented Jan 17, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants
You can’t perform that action at this time.