Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED]can't emerge --sync
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Tue Nov 27, 2007 4:31 pm    Post subject: [SOLVED]can't emerge --sync Reply with quote

I am trying more than a week to emerge --sync but I can't. I tried several portage rsync. Here are the errors I get with rsync://rsync.namerica.gentoo.org/gentoo-portage
Code:
>>> Starting rsync with rsync://209.189.242.21/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9]
>>> Retrying...

>>> Starting retry 1 of 3 with rsync://150.135.81.231/gentoo-portage
>>> Checking server timestamp ...
rsync8.us.gentoo.org
mirror.espri.arizona.edu
150.135.81.231
AMD Athlon 900 w/256 Megs SDRAM
100 Mbit connection
no user limit (unless bandwidth usage skyrockets)
University of Arizona, Geo-Sciences Department
Tucson, Arizona
Nick Lopez
nlopez@email.arizona.edu

timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9]
>>> Retrying...


>>> Starting retry 2 of 3 with rsync://206.75.218.53/gentoo-portage
>>> Checking server timestamp ...
Welcome to mirror2.arcticnetwork.ca

This server is one of two: (two of two, technically)
IBM eServer 340 - Dual Intel Xeon 3.06 GHz
4 Gigabytes RAM, 700GB Storage
1 Gigabit Ethernet (Dedicated)


Please visit http://mirror.arcticnetwork.ca.  We carry mirrors for:
FreeBSD, Gentoo, Solaris, Redhat/Fedora, and more!

admin@arcticnetwork.ca


Are you a gamer?  Visit www.agsn.ca.  The best games servers in the arctic!
Do you IRC?  If not, you should.  EFNet welcomes you!  Try irc.arcti.ca.


Arctic Network Mirrors - http://mirror.arcticnetwork.ca

timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9]
>>> Retrying...


>>> Starting retry 3 of 3 with rsync://128.213.5.35/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9]

