failed to create pid file /var/run/rsyncd.pid: File exists报错

[[email protected] ansible_playbooks]# ps aux|grep rsync
root      1799  0.0  0.0 114652   480 ?        Ss   Jun29   0:00 rsync --daemon
root     61754  0.0  0.0 112664   972 pts/2    S+   11:17   0:00 grep --color=auto rsync
[[email protected] ansible_playbooks]# kill -9  1799
You have new mail in /var/spool/mail/root
[[email protected] ansible_playbooks]# rsync --daemon
failed to create pid file /var/run/rsyncd.pid: File exists
[[email protected] ansible_playbooks]# ps aux|grep rsync
root     61790  0.0  0.0 112660   968 pts/2    S+   11:18   0:00 grep --color=auto rsync
[[email protected] ansible_playbooks]# rsync --daemon
failed to create pid file /var/run/rsyncd.pid: File exists

#删除 /var/run/rsyncd.pid即可
[[email protected] ansible_playbooks]# rm -fr /var/run/rsyncd.pid
[[email protected] ansible_playbooks]# rsync --daemon

原文地址：https://www.cnblogs.com/Dev0ps/p/9293530.html

时间： 2024-10-11 07:38:29

failed to create pid file /var/run/rsyncd.pid: File exists报错的相关文章

解决opensips启动时出现PID file /var/run/opensips.pid does not exist 的错误

启动opensips时报下列错误 [[email protected] opensips]# opensipsctl start INFO: Starting OpenSIPS : ERROR: PID file /var/run/opensips.pid does not exist -- OpenSIPS start failed 查看日志文件 [[email protected] opensips]# tail -f /var/log/messages May 14 15:52:41 Op

yum被lock Existing lock /var/run/yum.pid: another copy is running as pid 1580. Another app is currently holding the yum lock; waiting for it to exi

[[email protected] bin]# yum -y install lrzszLoaded plugins: fastestmirrorExisting lock /var/run/yum.pid: another copy is running as pid 1580.Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memor

nginx: [error] open() "/usr/local/var/run/nginx.pid" failed (2: No such file or directory)

nginx: [error] open() "/usr/local/var/run/nginx.pid" failed (2: No such file or directory) 2017年09月14日 09:15:45 阅读数:7742 启动Nginx出现这个错误 nginx: [error] open() "/usr/local/var/run/nginx.pid" failed (2: No such file or directory) 1  解决方法:找

error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory 解决办法

服务器版本:CentOS Linux release 7.4 Linux lb 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux 参考:https://www.cnblogs.com/yogurtwu/p/9988974.html 注:在翻了很多baidu和google相关文章后,逐步排查,根据手动执行libvirtd命令出现的报错信息才查到解决方法.一路坑. 对装有k

Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory错误处理

redhat7 ERROR    Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory yum -y install avahi systemctl start libvirtd Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory错误处理

Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or director

error: Failed to reconnect to the hypervisorerror: no valid connectionerror: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Further investigation found avahi was needed for this to work. The final fix was runni

/var/run/syslogd.pid can not write pid

场景描述:系统启动之后,将分区挂载到/var目录下,保存日志文件到其他的硬盘分区之上.出现如下的问题: 1重新挂载硬盘的分区到/var/log,接收系统的日志 如果已经指向一个设备,重新挂载到一个设备,以前 的将被覆盖 2 starting system logger :can not open or create /var/run/syslogd.pid  can not write pid /var/run/syslogd.pid can not write pid

/var/run/yum.pid 已被锁定，PID 为 XXXX 的另一个程序正在运行。

安装st-load时, 终端提示 “/var/run/yum.pid 已被锁定,PID 为 13908 的另一个程序正在运行.” 解决方法:直接在终端运行 rm -f /var/run/yum.pid 将该文件删除,然后再次运行yum. 即出现如下提示: [[email protected] ~]# yum install git unzip patch gcc gcc-c++ make已加载插件:fastestmirror, langpacks/var/run/yum.pid 已被锁定,PID

运行yum系统提示Existing lock /var/run/yum.pid: another copy is running as pid

运行yum,系统提示Existing lock /var/run/yum.pid: another copy is running as pid 3046 问题描述:登录系统后,执行yum install vsftpd,提示Existing lock /var/run/yum.pid: another copy is running as pid 5048.有时等5~10分钟yum可以正常使用. 问题分析:主要原因就是yum在自动更新,所以再运行yum就会报这个错. 问题解决:只要关掉正在执行的