-
Notifications
You must be signed in to change notification settings - Fork 246
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
Centos6 / RHEL 6 Recovery / selinux issue #316
Comments
It also helps to have SElinux set to PERMISSIVE after the first boot with selinux=0, afterwards boot up the system and set it back to enforced, then the regular boot works again with selinux enabled after recovery. |
Did you redefine |
Ah here we go, no, i did not redefine the setting but the regular file backup came from a third party tool! That explains it all. Just wanted to stick something like this around in the bugtracker so people catching the same issue know how to deal with it :) Thanks! |
Was your backup tool already integrated within Rear? That is one of the purposes of integrating the (commercial) backup programs. We can do it for you (via sponsoring or consultancy) or you can give it a try... |
Is the following from you? |
Hi @sepsesam and welcome! I talked to people from your company at every conference I had a chance - about 5 to 6 years ago. I was trying to convince your company to sponsor REAR a little bit to get SEP SESAM integrated into it... It seems to me that now you did the opposite, integrating REAR into your backup client. Is this correct? If so, it would be nice of you to link to our homepage on your documentation Wiki... We would be happy to list SESAM as a tool that ships REAR and point to your documentation page in return. If you want to talk about deeper integration strategies or how to simplify the configuration for your users (I read the wiki, it does not look simple to me), please don't hesitate to talk to us on the mailing list or privately. Another question: Do you offer commercial support for your fork of REAR? Regards, |
Dear Schlomo Schapiro, Am 04.11.2013 19:50, schrieb Schlomo Schapiro:
basically we ship a slightly modified version of the REAR client with This way it allows our customers to use all the functions of a How the users may use the REAR shipped with our sesam client beyond We have now put the Link to your Homepage on the top of the page (before
As said, at the moment the fork only contains small changes, however, For further contact please get in touch via service@sep.deMichael Ablassmeier Ziegelstrasse 1 Fon +49 (0) 80 20 / 180-0 Mail support@sep.de |
@sepsesam is there any chance rear will ever contain a proper sepsesam integration? Perhaps for rear-1.18 (for rear-1.17 as we froze the feature list to get it all stable before we release it end of this month) |
currently there are not plans to change the integration |
no need to keep this open for now |
hi,
currently testing backup / restore on Centos6 and RHEL 6 with latest rear release (1.15) It seems a recovered system wont boot if selinux still active. It complains about missing liblkid and fails to mount the root system.
As it stands the issue is caused by selinux after recovery as described here:
https://bugzilla.redhat.com/show_bug.cgi?id=451503
booting the recovered system with selinux=0 in grub works fine :)
The text was updated successfully, but these errors were encountered: