Skip to main content
NetApp Knowledge Base

SnapCenter clone deletion operations failing due to MYSQL “Thread was being aborted” error

Views:
37
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • Snapcenter server [SC]
  • SnapCenter Plugin-for SQL [SCSQL]
  • Microsoft Internet Information Server [IIS]

Issue

  • SnapCenter Clone deletion operations failing due to MYSQL “Thread was being aborted” error .
  • This happens before the ‘Deleting clone’ sub job was triggered which in turn is causing backup deletion operations to fail as the SnapCenter repository has the backups marked as backing clone volumes
Windows application logs report the following
4/6/2024,1:8:28,878,Warning,hostname.xx.int,ASP.NET 4.0.30319.0,1309,"Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 4/6/2024 1:08:28 AM 
Event time (UTC): 4/6/2024 5:08:28 AM 
Event ID: e3499a2dc7cd43c18966734455da9704 
Event sequence: 8 
Event occurrence: 1 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/2/ROOT-1-133568537033053650 
    Trust level: Full 
    Application Virtual Path: / 
    Application Path: C:\Program Files\NetApp\SnapCenter WebApp\ 
    Machine name: hostname 
 
Process information: 
    Process ID: 4884 
    Process name: w3wp.exe 
    Account name: IIS APPPOOL\SnapCenter 
 
Exception information: 
    Exception type: HttpException 
    Exception message: The remote host closed the connection. The error code is 0x80070057.
   at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
   at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
   at System.Web.WebSocketPipeline.DoFlush()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Web.WebSocketPipeline.<ProcessRequestImplAsync>d__9.MoveNext()
 
 
 
Request information: 
    Request URL:  
    Request path:  
    User host address:  
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: IIS APPPOOL\SnapCenter 
 
Thread information: 
    Thread ID: 11 
    Thread account name: IIS APPPOOL\SnapCenter 
    Is impersonating: False 
    Stack trace:    at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
   at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
   at System.Web.WebSocketPipeline.DoFlush()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Web.WebSocketPipeline.<ProcessRequestImplAsync>d__9.MoveNext()

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.