On Fri, 2016-02-12 at 15:49 -0500, Bowie Bailey wrote: > On 2/12/2016 3:45 PM, Sebastian Arcus wrote: > > On 12/02/16 20:31, Antony Stone wrote: > > > On Friday 12 February 2016 at 17:29:23, Sebastian Arcus wrote: > > > > > > > As per advice from this list, I have been re-using my bayes > > > > databases on > > > > several different servers running SA. On one of the servers > > > > though, the > > > > database is not accepted. > > > Are the servers all the same distro, release and version? > > > > > > Are they all up to date (or at least, all equally up to date as > > > each > > > other)? > > No - there are definitely variations in kernel versions and other > > software versions. So far I have only made sure the SA version is > > the > > same. Any possible culprit comes to mind in terms of a certain > > library > > or software that might cause this? > > > > The thing that always comes to mind when I see strange permission > problems is selinux. If you have it active, check to see if selinux > is blocking access to the file for some reason. > In my experience, as somebody who doesn't always leave files in their default positions, changing the absolute paths of files used by standard servers will almost always upset SELinux.
For starters, set Selinux to permissive mode and reboot. Its default is Enforcing more and a reboot is accept a mode change. Running in permissive mode prevents SElinux from applying its rules to running processes but still generates violation reports. These are sent posted to the bug reporting tool. I'm running Fedora with XFCE, so names and actions will probably differ for other distros. Fedora with XFCE calls this tool Abrt and makes violations accessible from the XFCE menu bar. The violation report shows text explaining what the problem is and also suggesting what command should be run to fix it. Open a terminal window and run this command by copying and pasting it, preceded by 'sudo '. This usually fixes problems caused by moving files to a nonstandard location. Di this for all the reported violations. Check by rebooting again. If all is now clean, run in permissive mode for another few days to see that you've got the lot. If more errors are reported, rince, wash and repeat. When no more Selinux errors are appearing you can either continue running in permissive mode or switch back to enforcing mode and reboot to let that take effect. HTH Martin
