Bug#930446: popularity-contest: unable to submit report, impossible to debug

2020-03-22 Thread Bill Allombert
On Sun, Sep 01, 2019 at 05:52:37PM +0200, Ludovic Rousseau wrote: > So the cron job is executed at 7h57. > > > > > 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? > > > > W

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-09-01 Thread Ludovic Rousseau
Le 01/09/2019 à 09:51, Bill Allombert a écrit : 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

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-09-01 Thread Bill Allombert
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 detec

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-08-31 Thread Ludovic Rousseau
Le 31/08/2019 à 16:05, Bill Allombert a écrit : On Thu, Aug 29, 2019 at 10:38:29PM +0200, Ludovic Rousseau wrote: On Wed, 12 Jun 2019 22:52:59 +0200 Bill Allombert wrote: On Wed, Jun 12, 2019 at 09:46:58PM +0200, Stefan Fritsch wrote: Package: popularity-contest Version: 1.67 Severity: normal

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-08-31 Thread Bill Allombert
On Thu, Aug 29, 2019 at 10:38:29PM +0200, Ludovic Rousseau wrote: > On Wed, 12 Jun 2019 22:52:59 +0200 Bill Allombert wrote: > > On Wed, Jun 12, 2019 at 09:46:58PM +0200, Stefan Fritsch wrote: > > > Package: popularity-contest > > > Version: 1.67 > > > Severity: normal > > > > Dear Maintainer, > >

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-08-29 Thread Ludovic Rousseau
On Wed, 12 Jun 2019 22:52:59 +0200 Bill Allombert 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 h

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-06-20 Thread Stefan Fritsch
Am 20.06.19 um 13:25 schrieb Bill Allombert: >> When submission fails, popcon-upload dies with a timeout. There should >> probably be a randomized sleep to distribute the server load better. I >> think there could be a lot more popcon submissions if this is done. > > What is the time in /etc/cron.

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-06-20 Thread Bill Allombert
On Thu, Jun 20, 2019 at 11:09:10AM +0200, Stefan Fritsch wrote: > Hi Bill, > > I have some new info: Thanks for coming back to me! > When submission fails, popcon-upload dies with a timeout. There should > probably be a randomized sleep to distribute the server load better. I > think there could

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-06-20 Thread Stefan Fritsch
Hi Bill, I have some new info: When submission fails, popcon-upload dies with a timeout. There should probably be a randomized sleep to distribute the server load better. I think there could be a lot more popcon submissions if this is done. Also, popcon-upload should log errors to syslog. The f

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-06-12 Thread Stefan Fritsch
Hmm. After comparing the log files, I think I may have found the issue: Jun 05 06:25:01 c CRON[8719]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Jun 05 06:25:05 c runuser[8833]: pam_unix(runuser:session): session opened for user nobody by (uid=0) Jun 0

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-06-12 Thread Stefan Fritsch
Am 12.06.19 um 22:52 schrieb Bill Allombert: > /usr/share/popularity-contest/popcon-upload has an option -d for > debugging that you could try. >From the command line, this works without errors: /usr/share/popularity-contest/popcon-upload -d -u http://popcon.debian.org/cgi-bin/popcon.cgi -f /va

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-06-12 Thread Bill Allombert
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 su

Bug#930446: popularity-contest: unable to submit report, impossible to debug

2019-06-12 Thread Stefan Fritsch
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 trigg