!!! Rsync has not successfully finished. It is recommended that you keep
!!! trying or that you use the 'emerge-webrsync' option if you are unable
!!! to use rsync due to firewall or other restrictions. This should be a
!!! temporary problem unless complications exist with your network
!!! (and possibly your system's filesystem) configuration.


When I try with belnet rsync mirror ( rsync://rsync.belnet.be/gentoo-portage) get this error:
Code:
>>> Starting rsync with rsync://193.190.198.20/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9]
>>> Retrying...>>> Starting retry 1 of 3 with rsync://193.190.198.20/gentoo-portage
>>> Checking server timestamp ...
        Welcome to the BELNET public rsync daemon rsync.belnet.be::

This rsync archive resides on a quad-processor SunFire V440 with  16GB  RAM
and three StorEdge 3510 Arrays with more 4 TB of disk  space  for  the  FTP
archives.

This server is located in Brussels, Belgium and  operated  by  BELNET,  the
Education and research network  of  Belgium.   If  you  have  any  problem,
question or mirror request, please send them to ftpmaint@belnet.be

        This archive is also available through the following means
                        FTP     ftp://ftp.belnet.be
                       HTTP    http://ftp.belnet.be

          *   Note: opening many parallel connections to this   *
          *             host is considered an abuse             *


receiving file list ... timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9]
>>> Retrying...



Even if I try emerge-webrsync it is stucked.

Here is my /etc/make.conf file:
Code:
# Copyright 1999-2004 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-src/portage/cnf/make.conf.x86,v 1.5.2.5 2005/04/13 15:28:38 jstubbs Exp $
# Contains local system settings for Portage system

# Please review 'man make.conf' for more information.

# Build-time functionality
# ========================
#
# The USE variable is used to enable optional build-time functionality.
# For example, quite a few packages have optional X, gtk or GNOME functionality
# that can only be enabled or disabled at compile-time. Gentoo Linux has a
# very extensive set of USE variables described in our USE variable HOWTO at
# http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1
#
# The available list of use flags with descriptions is in your portage tree.
# Use 'less' to view them:  --> less /usr/portage/profiles/use.desc <--
#
# 'ufed' is an ncurses/dialog interface available in portage to make handling
# useflags for you. 'emerge app-portage/ufed'
#
# Example:

USE="bitmap-fonts truetype-fonts type1-fonts corefonts terminus-font \
     wxwindows X a52 arts avi aac bidi cdda crypt cups dvd dri \
     ffmpeg flac freetype gtk2 gtk gnutls httpd jpeg libg++ libwww \
     mmx sse sse2 mod mpeg ncurses oggvorbis opengl pdflib png \
     python qt readline spell stream ssl truetype usb vorbis xv xml2 xmms \
     xvmc xvid zlib win32codecs gnome kde alsa oss nptl nptlonly"

# Host Setting
# ============
#
# DO NOT CHANGE THIS SETTING UNLESS YOU ARE USING STAGE1!
# Change this line as appropriate (i686, i586, i486 or i386).
# All modern systems (even Athlons) should use "i686-pc-linux-gnu".
# All K6's are i586.
CHOST="i686-pc-linux-gnu"

# Host and optimization settings
# ==============================
#
# For optimal performance, enable a CFLAGS setting appropriate for your CPU.
#
# Please note that if you experience strange issues with a package, it may be
# due to gcc's optimizations interacting in a strange way. Please test the
# package (and in some cases the libraries it uses) at default optimizations
# before reporting errors to developers.
#
# -mcpu=<cpu-type> means optimize code for the particular type of CPU without
# breaking compatibility with other CPUs.
#
# -march=<cpu-type> means to take full advantage of the ABI and instructions
# for the particular CPU; this will break compatibility with older CPUs (for
# example, -march=athlon-xp code will not run on a regular Athlon, and
# -march=i686 code will not run on a Pentium Classic.
#
# CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp,
# athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
# (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron),
# pentium3, and pentium4.
#
# Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
#
# CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686
# (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95*
#
# CRITICAL WARNINGS: ****************************************************** #
# K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. #
# Pentium-M CPU's should not enable sse2 until at least gcc-3.4. Bug 50616. #
# ************************************************************************* #
#
# Decent examples:
#
#CFLAGS="-mcpu=athlon-xp -O3 -pipe"
CFLAGS="-march=pentium-m -O2 -fomit-frame-pointer -ftracer -msse -msse2 -mmmx -pipe"

# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
CXXFLAGS="${CFLAGS}"

# Advanced Masking
# ================
#
# Gentoo is using a new masking system to allow for easier stability testing
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
# on the platform they are set for. A special form has been added that
# indicates packages and revisions that are expected to work, but have not yet
# been approved for the stable set. '~arch' is a superset of 'arch' which
# includes the unstable, in testing, packages. Users of the 'x86' architecture
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
# '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
#
# Please note that this is not for development, alpha, beta, nor cvs release
# packages. "Broken" packages will not be added to testing and should not be
# requested to be added. Alternative routes are available to developers
# for experimental packages, and it is at their discretion to use them.
#
# DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
#
ACCEPT_KEYWORDS="x86"

# Portage Directories
# ===================
#
# Each of these settings controls an aspect of portage's storage and file
# system usage. If you change any of these, be sure it is available when
# you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
#
# PORTAGE_TMPDIR is the location portage will use for compilations and
#     temporary storage of data. This can get VERY large depending upon
#     the application being installed.
PORTAGE_TMPDIR=/var/tmp/portage
#
# PORTDIR is the location of the portage tree. This is the repository
#     for all profile information as well as all ebuilds. If you change
#     this, you must update your /etc/make.profile symlink accordingly.
PORTDIR=/usr/portage
#
# DISTDIR is where all of the source code tarballs will be placed for
#     emerges. The source code is maintained here unless you delete
#     it. The entire repository of tarballs for gentoo is 9G. This is
#     considerably more than any user will ever download. 2-3G is
#     a large DISTDIR.
DISTDIR=${PORTDIR}/distfiles
#
# PKGDIR is the location of binary packages that you can have created
#     with '--buildpkg' or '-b' while emerging a package. This can get
#     upto several hundred megs, or even a few gigs.
PKGDIR=${PORTDIR}/packages
#
# PORT_LOGDIR is the location where portage will store all the logs it
#     creates from each individual merge. They are stored as NNNN-$PF.log
#     in the directory specified. This is disabled until you enable it by
#     providing a directory. Permissions will be modified as needed IF the
#     directory exists, otherwise logging will be disabled. NNNN is the
#     increment at the time the log is created. Logs are thus sequential.
PORT_LOGDIR=/var/log/portage
#
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
#     concern that they will be deleted by rsync updates. Default is not
#     defined.
PORTDIR_OVERLAY=/usr/local/portage

# Fetching files
# ==============
#
# If you need to set a proxy for wget or lukemftp, add the appropriate "export
# ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
# all users on your system should use them.
#
# Portage uses wget by default. Here are some settings for some alternate
# downloaders -- note that you need to merge these programs first before they
# will be available.
#
# Default fetch command (5 tries, passive ftp for firewall compatibility)
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#
# Using wget, ratelimiting downloads
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#
# Lukemftp (BSD ftp):
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
#
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
# The list is a space separated list which is read left to right. If you use
# another mirror we highly recommend leaving the default mirror at the end of
# the list so that portage will fall back to it if the files cannot be found
# on your specified mirror. We _HIGHLY_ recommend that you change this setting
# to a nearby mirror by merging and using the 'mirrorselect' tool.
GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo http://mirror.switch.ch/ftp/mirror/gentoo/ http://mirror.hamakor.org.il/pub/mirrors/gentoo http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror http://www.ibiblio.org/pub/Linux/distributions/gentoo"
#
# Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
# The list is a single entry specifying the full address of the directory
# serving the tbz2's for your system. Running emerge with either '--getbinpkg'
# or '--getbinpkgonly' will cause portage to retrieve the metadata from all
# packages in the directory specified, and use that data to determine what will
# be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
# consult the man pages and 'emerge --help' for more information. For FTP, the
# default connection is passive -- If you require an active connection, affix
# an asterisk (*) to the end of the host:port string before the path.
#PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
# This ftp connection is passive ftp.
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
# This ftp connection is active ftp.
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site:21*/pub/grp/i686/athlon-xp/"

# Synchronizing Portage
# =====================
#
# Each of these settings affects how Gentoo synchronizes your Portage tree.
# Synchronization is handled by rsync and these settings allow some control
# over how it is done.
#
#
# SYNC is the server used by rsync to retrieve a localized rsync mirror
#     rotation. This allows you to select servers that are geographically
#     close to you, yet still distribute the load over a number of servers.
#     Please do not single out specific rsync mirrors. Doing so places undue
#     stress on particular mirrors.  Instead you may use one of the following
#     continent specific rotations:
#
#   Default:       "rsync://rsync.gentoo.org/gentoo-portage"
#   North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
#   South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
#   Europe:        "rsync://rsync.europe.gentoo.org/gentoo-portage"
#   Asia:          "rsync://rsync.asia.gentoo.org/gentoo-portage"
#   Australia:     "rsync://rsync.au.gentoo.org/gentoo-portage"
SYNC="rsync://rsync.belnet.be/gentoo-portage"
# rsync://rsync.namerica.gentoo.org/gentoo-portage rsync://linux.rz.ruhr-uni-bochum.de/gentoo-portage/ rsync://trumpetti.atm.tut.fi/gentoo-portage/ rsync://mirror.hamakor.org.il/gentoo-portage"
#
# RSYNC_RETRIES sets the number of times portage will attempt to retrieve
#     a current portage tree before it exits with an error. This allows
#     for a more successful retrieval without user intervention most times.
PORTAGE_RSYNC_RETRIES="5"
#
# RSYNC_TIMEOUT sets the length of time rsync will wait before it times out
#     on a connection. Most users will benefit from this setting as it will
#     reduce the amount of 'dead air' they experience when they run across
#     the occasional, unreachable mirror. Dialup users might want to set this
#     value up around the 300 second mark.
PORTAGE_RSYNC_RETRIES=3
# Advanced Features
# =================
#
# MAKEOPTS provides extra options that may be passed to 'make' when a
#     program is compiled. Presently the only use is for specifying
#     the number of parallel makes (-j) to perform. The suggested number
#     for parallel makes is CPUs+1.
MAKEOPTS="-j2"
#
# PORTAGE_NICENESS provides a default increment to emerge's niceness level.
#     Note: This is an increment. Running emerge in a niced environment will
#     reduce it further. Default is unset.
PORTAGE_NICENESS=3
#
# AUTOCLEAN enables portage to automatically clean out older or overlapping
#     packages from the system after every successful merge. This is the
#     same as running 'emerge -c' after every merge. Set with: "yes" or "no".
#     This does not affect the unpacked source. See 'noclean' below.
AUTOCLEAN="yes"
#
# PORTAGE_TMPFS is a location where portage may create temporary files.
#     If specified, portage will use this directory whenever possible
#     for all rapid operations such as lockfiles and transient data.
#     It is _highly_ recommended that this be a tmpfs or ramdisk. Do not
#     set this to anything that does not give a significant performance
#     enhancement and proper FS compliance for locks and read/write.
#     /dev/shm is a glibc mandated tmpfs, and should be a reasonable
#     setting for all linux kernel+glibc based systems.
PORTAGE_TMPFS="/dev/shm"
#
# FEATURES are settings that affect the functionality of portage. Most of
#     these settings are for developer use, but some are available to non-
#     developers as well.
#
#  'autoaddcvs'  causes portage to automatically try to add files to cvs
#                that will have to be added later. Done at generation times
#                and only has an effect when 'cvs' is also set.
#  'buildpkg'    causes binary packages to be created of all packages that
#                are being merged.
#  'ccache'      enables ccache support via CC.
#  'collision-protect'
#                prevents packages from overwriting files that are owned by
#                another package or by no package at all.
#  'cvs'         causes portage to enable all cvs features (commits, adds),
#                and to apply all USE flags in SRC_URI for digests -- for
#                developers only.
#  'digest'      causes digests to be generated for all packages being merged.
#  'distcc'      enables distcc support via CC.
#  'distlocks'   enables distfiles locking using fcntl or hardlinks. This
#                is enabled by default. Tools exist to help clean the locks
#                after crashes: /usr/lib/portage/bin/clean_locks.
#  'fixpackages' allows portage to fix binary packages that are stored in
#                PKGDIR. This can consume a lot of time. 'fixpackages' is
#                also a script that can be run at any given time to force
#                the same actions.
#  'gpg'         enables basic verification of Manifest files using gpg.
#                This features is UNDER DEVELOPMENT and reacts to features
#                of strict and severe. Heavy use of gpg sigs is coming.
#  'keeptemp'    prevents the clean phase from deleting the temp files ($T)
#                from a merge.
#  'keepwork'    prevents the clean phase from deleting the WORKDIR.
#  'maketest'    causes ebuilds to perform testing phases if they are capable
#                of it. Some packages support this automaticaly via makefiles.
#  'noauto'      causes ebuild to perform only the action requested and
#                not any other required actions like clean or unpack -- for
#                debugging purposes only.
#  'noclean'     prevents portage from removing the source and temporary files
#                after a merge -- for debugging purposes only.
#  'nostrip'     prevents the stripping of binaries.
#  'notitles'    disables xterm titlebar updates (which contain status info).
#  'sandbox'     enables sandboxing when running emerge and ebuild.
#  'strict'      causes portage to react strongly to conditions that are
#                potentially dangerous, like missing/incorrect Manifest files.
#  'userpriv'    allows portage to drop root privileges while it is compiling,
#                as a security measure.  As a side effect this can remove
#                sandbox access violations for users.
#  'usersandbox' enables sandboxing while portage is running under userpriv.
#FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork autoaddcvs"
FEATURES="sandbox ccache distcc distlocks autoaddcvs"
#
# CCACHE_SIZE sets the space use limitations for ccache. The default size is
#     2G, and will be set if not defined otherwise and ccache is in features.
#     Portage will set the default ccache dir if it is not present in the
#     user's environment, for userpriv it sets: ${PORTAGE_TMPDIR}/ccache
#     (/var/tmp/ccache), and for regular use the default is /root/.ccache.
#     Sizes are specified with 'G' 'M' or 'K'.
#     '2G' for 2 gigabytes, '2048M' for 2048 megabytes (same as 2G).
CCACHE_SIZE="512M"
#
# DISTCC_DIR sets the temporary space used by distcc.
#DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"
#
# RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates
#     the portage tree. Specific chunks of the tree may be excluded from
#     consideration. This may cause dependency failures if you are not careful.
#     The file format is one pattern per line, blanks and ';' or '#' lines are
#     comments. See 'man rsync' for more details on the exclude-from format.
#RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes

# logging related variables:
# PORTAGE_ELOG_CLASSES: selects messages to be logged, possible values are:
#                          info, warn, error, log, qa
#                       Warning: commenting this will disable elog
PORTAGE_ELOG_CLASSES="warn error info log"

# PORTAGE_ELOG_SYSTEM: selects the module(s) to process the log messages. Modules
#                      included in portage are (empty means logging is disabled):
#                          save (saves one log per package in $PORT_LOGDIR/elog,
#                                /var/log/portage/elog if $PORT_LOGDIR is unset)
#                          custom (passes all messages to $PORTAGE_ELOG_COMMAND)
#                          syslog (sends all messages to syslog)
#                          mail (send all messages to the mailserver defined
#                                in $PORTAGE_ELOG_MAILURI)
#                          save_summary (like "save" but merges all messages
#                                        in $PORT_LOGDIR/elog/summary.log,
#                                        /var/log/portage/elog/summary.log if
#                                        $PORT_LOGDIR is unset)
#                          mail_summary (like "mail" but sends all messages in
#                                        a single mail when emerge exits)
#                      To use elog you should enable at least one module
PORTAGE_ELOG_SYSTEM="save"

# PORTAGE_ELOG_COMMAND: only used with the "custom" logging module. Specifies a command
#                      to process log messages. Two variables are expanded:
#                          ${PACKAGE} - expands to the cpv entry of the processed
#                                       package (see $PVR in ebuild(5))
#                          ${LOGFILE} - absolute path to the logfile
#                                               Both variables have to be quoted with single quotes
#PORTAGE_ELOG_COMMAND="/path/to/logprocessor -p '\${PACKAGE}' -f '\${LOGFILE}'"

# PORTAGE_ELOG_MAILURI: this variable holds all important settings for the mail
#                       module. In most cases listing the recipient address and
#                       the receiving mailserver should be sufficient, but you can
#                       also use advanced settings like authentication or TLS. The
#                       full syntax is:
#                           address [[user:passwd@]mailserver[:port]]
#                       where
#                           address:    recipient address
#                           user:       username for smtp auth (defaults to none)
#                           passwd:     password for smtp auth (defaults to none)
#                           mailserver: smtp server that should be used to deliver the mail (defaults to localhost)
#                                       alternatively this can also be a the path to a sendmail binary if you don'$
#                           port:       port to use on the given smtp server (defaults to 25, values > 100000 indi$
#                       Examples:
#PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting)
PORTAGE_ELOG_MAILURI="sapirf@gmail.com gmail.com"
#PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader$

# PORTAGE_ELOG_MAILFROM: you can set the from-address of logmails with this variable,
#                        if unset mails are sent by "portage" (this default may fail
#                        in some environments).
#PORTAGE_ELOG_MAILFROM="portage@some.domain"

# PORTAGE_ELOG_MAILSUBJECT: template string to be used as subject for logmails. The following
#                           variables are expanded:
#                               ${PACKAGE} - see description of PORTAGE_ELOG_COMMAND
#                               ${HOST} - FQDN of the host portage is running on
PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} with notice"

