syncproxy.eu.debian.org stale since March 15th — A UIP stuck, affecting downstream mirrors

--000000000000abb0a8064d4f274a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Debian Mirror Team and Community,

We are writing to report that syncproxy.eu.debian.org appears to be stuck
since 2026-03-15 20:25:07 UTC, with a persistent Archive-Update-in-Progress
(AUIP) file that is preventing downstream mirrors from completing stage2
syncs.

We operate mirror.raiolanetworks.com, an official Debian mirror in Spain
that syncs from syncproxy.eu.debian.org. Since March 15th, every ftpsync
run completes stage1 successfully (returncode 0), but stage2 is skipped
every time because an upstream AUIP file is always present. After 3 retries
(the default UIPRETRIES), each sync run aborts with errors.

The situation as observed from mirror-master status pages:

- syncproxy.eu.debian.org:
  mirror version: 2026-03-15 20:25:07 (over 2 days stale)
  sitetrace: frozen at 2026-03-15 20:38:06
  score: 77.08 and dropping
  AUIP file continuously present
  Status:
https://mirror-master.debian.org/status/mirror-info/syncproxy.eu.debian.org=
.html

- syncproxy2.eu.debian.org (its upstream):
  mirror version: 2026-03-18 14:22:49 (current)
  score: 100.00
  No AUIP issues
  Status:
https://mirror-master.debian.org/status/mirror-info/syncproxy2.eu.debian.or=
g.html

This confirms the problem is isolated to syncproxy.eu.debian.org itself
(hosted by CARNet, also known as debian.carnet.hr / ftp.hr.debian.org), not
its upstream. There may be a stale AUIP file on the host or a broken sync
process that needs manual intervention.

Our mirror status showing the impact:
https://mirror-master.debian.org/status/mirror-info/mirror.raiolanetworks.c=
om.html

This is likely affecting all downstream mirrors that sync from
syncproxy.eu.debian.org.

Note: A similar global archive stagnation was reported in February 2026 on
this list (subject: "Global archive stagnation? Release files not updated
since Feb 24th 14:16 UTC").

We have temporarily switched our upstream to work around the issue, but
syncproxy.eu.debian.org needs attention from its administrators.

Best regards,
=E2=80=94
*Mart=C3=ADn G=C3=B3mez*
[email protected]

--000000000000abb0a8064d4f274a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello Debian Mirror Team and Community,<br><br>We are=
 writing to report that <a href=3D"http://syncproxy.eu.debian.org">syncprox=
y.eu.debian.org</a> appears to be stuck since 2026-03-15 20:25:07 UTC, with=
 a persistent Archive-Update-in-Progress (AUIP) file that is preventing dow=
nstream mirrors from completing stage2 syncs.<br><br>We operate <a href=3D"=
http://mirror.raiolanetworks.com">mirror.raiolanetworks.com</a>, an officia=
l Debian mirror in Spain that syncs from <a href=3D"http://syncproxy.eu.deb=
ian.org">syncproxy.eu.debian.org</a>. Since March 15th, every ftpsync run c=
ompletes stage1 successfully (returncode 0), but stage2 is skipped every ti=
me because an upstream AUIP file is always present. After 3 retries (the de=
fault UIPRETRIES), each sync run aborts with errors.<br><br>The situation a=
s observed from mirror-master status pages:<br><br>- <a href=3D"http://sync=
proxy.eu.debian.org">syncproxy.eu.debian.org</a>:<br>=C2=A0 mirror version:=
 2026-03-15 20:25:07 (over 2 days stale)<br>=C2=A0 sitetrace: frozen at 202=
6-03-15 20:38:06<br>=C2=A0 score: 77.08 and dropping<br>=C2=A0 AUIP file co=
ntinuously present<br>=C2=A0 Status: <a href=3D"https://mirror-master.debia=
n.org/status/mirror-info/syncproxy.eu.debian.org.html">https://mirror-maste=
r.debian.org/status/mirror-info/syncproxy.eu.debian.org.html</a><br><br>- <=
a href=3D"http://syncproxy2.eu.debian.org">syncproxy2.eu.debian.org</a> (it=
s upstream):<br>=C2=A0 mirror version: 2026-03-18 14:22:49 (current)<br>=C2=
=A0 score: 100.00<br>=C2=A0 No AUIP issues<br>=C2=A0 Status: <a href=3D"htt=
ps://mirror-master.debian.org/status/mirror-info/syncproxy2.eu.debian.org.h=
tml">https://mirror-master.debian.org/status/mirror-info/syncproxy2.eu.debi=
an.org.html</a><br><br>This confirms the problem is isolated to <a href=3D"=
http://syncproxy.eu.debian.org">syncproxy.eu.debian.org</a> itself (hosted =
by CARNet, also known as <a href=3D"http://debian.carnet.hr">debian.carnet.=
hr</a> / <a href=3D"http://ftp.hr.debian.org">ftp.hr.debian.org</a>), not i=
ts upstream. There may be a stale AUIP file on the host or a broken sync pr=
ocess that needs manual intervention.<br><br>Our mirror status showing the =
impact:<br><a href=3D"https://mirror-master.debian.org/status/mirror-info/m=
irror.raiolanetworks.com.html">https://mirror-master.debian.org/status/mirr=
or-info/mirror.raiolanetworks.com.html</a><br><br>This is likely affecting =
all downstream mirrors that sync from <a href=3D"http://syncproxy.eu.debian=
.org">syncproxy.eu.debian.org</a>.<br><br>Note: A similar global archive st=
agnation was reported in February 2026 on this list (subject: &quot;Global =
archive stagnation? Release files not updated since Feb 24th 14:16 UTC&quot=
;).<br><br>We have temporarily switched our upstream to work around the iss=
ue, but <a href=3D"http://syncproxy.eu.debian.org">syncproxy.eu.debian.org<=
/a> needs attention from its administrators.<br><br>Best regards,</div><div=
><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signatu=
re"><div dir=3D"ltr"><div style=3D"color:rgb(0,0,0)">=E2=80=94=C2=A0</div><=
div><b><font color=3D"#000000">Mart=C3=ADn G=C3=B3mez</font></b></div><div =
style=3D"color:rgb(136,136,136)"><a href=3D"mailto:[email protected]=
" style=3D"color:rgb(17,85,204)" target=3D"_blank">[email protected]=
</a></div></div></div></div></div>

--000000000000abb0a8064d4f274a--