StorageGRID HTTP 500 errors during GETs due to a faulty NIC on the Storage Node
Applies to
Issue
- Clients are experiencing sporadic 500 errors when attempting GET requests
Broken pipeandno consumererrors can be found in /var/local/log/bycast.log.
Example log:Dec 23 07:31:19 Node1 ADE: |12241252 0000000000 ---- ---- 2025-12-23T07:31:19.448355| NOTICE 2115 HFCS: Connection 1766474049291315/1.1.3.4:33142 (STIN):responseWrote Broken pipe 49152 targetResult
Dec 23 07:31:19 Node1 ADE: |12241252 0556084325 S3RQ PSHD 2025-12-23T07:31:19.448412| ERROR 1828 dd8b7c3af114ce81 S3RQ: S3 request error (after response): connection=1766474049291315, Resource=/bucket/data.jpg, HTTP Method=GET, HTTP Status Code (not sent)=500, ErrorMsg=InternalError, ErrorType=Client, CustomErrorMessage={<none>}, Details={asyncPush error: no consumer
No chunk write serviceare found in the /var/local/log/bycast.log on the affected node.
Example log:Dec 24 16:15:00 Affected Node ADE: |12985754 2005355430 ECGQ EGRQ 2025-12-24T16:15:00.110472| NOTICE 0667 ECGQ: No chunk write service found at address 1.1.1.1 (node 12901158)
TLS handshake errors in /var/local/log/bycast.log across all nodes.- There will be marginally more errors on the affected node compared to its peers.
Example log: Dec 24 16:15:01 Affected Node chunk[28256]: http: TLS handshake error from 1.1.1.1:49248: EOF
