Bug#930446: popularity-contest: unable to submit report, impossible to debug
On Thu, Aug 29, 2019 at 10:38:29PM +0200, Ludovic Rousseau wrote:
> On Wed, 12 Jun 2019 22:52:59 +0200 Bill Allombert <ballombe@debian.org> wrote:
> > On Wed, Jun 12, 2019 at 09:46:58PM +0200, Stefan Fritsch wrote:
> > > Package: popularity-contest
> > > Version: 1.67
> > > Severity: normal
> > > > Dear Maintainer,
> > > > on several of my hosts, popularity-contest logs
> > > > unable to submit report to
> > http://popcon.debian.org/cgi-bin/popcon.cgi.
> > > unable to submit report.
> > > > But it does not log why and there is no way that I could find to
> > trigger
> > > the sending from the command line with debug output enabled.
> > > > http://popcon.debian.org/cgi-bin/pop is reachable from the host via
> > curl. Also,
> > > according to the documentation it should fall back to email, which it does not
> > > do. It does not log why it does not do that.
> >
> > Hello Stefan!
> >
> > This comes from /etc/cron.daily/popularity-contest:
> > # try to post the report through http POST
> > if [ "$SUBMITURLS" ] && [ "yes" = "$USEHTTP" ]; then
> > for URL in $SUBMITURLS ; do
> > if setsid /usr/share/popularity-contest/popcon-upload \
> > -u $URL -f $POPCON 2>/dev/null ; then
> > SUBMITTED=yes
> > else
> > logger -t popularity-contest "unable to submit report to
> > $URL."
> > fi
> > done
> > fi
> >
> > /usr/share/popularity-contest/popcon-upload has an option -d for
> > debugging that you could try.
>
> I added the -d to get some more debug.
Hello Ludovic,
This report is about Stefan problem.
Stefan problem is that popcon is reporting twice, one with cron.d
time and one with the cron.daily fallback, which means somehow the
mechanism to detect that the report was already sent did not work.
Is it your problem too ? According to the email you send me, your report
is also sent at 6:25 which suggests this is the case, since the cron.daily
fallback run at 6:25.
In which case, could you check what is the issue with the timestamp
(see the full buildlog) ?
In you have an unrelated problem, please open a separate bug report.
The debug output you got just means that the server failed to answer.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: