Rsync 故障排查整理(经典)

Rsync 故障排查整理
Rsync服务常见问题汇总讲解:

1 客户端的错误现象:No route to host
rsync服务端开启的iptables防火墙

[[email protected] tmp]# rsync -avz /etc/hosts [email protected]::backup

rsync: failed to connect to 172.16.1.41: No route to host (113)

rsync error: error in socket IO (code 10) at clientserver.c(124) [sender=3.0.6]

异常问题解决:

   关闭rsync服务端的防火墙服务(iptables)

   [[email protected] mnt]# /etc/init.d/iptables stop

   iptables: Setting chains to policy ACCEPT: filter          [  OK  ]

   iptables: Flushing firewall rules:                         [  OK  ]

   iptables: Unloading modules:                               [  OK  ]

   [[email protected] mnt]# /etc/init.d/iptables status

   iptables: Firewall is not running.

==============================================================================================

2 ERROR: The remote path must start with a module name not a /
rsync客户端执行rsync命令错误:

客户端的错误现象:

[[email protected] tmp]# rsync -avz /etc/hosts [email protected]::/backup

ERROR: The remote path must start with a module name not a /

rsync error: error starting client-server protocol (code 5) at main.c(1503) [sender=3.0.6]

 异常问题解决:

   rsync命令语法理解错误,::/backup是错误的语法,应该为::backup(rsync模块)

==============================================================================================

3 @ERROR: auth failed on module backup

  1. @ERROR: auth failed on module oldboy

    客户端的错误现象:

    [[email protected] tmp]# rsync -avz /etc/hosts [email protected]::backup

Password:

@ERROR: auth failed on module backup

rsync error: error starting client-server protocol (code 5) at main.c(1503) [sender=3.0.6]

异常问题解决:

   1. 密码真的输入错误,用户名真的错误

   2. secrets file = /etc/rsync.password指定的密码文件和实际密码文件名称不一致

   3. /etc/rsync.password文件权限不是600

   4. rsync_backup:123456密码配置文件后面注意不要有空格

   5. rsync客户端密码文件中只输入密码信息即可,不要输入虚拟认证用户名称

==============================================================================================

4 @ERROR: Unknown module ‘backup‘

  1. Unknown module ‘backup‘

[[email protected] tmp]# rsync -avz /etc/hosts [email protected]::backup

@ERROR: Unknown module ‘backup‘

rsync error: error starting client-server protocol (code 5) at main.c(1503) [sender=3.0.6]

 异常问题解决:

   1、 /etc/rsyncd.conf配置文件模块名称书写错误

   2、配置文件中网段限制不对

==============================================================================================

5 Permission denied
[[email protected] tmp]# rsync -avz /etc/hosts [email protected]::backup

Password:

sending incremental file list

hosts

rsync: mkstemp ".hosts.5z3AOA" (in backup) failed: Permission denied (13)

sent 196 bytes received 27 bytes 63.71 bytes/sec

total size is 349 speedup is 1.57

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]

 异常问题解决:

   1. 共享目录的属主和属组不正确,不是rsync

   2. 共享目录的权限不正确,不是755

==============================================================================================

6 chdir failed
[[email protected] tmp]# rsync -avz /etc/hosts [email protected]::backup

Password:

@ERROR: chdir failed

rsync error: error starting client-server protocol (code 5) at main.c(1503) [sender=3.0.6]

异常问题解决:

1. 备份存储目录没有建立

2. 建立的备份存储目录和配置文件定义不一致

[[email protected] backup]# /etc/init.d/xinetd restart

shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

Stopping xinetd: [ OK ]

Starting xinetd: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

                                                       [  OK  ]

说明:如果没有备份存储目录,xinetd服务都不能正确启动

==============================================================================================

7 invalid uid rsync
[[email protected] tmp]# rsync -avz /etc/hosts [email protected]::backup

Password:

@ERROR: invalid uid rsync

rsync error: error starting client-server protocol (code 5) at main.c(1503) [sender=3.0.6]

异常问题解决:

rsync服务对应rsync虚拟用户不存在了

==============================================================================================

8 客户端已经配置了密码文件,但免秘钥登录方式,依旧需要输入密码
password file must not be other-accessible

[[email protected] tmp]# rsync -avz /etc/hosts [email protected]::backup --password-file=/etc/rsync.password

