SnapCenter backup jobs fail due to System.Net.Sockets.SocketException randomly occurring
- Views:
- 20
- Visibility:
- Public
- Votes:
- 0
- Category:
- snapcenter
- Specialty:
- snapx
- Last Updated:
- 2/28/2025, 12:37:43 AM
Applies to
- SnapCenter Server
- No firewalls between SnapCenter server and plug-in hosts
Issue
- SnapCenter backup jobs fail due to
System.Net.Sockets.SocketException
randomly occurring on the SnapCenter server host side or plug-in host. - The error appears in
SnapManagerWeb_<JOBID>.log
on SnapCenter server orSMCore_<JOBID>.log
on a plug-in host.
Example:
ERROR SMCore_309 PID=[9244] TID=[36] PostRequestAsync exception : System.Net.Http.HttpRequestException: An error occurred while sending the request.
---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
- No errors in the job logs and Windows event logs on the remote host side.
- The phase or operation in a backup job where the error occurs is random and inconsistent.
- Depending on the phase where the error occurs, the job status keeps running and never completes.
- Sometimes, the job keeps running without any explicit error in
SnapManagerWeb_<JOBID>.log
on SnapCenter server orSMCore_<JOBID>.log
on a plug-in host. - Packet traces captured both on the SnapCenter server side and the plug-in host side show many TCP retransmissions and lost packets.