Skip to main content
NetApp Knowledge Base

A host removal job in SnapCenter stopped with MySQL errors in the Application Event log

  1. Last updated
  2. Save as PDF
Views:
65
Visibility:
Public
Votes:
4
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Server

Issue

The Job for removal of a Host appears to stop without any other errors while still in the "Running" state, while showing MySQL with a connection issue in the Windows Application Event log, the Host remains listed in the SnapCenter Hosts listing, making it impossible to remove the host.
 
The MySQL event says the following:
 
Information, Application: MySQL, Event-ID: 100,"Aborted connection 3138 todb: 'nsm' user: 'root' host: 'localhost'
(Got anerror reading communication packets)For more information, see Helpand Support Center at http://www.mysql.com.  "
 
And at the same time, an IIS SnapCenter WebApp event will show up in the System Event Log of the SnapCenter Server:
 
Warning, Application: Microsoft-Windows-WAS, Event-ID: 5010,"A process serving application pool 'SnapCenter' failed to respond  to a ping. The process id was '<PROCESS_ID>'."
 
Note: the process ID is equivalent with the PID=[<PROCESS_ID>] found in the SnapManagerWeb_<JOB_ID>.log lines of the still "Running" Job that no longer actually runs, since the process terminated during thete errors.

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.