LINGUAS="il"
INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="i810"
ALSA_CARDS="intel8x0,intel8x0m"
LIRC_DEVICES="devinput"


What is wrong? I am behind a router but I never had such a problem. I never opened a port to emerge sync.


Last edited by queen on Tue Dec 04, 2007 8:00 am; edited 3 times in total
Back to top
View user's profile Send private message
Paulathome
n00b
n00b


Joined: 05 Jan 2006
Posts: 17

PostPosted: Tue Nov 27, 2007 5:41 pm    Post subject: Reply with quote

I am having a similar problem, but at least emerge-webrsync works for me. I have been unable to find a solution so if u come across a fix let us know!

Paul
Back to top
View user's profile Send private message
didymos
Advocate
Advocate


Joined: 10 Oct 2005
Posts: 4798
Location: California

PostPosted: Tue Nov 27, 2007 5:55 pm    Post subject: Re: can't emerge --sync Reply with quote

queen wrote:
Here are the errors I get with http://www.voicetrading.com/index.html


What does that site have to do with this?
_________________
Thomas S. Howard
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Tue Nov 27, 2007 5:59 pm    Post subject: Re: can't emerge --sync Reply with quote

didymos wrote:
queen wrote:
Here are the errors I get with http://www.voicetrading.com/index.html


