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 1268654 - [RHEL7] systemd: all processes in scopes (including user sessions) SIGKILLed immediately on shutdown with no opportunity to shut down cleanly
Summary: [RHEL7] systemd: all processes in scopes (including user sessions) SIGKILLed ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 1170765
Blocks: 1139380
TreeView+ depends on / blocked
 
Reported: 2015-10-04 12:03 UTC by Jiří Dostál
Modified: 2015-12-07 12:05 UTC (History)
43 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1170765
Environment:
Last Closed: 2015-12-07 12:05:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jiří Dostál 2015-10-04 12:03:16 UTC 
Cloning for RHEL7 bug fix request

+++ This bug was initially created as a clone of Bug #1170765 +++

Description of problem:

I have been noticing during F21 cloud and atomic testing that I sometimes lose my bash history. This seems to be triggered by reboots as can be shown below:

[root@f21 ~]# cat .bash_history | wc -l
2
[root@f21 ~]# history | wc -l
123
[root@f21 ~]# reboot
Connection to 172.24.4.228 closed by remote host.
Connection to 172.24.4.228 closed.
[root@localhost ~(keystone_admin)]# 
[root@localhost ~(keystone_admin)]# ssh -i key1.pem
fedora.4.228
Last login: Thu Nov 20 18:54:48 2014 from 172.24.4.225
[fedora@f21 ~]$ 
[fedora@f21 ~]$ sudo su -
[root@f21 ~]# history | wc -l
3


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

This is from the F21 Cloud RC5 image:

[fedora@f21 ~]$ rpm -q systemd
systemd-216-12.fc21.x86_64

How reproducible:

Seems to be pretty consistent to me. 

Steps to Reproduce:

See description.

Actual results:

My bash history is not saved. 

Expected results:

My bash history is saved.


Additional info:

I think this is an issue with systemd but it could be some other component. Feel free to re-assign where appropriate.

+++++++++++++++++

Hello,

I've created this BZ in order to request a fix for the bug described above. I'm facing the same issue on RHEL7. 

More detailed - There is a feature in Satellite 5 that allows you to execute shell command on remote machine via WebUI. Then you can check status of the command - Pending/Picked Up/Failed/Complete ... When you execute "shutdown -h now" via remote command, the machine shuts down immediately and does not have a chance to report back to server. This results in bad command status and might even cause shutdown loop. Original Satellite 5 BZ https://bugzilla.redhat.com/show_bug.cgi?id=1260527)

Using systemd-219-17.el7
Comment 2 Lukáš Nykrýn 2015-10-05 10:35:30 UTC 
That can't be the same issue. We have reverted the patched which caused this in rhel. Can you reproduce it and provide shutdown log? https://wiki.freedesktop.org/www/Software/systemd/Debugging/
Note You need to log in before you can comment on or make changes to this bug.