This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2101793 - dmeventd needs to quit upon receiving SIGTERM
Summary: dmeventd needs to quit upon receiving SIGTERM
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: LVM Team
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-28 11:45 UTC by Renaud Métrich
Modified: 2023-09-26 20:09 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-23 18:34:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-8288 0 None Migrated None 2023-09-26 20:09:08 UTC
Red Hat Issue Tracker RHELPLAN-126481 0 None None None 2022-06-28 11:52:35 UTC

Comment 1 Zdenek Kabelac 2022-06-28 16:57:11 UTC 
User is supposed to  *UNMONITOR*  LVs  before  quiting dmeventd.

'dmveventd' is protected  against signal - so processed commands which *MAY* freeze your system (i.e.  suspend devices) aren't leaving  system in unusable state.

So I'm not sure what  '--force reboot' is doing - but  it should run   'vgchange --monitor n' first.

This is not seen as bug in dmeventd -  rather some logical problem with  reboot sequence.
Comment 2 Renaud Métrich 2022-06-29 07:29:01 UTC 
Hi Zdenek,

From your comment, I understand it's really necessary to go through the normal shutdown sequence, so I think there is nothing to do on this side.
Specifically here we need lvm2-monitor.service to stop, which will lead to stopping dmeventd.service as well.
This is what I see on normal shutdown:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Jun 28 10:04:36.507032 vm-thin8 systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
...
Jun 28 10:04:36.514671 vm-thin8 dmeventd[873]: dmeventd detected break while being idle for 0 second(s), exiting.
Jun 28 10:04:36.514675 vm-thin8 dmeventd[873]: dmeventd shutting down.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Comment 4 RHEL Program Management 2023-09-23 18:21:18 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5 RHEL Program Management 2023-09-23 18:34:59 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 6 Zdenek Kabelac 2023-09-26 20:09:09 UTC 
Upstream lvm2  (2.03.23)  implemented support for allowing to TERMinate   'dmeventd'  if there is  /run/nologin file present  (should be created on shutdown by systemd).
Note You need to log in before you can comment on or make changes to this bug.