Suggestions for basic rsync configuration

[Peter Heiss]

Hello,

I am very new to rsync and am wanting to have it back up more than 4 remote linux servers via ftp. I want to write a script that will open up a ftp connection using "ftp://username:[e-mail]" with a server, then mount the drive containing the backups, copy the data that is new, unmount the drive, close the connection and move onto the next server until every server is successfully backed up to a external drive on my linux machine which is on my local network. I know that I have to use ssh with the connection to the servers for backup, but where to start is where I am at right now. Here are a couple of noobish questions:

1. Do I have to write my own file from scratch and hope it works?
2. How should I start to write my file in order to have it correlate with backing up multiple servers (syntax, switches, and so on)?

If anyone has any advise on how I should start writing my config file, please let me know if you have any suggestions.

Thanx,

gxr

[Stuart Halliday]

Whilst it is possible to write a script to mount FTP and copy the files
across. This isn't what is usually done with Rsync.

Rsync can be a replacement for FTP client.

So it collects a list of altered files between two directories and puts
these files into a remote directory. No FTP required.

All you need to do is open up a port on your server to the Internet,
install Rsync as a server(daemon) on one end and then run Rsync on the
source whenever you need to do the backup.

The cute thing is that Rsync don't care what platform the source or server
is or whether or not it's across a LAN or WAN.


Here is a batch line I typically use on Windows for backing up a directory
across the Internet.

rsync -zav --delete --recursive '/cygdrive/c/sourcedirectory/'
username@...::backupdirectory/

Easy.
This syncs the source to the backup directory. ie Rsync assumes the source
is the 'master'.

Once you've got Rsync working, you can then add a SSH layer so the traffic
is encrypted.

I'd advise getting the basic daemon working first, then on the client PC,
issue a Rsync command to list the contents of the remote folder.
Once you've got that listing working you know things like firewalls, port
forwarding of routers is working. :-)


Rsync by default using port 873. But it's easy to change this. Just ensure
you do it with the daemon and client. ;-)



To list the public remote directories.

Rsync domain.dom::

Listing the contents of a directory set up in the daemon confg file is
done by:

Rsync domain.dom::backup

Once you've got the basics, you can then add username and password
protection in the confg file.

Performing a list of a directory with a username is done like this:

Rsync username@...::backup

if a password is required, you're prompted for it.
If you want the password auto-inserted, then you set a environmental variable
In Windows this is added to the batch file of the client rsync.

SET RSYNC_PASSWORD=mypassword



A basic daemon conf.cfg file is something like this:

------------------------------------------------------------------------
log file = rsyncd.log
pid file = rsyncd.pid
use chroot=false
uid=administrator
gid=administrators
charset = utf-8

strict modes = false
secrets file =/cygdrive/c/cwrsync/passwordfile

[backup]
comment=rsync directory
path = /cygdrive/c/mybackup/
read only = false
transfer logging = yes
list=yes
#auth users=username
------------------------------------------------------------------------

password file is a list of users and passwords "username:password" on a
single line.


--
Stuart Halliday



-----Original Message-----
From: Geofoxer <pete.heiss@...>
To: rsync@...
Date: Thu, 13 Mar 2008 05:39:40 -0700 (PDT)
Subject: Suggestions for basic rsync configuration

>
> Hello,
>
> I am very new to rsync and am wanting to have it back up more than 4
> remote
> linux servers via ftp. I want to write a script that will open up a ftp
> connection using "ftp://username:password@..." with a
> server,
> then mount the drive containing the backups, copy the data that is new,
> unmount the drive, close the connection and move onto the next server
> until
> every server is successfully backed up to a external drive on my linux
> machine which is on my local network. I know that I have to use ssh
> with the
> connection to the servers for backup, but where to start is where I am
> at
> right now. Here are a couple of noobish questions:
>
> 1. Do I have to write my own file from scratch and hope it works?
> 2. How should I start to write my file in order to have it correlate
> with
> backing up multiple servers (syntax, switches, and so on)?
>
> If anyone has any advise on how I should start writing my config file,
> please let me know if you have any suggestions.
>
> Thanx,
>
> gxr
>
> -----
> Computers are like air conditioners. They both dont work, if you open
> windows.
> --
> View this message in context:
> http://www.nabble.com/Suggestions-for-basic-rsync-configuration-tp16025
> 015p16025015.html
> Sent from the Samba - rsync mailing list archive at Nabble.com.
>
> --
> To unsubscribe or change options:
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read:
> http://www.catb.org/~esr/faqs/smart-questions.html

