Job for mysql service failed because the control process exited with error code

How fix permanently: Job for mysql.service failed because the control process exited with error code

I am working with Ubuntu 18.04 and MySQL Server — 8.0.18

Suddenly today MySQL can’t start anymore

With the sudo service mysql status command appears:

With the sudo service mysql restart command appears:

Following and executing the two suggested commands:

• systemctl status mysql.service
• journalctl -xe

Therefore: sudo systemctl status mysql.service

And with journalctl -xe

I followed the solution about this post:

I used the innodb_force_recovery = 10 (ten), it playing, because with 1 and 2 did not work

Therefore with the sudo systemctl start mysql command is possible start the server. I can see all the data and users saved in peace.

Now through the sudo systemctl status mysql command I get

Until this point would has no sense this post, but if I do either Alpha or Beta steps:

the same problem happens again.

Therefore now is mandatory keep the innodb_force_recovery = 10 , otherwise it returns to the same problem

Warning:

The correct range is from 1 to 6, I am assuming 10 is «interpreted» how the maximum value (6)

Is there a way to configure something and remove innodb_force_recovery ? It to return to the normal or old configuration where all worked fine (without innodb_force_recovery )

Note the final content of /var/log/mysql/error.log is

I am working with VirtualBox — Ubuntu is a guest. It had been working for more of 3 months, now suddenly this situation appeared.

More Info:

One

As requested desertangels

Two

Executing cat /etc/mysql/mysql.conf.d/mysqld.cnf

Three

BTW: just in case, with mysql -u root -p appears:

Источник

MySQL not starting due to errors

I’m trying to get MySQL to work on my ubuntu server. It seems I ran into some errors and I’ve been trying to sort them out myself but I haven’t had any success. I ran:

After the installation I tried to make sure it was turned on by doing sudo service mysql start which ended up in it saying

Job for mysql.service failed because the control process exited with error code. See «systemctl status mysql.service» and «journalctl -xe» for details.

I ran sudo service mysql status Which returned this:

If someone could help with this I would appreciate it.

Here is the output of journalctl -xe after trying to start MySql:

I put it all into hastebin so the gazillion lines can actually fit into there :p

I went by the steps and during the re-install I noted these:

AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld in /etc/apparmor.d/usr.sbin.mysqld at line 9: Could not open ‘abstractions/mysql’.

E: Sub-process /usr/bin/dpkg returned an error code (1)

W: Operation was interrupted before it could finish.

Output of MySQL Install Command:

Output of sudo apt -o Dpkg::Options::=»—force-confmiss» install —reinstall mysql-server :

3 Answers 3

As described here after installing mysql-server using:

You should configure mysql:

Afterwards tests your configuration using:

If MySQL isn’t running, you can start it with sudo systemctl mysql start .

For an additional check, you can try connecting to the database using the mysqladmin tool, which is a client that lets you run administrative commands. For example, this command says to connect to MySQL as root (-u root), prompt for a password (-p), and return the version.

Firstly, you want to stop using the service structure and start getting used to systemctl structure instead

Secondly, systemd can give you some better information if you check the logging via its tool journalctl :

This should give you more information about what happened. The «status» will not necessarily tell you the events leading to the error.

The problem with starting the server was a protection by Apparmor to protect against unauthorized applications running.

This remedied by added the command line:

Other important components were ensuring against conflicts from the installed mysql-server, but purging it and reinstalling it. Ensuring the defaults are set by removing what’s failing and reinstalling what’s tested from the repository, which works.

During the process of the reinstall (in this case) there was a problem with the perl script which is part of the install routine. Fixing those problems and errors assisted in the reinstall.

The details of the issues that were causing problems were presented at to the concole of which, removing each of the issues was a step by step recovery.

Источник

mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

Ошибка запуска Job for mysql.service failed

Если у вас упала база данных MySQL и при запуске «service mysql restart» пишет такую ошибку:

Job for mysql.service failed because the control process exited with error code. See «systemctl status mysql.service» and «journalctl -xe» for details.

При выполнении команды

мы выдим такую строку:

mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

Решение проблемы mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

Добавляем в файл конфигурации /etc/mysql/my.cnf (в зависимости от вашей конфигурации my.cnf и ОС может иметь другое местоположение) строку:

Сохраняем файл my.cnf и выполняем команду:

Если это не сработало, то нужно увеличить число «innodb_force_recovery = 2» или 3, и снова запустить обновления конфигурации «sudo systemctl start mysql».

После успешного выполнения нужно закомментировать строку innodb_force_recovery и перезагрузиться (некоторые операции не разрешены в режиме принудительного восстановления).

Для более детальной консультации обращайтесь в нашу техническую поддержку, где опытные системные администраторы помогут восстановить сервер или заказывайте хостинг сайта в нашей компании уже с включенной полной поддержкой

Источник

mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

Ошибка запуска Job for mysql.service failed

Если у вас упала база данных MySQL и при запуске «service mysql restart» пишет такую ошибку:

Job for mysql.service failed because the control process exited with error code. See «systemctl status mysql.service» and «journalctl -xe» for details.

При выполнении команды

мы выдим такую строку:

mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

Решение проблемы mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

Добавляем в файл конфигурации /etc/mysql/my.cnf (в зависимости от вашей конфигурации my.cnf и ОС может иметь другое местоположение) строку:

Сохраняем файл my.cnf и выполняем команду:

Если это не сработало, то нужно увеличить число «innodb_force_recovery = 2» или 3, и снова запустить обновления конфигурации «sudo systemctl start mysql».

После успешного выполнения нужно закомментировать строку innodb_force_recovery и перезагрузиться (некоторые операции не разрешены в режиме принудительного восстановления).

Для более детальной консультации обращайтесь в нашу техническую поддержку, где опытные системные администраторы помогут восстановить сервер или заказывайте хостинг сайта в нашей компании уже с включенной полной поддержкой

Источник

Failing to start mysql.service for MySQL 5.6 on Ubuntu 16.04

After following the instructions in this post on how to install MySQL 5.6 over an existing 5.7 installation on Ubuntu 16.04 I had multiple problems starting the service.

First this happened:

Which was solved by running systemctl unmask mysql.service . However then I repeatedly had this message:

Inspecting systemctl status mysql.service showed:

3 Answers 3

After Downgrading MySQL version I am also facing this try following command

The fix for this contained multiple steps including different debug logs and then following clues in those logs. I’m documenting them to help others — your problems might be different but this process should help to discover what’s wrong:

Firstly journalctl -xe contains a lot more information. In my case it contained:

This could be fixed with vi /etc/apparmor.d/usr.sbin.mysqld and adding lines for:

An interesting point is that it needs a separate line for a directory and wildcard files within it — this can be common for some unix applications but not all so might trip you up.

Once all the apparmor changes were done the system still wouldn’t start, and this time the journalctl -xe command yielded nothing useful.

I was then able to run sudo -u mysql mysqld to try starting the daemon manually. This showed a failure with InnoDB starting up, but not why.

On a whim I deleted the files /var/lib/mysql/ib_logfile* and ib_binlog and tried again; this time the server started. I was then able to terminate this and run service start mysql which worked.

Separately I deleted /var/lib/mysql/debian-5.7.flag — I am unsure if this helped or would have caused subsequent problems if I had not done so.

Hopefully this example helps somebody; please feel free to add other answers along a similar line if you encountered different problems with this process.

Источник