Hi forum

when tryin to sync sbopkg, i get this error...

rsync: failed to connect to slackbuilds.org: connection timed out rsync error : error in socket IO (code 10 ) at clientserver.c(124)

rsync reported a socket error which may be due to a problem with the LINK value in sbopkg.conf

the repo's link is currently set to: slackbuilds.org::slackbuilds

please check your settings and try again later...


I installed sbopkg with the default configuration..

How did this happen...?

How can I solve it...?


Here-s my sbopkg.conf

# $Id: sbopkg.conf.new 673 2009-07-09 14:05:44Z mauro.giachero $
#
# Please read the sbopkg.conf(5) man page for information about this
# configuration file, including an explanation of how to set these
# variables.

# The following are variables used by sbopkg. Any of these variables could
# be exported, if desired.
# Directory variables
REPO_ROOT=${REPO_ROOT:-/var/lib/sbopkg}
LOGDIR=${LOGDIR:-/var/log/sbopkg}
QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}
SRCDIR=${SRCDIR:-/var/cache/sbopkg}
SBOPKGTMP=${SBOPKGTMP:-/tmp/sbopkg}
# Non-directory variables:
REPO_NAME=${REPO_NAME:-SBo}
REPO_BRANCH=${REPO_BRANCH:-13.0}
KEEPLOG=YES
LOGFILE=$LOGDIR/sbopkg-build-log
DEBUG=0
CLEANUP=NO

# The following variables are used by sbopkg and by the SlackBuild scripts
# themselves. They are exported for this reason.
export TMP=${TMP:-/tmp/SBo}
export OUTPUT=${OUTPUT:-/tmp}

# The following variables are required and can be tweaked if desired,
# although most users should leave them alone. Note: rsync already uses
# --archive, --delete, --no-owner, and --exclude in the main sbopkg script
# so there is no need to add those flags here. Similarly, wget already
# uses the -O options so there is no need to add that either. In general,
# it is not recommended that users change these default values.
RSYNCFLAGS="--verbose --timeout=10"
WGETFLAGS="--continue --progress=bar --timeout=15 --tries=5"
DIFF=${DIFF:-diff}
DIFFOPTS=${DIFFOPTS:--u}



is there anything unusual here...?


BRGDS


ALEX


BTW

I have internet connection in this machine.... in fact, I am posting from my laptop right now... but some things are strange.... for instance this...


bash-3.1# git clone git://repo.or.cz/OpenFOAM-1.6.x.git
Initialized empty Git repository in /home/alex/OpenFOAM/OpenFOAM-1.6.x/.git/
repo.or.cz[0: 62.24.64.27]: errno=Connection timed out

but

bash-3.1# git clone http://repo.or.cz/r/OpenFOAM-1.6.x.git
Initialized empty Git repository in /home/alex/OpenFOAM/OpenFOAM-1.6.x/.git/
got 384e9c2ea6d32f8b38b9b6e923ff8f43bd4f6ce2
walk 384e9c2ea6d32f8b38b9b6e923ff8f43bd4f6ce2
got 66599da098989f8dc1008f2bb29add6c1a1f80fe
got e136aa2662a347d948314d4122e7f1276541394e
Getting alternates list for http://repo.or.cz/r/OpenFOAM-1.6.x.git
walk e136aa2662a347d948314d4122e7f1276541394e
Getting pack list for http://repo.or.cz/...............

........................................


works ok... is it a firewall problem that is stopping the sync of sbopkg...?


BRGDS

Alex


.

mmm.... I'd say:
Maybe you upgraded sbopkg and forgot to merge sbopkg.conf. You now have sbopkg.conf and
sbopkg.conf.new in /etc/sbopkg/

EDIT: nvm, ignore my post. Mine has it too, sorry.

2 members found this post helpful.

Can you use slackpkg? Try to get the changelog using slackpkg and see if it works. sbopkg is working fine for me. Maybe due to a mirror timeout? Although the error doesn't indicate that.

2 members found this post helpful.

I had this problem & had to lengthen the "timeout" parameter in the "RSYNCFLAGS" line. However, since the last upgrade, the default value has been working fine for me.
Note: You maybe should copy your first post to the sbopkg mailing list.
Regards,
Bill

1 members found this post helpful.

It might because firewall has blocked rsync (port 873).

Solution:
1. Download & install TOR from www.torproject.org
2. Install polipo & torsocks
3. Run "sudo torsocks sbopkg -r"
4. Done, repository synced!

2 members found this post helpful.

Yeah, the .new is in the name of the file in revision control, so shows up in that line (which is confusing and will probably be changed) but the OP has either forgotten to merge files for a long time or is using a very out-of-date sbopkg - that's from 0.30.1 and the current release is 0.34.1.

Yep, based on the fact that http for git works and the git protocol doesn't and the fact that rsync isn't working, it's very likely the case that that's blocked, too.

Yeah and I hope it helps.

I'm having the same problem and I just installed sbopkg.

I'm on version 0.37.0 - I think the rsync port is being blocked.

I will try the Tor solution and report back when I have time.