It's probably due to the same problem that I've been seeing with always
getting:
opening tcp connection to ftp.slackware.com port 873
@ERROR: max connections (25) reached - try again later
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(359)
That's been going on for some time now. It's almost like someone is running
a DOS attack against the server. With a max of 25 connections, that
wouldn't be too hard.
Mark Post
>On Sat, 22 Jan 2005 23:28:13 +0000 (UTC), Cichlidiot
><fish...@nospam.invalid> wrote:
>
>>I usually use ftp.scarlet.be (and its predecessor before it) to get my
>>updates, but its slackware-current branch has not synced since the Jan 3rd
>>update. Is it no longer a functioning mirror site or is this just a
>>temporary glitch?
>
>It's probably due to the same problem that I've been seeing with always
>getting:
>opening tcp connection to ftp.slackware.com port 873
>@ERROR: max connections (25) reached - try again later
Consider rsync'ing from mirror sites instead of hitting the main
distro server. Rsync puts a high load on servers, one of the
mirrors I use will handle 2000 ftp users but only 60 rsync users.
I'm running slack-current, and keep a local mirror -- that way I
already have most of 10.1 now, and wont be in the mad scramble
finding open ftp servers for the .iso's when 10.1 is released.
Cheers,
Grant.
In alt.os.linux.slackware, Mark Post dared to utter,
> It's probably due to the same problem that I've been seeing with always
> getting:
> opening tcp connection to ftp.slackware.com port 873
> @ERROR: max connections (25) reached - try again later
> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
> rsync error: error in rsync protocol data stream (code 12) at io.c(359)
I'm not sure if Pat has admin rights on ftp.slackware.com (IIRC some
one donates the bandwidth to him?), but it might be worth doing a
three-tier approach.
1st tier - ftp.slackware.com
2nd tier - registered mirrors
3rd tier - rest of the world
Idea is to only allow connections from the second tier to the 1st. I
think the BSD's do something like this, and IIRC Red Hat did something
similar by only allowing mirrors and RHN subscribers to access their
files for a brief time period.
- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFB8wnblKR45I6cfKARAqkdAKCsttAKq3eAk9MHPw2d0Y5TQg0UDwCeI67H
/CPZ7Td1npYUIrK/p+N6Si4=
=RxcY
-----END PGP SIGNATURE-----
>Consider rsync'ing from mirror sites instead of hitting the main
>distro server. Rsync puts a high load on servers, one of the
>mirrors I use will handle 2000 ftp users but only 60 rsync users.
This only works if the mirrors are able to get updated. I don't believe
they can because of the problem I described.
Mark Post
>I'm not sure if Pat has admin rights on ftp.slackware.com (IIRC some
>one donates the bandwidth to him?), but it might be worth doing a
>three-tier approach.
No, he doesn't. That's why all the packages you see on the server are owned
by "volkderdi:users" instead of "root:root."
Mark Post
That could also be because Pat prefers not to use the root account
unless he really has to. It's usually best to disable remote root
logins (over any protocol) and just use a user account.
--
Simon <si...@no-dns-yet.org.uk> **** GPG: F4A23C69
"We demand rigidly defined areas of doubt and uncertainty."
- Douglas Adams
This morning, I was checking several of the mirroring sites that offer
rsync (and use it to sync up with slackware.com) and I found that all of
those that I checked are still many days behind. I can not get into
slackware.com (on an rsync command) and I believe something is amiss,
here. Whether it is a DOS or an internal glitch, I guess we will have to
wait and see.
After a couple of the mirror sites get updated, I will try again.
--
humjohn AT aerosurf DOT net
>On Sat, 22 Jan 2005 23:17:46 -0500, Mark Post <mar...@nospam.net> wrote:
>> No, he doesn't. That's why all the packages you see on the server
>> are owned by "volkderdi:users" instead of "root:root."
>
>That could also be because Pat prefers not to use the root account
>unless he really has to. It's usually best to disable remote root
>logins (over any protocol) and just use a user account.
No, it's because the people who own the system won't give him root access.
Strange, but true.
Mark Post
>>I usually use ftp.scarlet.be (and its predecessor before it) to get my
>>updates, but its slackware-current branch has not synced since the Jan 3rd
>>update. Is it no longer a functioning mirror site or is this just a
>>temporary glitch?
> It's probably due to the same problem that I've been seeing with always
> getting:
> opening tcp connection to ftp.slackware.com port 873
> @ERROR: max connections (25) reached - try again later
> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
> rsync error: error in rsync protocol data stream (code 12) at io.c(359)
That could be it. And with the 10.1 rc announcement I doubt it will get
any better any time soon. I suppose I'll have to look around for a mirror
that has as nice of speed as scarlet does. The speed is what turned me on
to that mirror above all the others years ago. Alternatively, I suppose I
could just wait for my 10.1 subscription to come. The new box has sat idle
since I built it around Thanksgiving anyways due to a combo of work,
school and a sidelining sinus infection. What's a few more weeks at this
rate, heh.
ftp://ftp.slackware.com/pub/slackware/slackware-current/ChangeLog.txt:
Sat Jan 22 18:12:37 PST 2005
"Goes to show, you don't ever know"
grant@peetoo:~$ ls -l /home/install/slackware-current/ChangeLog.txt
-rw-r--r-- 1 grant wheel 60519 2005-01-23 13:12 /home/install/slackware-current/ChangeLog.txt
grant@peetoo:~$ head -n 3 /home/install/slackware-current/ChangeLog.txt
Sat Jan 22 18:12:37 PST 2005
"Goes to show, you don't ever know"
grant@peetoo:~$
Cheers,
Grant.
> It's probably due to the same problem that I've been seeing with always
> getting:
> opening tcp connection to ftp.slackware.com port 873
> @ERROR: max connections (25) reached - try again later
> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
> rsync error: error in rsync protocol data stream (code 12) at io.c(359)
>
>
> That's been going on for some time now. It's almost like someone is running
> a DOS attack against the server. With a max of 25 connections, that
> wouldn't be too hard.
Hi Mark, :-)
We will be pointing ftp.slackware.com to some other place (we meant to
do it some time ago, but with Pat's personal issues it just went low on
priority) as soon as possible, and in the mean time we already have
another place where Pat pushes updates to
I'm not going to write it on this newsgroup because then everyone would
start using it, and we'd be forced to login/pass restrict it for mirrors
only.
Anyway, if you or any mirror admin (just those listed on /getslack) is
having problems rsyncing from ftp.slackware.com, drop me an email at
mirrors@ or fizban@ and I'll point you out to the right direction - as
far as I know, ftp.scarlet.be should be aware of that server already,
but I might be wrong.
Also, to the users: if you notice a server "not so up to date", please
drop the server admin an email, and tell him/her to get in touch with
me. For me it's impossible to go mirror by mirror and check.. so your
help would be appreciated :-)
Andreas
I asked Patrick about this problem and he is aware.
There is another site which should be used by oficial mirrors
but some still appear to be using the slackware.com site in error.
I will pass on details of this site to MIRRORS ONLY if they
email me at crn(at)netunix(dot)com
Patrick is in the process of moving his official site and expects
to re-point DNS to the new site when he has finished work on 10.1
--
My real address is crn (at) netunix (dot) com
WARNING all messages containing attachments or html will be silently
deleted. Send only plain text.
> This morning, I was checking several of the mirroring sites that offer
> rsync (and use it to sync up with slackware.com) and I found that all of
> those that I checked are still many days behind. I can not get into
> slackware.com (on an rsync command) and I believe something is amiss,
> here. Whether it is a DOS or an internal glitch, I guess we will have to
> wait and see.
>
> After a couple of the mirror sites get updated, I will try again.
try http://alphageek.dyndns.org/linux/slackware-mirrors.shtml
those mirrors are up-to-date more than you'd expect.
>I'm not going to write it on this newsgroup because then everyone would
>start using it, and we'd be forced to login/pass restrict it for mirrors
>only.
Why not just post it to alt.binaries.cd.image.linux
ftp.scarlet.be is now back in action, I gave the mirror admin the
alternative source for rsyncing from
Andreas
Thanks for the link.