Re: Got "fact submission failed: first byte timeout", but still report got posted; why?

[email protected] (Slaven Rezic) Sun, 28 Jun 2026 07:50:02 +0200
Newsgroups	perl.cpan.testers.discuss
Message-ID	<[email protected]>
--------------2VJvLNiHQAqZjBLAVSeK9dL3
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

25. 06. 2026. u 04:01, James Keenan pi=C5=A1e:

> As stated above, I have always assumed that if I get error output beginn=
ing with "fact submission failed: first byte timeout", the report for that=
 particular distro did not get transmitted and is utterly lost.  Has the b=
ehavior of the metabase changed?  Or was my assumption wrong from the star=
t?

Hi James,

yes, I observed this problem, and Andreas also told me about it. What=20
probably goes wrong: the reverse proxy in front of the system (still=20
fastly?) has a lower timeout than the processing backends. So while the=20
backend are still happily trying to write the report to the database=20
(and eventually might be successful, or not) the reverse proxy gives up=20
and send the "first byte timeout" response.

Regards,
 =C2=A0 =C2=A0 Slaven

--------------2VJvLNiHQAqZjBLAVSeK9dL3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-=
8">
  </head>
  <body>
    <p>25. 06. 2026. u 04:01, James Keenan pi=C5=A1e:</p>
    <blockquote type=3D"cite"
      cite=3D"mid:[email protected]">
      <pre class=3D"moz-quote-pre" wrap=3D"">As stated above, I have alway=
s assumed that if I get error output beginning with "fact submission faile=
d: first byte timeout", the report for that particular distro did not get =
transmitted and is utterly lost.  Has the behavior of the metabase changed=
?  Or was my assumption wrong from the start?</pre>
    </blockquote>
    <p>Hi James,</p>
    <p>yes, I observed this problem, and Andreas also told me about it.
      What probably goes wrong: the reverse proxy in front of the system
      (still fastly?) has a lower timeout than the processing backends.
      So while the backend are still happily trying to write the report
      to the database (and eventually might be successful, or not) the
      reverse proxy gives up and send the "first byte timeout" response.<b=
r>
      <br>
      Regards,<br>
      =C2=A0 =C2=A0 Slaven<br>
      <br>
    </p>
  </body>
</html>

--------------2VJvLNiHQAqZjBLAVSeK9dL3--