This email is the property of ECS Technology Ltd.
This company is registered in Scotland with company number 212513.
VAT registered GB 761 7456 12  
http://www.ecs-tech.com/


--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Peter Heiss]

Thanks for your response, I think that I am on my way of getting stuff configured here. I still have a couple of questions though. I am also using linux with rsync!!! There are a couple of errors that I am getting, and I don't exactly understand why...

I have set up the rysnc daemon successfully on the remote server (I think), which prompts for the password when I connect. I get the following error when I run rsync daemon:

# rsync daemon
rsync: link_stat "/directory-path/daemon" failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9]

Is there anything that I still have to configure for the rsync daemon? I also get the following error when I run the following command:

# rsync --progress -zav -e ssh /random/file-or-directory <remote-server-ip-address>:/random/file-or-directory
Password:
building file list ...
1 file to consider
ERROR: cannot overwrite non-directory with a directory
rsync error: errors selecting input/output files, dirs (code 3) at main.c(488) [receiver=2.6.8]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(453) [sender=2.6.9]

Is this an error from a lack of rights to the files and folders that I want to copy? I might have misconfigured my config, I can post it if you want.

Stuart Halliday wrote:

Whilst it is possible to write a script to mount FTP and copy the files
across. This isn't what is usually done with Rsync.

Rsync can be a replacement for FTP client.

So it collects a list of altered files between two directories and puts
these files into a remote directory. No FTP required.

All you need to do is open up a port on your server to the Internet,
install Rsync as a server(daemon) on one end and then run Rsync on the
source whenever you need to do the backup.

The cute thing is that Rsync don't care what platform the source or server
is or whether or not it's across a LAN or WAN.


Here is a batch line I typically use on Windows for backing up a directory
across the Internet.

rsync -zav --delete --recursive '/cygdrive/c/sourcedirectory/'
[e-mail]::backupdirectory/

Easy.
This syncs the source to the backup directory. ie Rsync assumes the source
is the 'master'.

Once you've got Rsync working, you can then add a SSH layer so the traffic
is encrypted.

I'd advise getting the basic daemon working first, then on the client PC,
issue a Rsync command to list the contents of the remote folder.
Once you've got that listing working you know things like firewalls, port
forwarding of routers is working. :-)


Rsync by default using port 873. But it's easy to change this. Just ensure
you do it with the daemon and client. ;-)



To list the public remote directories.

Rsync domain.dom::

Listing the contents of a directory set up in the daemon confg file is
done by:

Rsync domain.dom::backup

Once you've got the basics, you can then add username and password
protection in the confg file.

Performing a list of a directory with a username is done like this:

Rsync [e-mail]::backup

if a password is required, you're prompted for it.
If you want the password auto-inserted, then you set a environmental variable
In Windows this is added to the batch file of the client rsync.

SET RSYNC_PASSWORD=mypassword



A basic daemon conf.cfg file is something like this:

------------------------------------------------------------------------
log file = rsyncd.log
pid file = rsyncd.pid
use chroot=false
uid=administrator
gid=administrators
charset = utf-8

strict modes = false
secrets file =/cygdrive/c/cwrsync/passwordfile

[backup]
comment=rsync directory
path = /cygdrive/c/mybackup/
read only = false
transfer logging = yes
list=yes
#auth users=username
------------------------------------------------------------------------

password file is a list of users and passwords "username:password" on a
single line.


--
Stuart Halliday



-----Original Message-----
From: Geofoxer <[e-mail]>
To: [e-mail]
Date: Thu, 13 Mar 2008 05:39:40 -0700 (PDT)
Subject: Suggestions for basic rsync configuration

