Since yesterday we're getting large emails to root@ from boron for the wmf-auto-restart crontabs due lsof printing to stderr lsof: no pwd entry for UID 1234 thousands of times.
UID 1234 is the pbuilder ID and there is a build of the JDK packages that takes long time.
Given that the script is currently not checking stdout from lsof, as a quick bandaid I'll add an ignore to stderr when running lsof, and then we can add a better solution later.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| base: ignore lsof stderr in wmf-auto-restart | operations/puppet | production | +2 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T294906 Puppet Improvements | |||
| Duplicate | jbond | T265138 Work required to prepare for puppet 7 | |||
| Resolved | SLyngshede-WMF | T273673 replace all puppet crons with systemd timers | |||
| Open | None | T132324 Tracking and Reducing cron-spam to root@ | |||
| Resolved | Volans | T224661 cron-spam to root@: lsof stderr generates large emails on boron from wmf-auto-restart |
Change 513270 had a related patch set uploaded (by Volans; owner: Volans):
[operations/puppet@production] base: ignore lsof stderr in wmf-auto-restart
Change 513270 merged by Volans:
[operations/puppet@production] base: ignore lsof stderr in wmf-auto-restart
Bandaid applied, no output from running wmf-auto-restart on boron. It should be good for now. Leaving open for a better long-term solution.