Bug 1033585 - Unable to start abrt-addon-vmcore
Summary: Unable to start abrt-addon-vmcore
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-22 12:45 UTC by Frank Büttner
Modified: 2013-11-26 11:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-26 11:15:26 UTC
Type: Bug

Attachments (Terms of Use)
configuration for kdump (4.69 KB, text/plain)
2013-11-22 12:45 UTC, Frank Büttner 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.