>
> Hello,
>
> I am very new to rsync and am wanting to have it back up more than 4
> remote
> linux servers via ftp. I want to write a script that will open up a ftp
> connection using "ftp://username:[e-mail]" with a
> server,
> then mount the drive containing the backups, copy the data that is new,
> unmount the drive, close the connection and move onto the next server
> until
> every server is successfully backed up to a external drive on my linux
> machine which is on my local network. I know that I have to use ssh
> with the
> connection to the servers for backup, but where to start is where I am
> at
> right now. Here are a couple of noobish questions:
>
> 1. Do I have to write my own file from scratch and hope it works?
> 2. How should I start to write my file in order to have it correlate
> with
> backing up multiple servers (syntax, switches, and so on)?
>
> If anyone has any advise on how I should start writing my config file,
> please let me know if you have any suggestions.
>
> Thanx,
>
> gxr
>
> -----
> Computers are like air conditioners. They both dont work, if you open
> windows.
> --
> View this message in context:
> http://www.nabble.com/Suggestions-for-basic-rsync-configuration-tp16025
> 015p16025015.html
> Sent from the Samba - rsync mailing list archive at Nabble.com.
>
> --
> To unsubscribe or change options:
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read:
> http://www.catb.org/~esr/faqs/smart-questions.html


This email is the property of ECS Technology Ltd.
This company is registered in Scotland with company number 212513.
VAT registered GB 761 7456 12  
http://www.ecs-tech.com/


--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Stuart Halliday]

> Thanks for your response, I think that I am on my way of getting stuff
> configured here. I still have a couple of questions though. I am also
> using linux with rsync!!! I want to clear up the usage of the
> following command:
>
> rsync --progress -zav -e ssh /random/file-or-directory
> <remote-server-ip-address>:/random/file-or-directory
>
> Does that command mean that I connecting to the remote server and
> coping the desired folder and files,

Yes. Well the contents of the directory not the directory and its contents
due to the missing trailing '/'.



>
> rsync --progress -zav -e ssh
> <remote-server-ip-address>:/random/file-or-directory
> /random/file-or-directory

Then the opposite happens. Remote to local files are copied. But remember
any extra files in the destination will not be deleted. You need to use
--delete for that to happen.

 

> I have set up the rysnc daemon successfully on the remote server (I
> think),
> which prompts for the password when I connect. I get the following
> error
> when I run rsync daemon:
>
> # rsync daemon
> rsync: link_stat "/directory-path/daemon" failed: No such file or
> directory
> (2)
> rsync error: some files could not be transferred (code 23) at
> main.c(977)
> [sender=2.6.9]
>
> Is there anything that I still have to configure for the rsync daemon?

read this site:
http://www.fredshack.com/docs/rsync.html

> I
> also get the following error when I run the following command:
>
> # rsync --progress -zav -e ssh /random/file-or-directory
> <remote-server-ip-address>:/random/file-or-directory
> Password:
> building file list ...
> 1 file to consider
> ERROR: cannot overwrite non-directory with a directory
> rsync error: errors selecting input/output files, dirs (code 3) at
> main.c(488) [receiver=2.6.8]
> rsync: connection unexpectedly closed (8 bytes received so far)
> [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(453)
> [sender=2.6.9]

> Is this an error from a lack of rights to the files and folders that I
> want
> to copy? I might have misconfigured my config, I can post it if you
> want.

Forget ssh until you've got it working as plain vanilla Rsync.

Like I said in my 1st posting. Get a working daemon and then list a rsync
folder using a Rsync list command.

Don't do anything else until you've got that working.
You're trying to skip ahead me thinks. :-)

--
Stuart Halliday
 


This email is the property of ECS Technology Ltd.
This company is registered in Scotland with company number 212513.
VAT registered GB 761 7456 12  
http://www.ecs-tech.com/


--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Matt McCutchen-7]

I'd like to expand on Stuart's response a bit...

On Fri, 2008-03-14 at 06:29 -0700, Geofoxer wrote:
> Thanks for your response, I think that I am on my way of getting stuff
> configured here. I still have a couple of questions though. I am also using
> linux with rsync!!! I want to clear up the usage of the following command:
>
> rsync --progress -zav -e ssh /random/file-or-directory
> <remote-server-ip-address>:/random/file-or-directory

Like most copy commands, rsync interprets its last argument as the
destination and the previous argument(s) as source(s).  Thus, that
command pushes files from your machine to the remote server.

To decide whether you want to use a trailing slash on the source, see
the "USAGE" section of the rsync man page.

> And what happens
> when I switch it around like the following:
>
> rsync --progress -zav -e ssh
> <remote-server-ip-address>:/random/file-or-directory
> /random/file-or-directory

That one pulls files from the remote server to your machine, which is
probably what you want in order to back up the remote server to a drive
on your machine.

> I have set up the rysnc daemon successfully on the remote server (I think),
> which prompts for the password when I connect. I get the following error
> when I run rsync daemon:
>
> # rsync daemon
> rsync: link_stat "/directory-path/daemon" failed: No such file or directory
> (2)
> rsync error: some files could not be transferred (code 23) at main.c(977)
> [sender=2.6.9]
>
> Is there anything that I still have to configure for the rsync daemon? I
> also get the following error when I run the following command:
>
> # rsync --progress -zav -e ssh /random/file-or-directory
> <remote-server-ip-address>:/random/file-or-directory
> Password:
> building file list ...
> 1 file to consider
> ERROR: cannot overwrite non-directory with a directory
> rsync error: errors selecting input/output files, dirs (code 3) at
> main.c(488) [receiver=2.6.8]
> rsync: connection unexpectedly closed (8 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(453)
> [sender=2.6.9]
>
> Is this an error from a lack of rights to the files and folders that I want
> to copy? I might have misconfigured my config, I can post it if you want.

OK, let's be clear here.  If you want to start a daemon to accept
connections, the command is "rsync --daemon"; pass a --config=FILE
option if you want to use a configuration file other than the
default /etc/rsyncd.conf .  If you want to access an rsync daemon, put a
*double* colon after the remote hostname:

<remote-server-ip-address>::/random/file-or-directory

In your second command above, you used a *single* colon, so rsync used
plain ssh, not a daemon.  The fact that the run got as far as "building
file list" is evidence that the ssh part is working.  You can continue
using ssh, or you can switch to using the daemon by putting a double
colon after the remote hostname (and removing "-e ssh" unless you want
to use the special daemon-over-remote-shell mode).

The "ERROR: cannot overwrite non-directory with a directory" means
exactly what it says.  If you are trying to copy a directory (or
multiple files, which rsync will put in a directory), the destination
path must not refer to an existing file that is not a directory.  Delete
or move away the offending destination file and try again.

Matt

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Matt McCutchen-7]

On Fri, 2008-03-14 at 14:15 +0000, Stuart Halliday wrote:
> Forget ssh until you've got it working as plain vanilla Rsync.
>
> Like I said in my 1st posting. Get a working daemon and then list a rsync
> folder using a Rsync list command.
>
> Don't do anything else until you've got that working.
> You're trying to skip ahead me thinks. :-)

That may be good advice on Windows, where installing ssh and setting up
an ssh server can involve several extra steps.  On Linux, I beg to
differ.  Most Linux machines already have ssh set up, so rsync over ssh
is simpler and easier than setting up a daemon (but not necessarily
better depending on server security requirements).

Matt

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Peter Heiss]



Matt McCutchen-7 wrote:

>OK, let's be clear here.  If you want to start a daemon to accept
>connections, the command is "rsync --daemon"; pass a --config=FILE
>option if you want to use a configuration file other than the
>default /etc/rsyncd.conf .  If you want to access an rsync daemon, put a
>*double* colon after the remote hostname:

><remote-server-ip-address>::/random/file-or-directory

I am now able to backup from the remote server, I have tested it several times with random file backups. Although, I am still having problems with the daemon on the remote server. I ran the command "rsync --daemon" on the remote server, no error there. But then I ran the following error to do a test backup and received this error:

# rsync <server-ip>::/random/file-or-directory/ /random/file-or-directory/
ERROR: The remote path must start with a module name not a /
rsync error: error starting client-server protocol (code 5) at main.c(1383) [receiver=2.6.9]

What does the error mean, do I need to make a new configuration file as a module? I will post the config that I have on the remote server and on my local machine:

Remote server config:

uid = admin
gid = admins
read only = true
use chroot = true
transfer logging = true
log format = %h %o %f %l %b
log file = /var/log/rsyncd.log
hosts allow = trusted.hosts
slp refresh = 300

[Realperson Backups]
        path = /random/file-or-directory
        comment = for running backups
        auth users = admin
        secrets file = /etc/rsyncd.secrets

[Realperson Backup Daemon]
path = /random/file-or-directory/daemon
        comment = for running Daemon backups
        auth users = admin
        secrets file = /etc/rsyncd.secrets

And the local config from my local linux machine:

uid = rsync-admin
gid = admins
read only = true
use chroot = true
transfer logging = true
log format = %h %o %f %l %b
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
hosts allow = trusted.hosts
slp refresh = 300

[Backup Directory]
        comment = rsync Datensicherung Verzeichnis
        path = /random/file-or-directory
        readonly = false
        transfer logging = yes
        list = yes
#       auth users = root
        secrets file = /etc/rsyncd.secrets


Is there anything that I missed in my configuration files? I was not sure whether or not I needed the second configuration, can I delete it?

[Matt McCutchen-7]

On Mon, 2008-03-17 at 05:58 -0700, Peter Heiss wrote:
> Although, I am still having problems with
> the daemon on the remote server. I ran the command "rsync --daemon" on the
> remote server, no error there. But then I ran the following error to do a
> test backup and received this error:
>
> # rsync <server-ip>::/random/file-or-directory/ /random/file-or-directory/
> ERROR: The remote path must start with a module name not a /
> rsync error: error starting client-server protocol (code 5) at main.c(1383)
> [receiver=2.6.9]

> [Realperson Backups]
>         path = /random/file-or-directory
>         comment = for running backups
>         auth users = admin
>         secrets file = /etc/rsyncd.secrets

To access something on a daemon, you must express the path relative to
one of the daemon's modules.  The command should be:

rsync '<server-ip>::Realperson Backups/' /random/file-or-directory/

To pull /random/file-or-directory/foo , the command would be:

rsync '<server-ip>::Realperson Backups/foo' /random/file-or-directory/foo

(I'm using single quotes due to the space in the module name, which you
might want to get rid of.)

> I was not sure
> whether or not I needed the second configuration, can I delete it?

Yes, you can delete it.

Matt

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Matt McCutchen-7]

On Mon, 2008-03-17 at 05:58 -0700, Peter Heiss wrote:
> hosts allow = trusted.hosts

BTW, the "hosts allow" field needs to contain the actual list of trusted
hosts, not the name of a file holding the list.

Matt

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Peter Heiss]

Matt McCutchen-7 wrote:

> hosts allow = trusted.hosts

BTW, the "hosts allow" field needs to contain the actual list of trusted
hosts, not the name of a file holding the list.

So now I have tried the daemon again, and got a password prompt, which is better. I edited the "host allow = *" so that it would allow all hosts. But I tried at first adding the IP Address of my local router, and it didnt work. How can I configure the "hosts allow" field correctly to allow any requests from my network. Here is the error that I got:


# rsync -zav <remote-server-ip>::realperson2 /random/file-or-directory
Password:
@ERROR: auth failed on module realperson2
rsync error: error starting client-server protocol (code 5) at main.c(1383) [receiver=2.6.9]


I know that I had the password right, I even checked the rsync.secret file to double check. Do I have to have an actual domain name in order to give access to the daemon, or would putting in a IP Address be ok?

[Matt McCutchen-7]

On Tue, 2008-03-18 at 03:38 -0700, Peter Heiss wrote:

> So now I have tried the daemon again, and got a password prompt, which is
> better. I edited the "host allow = *" so that it would allow all hosts. But
> I tried at first adding the IP Address of my local router, and it didnt
> work. How can I configure the "hosts allow" field correctly to allow any
> requests from my network. Here is the error that I got:
>
>
> # rsync -zav <remote-server-ip>::realperson2 /random/file-or-directory
> Password:
> @ERROR: auth failed on module realperson2
> rsync error: error starting client-server protocol (code 5) at main.c(1383)
> [receiver=2.6.9]

Your "hosts allow" is fine; that error message indicates a problem with
the username/password authentication.  Since you set "auth users =
admin", you need to tell rsync to log in to the daemon with username
"admin"; otherwise it will default to using your system username,
"root", which isn't present on the daemon.  Here's the command:

rsync -zav admin@<remote-server-ip>::realperson2 /random/file-or-directory

Matt

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Peter Heiss]

Now I have a new situation, the linux OS was reinstalled (it crashed after a bad restart) on the remote linux box where I was working with rsync. I have reconfigured everything back to the way tit was before and I am now getting a new error with the following command:

# rsync -zav --progress <remote-server-ip>:/random/file-or-directory /random/file-or-directory
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
e4:00:85:b2:5b (I deleted a section from this value before posting).
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending key in /root/.ssh/known_hosts:1
RSA host key for <remote-server-ip> has changed and you have requested strict checking.
Host key verification failed.
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: unexplained error (code 255) at io.c(453) [receiver=2.6.9]

And when I run the command to access my daemon on the remote server it just sits there and does nothing for about 2 minutes, and then it drops the connection with this error. I have enabled rsync on the network services again through yast and all that. I have checked "/root/.ssh/known_hosts", and the folder doesnt exist under the "root" directory. I also installed ssl and the ssl-devel again on the server.

Is there anything that I am missing so far? How can I go about creating/editing this file so I can get rsync up and running again?

[Paul Slootman-5]

On Wed 19 Mar 2008, Peter Heiss wrote:

>
> Now I have a new situation, the linux OS was reinstalled (it crashed after a
> bad restart) on the remote linux box where I was working with rsync. I have
> reconfigured everything back to the way tit was before and I am now getting
> a new error with the following command:
>
> # rsync -zav --progress <remote-server-ip>:/random/file-or-directory
> /random/file-or-directory
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> Someone could be eavesdropping on you right now (man-in-the-middle attack)!
> It is also possible that the RSA host key has just been changed.

Obviously the host key has changed, as you reinstalled the OS...

> Offending key in /root/.ssh/known_hosts:1
[...]
> again through yast and all that. I have checked "/root/.ssh/known_hosts",
> and the folder doesnt exist under the "root" directory. I also installed ssl

On the client system? I.e. not the newly reinstalled system? I find that
hard to believe.

This is a simple ssh issue, nothing to do with rsync.


Paul Slootman
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Peter Heiss]

I figured out the ssh error. Although I am still unable to connect to the remote host with the rsync daemon. Here is the error that I am getting again:

# rsync -zav --progress root@<remote-server-ip>::realperson /random/file-or-directory
rsync: failed to connect to <remote-server-ip>: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(104) [receiver=2.6.9]

I have set up the daemon on the remote machine and I have ran "rsync --daemon" to start up the daemon server. I also have enabled the rsync server on the firewall. I also want to restate that I am reconfiguring rsync on a previously new installed system, and the ssh errors are fixed. What am I still missing?

[Paul Slootman-5]

On Thu 20 Mar 2008, Peter Heiss wrote:
>
> I figured out the ssh error. Although I am still unable to connect to the
> remote host with the rsync daemon. Here is the error that I am getting
> again:

To clarify: you know that ssh is now not involved, right?

> # rsync -zav --progress root@<remote-server-ip>::realperson
> /random/file-or-directory
> rsync: failed to connect to <remote-server-ip>: Connection timed out (110)

A timeout would indicate a firewall problem, the rsync port (873) is
probably not allowed.


Paul Slootman
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Peter Heiss]

Paul Slootman-5 wrote:

> # rsync -zav --progress root@<remote-server-ip>::realperson
> /random/file-or-directory
> rsync: failed to connect to <remote-server-ip>: Connection timed out (110)

A timeout would indicate a firewall problem, the rsync port (873) is
probably not allowed.

Yes I understand that ssh is not involved anymore here. I opened up the port on the firewall, so that problem is out of the way. The weird thing is that when I use the following command I dont get an error, I only get the timeout when i use the daemon to connect the remote server:

# rsync -zav <remote-server-ip>:/random/file-or-directory/ /random/file-or-directory/
Password:

With this command I can transfer files without any errors, it works perfectly. But when I use call the daemon on the remote server, it just sits there and does nothing until the connection times out. I haved double checked the firewall and everything is set up the way it should be. here my config files just in case there is something wrong with them (they look right ok to me):

uid = root
gid = roots
read only = true
use chroot = true
transfer logging = true
log format = %h %o %f %l %b
log file = /var/log/rsyncd.log
hosts allow = *
slp refresh = 300

[realperson]
        path = /srv/www/vhosts/rsync/backup_out
        comment = Verzeichnis fuer rsync
        auth users = root
        secrets file = /etc/rsyncd.secrets

Is there anything else that I can do here?

[EDIT: I forgot to say that I will not be back until next tuesday. I will get back to this then... Happy Easter!!!]

[Stuart Halliday]

 

> I figured out the ssh error. Although I am still unable to connect to
> the
> remote host with the rsync daemon. Here is the error that I am getting
> again:
>
> # rsync -zav --progress root@<remote-server-ip>::realperson
> /random/file-or-directory
> rsync: failed to connect to <remote-server-ip>: Connection timed out
> (110)
> rsync error: error in socket IO (code 10) at clientserver.c(104)
> [receiver=2.6.9]
>
> I have set up the daemon on the remote machine and I have ran "rsync
> --daemon" to start up the daemon server. I also have enabled the rsync
> server on the firewall. I also want to restate that I am reconfiguring
> rsync
> on a previously new installed system, and the ssh errors are fixed.
> What am
> I still missing?

I know I keep asking you this. :-))

But can you get a simple list of the remote rsync's module contents?

ie
rsync root@<remote-server-ip>::

or

rsync root@<remote-server-ip>::realperson

Obviously this needs the rsync daemon config list option set to yes

--
Stuart Halliday


This email is the property of ECS Technology Ltd.
This company is registered in Scotland with company number 212513.
VAT registered GB 761 7456 12  
http://www.ecs-tech.com/


--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Stuart Halliday]

> when I use the following command I dont get an error, I only get the
> timeout when i use the daemon to connect the remote server:

I don't use a daemon on the local pc to sync files with a remote server.

It's there only for responding to remote incoming rsync requests.

--
Stuart Halliday


This email is the property of ECS Technology Ltd.
This company is registered in Scotland with company number 212513.
VAT registered GB 761 7456 12  
http://www.ecs-tech.com/


--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Paul Slootman-5]

On Thu 20 Mar 2008, Peter Heiss wrote:

> >> # rsync -zav --progress root@<remote-server-ip>::realperson
> >> /random/file-or-directory
> >> rsync: failed to connect to <remote-server-ip>: Connection timed out
> >> (110)
> >
> > A timeout would indicate a firewall problem, the rsync port (873) is
> > probably not allowed.
> >
>
> Yes I understand that ssh is not involved anymore here. I opened up the port
> on the firewall, so that problem is out of the way. The weird thing is that

Well, I must disagree :-)  A timeout on one port while another port
connects fine is a firewall problem... Maybe the _outgoing_ firewall is
the cause?

> when I use the following command I dont get an error, I only get the timeout
> when i use the daemon to connect the remote server:
>
> # rsync -zav <remote-server-ip>:/random/file-or-directory/
> /random/file-or-directory/
> Password:

So port 22 is allowed to connect, while port 873 is not.


Paul Slootman
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Matt McCutchen-7]

On Thu, 2008-03-20 at 07:04 -0700, Peter Heiss wrote:

> # rsync -zav --progress root@<remote-server-ip>::realperson
> /random/file-or-directory
> rsync: failed to connect to <remote-server-ip>: Connection timed out (110)
> rsync error: error in socket IO (code 10) at clientserver.c(104)
> [receiver=2.6.9]
>
> I have set up the daemon on the remote machine and I have ran "rsync
> --daemon" to start up the daemon server. I also have enabled the rsync
> server on the firewall. I also want to restate that I am reconfiguring rsync
> on a previously new installed system, and the ssh errors are fixed. What am
> I still missing?

I don't know, but here are a few things you can try.  First, confirm
that the daemon is accepting connections by running "nc localhost 873"
on the remote machine.  You should see the daemon's greeting, beginning
with "@RSYNCD".  Then, attempt to the daemon by running
"nc <remote-server-ip> 873" on the local machine.  If the first command
works but the second times out, then there is something blocking the
connection.  The most common cause would be a firewall, but you say
you've opened the port in the firewall, so I don't know what it could
be.

Matt

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html