My mirror didn't sync up last night, just tried it manually and it's
erroring. Is there a problem?
@ERROR: max connections (25) reached - try again later
rsync: connection unexpectedly closed (68 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(151)
--
Just tried it myself and got the same error. I'll forward this on to our
server administrator and see if he can figure out who is clogging up all
the connections.
On Fri, 24 Jan 2003, Landon J. Dirgo (Digital Space, Corp.) wrote:
My mirror didn't sync up last night, just tried it manually and
In particular, there is currently one client tying up all 25 rsync
connections. We'll see what we can do to get this worked out.
Joshua.
On Fri, 24 Jan 2003, Landon J. Dirgo (Digital Space, Corp.) wrote:
My mirror didn't sync up last night, just tried it manually and it's
erroring. Is
not acked
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
Millennium hand and shrimp!
---BeginMessage---
I noticed that www.apache.org no longer
allows downloads, but requires the use of mirrors instead.
The offending site has been (at least temporarily) banned, and there are
now rsync slots available again.
Joshua.
On Fri, 24 Jan 2003, Landon J. Dirgo (Digital Space, Corp.) wrote:
My mirror didn't sync up last night, just tried it manually and it's
erroring. Is there a problem?
@ERROR:
I'm still not able to get through. Did they fill it up again or is it just
high traffic from the down period?
--
Landon J. Dirgo
[EMAIL PROTECTED]
Digital Space, Corp.
http://www.digitalspace.net
- Original Message -
From: Joshua Slive [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
Ugh. One client blocked, then another one came in and filled all the
slots again. I'm not sure what is going on, but it doesn't appear to be
a maliscious attack. Perhaps there is a problem on the apache.org side.
Some people are getting through, however.
We'll see what we can do.
Joshua.
The rsync slots are once again clear and we have banned the second site.
It is still unclear whether this was caused by
a) A coincidence of two very badly behaved clients
b) A problem on apache.org
c) Something else
Please do let us know if you have problems again.
Joshua.
On Fri, 24 Jan 2003,