password file must not be other-accessible

continuing without password file

Password:

sending incremental file list

sent 26 bytes received 8 bytes 5.23 bytes/sec

total size is 349 speedup is 10.26

异常问题解决:

rsync客户端的秘钥文件也必须是600权限

==============================================================================================

9 rsync客户端连接慢问题
错误日志输出

2017/03/08 20:14:43 [3422] params.c:Parameter() - Ignoring badly formed line in configuration file: ignore errors

2017/03/08 20:14:43 [3422] name lookup failed for 172.16.1.31: Name or service not known

2017/03/08 20:14:43 [3422] connect from UNKNOWN (172.16.1.31)

2017/03/08 20:14:43 [3422] rsync to backup/ from [email protected] (172.16.1.31)

2017/03/08 20:14:43 [3422] receiving file list

2017/03/08 20:14:43 [3422] sent 76 bytes received 83 bytes total size 349

正确日志输出

2017/03/08 20:16:45 [3443] params.c:Parameter() - Ignoring badly formed line in configuration file: ignore errors

2017/03/08 20:16:45 [3443] connect from nfs02 (172.16.1.31)

2017/03/08 20:16:45 [3443] rsync to backup/ from [email protected] (172.16.1.31)

2017/03/08 20:16:45 [3443] receiving file list

2017/03/08 20:16:45 [3443] sent 76 bytes received 83 bytes total size 349

异常问题解决:

查看日志进行分析

==============================================================================================

10 rsync服务没有正确启动Connection refused (111)
[[email protected] ~]# rsync -avz /etc/hosts [email protected]::backup

rsync: failed to connect to 172.16.1.41: Connection refused (111)

rsync error: error in socket IO (code 10) at clientserver.c(124) [sender=3.0.6]

解决 rsync服务没开启

[[email protected] ~]# rsync --daemon

[[email protected] ~]# ss -lntup |grep rsync

tcp LISTEN 0 5 :::873 :::* users:(("rsync",1434,5))

tcp LISTEN 0 5 :873 :* users:(("rsync",1434,4))

[[email protected] ~]# rsync -avz /etc/hosts [email protected]::backup

Password:

sending incremental file list

hosts

sent 196 bytes received 27 bytes 49.56 bytes/sec

total size is 349 speedup is 1.57

==============================================================================================

11 port 22: Connection refused
环境:本地服务器集群内部传输利用远程ssh 报错

利用(telnet 172.16.1.31 22) 排查服务监听状态后采取的解决方法

[[email protected] ~]# rsync /etc/hosts 172.16.1.31:/tmp

ssh: connect to host 172.16.1.31 port 22: Connection refused

rsync: connection unexpectedly closed (0 bytes received so far) [sender]

rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6]

排错思路:

[[email protected] ~]# ping 172.16.1.31

PING 172.16.1.31 (172.16.1.31) 56(84) bytes of data.

64 bytes from 172.16.1.31: icmp_seq=1 ttl=64 time=0.628 ms

64 bytes from 172.16.1.31: icmp_seq=2 ttl=64 time=0.393 ms

64 bytes from 172.16.1.31: icmp_seq=3 ttl=64 time=1.06 ms

64 bytes from 172.16.1.31: icmp_seq=4 ttl=64 time=0.745 ms

[[email protected] ~]# traceroute 172.16.1.31

traceroute to 172.16.1.31 (172.16.1.31), 30 hops max, 60 byte packets

1 nfs01 (172.16.1.31) 0.597 ms 0.189 ms 0.965 ms

/etc/init.d/iptables status

iptables: Firewall is not running.

[[email protected] ~]#

[[email protected] ~]# netstat -lntup|grep 22

p 0 0 10.0.0.31:22 0.0.0.0:* LISTEN 1187/sshd

故障原因:无法连接

telnet 172.16.1.31 22

解决方法:

[[email protected]]# vim /etc/ssh/sshd_config

#Port 22

#AddressFamily any

#ListenAddress 10.0.0.31 改为 0.0.0.0

#ListenAddress ::

总结:内网传输通过SSH pro 22 表明22端口链接不上

==============================================================================================

12 --passwd-file=/etc/rsync.passwd: unknown option 没有正确输入password文件名
报错:--passwd-file=/etc/rsync.passwd: unknown option

