Skip to main content
NetApp Knowledge Base

Upgrade of SCU package to 4.5 fails to start SPL when using sudoer Domain account

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

Applies to

SnapCenter Plug-in for Unix (SCU) 4.5 and higher

Issue

When upgrading or installing the Linux package to a Linux host, with the sudoers prepared to use a Windows Domain account, the SPL will not start, and SnapCenter will show the Host's Plug-in as "Service Stopped".
 
The installation log, after having uploaded and run the plug-in package installer (*), shows:
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it <IP_ADDRESS>:8145
 
*) with a new Host addition (without a previous version of the plug-in being installed) the first of these messages are normal before the installation attempt in the log, since the SPL isn't running, listening on port 8145 yet. The message is only a real issue when coming after the package installation attempt.

 

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.