#371 Package upgrades leave the mail worker stopped
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#371
- issue
- state:closed
Upgrading the Debian/Ubuntu package leaves the account-email worker stopped. `deploy/debian-server/prerm` stops both `openchronology.service` and `openchronology-mail.service` on upgrade, but `openchronology-migrate` (which the upgrade instructions and `postinst` use to start the server again) restarts only `openchronology.service`. So after every upgrade the mail worker stays down until someone starts it by hand, although it is still enabled. On timescale.info it had been stopped since an upgrade on 25 October, with `systemctl is-enabled` → `enabled` and `is-active` → `inactive`; account email (confirmations, password resets, security notices) waits in `oc_mail_outbox` until it expires. (The queue happened to be empty there.) **Proposed fix:** after restarting the server, `openchronology-migrate` also restarts `openchronology-mail.service` when it is enabled (and the RPM package's equivalent, if it has the same split); a test in `test/server-deb.mjs` / `test/server-rpm.mjs` that an upgrade with the mail worker enabled leaves it active; and a note in the upgrade docs. https://github.com/openchronology/timeline-app/issues/371
Related
- #373 Package upgrades start the enabled mail worker again (#371)
- #374 Package upgrades leave the syslog and journald importers stopped
- #375 openchronology-migrate restarts the enabled syslog and journald importers after an upgrade
- openchronology-migrate starts the enabled mail worker again after an upgrade (#371)
- Merge pull request #373 from openchronology/fix/371-mail-worker-restart
Open #371 Package upgrades leave the mail worker stopped in the timeline