What does that site have to do with this?


Sorry a paste mistake. Corrected now.

Do you happen to know what's the problem?


Last edited by queen on Tue Nov 27, 2007 6:02 pm; edited 1 time in total
Back to top
View user's profile Send private message
didymos
Advocate
Advocate


Joined: 10 Oct 2005
Posts: 4798
Location: California

PostPosted: Tue Nov 27, 2007 6:01 pm    Post subject: Reply with quote

Ah, OK. I couldn't figure out what the hell that meant. Anyway, did your ISP maybe start blocking rsync or something?
_________________
Thomas S. Howard
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Tue Nov 27, 2007 6:05 pm    Post subject: Reply with quote

didymos wrote:
Ah, OK. I couldn't figure out what the hell that meant. Anyway, did your ISP maybe start blocking rsync or something?


I don't know. They don't say anything. But I have lately lots of problems with p2p, ftp to holland. You think this could be a problem? I have a fixed IP, and I am using my router to forward ports. Never opened ports for rsync.

What are the ports for rsync? I will ask them.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Tue Nov 27, 2007 8:15 pm    Post subject: Reply with quote

Paulathome wrote:
I am having a similar problem, but at least emerge-webrsync works for me. I have been unable to find a solution so if u come across a fix let us know!

Paul


I managed to emerge-webrsync. No solution yet for emerge --sync. I wait for the isp call. Maybe they block ports.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Wed Nov 28, 2007 6:53 am    Post subject: Reply with quote

