RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1467522 - systemd timer define 1s excute but leak 5s
Summary: systemd timer define 1s excute but leak 5s
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-04 06:41 UTC by muahao
Modified: 2019-01-31 11:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-31 11:58:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description muahao 2017-07-04 06:41:52 UTC 
everyone , I define a foo.timer to excute foo.service every seconds

my OS version is centos7u2

    #systemctl --version
    systemd 219
    -PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN

    #systemctl cat  foo.timer
    # /etc/systemd/system/foo.timer
    [Unit]
    Description=Run foo weekly and on boot
    
    [Timer]
    OnBootSec=15min
    OnUnitActiveSec=1s
    AccuracySec=1us
    
    
    [Install]
    WantedBy=timers.target


look what I excute:

    #systemctl cat  foo.service
    # /etc/systemd/system/foo.service
    [Unit]
    Description=test
    
    [Service]
    Type=oneshot
    ExecStart=/usr/lib/aa.sh
    StandardOutput=journal
    StandardError=journal
    
    [Install]
    WantedBy=multi-user.target

script:

    #cat /usr/lib/aa.sh
    #!/bin/sh
    aa=`date`
    echo $aa >> /var/log/aa.log

log file:

    Mon Jul 3 20:28:36 HDT 2017
    Mon Jul 3 20:28:37 HDT 2017
    Mon Jul 3 20:28:38 HDT 2017
    
    Mon Jul 3 20:28:44 HDT 2017
    Mon Jul 3 20:28:45 HDT 2017
    Mon Jul 3 20:28:46 HDT 2017
    Mon Jul 3 20:28:47 HDT 2017
    Mon Jul 3 20:28:48 HDT 2017
    
    
    Mon Jul 3 20:28:54 HDT 2017
    Mon Jul 3 20:28:55 HDT 2017
    Mon Jul 3 20:28:56 HDT 2017
    Mon Jul 3 20:28:57 HDT 2017
    Mon Jul 3 20:28:58 HDT 2017

look this log file ,we can see , I lost 5 seconds contents. I try to OnUnitActiveSec=2s , this problem not appear ,That's why ?
Comment 2 Michal Sekletar 2017-07-04 07:25:53 UTC 
Does the issue occur even when you disable start rate limiting for foo.service? Note that to disable ratelimiting you should set in [Service] section following options,

StartLimitBurst=0
StartLimitInterval=0
Comment 3 David Tardon 2019-01-31 11:58:13 UTC 
No answer for 1.5 years...
Note You need to log in before you can comment on or make changes to this bug.