New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rear mkrescue fails on new system #440
Comments
How did you install ReaR? Please provide the output of "rear dump" On 16 July 2014 15:08, BenGig notifications@github.com wrote:
|
On RHEL6, by yum from EPEL:
Output of rear dump:
|
@BenGig it works for me. If you remove rear (via |
Sorry about the vacation related delay. After rpm -e rear: /var/lib/rear remained with the three subdirs output, layout and recovery. I then cleaned up with rm -rf /var/lib/rear. Reinstalled with yum install rear, the installation created /var/lib/rear as an empty directory. I found that configuring OUTPUT=ISO does indeed creates all the directories necessary. But: the option OUTPUT=PXE is triggering the problem, I could verify it on RHEL6 and on Fedora 20. |
@BenGig I've fixed the issue - thanks for doing the troubleshooting... |
added to the release notes so we can close this issue |
Hi
95_copy_result_files.sh wants to copy files to /var/lib/rear/output which does not exists on a new system. Consequently the job fails. I searched the issues but did not found anything, is this by design to not create the directory, or just went unnoticed until now?
Regards
Ben
The text was updated successfully, but these errors were encountered: