This bug was fixed in the package systemd - 237-3ubuntu10.43
---
systemd (237-3ubuntu10.43) bionic; urgency=medium
[ Guilherme G. Piccoli ]
* d/p/lp1830746-bump-mlock-ulimit-to-64Mb.patch:
- Bump the memlock limit to match Focal and newer releases (LP: #1830746)
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896614
Title:
Race condition
# VERIFICATION
Note: As a reminder, the issue here is that there's a race condition
between any DBUS service and systemctl daemon-reload, where systemd adds
the DBUS filter (AddMatch) that looks for a name change when that has
already happened. I'll be using systemd-logind as the DBUS service in
Hello Victor, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.43 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[impact]
In certain scenarios, such as high load environments or when "systemctl
daemon-reload" runs at the same time a dbus service is starting (e.g.
systemd-logind), systemd is not able to track properly when the service
has started, keeping the job
** Changed in: systemd
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896614
Title:
Race condition when starting dbus services
To manage notifications about
** Description changed:
+ [impact]
+
+ In certain scenarios, such as high load environments or when "systemctl
+ daemon-reload" runs at the same time a dbus service is starting (e.g.
+ systemd-logind), systemd is not able to track properly when the service
+ has started, keeping the job
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Status: New =>
In the original report, the issue happened randomly on boot when a
service[1] was triggering a reload while systemd-logind was starting,
resulting in a list of queued jobs that were never executed.
The issue can happen too under high load conditions, as reported upstream:
restarting systemd-logind is not safe, as existing sessions can be
logged out.
also performing daemon-reload, mid-boot, also is not safe.
Can you explain the usecase and why these actions are performed
together, racing each other?
--
You received this bug notification because you are a member
10 matches
Mail list logo
