cannot make a local mirror of Slackware

igadoter · 09-10-2010, 10:01 AM

Hi,
I have done several attempts to build a local mirror of Salckware 13.0. There are two problems: I have to wait very long for a connection, they appear error during a connection which broke it so I have to restart. Is there any other way to build mirror? I am using Alien Bob scripts. Never before happened something like that. The connections with common web pages (google, etc) work well. Maybe I should look for some other mirror than those listed in mirror-slackware-current.sh. Please help to fix this. This is really very important for me.
Here is a listing

Code:

rsync: writefd_unbuffered failed to write 4 bytes to socket [generator]: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(1530) [generator=3.0.7]
rsync error: received SIGUSR1 (code 19) at main.c(1288) [receiver=3.0.7]
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(760) [receiver=3.0.7]
rsync: connection unexpectedly closed (651 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7]
Fri Sep 10 15:41:45 CEST 2010 [1958]: Done mirroring slackware-13.0 (exit code 0

hitest · 09-10-2010, 10:08 AM

Quote:

Originally Posted by igadoter

Hi,
I have done several attempts to build a local mirror of Salckware 13.0. There are two problems: I have to wait very long for a connection, they appear error during a connection which broke it so I have to restart. Is there any other way to build mirror? I am using Alien Bob scripts. Never before happened something like that. The connections with common web pages (google, etc) work well. Maybe I should look for some other mirror than those listed in mirror-slackware-current.sh. Please help to fix this. This is really very important for me.

Weird. Alien Bob's slackware-current script works perfectly for me. Perhaps try another mirror if you time out?

repo · 09-10-2010, 10:11 AM

I use

Quote:

rsync.osuosl.org::slackware/slackware-current

which works OK.
However seems to me most mirrors are overloaded, and refuse connections from time to time, when I try

Quote:

slackpkg update
slackpkg upgrade-all

Kind regards

rob.rice · 09-10-2010, 02:54 PM

use mc it has an ftp client built in
super easy to use hit F9 select left OR right then select ftp link give the dialog box the ftp address without the "ftp://" part of the address
after that you can copy what ever like from the ftp site just like it was a local file or directory and navigate the site like it was a local file system

BrZ · 09-10-2010, 11:30 PM

Erick's script is working perfect here. My mirror are synced from osuosl and it gave me almost the same error two days ago. Just Waited a few minutes and it mirrored. Today it worked fine.

Can you try RSYNCURLROOT=${RSYNCURLROOT:-"rsync.osuosl.org::slackware/"} and post the result? Thanks.

igadoter · 09-11-2010, 02:45 AM

Hi,
I have no idea what's going on. I am sure it is not about Eric's scripts. Ftp connections work well - I am thinking now about settings which may cause problems with rsync protocol - firewalls? - something which doesn't allow connection from internet to my local computer - eg. I know that for ftp one may need to set 'passive' mode to download files. I am thinking about something similar but for rsync.

repo · 09-11-2010, 03:15 AM

What happens if you disable the firewall?

igadoter · 09-11-2010, 05:25 AM

I disabled the firewall. Rsync started but after downloading ca. 1GB it reported an error:

Code:

rsync: writefd_unbuffered failed to write 311 bytes to socket [generator]: Connection timed out (110)
rsync error: error in rsync protocol data stream (code 12) at io.c(1530) [generator=3.0.7]
rsync error: received SIGUSR1 (code 19) at main.c(1288) [receiver=3.0.7]

BrZ · 09-11-2010, 10:14 AM

You can find some help here: http://www.samba.org/rsync/issues.html

"If you can't figure out why the failure happened, there are steps you can take to debug the situation. One way is to create a shell script on the remote system such as this one named "rsync-debug". You would use the script like this:

rsync -av --rsync-path=/some/path/rsync-debug host:source dest
rsync -av --rsync-path=/some/path/rsync-debug source host:dest

This script enables core dumps and also logs all the OS system calls that lead up to the failure to a file in the /tmp dir. You can use the resulting files to help figure out why the remote rsync failed."

'rsync-debug'

Quote:

#!/bin/sh

ulimit -c unlimited

# Some systems have "truss" or "tusc" instead of "strace".
# The -f option tells strace to follow children too.
strace -f rsync "${@}" 2>/tmp/rsync-$$.out