Phabricator weekly report was not generated (or at least sent) https://lists.wikimedia.org/mailman/private/phabricator-reports/2016-July/thread.html
Description
Details
Related Objects
- Mentioned In
- rOPUP2b76c50f7efb: phabricator: re-enable project-changes email
rOPUP355b4e6b9a0b: phabricator: re-enable project-changes email
rOPUP5ba6ed34a250: phabricator: re-enable project-changes email
rOPUP30b603be7625: phabricator: re-enable community metrics mail
rOPUPaed6bc6dddd6: phabricator: re-enable community metrics mail
rOPUP8d0a4e61f2f9: phabricator: re-enable community metrics mail
rOPUPbd43fb65cf95: phabricator: re-enable community metrics mail
rOPUP1b9e88427e97: phabricator: re-enable community metrics mail - Mentioned Here
- T85183: "Project creation/edits log" cronjob email for Phab admins
rOPUP1cc6c30e95ae: phabricator: send maintenance mail to list not individuals
T138460: Upgrade m3 (phabricator) db servers
Event Timeline
Didn't receive it either.
Needs someone to run manually to check whether some SQL query barks after DB schema changes or whether it's mail-related.
It was disabled because work running on the database slave would interfere with the upgrade. Running the report from a master database might be too much for it to handle.
As I comment on T138460#2454534, the slave is available from this very moment, after I fixed several data integrity issues.
We can either enable the crons back or wait for the db-master failover, I will be waiting for your feedback.
Can/Should this (the weekly report script) be run manually now but not enable the crons (there's other things there) until after the failover?
Can/Should this (the weekly report script) be run manually now but not enable the crons (there's other things there) until after the failover?
I do not know if you are asking me or your team. In case it is me:
I would suggest re-enabling everything if the failover is going to take a few days (and given the understandably slow pace this maintenance is going, I would recommend it). I am blocked on you at T138460 to setup a date for the failover. The only "but" is that it will have to be disabled again when the failover happens (or moved to another slave).
You have the last word, just ping me on IRC with a decision (but please no unpuppetized things, not matter if temporary).
Why don't you just enable the report separate from the other maintenance things?
It's a separate thing anyways..
190 # project changes mail (T85183) 191 # disabled due to maintenance: T138460 192 phabricator::logmail {'projectchanges': 193 ensure => absent,
Ok, I just ran the community_metrics script manually.
Sure I have no problem with that, though the other cron jobs are also important.
Change 299093 had a related patch set uploaded (by Dzahn):
phabricator: re-enable community metrics mail
@mmodell Obviously haven't as https://lists.wikimedia.org/mailman/private/phabricator-reports/2016-July/thread.html shows.
I think the archive of that list is private? Is only the archive and the access privat, or is the "can write a mail to the list" access restricted too? Could be the reason.
The stats generator can obviously send to the list. List archive is accessible to anybody who is maillist member (anybody can sign in).
And none of those previous manual attempts mentioned above generated that.
Cf. T85183: "Project creation/edits log" cronjob email for Phab admins and rOPUP1cc6c30e95ae: phabricator: send maintenance mail to list not individuals
Change 299663 had a related patch set uploaded (by Dzahn):
phabricator: re-enable project-changes email