Bug#930446: popularity-contest: unable to submit report, impossible to debug
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 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.
$ cat /etc/cron.d/popularity-contest
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
57 7 * * * root test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond
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?
What gives
ls -l /var/log/popularity-contest*
$ LANG=C ls -l /var/log/popularity-contest*
-rw-r--r-- 1 root root 24169 Aug 29 07:57 /var/log/popularity-contest
-rw-r--r-- 1 root root 0 Aug 29 07:57 /var/log/popularity-contest.0
-rw-r--r-- 1 root root 5563 Aug 22 07:57 /var/log/popularity-contest.1.gz
-rw-r--r-- 1 root root 41 Aug 22 07:57 /var/log/popularity-contest.2.gz
-rw-r--r-- 1 root root 5541 Aug 15 07:57 /var/log/popularity-contest.3.gz
-rw-r--r-- 1 root root 41 Aug 15 07:57 /var/log/popularity-contest.4.gz
-rw-r--r-- 1 root root 5583 Aug 8 07:57 /var/log/popularity-contest.5.gz
-rw-r--r-- 1 root root 41 Aug 8 07:57 /var/log/popularity-contest.6.gz
-rw-r--r-- 1 root root 8451 Aug 1 07:57 /var/log/popularity-contest.new.gpg
Do you run some program that change the timestamp of the file
/var/log/popularity-contest ? maybe logrotate ?
Not that I am aware of.
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.
popcon.debian.org is hosted by pinel.debian.org.
I could not find a real load issue from munin graphs at https://munin.debian.org/debian.org/pinel.debian.org/index.html
(login dsa-guest, password dsa-guest)
Ah OK.
popularity-contest has TWO cron configurations:
- /etc/cron.daily/popularity-contest
- /etc/cron.d/popularity-contest
Should I just ignore the messages generated by the cron.daily job?
Bye
--
Dr. Ludovic Rousseau
Reply to: