Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having trouble getting rsync to connect to the remote server. I piped in a grep of "password" on rsync's man page, and I see "you will receive a password prompt when you connect ..."
where user@host was the username, and the trailing rsync/ is my dest folder. I did not get a password prompt, and rsync failed to connect, because the connection was refused.
I emailed the support staff at the datacenter and asked them to open up the port for a specific IP address. They responded with the following:
Quote:
CSF doesn't allow the setting of a port by IP, but it will block an IP if anyone tries to execute an attack against it.
I did, however, have to open up the port in CSF, and you should be able to access it now. Please let me know if this is not the case.
I realized after making my initial post here that I did not do a good job in explaining my working environment. The (remote) webserver is running RedHat and rsync version 2.6.8 - which really doesn't matter. The computer that I am actually using to connect to the remote server is a Windows computer running cygwin. On Cygwin, I am running rsync version 3.0.4.
After receiving our datacenter's response, I tried issuing the following command (again) through Cygwin:
Any other ideas? Is there a way that I can verify that port 873 has been opened up? I'm not very familiar with CSF or with iptables. I do, however, have root ssh access to the server.
Your syntax to me looks wrong but it might just be the way I use rsync. My scripts look something like this:
rsync -avz user@host:/source /destination
Note: I haven't used rsync on Windows, just Linux.
Any other ideas? Is there a way that I can verify that port 873 has been opened up? I'm not very familiar with CSF or with iptables. I do, however, have root ssh access to the server.
Check that you are running rsync as a daemon on the redhat server and if so, do netstat -pantu|grep 873 to make sure that it is indeed listening. Then from the windows host, use nmap against the server IP to scan for the open port 873.
If you are not running rsync that way on the server, then your syntax should look like Myiagros's, where the transport is SSH.
Thanks guys. I already knew that I wasn't running rsync as a daemon on the server, so the syntax that Myiagros suggested worked. However, I am facing a new dilemma. I want to stick this rsync into a cron.
I have been told that by exporting the RSYNC_PASSWORD, this would create a security hole, and that instead I should use SSH Key Authentication. I am in the midst of researching how I go about this, and will post the steps shortly. I'm almost to the point of being ready to go to work on it.
I have been told that by exporting the RSYNC_PASSWORD, this would create a security hole, and that instead I should use SSH Key Authentication. I am in the midst of researching how I go about this, and will post the steps shortly. I'm almost to the point of being ready to go to work on it.
That's good, cuz this is a perfectly good research topic and i'd hate to deprive anyone of the satisfaction of finding the answer themselves . still, if you run into a block, you know where to go.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.