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.
Description of problem: We recently found an abrt-hook-ccpp process stuck on one of our nodes for more than a week. We found the following processes on the system: nscd 3453 1.7 0.0 2363160 972 ? Dsl Aug26 1739:29 /usr/sbin/nscd root 317150 0.0 0.0 83936 1532 ? S Oct23 2:31 /usr/libexec/abrt-hook-ccpp 11 0 3453 28 28 1445604670 nscd Tracing the abrt process showed a loop: # strace -f -p 317150 Process 317150 attached restart_syscall(<... resuming interrupted call ...>) = 0 symlinkat("317150", 5, ".lock") = -1 EEXIST (File exists) readlinkat(5, ".lock", "4017", 15) = 4 access("/proc/4017", F_OK) = 0 nanosleep({0, 500000000}, NULL) = 0 symlinkat("317150", 5, ".lock") = -1 EEXIST (File exists) readlinkat(5, ".lock", "4017", 15) = 4 access("/proc/4017", F_OK) = 0 nanosleep({0, 500000000}, NULL) = 0 symlinkat("317150", 5, ".lock") = -1 EEXIST (File exists) readlinkat(5, ".lock", "4017", 15) = 4 access("/proc/4017", F_OK) = 0 nanosleep({0, 500000000}, NULL) = 0 so I checked the file descriptor to get the path: # ls -l /proc/317150/fd total 0 lr-x------. 1 root root 64 Nov 2 14:37 0 -> pipe:[1577878550] lrwx------. 1 root root 64 Nov 2 14:37 1 -> /dev/null lrwx------. 1 root root 64 Nov 2 14:37 2 -> /dev/null lrwx------. 1 root root 64 Nov 2 14:37 3 -> socket:[1577881793] lr-x------. 1 root root 64 Nov 2 14:37 4 -> /var/spool/abrt lr-x------. 1 root root 64 Nov 2 14:37 5 -> /var/spool/abrt/ccpp-2015-10-05-15:04:14-262898 then found the .lock file in the directory was a broken symlink: # ls -la /var/spool/abrt/ccpp-2015-10-05-15:04:14-262898 total 2024 drwxr-x---. 2 root abrt 41 Oct 5 15:06 . drwxr-xr-x. 37 abrt abrt 4096 Oct 30 10:24 .. lrwxrwxrwx. 1 root root 4 Oct 5 15:05 .lock -> 4017 -rw-------. 1 root root 2066788 Oct 5 15:06 sosreport.tar.xz I removed the .lock file, and the processes exited, writing event_log and machine_id files to the directory: # ls -la /var/spool/abrt/ccpp-2015-10-05-15:04:14-262898 total 2028 drwxr-x---. 2 root abrt 61 Nov 2 14:53 . drwxr-xr-x. 17 abrt abrt 4096 Nov 2 14:51 .. -rw-r--r--. 1 root root 0 Nov 2 14:49 event_log -rw-r--r--. 1 root root 93 Nov 2 14:49 machineid -rw-------. 1 root root 2066788 Oct 5 15:06 sosreport.tar.xz