メインコンテンツへスキップ

「Connection timed out (Write failed)」によるEシリーズ AutoSupportの一時的な障害

Views:
3
Visibility:
Public
Votes:
0
Category:
e-series-santricity-os-controller-software
Specialty:
esg
Last Updated:

環境

  • Eシリーズ
  • SANtricity OS
  • StorageGRID アプライアンス
  • AutoSupport

問題

  • EシリーズがAutoSupportの配信に失敗しましたConnection timed out (Write failed)
  • アラートには次のイベントが含まれています
    • Event Message: An ASUP message could not be delivered from the array management host eos-a to NetApp ASUP  https gateway https://support.netapp.com/put/AsupPut/.
    • Event Priority: Critical
  • WEB-SERVER-TRACE-LOG は、support.netapp.com への接続がSocket read/write failedによって失敗したことを示します

INFO [SMMonitorTask-10407] trace [ASUPTask.java:1282] [requestId=0, deviceId=N/A] ASUP task start, task: AUTO_SUPPORT_DISPATCH, source: AUTO_SUPPORT_DAILY_SCHEDULE
INFO [SMMonitorTask-10407] trace [ASUPHTTPClient.java:1022] [requestId=0, deviceId=N/A] Connecting to HTTPS server: support.netapp.com:443, IP <ADDRESS>
INFO [SMMonitorTask-10407] trace [ASUPHTTPClient.java:1022] [requestId=0, deviceId=N/A] Connecting to HTTPS server: support.netapp.com:443, IP <ADDRESS>
INFO [SMMonitorTask-10407] trace [ASUPHTTPClient.java:1367] [requestId=0, deviceId=N/A] Reading file '/msw_data/data/monitor/supportdata/pending/BUNDLE.Daily.<FILE>.7z' and writing to output stream
WARN [BlockingScheduledPool-1] c.n.e.a.d.b.SingleDatabaseManager [SingleDatabaseManager.java:127] [requestId=0, deviceId=N/A] We attempted to run a regularly schedule database sync, but the link to the alternate is unavailable.
ERROR [SMMonitorTask-10407] trace [ASUPHTTPClient.java:749] [requestId=0, deviceId=N/A] Socket read/write failed.
Caller+0    at smmonitor.asup.ASUPHTTPClient.dispatchASUPMessage(ASUPHTTPClient.java:749)
Caller+1    at smmonitor.asup.ASUPTask.dispatchAutoSupportBundle(ASUPTask.java:1695)
Caller+2    at smmonitor.asup.ASUPTask.doTaskOperation(ASUPTask.java:1386)
Caller+3    at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:1290)
Caller+4    at smmonitor.asup.ASUPTask.doTask(ASUPTask.java:44)
java.net.SocketException: Connection timed out (Write failed)
   at java.base/java.net.SocketOutputStream.socketWrite0(Native Method)
   at java.base/java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:110)
   at java.base/java.net.SocketOutputStream.write(SocketOutputStream.java:150)
   at java.base/sun.security.ssl.SSLSocketOutputRecord.deliver(SSLSocketOutputRecord.java:345)
   at java.base/sun.security.ssl.SSLSocketImpl$AppOutputStream.write(SSLSocketImpl.java:1304)

  • AutoSupport は次のスケジュールで実行される再試行によって配信されます

 

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.

 

  • この記事は役に立ちましたか?