读写分离遇到的问题

本文记录了一次使用MySQL Proxy进行读写分离时遇到的问题及解决过程。主要问题为配置文件中Lua脚本路径错误导致Proxy启动失败,并给出了通过查看日志定位问题及最终通过kill命令结束异常进程的方法。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

在做读写分离的【proxy开启时,我把lua脚本的位置写错了;然后一致执行

[root@server1 mysql-proxy]#  /usr/local/mysql-proxy/bin/mysql-proxy --defaults-file=/usr/local/mysql-proxy/conf/mysql-proxy.conf

一直日志有错误

2017-10-21 11:45:16: (message) chassis-unix-daemon.c:136: [angel] we try to keep PID=1341 alive
2017-10-21 11:45:16: (critical) plugin proxy 0.8.5 started
2017-10-21 11:45:16: (critical) plugin admin 0.8.5 started
2017-10-21 11:45:16: (critical) last message repeated 1 times
2017-10-21 11:45:16: (critical) network-mysqld-lua.c:234: lua_load_file(/usr/local/mysql-proxy/share/doc/mysql-proxy/lua/rw-splitting.lua) failed: lua-scope.c:241: stat(/usr/local/mysql-proxy/share/doc/mysql-proxy/lua/rw-splitting.lua) failed: No such file or directory (2)
2017-10-21 11:45:16: (critical) network-socket.c:492: bind(172.25.28.1:3306) failed: Address already in use (98)
2017-10-21 11:45:16: (critical) chassis-mainloop.c:270: applying config of plugin proxy failed
2017-10-21 11:45:16: (critical) mysql-proxy-cli.c:599: Failure from chassis_mainloop. Shutting down.
2017-10-21 11:45:16: (message) Initiating shutdown, requested from mysql-proxy-cli.c:600
2017-10-21 11:45:16: (message) shutting down normally, exit code is: 1
2017-10-21 11:45:16: (message) chassis-unix-daemon.c:176: [angel] PID=1341 exited normally with exit-code = 1 (it used 1 kBytes max)
2017-10-21 11:45:16: (message) Initiating shutdown, requested from mysql-proxy-cli.c:273
2017-10-21 11:45:16: (message) shutting down normally, exit code is: 1

最后才知道执行上面那条,命令压根没有运行,这种proxy调用模块的不像其他的可以重启重新加载日志:所以我们应当kill掉原来的进程:

 killall mysql-proxy
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值