Bug 699363
Summary: | [abrt] mlocate-0.22.2-3.el6: Process /usr/bin/updatedb was killed by signal 6 (SIGABRT) | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Siddharth <swaikar> | ||||
Component: | mlocate | Assignee: | Miloslav Trmač <mitr> | ||||
Status: | CLOSED ERRATA | QA Contact: | Karel Srot <ksrot> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6.2 | CC: | jwest, vgaikwad | ||||
Target Milestone: | rc | Flags: | swaikar:
needinfo-
|
||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | mlocate-0.22.2-4.el6 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-10-10 08:46:34 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Siddharth
2011-04-25 11:40:37 UTC
Created attachment 494643 [details]
Backtrace, Dissassembly
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. Thanks for your report. This assertion failure most likely indicates a kernel error. Is this reproducible? (If not, perhaps it would be reproducible if you removed /var/lib/mlocate/mlocate.db .) If this were reproducible, the last thousand lines of log files produced by > strace -v -ff -o log /etc/cron.daily/mlocate.cron would probably identify the specific problematic file system, directory, and directory entry. > find / -inum 7077956 could also identify the directory: if this returns a directory, please attach the log file created by > strace -v -o log ls path_to_that_directory This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. (In reply to comment #6) > Thanks for your report. This assertion failure most likely indicates a kernel > error. > > Is this reproducible? (If not, perhaps it would be reproducible if you removed > /var/lib/mlocate/mlocate.db .) > > If this were reproducible, the last thousand lines of log files produced by > > strace -v -ff -o log /etc/cron.daily/mlocate.cron > would probably identify the specific problematic file system, directory, and > directory entry. > > > find / -inum 7077956 > could also identify the directory: if this returns a directory, please attach > the log file created by > > strace -v -o log ls path_to_that_directory I can add a workaround, but the kernel bug still needs diagnosing and fixing. Can you obtains specifics from the customer? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-1355.html |