Display MoreHi gang, I keep getting this error message every time I boot up.
SELinux :could not open policy file <= /etc/selinux/targeted/policy/policy.33: No such file or directory.
How can I fix this problem? I searched on Google and couldn't find any solution.
Any help would be great.
Thanks.
What does this have to do with OMV?
Hi KM0201 , I get this error message when I boot up in my OMV NAS. Never had that message appear before.
Uh... you're getting an error about SELinux (which I'm nearly certain is RH based), on OMV (which is Debian based)?
Is it causing the server to fail to boot?
Uh... you're getting an error about SELinux (which I'm nearly certain is RH based), on OMV (which is Debian based)?
SELinux is a RH (and it's derivitives) based thing. Essentially it is the RH alternate to the debian based apparmor, but it is a lot more restrictive and works in reverse in that it is a block access unless set otherwise kind of policy, while apparmor is more along the lines of allow access unless set otherwise.
QuoteNo it's not. I'm just baffled as to why I'm getting this error message after my server shutdown due to a power outage. When I rebooted, I started getting this message.
SELinux does not exist on Debian. Did you install anything natively that didn't come from the debian or OMV repos, like building something from source?
It does
SELinux/Setup - Debian Wiki
Selinux is in my OMV
$ dpkg -l | grep selinux
ii libselinux1:amd64 3.1-3 amd64 SELinux runtime shared librariesInteresting,
You learn something new every day. I don't know when that snuck in there exactly, but it is either not fully active/installed by default as that link suggests or so unobtrusive in debian I didn't even know it's there.
Try dealing with on on a RH based system and you will see why I thought so. I recently set up a system based on Rocky Linux 8, which is essentially an independent continuation of the now dead RH based CentOS project. The Selinux implementation on it would not even allow a samba share outside a user home directory. I managed to "relabel files" to allow for it, but even the official documentation regarding the samba setup outside a home directory was incomplete. After about 3 hours of going around in circles, re-installing and internet searching, I finally found an obscure post from someone that had one additional step in the process posted and it all of a sudden worked.
I later spoke to the supplier of the product and they basically told me that they often disable selinux because it is such a pain in the ass, unless the system is going into an installation where extreme security is required.
they often disable selinux because it is such a pain in the ass,
We have selinux disabled on all dev systems at work because of this.
SELinux is a RH (and it's derivitives) based thing. Essentially it is the RH alternate to the debian based apparmor, but it is a lot more restrictive and works in reverse in that it is a block access unless set otherwise kind of policy, while apparmor is more along the lines of allow access unless set otherwise.
SELinux does not exist on Debian. Did you install anything natively that didn't come from the debian or OMV repos, like building something from source?
Hi BernH, I did not install anything that required SELinux.
We have selinux disabled on all dev systems at work because of this.
Hi ryecoaaron, is there a way I can find out why it got installed and how I can remove this line at boot up?
Thanks
is there a way I can find out why it got installed and how I can remove this line at boot up?
Maybe. No idea what you have installed or done with your system. What is the output of:
sudo zgrep selinux /var/log/apt/*
dpkg -l | grep -E selinux
Removing the packages should remove the line at boot. Just have to be careful what it might uninstall.
Maybe. No idea what you have installed or done with your system. What is the output of:
sudo zgrep selinux /var/log/apt/*
dpkg -l | grep -E selinux
Removing the packages should remove the line at boot. Just have to be careful what it might uninstall.
I ran the command sudo zgrep selinux /var/log/apt/* and there are pages and pages of packages. Is this normal?
Also, the result from this command dpkg -l | grep -E selinux is ii libselinux1:amd64 3.1-3 amd64 SELinux runtime shared libraries
I ran the command sudo zgrep selinux /var/log/apt/* and there are pages and pages of packages. Is this normal?
Since I can't see them, I can't tell you. Cut&paste them into a file and attach the file.
Also, the result from this command dpkg -l | grep -E selinux is ii libselinux1:amd64 3.1-3 amd64 SELinux runtime shared libraries
I have that installed on my system and don't have the issue. Removing that package will remove nginx which will remove omv.
All of that output just shows the package being updated. And since it is installed by default, this is expected. I can't say how your system got in this state.
What is the output of: sudo find /etc/selinux/ -type f
Don’t have an account yet? Register yourself now and be a part of our community!
