This will affect @mattdm and @bcotton stats for various requirements
So something changed in the countme program after 2021-03-15 so that while it is processing logs, it does not seem to be updating the data in a way that its 'csv' part understands.
$ ls -l /var/lib/countme/ total 6570004 -rw-r--r--. 1 countme countme 6714286080 Apr 5 09:03 raw.db -rw-rw-r--. 1 countme countme 0 Apr 5 09:03 totals.csv -rw-r--r--. 1 root root 6656000 Mar 30 16:24 totals.db -rw-r--r--. 1 countme countme 6733824 Mar 25 09:03 totals.db-old
This is not urgent for me since my code reads the sqlite3 .db file instead of the CSV file, but would be nice eventually for making the data open to easy analysis by others.
.db
Could you check to see if the recent db data are working also? The db getting smaller from March 25 to March 30 has me worried.
Metadata Update from @mohanboddu: - Issue assigned to smooge - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
Ah, yeah -- it seems to end at March 15. I should have noticed that. :(
So it stopped working when I merged https://pagure.io/mirrors-countme/pull-request/2
Going to track down in the patch to what broke things.
Let me know if you need help
I am going to need help. I think that the various db are 'corrupted' from around March 11, 2021 and I am not sure I am 'helping' by rerunning data on it.
@mattdm I believe I have gotten some of the problems fixed but not sure yet if the totals.db you need is working. You will see a brontosaurus drop on 2020-03-24 -> 2020-03-27 due to rsync not getting all the logs off proxies. Those logs were rotated by the time I got it working
Ah, excellent. The first known dinosaur in the new dataset. :)
Metadata Update from @smooge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.