Skip to main content

Coming soon...New Support-Specific categorization of Knowledge Articles in the NetApp Knowledge Base site to improve navigation, searchability and your self-service journey.

NetApp Knowledge Base

SCO cloning using pre-script and/or post-script times out after three hours

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

Applies to

SnapCenter Plug-in for Oracle (SCO)

Issue

Failure on running the pre- and/or post-script after three hours (by default):
Activity 'Prescripts' failed with error: Run pre-scripts failed to execute. Pre script exited with script error code: -1,
script error message: The underlying connection was closed: An unexpected error occurred on a receive.
 
Which shows in SMCore logs with:

2020-12-02T11:51:26.1055919+00:00 DEBUG SMCore_924 PID=[4504] TID=[37] Running pre-scripts from co-located host, URL used: https://<PLUGIN_HOST>:8145/RunScripts
2020-12-02T11:51:26.1055919+00:00 DEBUG SMCore_924 PID=[4504] TID=[37] Request Data: ****************************
<?xml version="1.0" encoding="utf-16"?><SmRunScriptsRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><HostEx>
<Name /><Type /><Id i:nil="true" />...</SmRunScriptsRequest>

 

2020-12-02T14:51:26.6212723+00:00 ERROR SMCore_924 PID=[4504] TID=[37] WebException Encountered, Response null
2020-12-02T14:51:26.6212723+00:00 ERROR SMCore_924 PID=[4504] TID=[37] Exception in method: InvokeXML.
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.
---> System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the
 connected party did not properly respond after a period of time, or established connection failed because connected
 host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected
 party did not properly respond after a period of time, or established connection failed because connected host has failed
 to respond

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