Paulathome wrote:
I am having a similar problem, but at least emerge-webrsync works for me. I have been unable to find a solution so if u come across a fix let us know!

Paul


Dear Paul

I wrote now a letter to ftpmaint at belnet.be from where I sync my system and asked them maybe they know something. waiting for their reply.

Queen
Back to top
View user's profile Send private message
SteveYin
Tux's lil' helper
Tux's lil' helper


Joined: 20 Oct 2004
Posts: 91

PostPosted: Wed Nov 28, 2007 7:39 am    Post subject: Reply with quote

yes, I have some problems with my rsync mirror server, my server is rsync1.cn.gentoo.org

I can not use emerge --sync to this mirror, but if i only use rsync --av rsync://rsync1.cn.gentoo.org/gentoo-portage /usr/portage, then it work like a charm.

but another server can use emerge --sync on this mirror. I start to thinking if this problem is related to glibc-2.6.1, this rsync server is running with 2.6.1, and those gentoo computer can not use --sync also runs glibc-2.6.1, but the server can run rsync is run at glibc-2.3.5
_________________
Steve Yin
Back to top
View user's profile Send private message
SteveYin
Tux's lil' helper
Tux's lil' helper


Joined: 20 Oct 2004
Posts: 91

PostPosted: Wed Nov 28, 2007 7:40 am    Post subject: Reply with quote

