MySQL Bind on unix socket: Address already in use

内容导读

互联网集市收集整理的这篇技术教程文章主要介绍了MySQL Bind on unix socket: Address already in use，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含2933字，纯文字阅读大概需要5分钟。

内容图文

场景

[root@localhost bin]# ./mysqld
2020-01-15 17:52:02 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-01-15 17:52:02 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2020-01-15 17:52:02 0 [Note] ./mysqld (mysqld 5.6.44) starting as process 90367 ...
2020-01-15 17:52:02 90367 [Note] Plugin 'FEDERATED' is disabled.
2020-01-15 17:52:02 90367 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-01-15 17:52:02 90367 [Note] InnoDB: The InnoDB memory heap is disabled
2020-01-15 17:52:02 90367 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-01-15 17:52:02 90367 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-01-15 17:52:02 90367 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-01-15 17:52:02 90367 [Note] InnoDB: Using Linux native AIO
2020-01-15 17:52:02 90367 [Note] InnoDB: Not using CPU crc32 instructions
2020-01-15 17:52:02 90367 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-01-15 17:52:02 90367 [Note] InnoDB: Completed initialization of buffer pool
2020-01-15 17:52:02 90367 [Note] InnoDB: Highest supported file format is Barracuda.
2020-01-15 17:52:02 90367 [Note] InnoDB: 128 rollback segment(s) are active.
2020-01-15 17:52:02 90367 [Note] InnoDB: Waiting for purge to start
2020-01-15 17:52:02 90367 [Note] InnoDB: 5.6.44 started; log sequence number 18755961
2020-01-15 17:52:02 90367 [Note] Server hostname (bind-address): '*'; port: 3306
2020-01-15 17:52:02 90367 [Note] IPv6 is available.
2020-01-15 17:52:02 90367 [Note]   - '::' resolves to '::';
2020-01-15 17:52:02 90367 [Note] Server socket created on IP: '::'.
2020-01-15 17:52:02 90367 [ERROR] Can't start server : Bind on unix socket: Address already in use
2020-01-15 17:52:02 90367 [ERROR] Do you already have another mysqld server running on socket: /tmp/mysql.sock ?
2020-01-15 17:52:02 90367 [ERROR] Aborting

排查过程

1）管道文件已经存在

2020-01-15 17:52:02 90367 [ERROR] Can't start server : Bind on unix socket: Address already in use
2020-01-15 17:52:02 90367 [ERROR] Do you already have another mysqld server running on socket: /tmp/mysql.sock ?

2）查看文件属性以及查看进程占用

[root@localhost tmp]# file mysqld.sock
mysqld.sock: socket

[root@localhost tmp]# fuser /tmp/mysql.sock

没有发现任何进程占用，说明该文件不是由mysqld进程创建的，并且没有任何的服务占用该管道文件，该管道文件一般用于本地的mysql服务器和客户端通信的通道。默认情况下，mysql主进程在启动的时候创建该文件，退出的时候，会删除该文件，通过删除该文件，解决上面的问题。

3）启动mysql服务，查看占用过程

[root@localhost tmp]# fuser /tmp/mysql.sock
/tmp/mysqld.sock:    76533
[root@localhost tmp]# lsof /tmp/mysql.sock
COMMAND   PID  USER   FD   TYPE             DEVICE SIZE/OFF    NODE NAME
mysqld  76533 mysql   22u  unix 0x00000000f901123c      0t0 8234599 /tmp/mysql.sock

内容总结

以上是互联网集市为您收集整理的MySQL Bind on unix socket: Address already in use全部内容，希望文章能够帮你解决MySQL Bind on unix socket: Address already in use所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。

内容备注

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。

内容手机端

---