Bug#838561: 503 on lw07
Following up on this, the problem seems to be varnish-related; on lw07,
with a curl client eventually receiving a 503, the corresponding
varnishlog conversation with its apache backend looks like this:
* << BeReq >> 2818775
- Begin bereq 2818774 fetch
- Timestamp Start: 1497946411.684815 0.000000 0.000000
- BereqMethod GET
- BereqURL /archive/debian/20150929T041530Z/pool/main/c/curl/curl_7.38.0-4+deb8u2_amd64.deb
- BereqProtocol HTTP/1.1
- BereqHeader Host: snapshot.debian.org
- BereqHeader User-Agent: curl/7.51.0
- BereqHeader Accept: */*
- BereqHeader X-Forwarded-For: 81.252.32.75
- BereqHeader Accept-Encoding: gzip
- BereqHeader X-Varnish: 2818775
- VCL_call BACKEND_FETCH
- VCL_return fetch
- Backend 27 default default(127.0.0.1,,80)
- Timestamp Bereq: 1497946411.684854 0.000039 0.000039
- Timestamp Beresp: 1497946411.707409 0.022594 0.022555
- BerespProtocol HTTP/1.1
- BerespStatus 200
- BerespReason OK
- BerespHeader Date: Tue, 20 Jun 2017 08:13:31 GMT
- BerespHeader Server: Apache
- BerespHeader Expires: Fri, 30 Jun 2017 08:13:31 GMT
- BerespHeader Cache-Control: public, max-age=864000
- BerespHeader Accept-Ranges: bytes
- BerespHeader ETag: "c5aa0476c607871b645ee8351ed745538219b81b"
- BerespHeader X-Content-Type-Options: nosniff
- BerespHeader X-Frame-Options: sameorigin
- BerespHeader Referrer-Policy: no-referrer
- BerespHeader X-Xss-Protection: 1
- BerespHeader Last-Modified: Wed, 29 Apr 2015 17:26:50 GMT
- BerespHeader Content-Range: bytes 0-200017/200018
- BerespHeader Content-Length: 200018
- BerespHeader X-Clacks-Overhead: GNU Terry Pratchett
- BerespHeader Content-Type: application/x-debian-package
- TTL RFC 864000 -1 -1 1497946412 1497946412 1497946411 1498810411 864000
- VCL_call BACKEND_RESPONSE
- VCL_return deliver
- Storage file s0
- ObjProtocol HTTP/1.1
- ObjStatus 200
- ObjReason OK
- ObjHeader Date: Tue, 20 Jun 2017 08:13:31 GMT
- ObjHeader Server: Apache
- ObjHeader Expires: Fri, 30 Jun 2017 08:13:31 GMT
- ObjHeader Cache-Control: public, max-age=864000
- ObjHeader ETag: "c5aa0476c607871b645ee8351ed745538219b81b"
- ObjHeader X-Content-Type-Options: nosniff
- ObjHeader X-Frame-Options: sameorigin
- ObjHeader Referrer-Policy: no-referrer
- ObjHeader X-Xss-Protection: 1
- ObjHeader Last-Modified: Wed, 29 Apr 2015 17:26:50 GMT
- ObjHeader X-Clacks-Overhead: GNU Terry Pratchett
- ObjHeader Content-Type: application/x-debian-package
- Fetch_Body 3 length stream
- ExpKill LRU_Cand p=0x7f804ac7a380 f=0x0 r=3
- ExpKill LRU_Cand p=0x7f8047445800 f=0x0 r=3
- ExpKill LRU_Cand p=0x7f804a25bf80 f=0x0 r=2
- ExpKill LRU_Cand p=0x7f8045045d80 f=0x0 r=3
- ExpKill LRU_Cand p=0x7f804849fa00 f=0x0 r=1
- ExpKill LRU x=2655490
- ExpKill LRU_Cand p=0x7f804ac7a380 f=0x0 r=3
- ExpKill LRU_Cand p=0x7f8047445800 f=0x0 r=3
- ExpKill LRU_Cand p=0x7f804a25bf80 f=0x0 r=2
- ExpKill LRU_Cand p=0x7f8045045d80 f=0x0 r=3
- ExpKill LRU_Cand p=0x7f804849fa80 f=0x0 r=1
- ExpKill LRU x=2655492
- ExpKill LRU_Cand p=0x7f804ac7a380 f=0x0 r=3
- ExpKill LRU_Cand p=0x7f8047445800 f=0x0 r=3
- ExpKill LRU_Cand p=0x7f804a25bf80 f=0x0 r=2
- ExpKill LRU_Cand p=0x7f8045045d80 f=0x0 r=3
- ExpKill LRU_Fail
- FetchError Could not get storage
- BackendClose 27 default(127.0.0.1,,80)
- BereqAcct 236 0 236 528 102400 102928
- End
So apache is answering 200, but somehow when attempting to deliver that
back to the client, varnish is erroring out. I'd say that happens when
trying to push that object into the lru cache, but that's more of a
guess...
--Seb
Reply to: