👀 Views: 60 💬 Answers: 1 📅 Created: 2025-06-08

mysql fedora service bash

I've tried everything I can think of but I'm trying to debug Hey everyone, I'm running into an issue that's driving me crazy... After upgrading my Fedora 38 system, I'm working with an scenario where the MySQL service fails to start. The behavior message I'm getting in the logs is: `InnoDB: Unable to lock ./ibdata1 which is in use by another process`. I've checked that there are no other MySQL instances running, and the PID file located at `/var/lib/mysql/mysql.pid` is missing. I've tried restarting the machine and stopping any lingering processes that might be using the database files, but the scenario continues. I ran the following command to check for any MySQL-related processes: ```bash ps aux | grep mysql ``` This returned no results, indicating that the service is not running. I've also looked at the MySQL behavior log located at `/var/log/mysqld.log`, and it shows the same locking behavior. I tried running `mysqld_safe` manually: ```bash mysqld_safe --datadir=/var/lib/mysql & ``` But I still get the same locking scenario. The directory permissions for `/var/lib/mysql` seem correct, and I verified that the `mysql` user has the necessary access. I even attempted to change the ownership back just to be safe: ```bash sudo chown -R mysql:mysql /var/lib/mysql ``` What more can I do to resolve this locking scenario and get MySQL running again? Any insights would be greatly appreciated! For context: I'm using Bash on Windows. Has anyone else encountered this? I'm working with Bash in a Docker container on Windows 10. What am I doing wrong?