错误案例 本地rsync.password 文件要保持一致缺少字母都会报错

echo "123456">>/etc/rsync.passwd

[[email protected] ~]# chmod 600 /etc/rsync.passwd

[[email protected] ~]# ll /etc/rsync.passwd

-rw------- 1 root root 7 Mar 9 13:47 /etc/rsync.passwd

[[email protected] ~]# rsync -az -P /root/ [email protected]::backup --passwd-file=/etc/rsync.passwd

rsync: --passwd-file=/etc/rsync.passwd: unknown option

rsync error: syntax or usage error (code 1) at main.c(1422) [client=3.0.6]

正确做法:

[[email protected] ~]# echo "123456">>/etc/rsync.password

[[email protected] ~]# chmod 600 /etc/rsync.password

[[email protected] ~]# ll /etc/rsync.password

-rw------- 1 root root 7 Mar 9 13:49 /etc/rsync.password

rsync -az -P /server/files/secure-20161219 [email protected]::backup --password-file=/etc/rsync.password

sending incremental file list

secure-20161219

51053780 100%   14.31MB/s    0:00:03 (xfer#1, to-check=0/1)

rsync: mkstemp ".secure-20161219.lcnuWA" (in backup) failed: Permission denied (13)

sent 2210982 bytes received 27 bytes 491335.33 bytes/sec

total size is 51053780 speedup is 23.09

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]

[[email protected] ~]# ls /backup/

100.log cc.txt optimize-init_sys.sh

anaconda-ks.cfg

  1)可能是服务没有开启

  2)iptables SELinux

  3)本次遇见sshd传输受限 限制了传输的ip(安全)

==============================================================================================

Rsync服务端排错思路
m 查看rsync服务配置文件路径是否正确 /etc/rsyncd.conf

m 查看配置文件例的host allow,host deny,允许的ip网段是否是允许客户端访问的ip网段

m 查看配置文件中path参数里的路径是否存在,权限是否正确(正常应为配置文件中的UUID参数对应的属主和组)

m 查看rsync服务是否启动,端口是否存在 ps -ef netstat -lntup

m 查看iptables防火墙和SELinux是否开启允许rsync服务通过,也可以关闭

m 查看服务端rsync配置文件里的密码权限是否为600 密码文件格式是否正确,正确格式(用户名:密码)文件路径和配置文件里的secrect files 参数对应

m 如果是推送数据,要查看,配置rsyncd.conf 文件中用户是否对模块下目录有可读的权限

==============================================================================================

客户端排错思路
m 查看客户端rsync配置的密码文件是否为600的权限,密码文件格式是否正确,注意:仅需要有密码,并且和服务端的密码一致

m 用telnet链接rsync服务器ip地址873端口,查看服务是否启动(可测试服务端防火墙是否阻挡telnet10.0.0.100 873)

m 客户端执行命令是 rsync -avzP [email protected]::backup/test/test/ --password-file=/etc/rsync.password

m 此命令要记清楚尤其10.0.0.100::backup/test/处的双引号及随后的backup为模块名称

==============================================================================================

原文地址:https://blog.51cto.com/xiyuxingxia/2398024

时间: 2024-10-27 18:11:22

Rsync 故障排查整理(经典)的相关文章

Rsync 12种故障排查及思路

Rsync 故障排查整理 Rsync服务常见问题汇总讲解: ============================================================================================== 1 客户端的错误现象:No route to host rsync服务端开启的iptables防火墙 [[email protected] tmp]# rsync -avz /etc/hosts [email protected]::backup r

虚拟机性能监控与故障排查工具介绍

本文来读书籍<深入理解java虚拟机-JVM高级特性与最佳实践>的阅读笔记,并且对虚拟机性能监控与故障排查一节做了内容整理. 关于导图中的两部分内容还是希望大家能够亲自测试体验下,在网上也有不少的文章介绍,这里摘录几篇个人认为不错的文章,供参考: jstat/jinfo/jstack/jmap命令行工具使用详细介绍 VisualVM 官网介绍及使用说明 使用 VisualVM 进行性能分析及调优 使用VisualVm监控远程Linux服务器java进程 由于在 linux 服务器上面,使用远程

SQL Server 2008性能故障排查(二)——CPU

