Bug 1144509
Summary: | abrt-vmcore - service (fails?) does not meet conditions | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | lejeczek <peljasz> |
Component: | abrt | Assignee: | abrt <abrt-devel-list> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | abrt-devel-list, cristi.falcas, ekulik, jakub, jmilan, mhabrnal, michal.toman, mkyral, mmarusak, msuchy, peljasz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-06-30 14:22:05 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: | |
Embargoed: |
Description
lejeczek
2014-09-19 15:31:33 UTC
Hello, thank you for the report. Could you please provide the output of the following command: $ grep -v "^#" /etc/kdump.conf "ConditionDirectoryNotEmpty=/var/crash was not met" means that /var/crash directory is empty and systemd didn't start the service because it wasn't necessary because the service needs some files in /var/crash directory. path /var/crash core_collector makedumpfile -l --message-level 1 -d 31 ps. how do I make sure that my abrtd reports completely & properly my kernel's tains. (in text mode) (In reply to lejeczek from comment #3) > path /var/crash > core_collector makedumpfile -l --message-level 1 -d 31 > What's the contents of /var/crash? $ ls -al /var/crash > ps. how do I make sure that my abrtd reports completely & properly my > kernel's tains. (in text mode) Could you please provide output of the following command: $ abrt-cli list there is nothing in /var/crash even thought kdump service reports OK status. abrt-cli list shows nothing but I'd try to get there something, problem is libvirt/qemu with a SR-VIO to an Intel NIC tains the system so badly that it becomes completely unresponsive and hard-cold reboot is necessary. Please provide output of the following commands: $ grep var /etc/fstab $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.10.0-123.8.1.el7.x86_64 root=UUID=feecd027-d6c0-468d-a21f-26ca95871f51 ro vconsole.font=latarcyrheb-sun16 rd.lvm.lv=ol/swap rd.lvm.lv=ol/root crashkernel=auto vconsole.keymap=uk rhgb quiet no var in /etc/fstab Are you sure you experienced a kernel panic? What do you mean by "kernel taints"? We will very likely have no resources to fix this bug during Red Hat Enterprise Linux 7 time life. Moving to upstream. If you insisted on fixing in Red Hat Enterprise Linux 7 please open a support ticket. > Intel NIC tains the system so badly
??? by tainting we mean a process when 3rd party kernel module is inserted into kernel, but we do not have the source. So developer/support cannot do anything about it.
I am closing this because it took ages since last need info. But feel free to reopen if you can provide the info.
ok |