From: "Max R. Carrara" <m.carrara@proxmox.com>
To: "Max R. Carrara" <m.carrara@proxmox.com>, <pmg-devel@lists.proxmox.com>
Subject: [pmg-devel] superseded: [PATCH pmg-api master v1] systemd: fix report services failing if triggered to early by timers
Date: Tue, 23 Sep 2025 18:49:07 +0200 [thread overview]
Message-ID: <DD0C12V6JW9D.1DAFHYTDNTZCI@proxmox.com> (raw)
In-Reply-To: <20250923151929.415784-1-m.carrara@proxmox.com>
v2: https://lore.proxmox.com/pmg-devel/20250923164723.532488-1-m.carrara@proxmox.com/
On Tue Sep 23, 2025 at 5:19 PM CEST, Max R. Carrara wrote:
> Currently, the `pmgreport.service` and `pmgspamreport.service` units
> might fail if their corresponding timers activate them too early.
>
> To elaborate, both timers have `Persistent=true` in addition to their
> `OnCalendar` option. `Persistent=true` means that the timer's service
> unit will be triggered immediately when the timer is activated, but
> only if it would have been triggered while the timer was inactive [0].
>
> Since the timers are activated relatively early, they might trigger
> their service units before postfix.service and postgresql.service have
> come up, causing `pmgreport.service`, or `pmgspamreport.service`, or
> both of them to fail.
>
> Fix this by letting both service units wait until postfix and postgres
> are up, which are necessary for the units to run successfully. Do this
> by adding the `After` and `Wants` options for `postfix.service` and
> `postgresql.service` to both service units.
>
> [...]
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
prev parent reply other threads:[~2025-09-23 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 15:19 [pmg-devel] " Max R. Carrara
2025-09-23 15:34 ` Stoiko Ivanov
2025-09-23 16:55 ` Max R. Carrara
2025-09-23 16:49 ` Max R. Carrara [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DD0C12V6JW9D.1DAFHYTDNTZCI@proxmox.com \
--to=m.carrara@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.