Bug 1350233 - Race between systemctl start (and likely others) vs systemctl daemon-reload
Summary: Race between systemctl start (and likely others) vs systemctl daemon-reload
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 24
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1351793
TreeView+ depends on / blocked
 
Reported: 2016-06-26 15:51 UTC by Kari Hautio
Modified: 2021-09-09 11:52 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
: 1351793 (view as bug list)
Environment:
Last Closed: 2017-08-08 15:04:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kari Hautio 2016-06-26 15:51:15 UTC
Description of problem: If systemctl daemon reload is issued while some other sytemctl command is executing the latter might freeze and never return.


Version-Release number of selected component (if applicable): F24


How reproducible: at will, it is a race so may take a while


Steps to Reproduce:
1. while true; do { systemctl start sshd & } ; systemctl daemon-reload ; fg ; done 

Actual results:

The loop will eventually stop due to systemct start command getting stuck

Expected results:

The loop will execute for ever.

Additional info:

Also seen on RHEL7.

Comment 1 Kari Hautio 2016-06-26 15:52:21 UTC
BZ 1244342 may be same issue, however I was not able to reproduce this on Fedora 23.

Comment 2 Kari Hautio 2016-06-27 07:07:51 UTC
At time it is quite difficult to reproduce this, an alternative method is to execute systemctl start and systemctl daemon-reload in separate terminals.

Terminal 1: 
for ((N=1; N>0; N++)) ; do echo $N ; systemctl daemon-reload ; done 

Terminal 2: this is the one that gets stuck
for ((N=1; N>0; N++)) ; do echo $N ; systemctl start sshd ; done

Comment 4 Fedora End Of Life 2017-07-25 21:19:48 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-08-08 15:04:31 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.