Based on the results, my guess is somebody already had this same type of issue but disabled it with:[code]setenforce 0[/code] on the server, which is why it was working. On the next reboot, because it wasn’t disabled before, it just reset to enforcing.
