Thank you.
I have made:
service nfslock stop service xinetd restart service nfslock start
Then both is possible.
Best regards.
Viele Grüße i.V. Helmut Drodofsky ________________________________
Internet XS Service GmbH Heßbrühlstraße 15 D-70565 Stuttgart Fon : 0711/781941-0 Fax : 0711/781941-79 Geschäftsführer: Dr. Roswitha Hahn-Drodofsky HRB 21091 Stuttgart USt.ID.: DE 190582774
Am 12.07.2013 23:41, schrieb Eero Volotinen:
how about running rsync via ssh as normal way? you can also disable rpc* if you are not using nfs.. On Jul 13, 2013 12:24 AM, "Helmut Drodofsky" drodofsky@internet-xs.de wrote:
I have searched now:
port 837 is used by rpc.statd
And now rsync daemaon can not start.
No I am searching what to do wtith rpc.statd
Viele Grüße i.V. Helmut Drodofsky ________________________________
Internet XS Service GmbH Heßbrühlstraße 15 D-70565 Stuttgart Fon : 0711/781941-0 Fax : 0711/781941-79 Geschäftsführer: Dr. Roswitha Hahn-Drodofsky HRB 21091 Stuttgart USt.ID.: DE 190582774
Am 12.07.2013 23:01, schrieb m.roth@5-cent.us:
Helmut Drodofsky wrote:
Hello,
I use procedures for backup with rsync. The data where "pulled" by the backup server.
Sender: Now CentOS 5.9, receiver CentOS 6 updated on July 3.
Up to yesterday it run OK.
Today morning I made yum update to sender CentOS 5
Now I get
rsync: connection unexpectedly closed (0 bytes received so far)
[receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [receiver=3.0.6]
yum.log says, rsync was not updated this morning.
Both Versions 3.0.6
The command is like:
/usr/bin/rsync --password-file=/etc/rsync.server --delete --backup --backup-dir=/backup1 --bwlimit=5000 -rtz user@server::dir/ /backup/
any idea?
filesystem full? Network issue? Security issue? Selinux?
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos