relocate /var/lib/mysql based on DATA_DIR variable

SafeAF / enterprise-log-search-and-archive

Automatically exported from code.google.com/p/enterprise-log-search-and-archive

0 stars 0 forks source link

relocate /var/lib/mysql based on DATA_DIR variable #95

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1.Assume two physical storage devices (Boot / Data)
2.If DATA_DIR is pointing to the Data storage device, /var/lib/mysql is still 
on the Boot device
3. simply moving and symlinking the directory is insufficient and is broken by 
seLinux
4. mysql.sock also needs to be dealt with
5. there were issues with permissions after moving the databases that may be 
avoided upon initial creation.

What is the expected output? What do you see instead?
After a few days, the server falls over, potentially corrupting databases

What version of the product are you using? On what operating system?
latest as of Feb 1st

Original issue reported on code.google.com by m...@millertwinracing.com on 12 Feb 2013 at 9:52

GoogleCodeExporter commented 8 years ago

If SELinux were to be properly configured to allow the symlink, and the 
mysql.sock were moved via my.cnf, are the permission issues file system or 
SELinux related?

Original comment by mchol...@gmail.com on 13 Feb 2013 at 4:01

GoogleCodeExporter commented 8 years ago

I'm pretty sure it's the new location that needs to be white listed with
SElinux, not the symlink. Here's a walk through
http://crashmag.net/change-the-default-mysql-data-directory-with-selinux-enabled

I had another issue that I thought was file system ACL related, but I'm not
sure enough to commit it to the bug report.

I DID have to adjust both SElinux and file perms, but I don't have
specifics.
If the file locations in the my.cnf file are created at the right point in
the process, it may set it all up correctly in the first place.

On Tuesday, February 12, 2013, wrote:

Original comment by m...@millertwinracing.com on 13 Feb 2013 at 4:09

GoogleCodeExporter commented 8 years ago

I think this is a good thing to do, but I'm going to change it over to a 
feature request as I've got a few other more pressing bugs to fix first, and 
there's a workaround for the moment.

Original comment by mchol...@gmail.com on 15 Feb 2013 at 11:14

Changed state: Accepted
Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 8 years ago

Works for me, I solved it. :)

On Fri, Feb 15, 2013 at 4:14 PM, <
enterprise-log-search-and-archive@googlecode.com> wrote:

Original comment by m...@millertwinracing.com on 16 Feb 2013 at 2:24