Skip to main content
NetApp Knowledge Base

SnapCenter gets HTTPS Timeouts and Windows complains about memory shortage

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

Applies to

  • SnapCenter Server 1.1 and higher
  • SnapCenter Plug-in for Oracle (SCO)

Issue

Backups start failing with the following errors in the job logs:
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Connection to <SVM> on port 443 for protocol HTTPS timed out.   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
 
Errors in the System Event log of Windows show:
Error,HOST_FQDN,Schannel,36887,"A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 46."
Warning,HOST_FQDN,Microsoft-Windows-Resource-Exhaustion-Detector,2004,"Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: SMCoreServiceHost.exe (5496) consumed 25758760960 bytes, mysqld.exe (1792) consumed 5066813440 bytes, and w3wp.exe (23972) consumed 1202536448 bytes."
 
That is 25,7 Gb for SnapCenter's SMCore 5 Gb for MySQL and the SnapCenter NSM repository, 1.2Gb for Internet Information Server's SnapCenter application.
 
Note: the system in this example had 32Gb of RAM (VM assigned), and 36 Gb of Virtual memory (swap file)

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

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device