Your message dated Wed, 04 Aug 2021 14:11:59 +0100
with message-id
<ef4136d28bca9fedccc5b13a9ab13ea708591411.ca...@adam-barratt.org.uk>
and subject line Re: Bug#838561: 503 on lw07
has caused the Debian Bug report #838561,
regarding snapshot.debian.org: Error 503 Service Unavailable on some URL
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
838561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838561
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: snapshot.debian.org
Severity: normal
Open: http://snapshot.debian.org/package/console-setup/1.148/
then click on "console-setup_1.148.tar.xz", which corresponds to:
http://snapshot.debian.org/archive/debian/20160730T163631Z/pool/main/c/console-setup/console-setup_1.148.tar.xz
I get the following error:
Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 2776488
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Tue, 2017-06-20 at 10:27 +0200, Sébastien Delafond wrote:
> 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
>
[...]
> - 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...
>
Thanks for the analysis.
This looks similar to the log that was seen while diagnosing #960304,
which is hopefully now resolved. I'm going to assume they're the same
issue and close this one as well.
Regards,
Adam
--- End Message ---
