Здравствуйте, подскажите пж как исправить ошибку [FAIL] Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
1. debian 7 система чистая только по ставил.
2. mysql-server mysql-client
3. apache2
4. php5 php5-mysql
логи пустые выполнив команду mysqld_safe —log-error=/var/log/mysql.err
150911 14:58:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150911 14:58:17 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150911 14:58:17 [Note] /usr/sbin/mysqld (mysqld 5.5.44-0+deb7u1) starting as process 28559 .
150911 14:58:17 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150911 14:58:17 [Note] Plugin ‘FEDERATED’ is disabled.
150911 14:58:17 InnoDB: The InnoDB memory heap is disabled
150911 14:58:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150911 14:58:17 InnoDB: Compressed tables use zlib 1.2.7
150911 14:58:17 InnoDB: Using Linux native AIO
150911 14:58:17 InnoDB: Initializing buffer pool, size = 128.0M
150911 14:58:17 InnoDB: Completed initialization of buffer pool
150911 14:58:17 InnoDB: highest supported file format is Barracuda.
150911 14:58:18 InnoDB: Waiting for the background threads to start
150911 14:58:19 InnoDB: 5.5.44 started; log sequence number 1595685
150911 14:58:19 [Note] Server hostname (bind-address): ‘127.0.0.1’; port: 3306
150911 14:58:19 [Note] — ‘127.0.0.1’ resolves to ‘127.0.0.1’;
150911 14:58:19 [Note] Server socket created on IP: ‘127.0.0.1’.
150911 14:58:19 [ERROR] Can’t start server: Bind on TCP/IP port: Cannot assign requested address
150911 14:58:19 [ERROR] Do you already have another mysqld server running on port: 3306 ?
150911 14:58:19 [ERROR] Aborting
150911 14:58:19 InnoDB: Starting shutdown.
150911 14:58:19 InnoDB: Shutdown completed; log sequence number 1595685
150911 14:58:19 [Note] /usr/sbin/mysqld: Shutdown complete
150911 14:58:19 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
- Вопрос задан более трёх лет назад
- 4209 просмотров
Нашел решение даже если изменить порт не будет работать и на порту никто не весит
I am running ubuntu server. When I tried to login to mysql(which was running),I got the following error
But mysqld.sock file doesn’t exist inside /var/run/mysqld folder. On executing ps aux | grep mysql command,I realized that mysql server was not running.
I then tried to restart mysql server using
But,the start process failed in all 3 cases. /var/log/mysql/mysql.log and /var/log/mysql/mysql.err files are empty.
But /var/log/error.log shows following information:
10 Answers 10
Open a terminal( Ctrl + Alt + t ) and do the following:
and comment out the line record_buffer=64M in /etc/mysql/my.cnf [1]
and then restart msyql using:
This solved my problem:
chown -R mysql /var/run/mysqld
I solved the problem in the following way:
In another context, I faced it because the mysql daemon failed to start. So start daemon with command — mysqld start and then try to start the service.
I had the same error message and the same emptyness in the log files. In my config-file (my.cnf) I had specified that I wanted to use myisam tables, by adding this line in the [mysqld]-section:
After upgrading mysql it seems this causes mysql not to start. I have changed this to:
and now everything works fine.
Increasing the available RAM by adding new Swap space might also help. Steps are here
Make sure that you create /swapfile of the size smaller than the available space shown by
For example for me output of df- h was:
So I created using 2 G
And then just start the service
Hope this helps. All the best.
Check if in all /etc/rc1.d . /etc/rc5.d the mysql script starts with S (Ex S10mysql) and not K AS K10mysql.
Explanation: K prefix loads with stop, kind of kill service; and S prefix starts with start parameter.
In my case, it was a space issue. Check if you have enough space left.
from /var/log/mysql/error.log I got some hints from two lines:
I could see that it is a space issue.
From here, I could see that there was not enough space left on the virtual server /dev/mapper/server1—osticket—vg-root 8.3G 7.9G 0 100% / . And I thought on either migrating or increasing the virtual drive, but I decided to remove unnecessary files first.
So, had to clean up cache and files that were not needed:
Then, do not forget to remove the mysql corrupted log files afterwards. They would be generated again when you restart mysql
Check your mysql server service and it is probably up and running
I am facing serious issue. My hard disk was extremely full that 0 bytes available. I tried to empty the trash bin but it hanged. I restarted the system. But it failed. It gives this messages:
The cursors is blinking but I can’t type anything.
Is there any hope that I boot the system under sort of last known good configurations or safe mode like in Windows?
I made hardware test and the device is healthy. Please help me disable MySQL or boot my system I just need my data because lots of work there.
EDIT:
The device company can not help with data backup. They can only format and install the system. I need my data.