原文:SQL Server 2008性能故障排查(二)--CPU 承接上一篇:SQL Server 2008性能故障排查(一)--概论 说明一下,CSDN的博客编辑非常不人性化,我在word里面都排好了版,贴上来就乱得不成样了.建议CSDN改进这部分.也请大家关注内容不要关注排版.同时在翻译的过程中本人也整理了一次思路,所以还似乎非常愿意翻译,虽然有点自娱自乐,但是分享给大家也是件好事 CPU 瓶颈: CPU瓶颈可能因为某个负载所需的硬件资源不足而引起.但是过多的CPU使用通常可以通过查询优化(

51CTO学习笔记--Linux运维故障排查思路与系统调优技巧视频课程(高俊峰)

51CTO学习笔记--Linux运维故障排查思路与系统调优技巧视频课程 第一课 Linux运维经验分享与思路 1.一般把主机名,写到hosts下    127.0.0.1    hostname,因为很多应用要解析到本地.oracle没有这个解析可能启动不了. 2.注释掉UUID以及MAC地址,需要绑定网卡的时候,这个可能会有影响. 3.磁盘满了无法启动,  var下木有空间,无法创创建PID等文件,导致文件无法启动,按e   进入single  然后b  重启进入单用户模式. 4.ssh登陆系

[linux]df 磁盘100%Used告警,du显示目录状态良好的故障排查

1.回顾: 某在线主机深夜连续接到告警系统的disk Used 超限告警. 登陆主机查看却遇到了困惑:在检查磁盘使用量 df –h 出来的磁盘使用量确实和告警信息一样,已经被100%占用,但是查看目录大小 du 时,却显示实际目录大小并非这样,而是有很大空闲空间. 如图:磁盘用量 df –h 结果为100%Used, 目录实际总大小 du –h –max-depth=1,显示总目录大小为60k,几乎可以忽略的使用比例. [知识准备] [linux] lsof 命令了解: lsof(list op

Atitit.&#160;包厢记时系统&#160;的说明,教程,维护,故障排查手册v2&#160;pb25.doc

Atitit. 包厢记时系统 的说明,教程,维护,故障排查手册v2 pb25.doc 1. 服务器方面的维护1 1.1. 默认情况下,已经在系统的启动目录下增加了 个启动项目1 1.2. 后台服务.保持mysql数据库服务启动状态2 1.3. 服务器如无必要无需关闭,保持一直开启状态...2 1.4. 配置文件说明3 1.4.1. 指明选片服务端url3 1.4.2. 包厢计时系统提供的接口url (部分分店需要)3 1.4.3. 其他设置3 2. 故障排查4 3. 包厢记时系统5 3.1. 维

公司突然断网故障排查

记一次公司断网故障排查 本来大周一挺好的,刚坐在工位上不到半个小时,公司突然断网,此时,我是有点凌乱的! 下边是排查故障的过程 1,首先我看下本机电脑的IP地址,禁用启动,发现仍旧可以获取到IP地址,这代表DHCP分发是没问题的,因为是突然断网,代表着交换机路由器配置不可能出问题 2,接着我带着笔记本进入机房,看了下光猫,光猫状态正常,然后看了下路由器,路由器是H3C的,有web管理界面,进入web管理界面,发现IP地址状态也是正常的. 4,接着给公司网络运营商打电话,他说是他们那边的问题,有个

Kubernetes之kubectl常用命令使用指南:2:故障排查

kubectl是一个用于操作kubernetes集群的命令行接口,通过利用kubectl的各种命令可以实现各种功能,是在使用kubernetes中非常常用的工具.这里我们会通过一些简单的实例来展现其中一些高频命令的使用方法. 更为重要的是这些命令使用的场景以及能够解决什么样的问题.上篇文章我们介绍了创建和删除相关的几条命令,这篇文章我们来看一下出现问题时最常用的另外九条命令. 常用命令 kubectl故障排查相关,本文将会简单介绍一下如下命令 项番 命令 说明 No.1 version 显示客户

4核服务器cpu使用率10%负载飙到23.5故障排查

遇到一个故障,一台4核服务器cpu利用率是10%负载却飙到23,先看下问题现场,截图如下:...... 浏览全部请点击运维网咖社地址:4核服务器cpu使用率10%负载飙到23.5故障排查