Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #806251 +++
Description of problem:
Restart kdump service.
/var/log/messages has 'ln: failed to create symbolic link `/var/tmp/initramfs.PA2nCN//usr/lib64/libnss_files.so': No such file or directory'
Version-Release number of selected component (if applicable):
kexec-tools-2.0.3-38.fc17.x86_64
How reproducible:
100%
Steps to Reproduce:
1.touch /etc/kdump.conf
2.service kdump restart
3.
Actual results:
syslog prints `/var/tmp/initramfs.PA2nCN//usr/lib64/libnss_files.so': No such file or directory'
Expected results:
no error/warn
Additional info:
# cat /etc/kdump.conf
ext4 UUID=95617332-8967-4cbd-b1f5-64c31c0d2f6e
default shell
core_collector makedumpfile -E -d 31
# cat /var/log/messages
[snip]
Mar 23 05:56:26 intel-chiefriver-03 kdump: kexec: unloaded kdump kernel
Mar 23 05:56:26 intel-chiefriver-03 kdumpctl[7387]: Stopping kdump:
Mar 23 05:56:26 intel-chiefriver-03 kdump: stopped
Mar 23 05:56:26 intel-chiefriver-03 kdumpctl[7393]: Detected /etc/kdump.conf or /boot/vmlinuz-3.2.1-0.9.el7.x86_64 change
Mar 23 05:56:26 intel-chiefriver-03 kdumpctl[7393]: Rebuilding /boot/initramfs-3.2.1-0.9.el7.x86_64kdump.img
Mar 23 05:56:31 intel-chiefriver-03 kdumpctl[7393]: rpmversion
Mar 23 05:56:31 intel-chiefriver-03 kdumpctl[7393]: dm
Mar 23 05:56:34 intel-chiefriver-03 kdumpctl[7393]: kernel-modules
Mar 23 05:56:45 intel-chiefriver-03 kdumpctl[7393]: lvm
Mar 23 05:56:46 intel-chiefriver-03 kdumpctl[7393]: fstab-sys
Mar 23 05:56:46 intel-chiefriver-03 kdumpctl[7393]: rootfs-block
Mar 23 05:56:47 intel-chiefriver-03 kdumpctl[7393]: udev-rules
Mar 23 05:56:48 intel-chiefriver-03 kdumpctl[7393]: ln: failed to create symbolic link `/var/tmp/initramfs.PA2nCN//usr/lib64/libnss_files.so': No such file or directory
Mar 23 05:56:48 intel-chiefriver-03 kdumpctl[7393]: ln: failed to create symbolic link `/var/tmp/initramfs.PA2nCN//usr/lib64/libnss_files.so': No such file or directory
Mar 23 05:56:49 intel-chiefriver-03 kdumpctl[7393]: base
Mar 23 05:56:51 intel-chiefriver-03 kdumpctl[7393]: fs-lib
Mar 23 05:56:52 intel-chiefriver-03 kdumpctl[7393]: kdumpbase
Mar 23 05:56:53 intel-chiefriver-03 kdumpctl[7393]: shutdown
Mar 23 05:56:53 intel-chiefriver-03 systemd-tmpfiles[12852]: Successfully loaded SELinux database in 8ms 371us, size on heap is 478K.
Mar 23 05:56:54 intel-chiefriver-03 kdumpctl[7393]: E: ldconfig exited ungracefully
Mar 23 05:57:06 intel-chiefriver-03 kdump: kexec: loaded kdump kernel
Mar 23 05:57:06 intel-chiefriver-03 kdumpctl[7393]: Starting kdump:
Mar 23 05:57:06 intel-chiefriver-03 kdump: started up