Asup.aods.response.timeOut error reported after midnight
Applies to
- ONTAP 9
- AutoSupport (ASUP)
- AutoSupport OnDemand Server (AODS)
Issue
- Just after midnight, the AODS server responds with an
HTTP 503 Service Unavailableresponse:
Sun Sep 21 00:00:31 +0200 [cluster-01: notifyd: asup.aods.response.timeOut:error]: AutoSupport OnDemand Server (AODS) response was not received before the 30 second time limit.
Tue Sep 23 00:00:31 +0200 [cluster-01: notifyd: asup.aods.response.timeOut:error]: AutoSupport OnDemand Server (AODS) response was not received before the 30 second time limit.
Tue Sep 16 00:00:30 +0200 [cluster-02: notifyd: asup.aods.response.timeOut:error]: AutoSupport OnDemand Server (AODS) response was not received before the 30 second time limit.
- In the
notifydlogs, the timeout occurs, but the server responds shortly afterwards with anHTTP 200 request succeeded:
Fri Sep 05 2025 00:00:31 +02:00 [kern_notifyd:info:2334] 0x80c53fb00: 0: ERR: AutoSupport::OnDemand: Unable to send AOD request to OnDemand Server: Timeout was reached
Fri Sep 05 2025 00:00:31 +02:00 [kern_notifyd:info:2334] Connection timed out after 30002 milliseconds
Fri Sep 05 2025 00:00:31 +02:00 [kern_notifyd:info:2334] (category: 2334:0:deliver) (emittime: 9/4/2025 23:56:18) (message: HTTP/1.1 200 OK)
