Bug#884229: Bug #884229: [packages.debian.org] 500 error/Internal Server Error (in packages-pkgmirror-csail.debian.org)

Cyril Brulebois <[email protected]>
Newsgroups gmane.linux.debian.devel.www
Organization Debian
Message-ID <[email protected]>
Hi Olly,

Olly Betts <[email protected]> (2018-01-26):
> Yes.  The directory on pkgmirror-csail actually had two different
> versions of the database using different database backends, so the
> files which aren't in the directory on picconi are essentially an
> old version of the same database.
> 
> That alone shouldn't cause the search to fail though - it should just
> open one or the other (it looks like both Xapian 1.2.x and 1.4.x will
> open the old one in this rather odd situation).
> 
> Xapian's replication should cleanly handle the database being replicated
> switching backends so I'm guessing the replication here is using rsync
> (without --delete-after) or similar?  That might also explain why the
> old database is broken as the databases aren't safe to rsync if an
> update is in progress - if the last rsync of the old database happened
> while an update was in progress, it could have been left broken, which
> would typically result in particular searches failing.
> 
> Updating with rsync can also break searches on the mirror while the
> rsync is in progress even if the master isn't updating, so perhaps we
> should switch to using Xapian's replication?  That's already being
> used for the main website search (I set it up with weasel at Debconf
> 15).
> 
> Happy to assist with that, though I'll probably need ssh access to
> pkgmirror-csail (seems I currently only have it for picconi).  My
> Debian username is "olly".

Looking around without knowing much about pkg stuff:
 - picconi has: conf/pushpdo.mirror → csail pkgmirror-csail.debian.org pkg_user
 - those bits are read by bin/pushpdo, which calls rsync this way:
     rsync -e "ssh -i ${MKEYFILE} -${MPROTO} ${SSH_OPTS}" -av --stats  "${MIRRORPATH}"  ${MUSER}@${MHOSTNAME}:/does/not/matter >"${LOGDIR}/pushpdo.${MLNAME}.log"

I suppose help is welcome to possibly fix/improve that, but I'm no pkg
expert (I just happened to have helped one or twice in the past, and to
still be in the pkg_maint group…)


Cheers,
-- 
Cyril Brulebois ([email protected])            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAlpq2scACgkQ/5FK8MKz
VSDY/g/8DAwgR5XbaLs8luc1XBz2etlBFDkJjL7L63z8yA4C1ywXx7Ym+zHqQ/Ov
8/MBBh5EvAUW/wApDUvCBkN8fFqDARH8pilANv0nvUO1/sNFYSoEohucUiXdFq4y
VeikEPjPUD1NDvhvsD38uTVnFEPEtkMg9bbfSBME/W7nHE5CPHNCzdTukG3h1kMj
XyZbxbUDIhIEkjdIgoVGdoDSyjzm7jsYpKjV5j+3mrsxn4e6HnAryyjfCLDVIVHA
netnxmURpNx+YejLHNFBSvyl421KGnJrTpjivdPyKBWv3tWL5WFs6ssPh3s3HUV3
MQ1TcohANS1AueRAxwdndUJZ5K89kzDNbCoaw1P+5O6WAyLkOobak7Cg8Z44rl8K
qIF4bjjbZmrzij3fCfvWGhIGpB2RiFYLc/HtJxKkaUAYdE63s1Ualsz5qannEfbS
gtD//Q0Ov4kPLtuk0L2S7vKJSY7oe6ErMjbH8TFqnkPNVmDLvmrgG8wSF2BKZy+A
gSX89Oz5EM5con34RovisAXnESTCchgT7UwcDLI4rSvQ0wxmlQQ+fs0HobbtZLLi
Sqgw029DZgOrSloF0FaYHu/JyZ64x3eZn0h12g63DFvunI6v5B+iMN4jzO+hpoBA
ggTSh/YCfQ2n9oqlSn2nEOFeZoQuZoi6jBCXddQWXQBkbtxz8W0=
=toPE
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.