| Summary: | got lots of errors in journal after a reboot | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||||
| Component: | abrt | Assignee: | abrt <abrt-devel-list> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 25 | CC: | abrt-devel-list, iprikryl, jfilak, lnie, mhabrnal, michal.toman, mmilata, phelia | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-09-05 10:48:08 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 1196604 [details]
dmesg
Thank you for the report. Please, run the following command and provide us with its output: # ls -laRZ /var/spool/abrt/oops-2016-08-30-17:41:15-712-4 here is the output:) /var/spool/abrt/oops-2016-08-30-17:41:15-712-4: total 0 drwxr-x---. 3 root abrt system_u:object_r:abrt_var_cache_t:s0 277 Sep 1 16:24 . drwxr-x--x. 6 root abrt system_u:object_r:abrt_var_cache_t:s0 198 Sep 1 14:12 .. -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 abrt_version -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 analyzer -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 architecture -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 backtrace -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 cmdline -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 hostname -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 kernel -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 last_occurrence drwxr-x---. 2 root abrt system_u:object_r:abrt_var_cache_t:s0 19 Aug 30 17:41 .libreport -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 os_info -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 os_release -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 proc_modules -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 reason -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 suspend_stats -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 time -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 type /var/spool/abrt/oops-2016-08-30-17:41:15-712-4/.libreport: total 0 drwxr-x---. 2 root abrt system_u:object_r:abrt_var_cache_t:s0 19 Aug 30 17:41 . drwxr-x---. 3 root abrt system_u:object_r:abrt_var_cache_t:s0 277 Sep 1 16:24 .. -rw-r-----. 1 root abrt system_u:object_r:abrt_var_cache_t:s0 0 Aug 30 17:41 owner ~ (In reply to lnie from comment #3) Strange, all the files have 0 length. Something bad happened and we cannot do much about it because we need to know the reproducer. Perhaps we will find something relevant in journal. Please, run: # journalctl | grep "oops-2016-08-30-17:41:15-712-4" here is the output: Aug 30 17:42:52 localhost.localdomain abrtd[676]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Aug 31 17:15:09 localhost.localdomain abrtd[707]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 11:08:53 localhost.localdomain abrtd[708]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 11:31:29 localhost.localdomain abrtd[722]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 12:07:52 localhost.localdomain abrtd[721]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 14:03:15 localhost.localdomain abrtd[668]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 14:13:56 localhost.localdomain abrtd[679]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 14:54:48 localhost.localdomain abrtd[694]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 15:37:25 localhost.localdomain abrtd[691]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 15:43:37 localhost.localdomain abrtd[681]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 16:24:24 localhost.localdomain abrtd[689]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 21:41:36 localhost.localdomain abrtd[672]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 23:16:15 localhost.localdomain abrtd[685]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 23:18:28 localhost.localdomain abrtd[680]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 02 10:09:20 localhost.localdomain abrtd[680]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 05 13:50:02 localhost.localdomain abrtd[671]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 05 16:57:41 localhost.localdomain abrtd[671]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory ~ (In reply to lnie from comment #5) Thank you. Unfortunately, the output isn't very helpful. Please remove all directories in /var/spool/abrt that contains 0 lenght files, monitor your system some time and try to learn the reproducer. We need to find out who truncated the files. Till then I'm closing this bug as INSUFFICIENT_DATA. Please re-open it with the reproducer. |
Created attachment 1196603 [details] journal Description of problem: journal -p 3 : -- Reboot -- Sep 01 14:54:45 localhost.localdomain systemd[1]: Unable to fix SELinux security context of /run/systemd/inaccessible/fifo: Permission denied Sep 01 14:54:45 localhost.localdomain systemd[1]: Unable to fix SELinux security context of /run/systemd/inaccessible/blk: Permission denied Sep 01 14:54:45 localhost.localdomain systemd[1]: Unable to fix SELinux security context of /run/systemd/inaccessible/chr: Permission denied Sep 01 14:54:48 localhost.localdomain abrtd[694]: '/var/spool/abrt/oops-2016-08-30-17:41:15-712-4' is not a problem directory Sep 01 14:54:53 localhost.localdomain setroubleshoot[908]: SELinux is preventing systemd from getattr access on the blk_file /run/systemd/inaccessible/blk. For complete SELinux messages. run sealert -l 66bc034b-0d73-4718-b682-591fc456b35a Version-Release number of selected component (if applicable): abrt-2.8.2-2.fc25 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: