Bug 1033585

Summary: Unable to start abrt-addon-vmcore
Product: [Fedora] Fedora Reporter: Frank Büttner <bugzilla>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: abrt-devel-list, dvlasenk, iprikryl, jfilak, mmilata, mtoman, pkubat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-26 11:15:26 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:
Description Flags
configuration for kdump none

Description Frank Büttner 2013-11-22 12:45:12 UTC
Created attachment 827732 [details]
configuration for kdump

Description of problem:
unable to start it via:
systemctl start abrt-vmcore.service


Version-Release number of selected component (if applicable):
abrt-addon-vmcore-2.1.9-1.fc19.x86_64

How reproducible:
every time

Steps to Reproduce:
run /usr/sbin/abrt-harvest-vmcore or systemctl start abrt-vmcore.service


Actual results:
Path '/var/crash' cannot be an absolute path when mounting a dump partition.

Expected results:
no error

Comment 1 Petr Kubat 2013-11-26 08:05:22 UTC
Thank you for filing a bug report!

It seems you are trying to append an absolute path to another absolute path.
Please try changing the path in the kdump configuration to something that is relative, eg. var/crash.

Comment 2 Frank Büttner 2013-11-26 11:15:26 UTC
Thanks, that was it.
I think it was because of the LVM configuration.

path var/crash
ext4 /dev/mapper/VG_YYY-LV_YYYYY.

So I think I can close it, as not an bug.