Re: systemd timers are not enabled by default even though listed in preset files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 9, 2024 at 12:22 PM Felix Schwarz
<fschwarz@xxxxxxxxxxxxxxxxx> wrote:
> There is a long-standing issue with certbot that the certbot-renew timer is not
> enabled by default even though it is listed in "90-default.preset"
> (fedora-release/epel-release):
>
> https://src.fedoraproject.org/rpms/fedora-release/blob/rawhide/f/90-default.preset
>
> Any idea how to debug this? I think it is not specific to certbot - for example
> x509watch.timer seems to be affected as well.

This is what I see on Rawhide:
--------------------------------------------------
# dnf install certbot
[...]
[16/17] Installing certbot-0:2.11.0-3.fc41.noarch
[...]
# systemctl status certbot-renew.timer
○ certbot-renew.timer - This is the timer to set the schedule for
automated renewals
     Loaded: loaded (/usr/lib/systemd/system/certbot-renew.timer;
enabled; preset: enabled)
     Active: inactive (dead)
    Trigger: n/a
   Triggers: ● certbot-renew.service
--------------------------------------------------

On the "Loaded:" line after the first semicolon, there's the unit's
enablement state, which is "enabled". It means systemd will start this
unit on boot (in this case it's WantedBy timers.target). If you're not
seeing "enabled" here while seeing "enabled" in the next field,
perhaps there is a problem with scriptlets.

On the same line, "preset: enabled" tells us the preset value. If you
don't have "enabled" here, perhaps you have another preset file that
overrides 90-default.preset.

The "Active: inactive (dead)" line tells us that the unit is not
started. If I interpret your statement "the certbot-renew timer is not
enabled by default" loosely, this might be your actual problem.
Standard systemd scriptlets do not *start* units by default. There are
packages that do start their timer units after installation. See, for
example, the scriptlet of unbound-anchor:
https://src.fedoraproject.org/rpms/unbound/blob/b1fbf13e87c44119d2222dfb84613b75ed0fcae0/f/unbound.spec#_389

Michal

-- 
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux