RSYNC issue ; for tech guys ( pic for lurkers.. lol)

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • directfiesta
    Too lazy to set a custom title
    • Oct 2002
    • 30227
    #1

    RSYNC issue ; for tech guys ( pic for lurkers.. lol)

    Ok, a bit of a technical issue ... Don't expect much of a solution, but maybe....


    Rsync issue :

    I have server A ( big site ) , server B ( various sites ) , server C ( no sites ).
    I want to transfer server A ( big site ) to server C, using rsync ( rsync -av -e sss username@oldserverhost:/home/old_home/ /home/new_home/ )

    When I start rsync on server C to import A, I get this error :


    ssh: connect to host 111.111.11.11 port 22: Connection timed out
    rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
    rsync error: unexplained error (code 255) at io.c(453) [receiver=2.6.9]



    So, I want to see if Rsync works on C, so I run an import from B.... Works fine.
    Seems that rsync works on C. Let see if it works on A?
    So I star on A a rsync to import from B.... Works fine.

    But the actual Rsync from A to C doesn't work...

    The site is a bit over 100 gigs, so I don't feel to do ftp....


    I know that Asspimple is stoopid ... As he says, it is a FACT !

    But I can't figure out how he can breathe or type , at the same time ....
    Tags: None
    • Empfänger Emil
      So Fucking Banned
      • Aug 2004
      • 907
      #2
      [IMG]http://www.**************/Seiten/Auf_dem_Sofa/string-emil_0191.jpg[/IMG]

        Comment

        • directfiesta
          Too lazy to set a custom title
          • Oct 2002
          • 30227
          #3
          no surprise ...

          should stick to the " hit it " threads ....
          I know that Asspimple is stoopid ... As he says, it is a FACT !

          But I can't figure out how he can breathe or type , at the same time ....

            Comment

            • Superterrorizer
              Confirmed User
              • Sep 2003
              • 509
              #4
              Make sure your host has ssh running on port 22 and that it's not firewalled. The problem isn't rsync, it's that you can't connect to the remote server.

                Comment

                • directfiesta
                  Too lazy to set a custom title
                  • Oct 2002
                  • 30227
                  #5
                  Originally posted by Superterrorizer
                  Make sure your host has ssh running on port 22 and that it's not firewalled. The problem isn't rsync, it's that you can't connect to the remote server.
                  I am the host ...

                  But I can connect to the remote server from another server .... If I couldn't from any server, then I could deduct that it is a connection problem of server A ...

                  Will try to change the port that ssh uses...
                  I know that Asspimple is stoopid ... As he says, it is a FACT !

                  But I can't figure out how he can breathe or type , at the same time ....

                    Comment

                    • borked
                      Totally Borked
                      • Feb 2005
                      • 6284
                      #6
                      -e sss
                      you mean -e ssh, right?

                      also what are the ssh logs on the remote machine saying? it looks from the rsync errors, that the connection is being established, but the hadnshake is failing.

                      For coding work - hit me up on andy // borkedcoder // com
                      (consider figuring out the email as test #1)


                      All models are wrong, but some are useful. George E.P. Box. p202

                        Comment

                        • borked
                          Totally Borked
                          • Feb 2005
                          • 6284
                          #7
                          also is dns resolving correctly on all servers? ssh timeouts can happen if ssh is setup in the conf file to reverse dns each conenction, and the ssh host dns is failing for some reason...

                          For coding work - hit me up on andy // borkedcoder // com
                          (consider figuring out the email as test #1)


                          All models are wrong, but some are useful. George E.P. Box. p202

                            Comment

                            • directfiesta
                              Too lazy to set a custom title
                              • Oct 2002
                              • 30227
                              #8
                              Originally posted by borked
                              -e sss
                              you mean -e ssh, right?

                              also what are the ssh logs on the remote machine saying? it looks from the rsync errors, that the connection is being established, but the hadnshake is failing.
                              LOL... ssh was used .. typo error here.

                              I can ssh into that server no problem. Issue commands, make folders, etc... I can also Rsync into it from another server....
                              Very annoying....
                              Maybe I will rsync A to server B, then Rsync again B to server C ... Will take about 20-25 hours.,...

                              Logs on the remote are not showing an error .... but I will check them again.
                              Thx.
                              I know that Asspimple is stoopid ... As he says, it is a FACT !

                              But I can't figure out how he can breathe or type , at the same time ....

                                Comment

                                Previous template Next
                                Working...