On Sat, Aug 31, 2019 at 06:22:03PM +0200, Ludovic Rousseau wrote: > > 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. > > My problem is the same as the original issue reported by Stefan Fritsch. > In my logs I get (same as Stefan): > Aug 29 06:25:15 PiHole popularity-contest: unable to submit report to > http://popcon.debian.org/cgi-bin/popcon.cgi. > Aug 29 06:25:15 PiHole popularity-contest: unable to submit report > > I have no idea if the submission worked or not.
Check /etc/cron.d/popularity-contest for the time of the cron.d report. > > In which case, could you check what is the issue with the timestamp > > (see the full buildlog) ? > > Can you be more specific about what you want me to check? What gives ls -l /var/log/popularity-contest* Do you run some program that change the timestamp of the file /var/log/popularity-contest ? maybe logrotate ? > > 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. > > Sure. > Why did the server failed to answer? Probably too many people are trying to submit at the same time. Hence the move to cron.d with a user specific submission time. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
