Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 506120 - bobolink.gentoo.org's rsyncd doesn't seem to be working
Summary: bobolink.gentoo.org's rsyncd doesn't seem to be working
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Infrastructure
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-28 22:11 UTC by Matt Turner
Modified: 2014-04-11 16:11 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Turner gentoo-dev 2014-03-28 22:11:10 UTC
bobolink's rsyncd mirror doesn't seem to be working, but the box responds to pings and nmap -P0 -p 873 says the port is open.
Comment 1 Stefan Behte (RETIRED) gentoo-dev Security 2014-03-28 23:13:27 UTC
Well, it works for me:

$ rsync rsync://bobolink.gentoo.org/gentoo-portage/

Welcome to bobolink.gentoo.org / rsync.gentoo.org

Server Address : 140.211.166.189
Contact Name   : mirror-admin@gentoo.org
Hardware       : 4 x Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 3960MB RAM
Sponsor        : Gentoo Linux, Open Source Lab, Corvallis, OR, USA

Please note: common gentoo-netiquette says you should not sync more
than once a day.  Users who abuse the rsync.gentoo.org rotation
may be added to a temporary ban list.

MOTD autogenerated by update-rsync-motd on Sun Apr  1 01:06:12 UTC 2012

drwxr-xr-x        5000 2014/03/28 23:31:40 .
-rw-r--r--         121 2014/01/01 01:31:01 header.txt
-rw-r--r--        3658 2014/01/01 01:31:01 skel.ChangeLog
[...]

Are you using ipv6 or ipv4?
Comment 2 Matt Turner gentoo-dev 2014-03-28 23:40:03 UTC
I'm using IPv4.

server mattst88 # emerge --sync
>>> Synchronization of repository 'gentoo' located in '/usr/portage'...
>>> Starting rsync with rsync://140.211.166.189/gentoo-portage/...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(549) [Receiver=3.0.9]
>>> Retrying...
!!! Exhausted addresses for bobolink.gentoo.org

Running just rsync rsync://bobolink.gentoo.org/gentoo-portage/ works. So, some kind of user error?

/etc/portage/make.conf contains

SYNC="rsync://bobolink.gentoo.org/gentoo-portage/"
Comment 3 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2014-03-29 00:12:21 UTC
%% rsync bobolink.gentoo.org::
Welcome to bobolink.gentoo.org / rsync.gentoo.org

Server Address : 140.211.166.189
Contact Name   : mirror-admin@gentoo.org
Hardware       : 4 x Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 3960MB RAM
Sponsor        : Gentoo Linux, Open Source Lab, Corvallis, OR, USA

Please note: common gentoo-netiquette says you should not sync more
than once a day.  Users who abuse the rsync.gentoo.org rotation
may be added to a temporary ban list.

MOTD autogenerated by update-rsync-motd on Sun Apr  1 01:06:12 UTC 2012

gentoo-x86-portage	Gentoo Linux Portage tree
gentoo-portage 	Gentoo Linux Portage tree mirror
Comment 4 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2014-03-29 00:15:12 UTC
(In reply to Matt Turner from comment #2)

> Running just rsync rsync://bobolink.gentoo.org/gentoo-portage/ works. So,
> some kind of user error?
> 
> /etc/portage/make.conf contains
> 
> SYNC="rsync://bobolink.gentoo.org/gentoo-portage/"

Also WFM.
Comment 5 Stefan Behte (RETIRED) gentoo-dev Security 2014-03-29 23:20:22 UTC
Matt, can you try from a different location? For us it seems, that it works from everywhere, so please make sure there is no problem. I advice using tcpdump to verify your network works fine.
Comment 6 Matt Turner gentoo-dev 2014-04-11 16:11:27 UTC
(In reply to Stefan Behte from comment #5)
> Matt, can you try from a different location? For us it seems, that it works
> from everywhere, so please make sure there is no problem. I advice using
> tcpdump to verify your network works fine.

It works from different networks. It must be a problem specific to my network.