btw, I got the exact same error with you:
Code:

timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9]

_________________
Steve Yin
Back to top
View user's profile Send private message
Paulathome
n00b
n00b


Joined: 05 Jan 2006
Posts: 17

PostPosted: Wed Nov 28, 2007 7:05 pm    Post subject: Reply with quote

Hi queen,

interesting, belnet.be is one of the servers I use too (and one of the ones I am having a problem with!)

Did you find out what port rsync uses? I think i will check with my ISP to see if they are blocking it...



Steve,

I tried manual rsync like you did but it did not work... I left it sit there for about an hour and there was no error, no progress and it looked like there was no nnetwork traffic either (acticity lights on my router for that port showed nothing happening..)


let us know if you make any progress

cheers,
Paul.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Wed Nov 28, 2007 8:41 pm    Post subject: Reply with quote

Paulathome wrote:
Hi queen,

interesting, belnet.be is one of the servers I use too (and one of the ones I am having a problem with!)

Did you find out what port rsync uses? I think i will check with my ISP to see if they are blocking it...


Paul, I googled and found that port 873 tcp, udp are responsible for rsync. The ISP didn't call me yet, and from belnet I didn't receive any answer. But since we all have the same problem, I tend to think it's not isp blocking ports. The bad thing is that I tried usa portage as well and it didn't work either. ;-(
Back to top
View user's profile Send private message
Paulathome
n00b
n00b


Joined: 05 Jan 2006
Posts: 17

PostPosted: Thu Nov 29, 2007 4:22 pm    Post subject: Reply with quote

thanks,

I will check out wiht my ISP too...

Paul/
Back to top
View user's profile Send private message
linuxfreak.me
n00b
n00b


Joined: 29 Nov 2007
Posts: 3

PostPosted: Thu Nov 29, 2007 8:42 pm    Post subject: Reply with quote

:) Hi guys im a newbie to gentoo,i heard a lot about how good it is and finally im in a position to start learning it.

but my emerge --sync isnt workin and im unable to install nething.is ther ne other way to install,i wanna get my nvidia drivers first,everything else il be able to manage.....i have a .run file from the nvidia site.will it work???

coming to why emerge --sync is not workin.

i get this error.

Code:
>>> Starting rsync with rsync://134.68.220.97/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
>>> Retrying...


>>> Starting retry 1 of 3 with rsync://134.68.220.73/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
>>> Retrying...


>>> Starting retry 2 of 3 with rsync://140.211.166.165/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
>>> Retrying...


>>> Starting retry 3 of 3 with rsync://64.127.121.98/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]




im a student and am using the LAN provided by the collg.is it possible that they have blocked the ports??can u tell me which ports rsync works on so tht i can mail them abt tht.

thnks in Advance.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Thu Nov 29, 2007 9:22 pm    Post subject: Reply with quote

linuxfreak.me wrote:
:) Hi guys im a newbie to gentoo,i heard a lot about how good it is and finally im in a position to start learning it.

but my emerge --sync isnt workin and im unable to install nething.is ther ne other way to install,i wanna get my nvidia drivers first,everything else il be able to manage.....i have a .run file from the nvidia site.will it work???

coming to why emerge --sync is not workin.

i get this error.

Code:
>>> Starting rsync with rsync://134.68.220.97/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
>>> Retrying...


>>> Starting retry 1 of 3 with rsync://134.68.220.73/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
>>> Retrying...


>>> Starting retry 2 of 3 with rsync://140.211.166.165/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
>>> Retrying...


>>> Starting retry 3 of 3 with rsync://64.127.121.98/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]




im a student and am using the LAN provided by the collg.is it possible that they have blocked the ports??can u tell me which ports rsync works on so tht i can mail them abt tht.

thnks in Advance.


Hi linuxfreak

welcome to gentoo. We have currently a problem with emerge --sync. The reason is not clear yet. I tend to think it's not a blocking of ports issue. The ports that rsync work are 873 for udp, tcp. Ask the sys admin in the college if they block it.

Meanwhile, try emerge-webrsync. Start with installing gentoo according to the manual. After that go to the nvidia issue. There are a lot of posts in these forums about nvidia card. Try to check also http://www.gentoo-wiki.com

If I solve the issue, I will post it here.

Good luck.
Back to top
View user's profile Send private message
linuxfreak.me
n00b
n00b


Joined: 29 Nov 2007
Posts: 3

PostPosted: Thu Nov 29, 2007 9:37 pm    Post subject: Reply with quote

wowwwwww.......................

thats the fastest reply i ever got on a forum.thnks dude.

k,il check it on the wiki.and about the emerge-webrsync.i tried it but of no use.il give it a try again.

i installed from the live cd.is it ok bcoz we have a serious network problem here.they have deployed a server called Cyberoam which is not processing more than a request at a time and using package managers has become hell.

ne ways thnks again.

__________________________________________________________________________________



Quote:
"Out of clutter, find simplicity. From discord, find harmony. In the middle of difficulty, lies opportunity." - Albert Einstein.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Mon Dec 03, 2007 8:20 pm    Post subject: Reply with quote

I emerged world. Among it, was emerge glibc. The problem isn't solved yet. I can only say that glibc is not the problem.

I tried belnet , rsync://rsync.namerica.gentoo.org/gentoo-portage rsync://linux.rz.ruhr-uni-bochum.de/gentoo-portage/

None of them worked. ;-(

I tend to believe it's something with rsync. I saw some posts on google with the same error. No solution yet.
Back to top
View user's profile Send private message
linuxfreak.me
n00b
n00b


Joined: 29 Nov 2007
Posts: 3

PostPosted: Mon Dec 03, 2007 9:57 pm    Post subject: I Found a solution....... Reply with quote

i found a solution for ' emerge --sync '.
i googled the package name (portage-200711** - watever),and found a site and downloaded manually.i extracted it and replaced the folder /usr/portage with my extracted folder.i backed-up the old one for safety.then i used ' emerge nvidia-drivers ',eager it will work or not...luckily it updated itself in a sec and now its workin fyn.

better get it downloaded by a download manager,i use Internet download manager on wine,it works gr8.

Quote:
If your father is poor its ur fate,if ur father-in-law is poor its ur foolishness.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Tue Dec 04, 2007 7:39 am    Post subject: Reply with quote

freakinglinux, it's great that you found this solution. I did it once and it worked. Forgot to mention it. But it's quite annoying to sync it that way each time.


However I found a solution for emerge --sync, and this one is the best. I took the solution from another thread in gentoo forums. Here it comes:

In /etc/make.conf I added in SYNC field
Code:

SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"

This solved the problem. It searches through all europe mirrors and downloads from where it manages to connect. When I tried belgium, germany, switzerland specifically it didn't work. With europe it started to download from Holland and it worked. Moreover after finishing emerge --sync I did
Code:
emerge system
and it emerged rsync package version 2.6.9-r5 which I didn't had before (neither appeared there is such a version after I used
Code:
 emerge-webrsync
Code:
 emerge system && update-eix
). I suspect that emerge-webrsync is less updated.

I made another change with opendns, but I don't think it's related for this problem. If it won't work I will tell you.

Paul, let me know if that works for you.

Queen
Back to top
View user's profile Send private message
Paulathome
n00b
n00b


Joined: 05 Jan 2006
Posts: 17

PostPosted: Thu Dec 06, 2007 5:57 pm    Post subject: Reply with quote

HI queen,

glad you got it working!

I'm afraid that solution did not work for me. emere --sync is now trying lots of different servers alright but all are timing out. They download the timestamp file no problem but the sync itself is not working.

I am still waiting on a response from my ISP wrt pot blocking. I reckon it must be something like that..

webrsync is working fine for me so I am able to keep the system up to date anyway but it is much slower than rsync is (should be!)


cheers,

Paul.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Thu Dec 06, 2007 6:16 pm    Post subject: Reply with quote

Paulathome wrote:
HI queen,

glad you got it working!

I'm afraid that solution did not work for me. emere --sync is now trying lots of different servers alright but all are timing out. They download the timestamp file no problem but the sync itself is not working.

I am still waiting on a response from my ISP wrt pot blocking. I reckon it must be something like that..

webrsync is working fine for me so I am able to keep the system up to date anyway but it is much slower than rsync is (should be!)


cheers,

Paul.


I read in these forums that it's a dns problem. So I decided to try the opendns solution. It's free and you don't need to use the dns of the isp. Here are the instructions of opendns. https://www.opendns.com/start. I had a lot of problems lately with connection. Like linuxdcpp, gtalk disconnects.

They have the instructions how to make it permanent on suse, ubuntu. Otherwise the info changes if you reboot. I changed my /etc/conf.d/net. I can post it here, but I am not sure that mine is correct, because I still have some problems with the connection. Let me know if you want it here, maybe we will troubleshoot my network file.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1633

PostPosted: Thu Dec 06, 2007 8:29 pm    Post subject: Reply with quote

Here is the reply I got from belnet admin:

Quote:
Hi,

Some persons at BELNET use gentoo as well, and the rsync runs fine with
them so you probably tried on a busy moment. We limit the number of
rsync connections from the internet, so probably you had no luck :-)

with friendly regards,

Franky Van Liedekerke
BELNET support team
Back to top
View user's profile Send private message
wklam
n00b
n00b


Joined: 09 May 2005
Posts: 41

PostPosted: Wed Dec 19, 2007 5:51 am    Post subject: can't emerge --sync Reply with quote

I *SEEM* to have found a solution.

I was getting the same problem with emerge --sync timeout.

I tried to add the following line to my "/etc/make.conf"

Code:
PORTAGE_RSYNC_EXTRA_OPTS="--timeout=500"


with no effect.

I looked at python script "/usr/bin/emerge". I found another variable "PORTAGE_RSYNC_INITIAL_TIMEOUT" which could be related.

So I added the following line into "/etc/make.conf"

Code:
PORTAGE_RSYNC_INITIAL_TIMEOUT=500


This seems to fix the timeout problem.

By default, PORTAGE_RSYNC_INITIAL_TIMEOUT was set to 15 second. As a result, if the rsync is getting a slow response from the portage server (longer than 15 second), then emerge --sync will generate a timeout error.

If you are seeing the same "emerge --sync timeout" problem, you might want to add the PORTAGE_RSYNC_INITIAL_TIMEOUT to "/etc/make.conf" too.

Hope this helps.

-William
Back to top
View user's profile Send private message
atti_simon
n00b
n00b


Joined: 28 Oct 2006
Posts: 15
Location: Romania - Brasov

PostPosted: Sun Dec 23, 2007 9:47 am    Post subject: Reply with quote

Thanks, mate!

It works here too, with europe rsync servers.

Thanks again :)
Back to top
View user's profile Send private message
dark_knight
Tux's lil' helper
Tux's lil' helper


Joined: 22 Apr 2006
Posts: 112

PostPosted: Sun Dec 23, 2007 11:08 am    Post subject: Re: can't emerge --sync Reply with quote

wklam wrote:
If you are seeing the same "emerge --sync timeout" problem, you might want to add the PORTAGE_RSYNC_INITIAL_TIMEOUT to "/etc/make.conf" too.

Thanks, you saved my day ;)
_________________
You can say that you are a true Gentoo-addicted when you type emerge --update --deep --newuse happiness.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum