Hi Community, I have installed MySQL in Redhat Linux, however, MySQL is not getting started. I'm getting some error when I check journalctl. How can fix this issue?

Thank you for your help.

How did you install? A redhat rpm should have the selinux policies installed by default.

The best way to test is to turn off Selinux using "setenforce 0" and trying again. If you want to use this version, you will need to generate the policy probably using audit2allow.

Actually installed by someone else, and she's not with the company anymore. I'm not sure how she installed it, I think she downloaded the zip file. Not sure though. However, I can start it in permissive mode.
Howe audit2allow works? Can you help to provide the commands? I'm a newbie.
Thank you for your help.

Ok, so since this has probably never worked, why not just delete the existing MySQL installation, and install it from the RHEL repositories, which do everything for you, to make sure it's correct?? Since you're a 'newbie', that would be the far safest/easiest way to do it...and since you're using RHEL, you can easily just call Red Hat support for everything. How did you get into the Linux admin role, being a 'newbie'??

You don't say what version of RHEL you're using, but did you look at the (extensive) RHEL documentation??
https://access.redhat.com/documentat...ixing_problems

I meant newbie to SELinux. Actually I have been working as a windows administrator, and recently I started learning Linux. I can configure the webserver from different directories easily, however, MySQL is the first time looking into it. I added the SELinux label whatever is mentioned in MySQL documentation. It didn't work, that's why I thought community members have any idea about the issue.

Ok, so go back to the solution offered: install it from the RHEL repositories, and contact RHEL support for help, since your organization is paying for RHEL. One command, and it's installed and selinux is configured. Doubtful it was installed from a .ZIP file, since that's typically for Windows...most Linux software will come in tar.gz files, but what makes you think the previous admin installed it from a compressed file??

Have you read the documentation on how to use the audit command mentioned? Or tried the command for selinux enforce to see if that gets it going?? And now you're mentioning a web-server...how is that fitting in with MySQL now? Because if you don't install things from the repositories, you are not going to get the updates/bug-fixes, and be left with an unstable system, that takes a LOT more to maintain and administer. Would you tell a Windows admin to install random stuff from ZIP's, and not stay up to date??

I just guessed they installed it from a zip file. I haven't seen any MySQL log in /var, I thought they just untar the file from that custom directory which is in /mysql. They might installed it from the repository.
I haven't installed webserver, I was just telling you that I know how to configure SELinux for a webserver.

Ok, so if you know how to configure one service, apply that exact same procedure for MySQL. And have you (again) contacted RHEL support for help, or done any research?? Putting "rhel selinux mysql" into a search-engine pulls up quite a bit.
https://dev.mysql.com/doc/refman/8.0...-policies.html

You can look in /var/log/audit/audit.log, and run scripts to create a selinux policy to allow whatever mysql is doing. I've done this before (like 2 hours ago) but I am no expert on this so I can't give advice but there are plenty of tutorials on it.

This is if you don't want to move to a rhel version.

I second the call to Red Hat and having them help getting MySQL started. My worry about just clobbering the existing installation is that the OP's predecessor may have gotten the database up and running and it might contain data that ought to be exported before a re-installation from an RHEL rpm. Just bein' cautious.

You need to backup/export the data preferably in text form. That way, you can always import it. If you aren't doing this now, do this now. You can't back it up using "normal" tools if the database is running.

You need the db to be running, but not being changed ie used by anybody, then use the mysqldump tool.
This does actually work if the db is being used, but ofc it means the data may have changed as soon as it (mysqldump) releases the locks, so you won't know exactly what point in time data you have.

I applied SELinux policy "bin_t" on mysqld and that resolved the issue. Initially, I applied the SELinux policy "mysqld_db_t" on the directory and all files and sub-directory. Hope it helps someone if they are having the same issue.