Re: packages.debian.org
Hi,
On Sat Nov 01, 2014 at 00:58:00 +0100, Martin Zobel-Helas wrote:
> Hi,
>
> On Fri Oct 31, 2014 at 11:43:13 +0100, Gerfried Fuchs wrote:
> > * Geert Stappers <stappers@stappers.nl> [2014-10-29 06:31:04 CET]:
> > > On Tue, Oct 28, 2014 at 11:01:45PM +0100, Martin Zobel-Helas wrote:
> > > > On Tue Oct 28, 2014 at 22:55:44 +0100, Geert Stappers wrote:
> > > > > A short 'done' or 'fixed' in response to the original posting
> > > > > would have said "it has been handled, thanks for reporting".
> > > > > And would made it possible to close this thread,
> > > > > to allow us to work other Debian stuff we care about.
> > > >
> > > > no, it is not fixed.
> > > >
> > > > /usr/bin/perl -w ./bin/parse-translations --english-only currently
> > > > hangs. When i kill this process, the rest of the packages cronjob parts
> > > > run fine after that and update the website. If someone can find out why
> > > > parse-translations hangs, that would be very helpful.
> > >
> > >
> > > I have seen the request for help. What I not can see is if it only
> > > involves getting familiar with the website build process
> > > or it also needs getting access to the server where it runs.
> >
> > The packages code is stored in git. I am aware that setting up a
> > private test site to work on the issue isn't as easy as it could be (and
> > requires a fair mount of diskspace), but it's doable.
> >
> > > In other words: When someone steps forward, what are his / her chances
> > > to make a contribution?
> >
> > Trying to reproduce the issue would help. Given that it seems to
> > constantly run into from what I understood should make it easy to
> > reproduce, and suggesting a patch for adding debug information into that
> > script would definitely make it easier to track it down.
>
> I modified 200process_archive to the following:
>
> zobel@picconi:/srv/packages.debian.org/cron.d% git diff 200process_archive
> diff --git a/cron.d/200process_archive b/cron.d/200process_archive
> index 29a7385..8d8d6dc 100755
> --- a/cron.d/200process_archive
> +++ b/cron.d/200process_archive
> @@ -5,7 +5,8 @@
> cd "$topdir"
>
> date
> -./bin/parse-translations --english-only
> +#./bin/parse-translations --english-only
> +strace -ff -o /srv/packages.debian.org/tmp/parse-english -s 1024 ./bin/parse-translations --english-only
> date
> ./bin/parse-packages
> date
>
>
> Maybe that helps to find out what happens and what fails.
It helped.
It looks like we had a corrupted
/srv/packages.debian.org/files/db/descriptions_translated_english_only.db.new,
which parse-translations line 101 tried to opened and failed in the way
that the process got stuck. I removed the corrupted file and waited for
the next run. Now the cronjob is at parse-contents.
Cheers,
Martin
--
Martin Zobel-Helas <zobel@debian.org> Debian System Administrator
Debian & GNU/Linux Developer Debian Listmaster
http://about.me/zobel Debian Webmaster
GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B
Reply to: