【原创】系统宕机导致flare db 因为临时文件flare.xml 损坏不能启动故障排除记录

【原创】系统宕机导致flare db 因为临时文件flare.xml 损坏不能启动故障排除记录
/db/flare/flare/bin/flared --daemonize --data-dir /db/flare/data/proxy/ --index-server-name 127.0.0.1 --index-server-port 12120 --server-name 127.0.0.1 --server-port 11211
/db/flare/flare/bin/flared --daemonize --data-dir /db/flare/data/master1/ --index-server-name 127.0.0.1 --index-server-port 12120 --server-name 127.0.0.1 --server-port 11212  
/db/flare/flare/bin/flared --daemonize -f /db/flare/flare/etc/flare-proxy.conf
 
data-dir = /db/flare/data/proxy
index-server-name = localhost
index-server-port = 12120
log-facility = local1
server-name = localhost
server-port = 11211
 
1.查看flare日志:
[flare@server logs]# vi /etc/syslog.conf

# falre logs
local0.*                                                /opt/logs/flare-index.log
local2.*                                               /opt/logs/flare-master.log
local1.*                                               /opt/logs/flare-proxy.log
 
 
[flare@server flare]$ cd /opt/logs/
[flare@server logs]$ ll
总计 15836
-rw------- 1 flare flare 11889779 09-10 10:16 flare-index.log
-rw------- 1 flare flare    23490 09-04 17:15 flare-master.log
-rw------- 1 flare flare  4270801 09-10 09:55 flare-proxy.log
 
 
分析日志查询为啥起不起来。

[flare@server logs]# tail -f flare-proxy.log
 
2.查看端口是否被占用
[flare@server logs]# lsof -i:11212
[flare@server logs]# lsof -i:11211
[flare@server logs]# lsof -i:11210

3.查看tmp临时目录文件是否正常
vi /db/flare/tmp/flare.xml
发现改文件损坏,从备份程序拷贝
cp /opt/flare/tmp/flare.xml /db/flare/tmp/


启动成功

你可能感兴趣的:(【原创】系统宕机导致flare db 因为临时文件flare.xml 损坏不能启动故障排除记录)