Ошибка process already exists

Learn how to fix the “A mysqld process already exists” Error. Our MySQL Support team is here to help you with your questions and concerns.

“A mysqld process already exists” Error – Resolved

If you have been running into the following error message, you have come to the right place.

a mysqld process already exists

This error often occurs when we try to start the MySQL server, but there is already an instance of the MySQL server running on the system.

In other words, the error lets us know that another MySQL process is already running and occupying the required resources.

We can address this issue with these steps:

1. First, we have to use system-specific commands to verify if there are any running MySQL processes. For example, we can use this command on Linux:

   ps aux | grep mysqld

2. Next, we can locate a running MySQL process and stop it before starting a new one.
   The command to stop the MySQL process depends on our operating system and how we have installed MySQL.

   For instance,

   • On Linux with systemd:

     sudo systemctl stop mysql
     Or
     sudo systemctl stop mysqld

   • On macOS with Homebrew:

     brew services stop mysql

3. After we stop the MySQL process, we can verify if it has actually stopped by rechecking the running processes as seen in step 1.
4. Now that we are sure no other MySQL processes are running, we can try starting the MySQL server again.
   • On Linux with systemd:

     sudo systemctl start mysql
     Or
     sudo systemctl start mysqld

   • On macOS with Homebrew:

     brew services start mysql

5. Next, we have to check the status of MySQL to ensure it is running correctly.
   • On Linux with systemd:

     sudo systemctl status mysql
     Or
     sudo systemctl status mysqld
   • On macOS with Homebrew:

     brew services list

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

To conclude, our Support Techs demonstrated how to resolve the “A mysqld process already exists” Error

I’m using mariaDB.
Basically everytime I start it, it tells me a mysqld process already exists.
Why do I have to run sudo apachectl start for mysql to work?
Shouldn’t I only need mysql.server start?

mysql.server restart
Shutting down MySQL
.. SUCCESS!
Starting MySQL
.171102 15:59:35 mysqld_safe Logging to '/usr/local/var/mysql/****.err'.
171102 15:59:35 mysqld_safe A mysqld process already exists
SUCCESS!

And a related problem is that when I edit etc/my.cnf it doesn’t do anything.
I just know I’m doing something wrong, but I can’t see what.

edit:
After doing mysql.server stop, then ps aux, this is what I get:
`

drewson           9625   0.0  0.0  2466636   2756 s001  S+    3:55pm  0:00.59 mysql -u root -p --max_allowed_packet=1073741824 -D hive
drewson          10235   0.0  0.0  2442020   1936 s000  S+    4:36pm   0:00.00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn mysql
drewson          10186   0.0  1.3  2969520 108876   ??  S     4:35pm   0:00.26 /usr/local/opt/mariadb/bin/mysqld --basedir=/usr/local/opt/mariadb --datadir=/usr/local/var/mysql --plugin-dir=/usr/local/opt/mariadb/lib/plugin --log-error=/usr/local/var/mysql/drewson.err --pid-file=drewson.pid
drewson          10105   0.0  0.0  2444660   2376   ??  S     4:35pm   0:00.02 /bin/sh /usr/local/opt/mariadb/bin/mysqld_safe --datadir=/usr/local/var/mysql`

And here’s info from my err log:

2017-11-02 16:35:05 140735735079872 [ERROR] mysql.user has no `Event_priv` column at position 29
2017-11-02 16:35:05 140735735079872 [ERROR] Incorrect definition of table mysql.event: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTION','PAD_CHAR_TO_FULL_LENGTH'), found type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
2017-11-02 16:35:05 140735735079872 [ERROR] mysqld: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2017-11-02 16:35:05 140735735079872 [Note] Reading of all Master_info entries succeded
2017-11-02 16:35:05 140735735079872 [Note] Added new Master_info '' to hash table
2017-11-02 16:35:05 140735735079872 [Note] /usr/local/opt/mariadb/bin/mysqld: ready for connections.
Version: '10.2.10-MariaDB'  socket: '/tmp/mysql.sock'  port: 3306  Homebrew`

# killall mysqld mysqld_safe

# ps aux | grep mysqld

If you still able to see more than run this command:

killall -9 mysqld mysqld_safe

0

1