Hi,
On 3/12/2012 3:20 PM, Adam Ring wrote:
I am all of a sudden getting the same issue started with my midnight sync and has happened every since:
Mon Mar 12 00:05:02 EDT 2012 msync-dvd.centos.org: 64.131.88.98
Mon Mar 12 04:05:02 EDT 2012 msync-dvd.centos.org: 64.131.83.114
Mon Mar 12 08:05:04 EDT 2012 msync-dvd.centos.org: 67.203.12.30
All produce:
receiving file list ... pre-xfer exec returned failure (256) rsync error: requested action not supported (code 4) at clientserver.c(869) [sender=3.0.6] rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(759) [receiver=3.0.6]
Looks like 62.141.54.220 affected too.
I also get same issue on following servers: 91.215.65.226 94.228.209.140 88.208.217.170
Regards, Damjan
On 03/13/2012 01:23 AM, Damjan Sirnik wrote:
Hi,
On 3/12/2012 3:20 PM, Adam Ring wrote:
I am all of a sudden getting the same issue started with my midnight sync and has happened every since:
Mon Mar 12 00:05:02 EDT 2012 msync-dvd.centos.org: 64.131.88.98
Mon Mar 12 04:05:02 EDT 2012 msync-dvd.centos.org: 64.131.83.114
Mon Mar 12 08:05:04 EDT 2012 msync-dvd.centos.org: 67.203.12.30
All produce:
receiving file list ... pre-xfer exec returned failure (256) rsync error: requested action not supported (code 4) at clientserver.c(869) [sender=3.0.6] rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(759) [receiver=3.0.6]
Looks like 62.141.54.220 affected too.
I also get same issue on following servers: 91.215.65.226 94.228.209.140 88.208.217.170
Regards, Damjan _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
You can only open one connection at a time.
Are you trying to do more than one connection at a time?
On 03/14/2012 02:21 PM, Johnny Hughes wrote:
On 03/13/2012 01:23 AM, Damjan Sirnik wrote:
Hi,
On 3/12/2012 3:20 PM, Adam Ring wrote:
I am all of a sudden getting the same issue started with my midnight sync and has happened every since:
Mon Mar 12 00:05:02 EDT 2012 msync-dvd.centos.org: 64.131.88.98
Mon Mar 12 04:05:02 EDT 2012 msync-dvd.centos.org: 64.131.83.114
Mon Mar 12 08:05:04 EDT 2012 msync-dvd.centos.org: 67.203.12.30
All produce:
receiving file list ... pre-xfer exec returned failure (256) rsync error: requested action not supported (code 4) at clientserver.c(869) [sender=3.0.6] rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(759) [receiver=3.0.6]
Looks like 62.141.54.220 affected too.
I also get same issue on following servers: 91.215.65.226 94.228.209.140 88.208.217.170
Regards, Damjan _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
You can only open one connection at a time.
Are you trying to do more than one connection at a time?
For the record, there were a couple of jerks who decided that they could open up 20-30 rsyncs at the same time on different directory paths. This practice hogged all the resources during the release, not allowing others to rsync.
Now, you may only make one rsync connection to a server at a time for a given module.
Make sure to thank the abusers for us.
will rsync automatically limit to 1 connection or do we have to set it to 1 connection?
if so could you elaborate on how?
i'm not all that familiar with it tbh
On 14 March 2012 19:27, Johnny Hughes johnny@centos.org wrote:
On 03/14/2012 02:21 PM, Johnny Hughes wrote:
On 03/13/2012 01:23 AM, Damjan Sirnik wrote:
Hi,
On 3/12/2012 3:20 PM, Adam Ring wrote:
I am all of a sudden getting the same issue started with my midnight sync and has happened every since:
Mon Mar 12 00:05:02 EDT 2012 msync-dvd.centos.org: 64.131.88.98
Mon Mar 12 04:05:02 EDT 2012 msync-dvd.centos.org: 64.131.83.114
Mon Mar 12 08:05:04 EDT 2012 msync-dvd.centos.org: 67.203.12.30
All produce:
receiving file list ... pre-xfer exec returned failure (256) rsync error: requested action not supported (code 4) at clientserver.c(869) [sender=3.0.6] rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(759) [receiver=3.0.6]
Looks like 62.141.54.220 affected too.
I also get same issue on following servers: 91.215.65.226 94.228.209.140 88.208.217.170
Regards, Damjan _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
You can only open one connection at a time.
Are you trying to do more than one connection at a time?
For the record, there were a couple of jerks who decided that they could open up 20-30 rsyncs at the same time on different directory paths. This practice hogged all the resources during the release, not allowing others to rsync.
Now, you may only make one rsync connection to a server at a time for a given module.
Make sure to thank the abusers for us.
CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
On 03/14/2012 08:17 PM, LWNetwork Mirror wrote:
will rsync automatically limit to 1 connection or do we have to set it to 1 connection?
Yes, rsync will limit itself to one connection per instance that you start up, most people would / should only have 1.
the test at msync.centos.org is done on IP per Module. So you can get multiple connections if you are using different modules.
If anyone gets errors when they only have 1 rsync running, please let us know so we can investigate.
Between 12 March 0830 (UTC) and 13 March 0130 (UTC) I got that error message from msync-dvd.centos.org despite our server only had one connection at a time. Our script which initiates the mirroring prevents to start rsync whenever a previous connection for the same package is active, and we have only a single package defined for centos.
Since 13 March 0130 (UTC) I haven't seen that error message.
Regards, Thomas
On 14.03.12 22:24, Karanbir Singh wrote:
On 03/14/2012 08:17 PM, LWNetwork Mirror wrote:
will rsync automatically limit to 1 connection or do we have to set it to 1 connection?
Yes, rsync will limit itself to one connection per instance that you start up, most people would / should only have 1.
the test at msync.centos.org is done on IP per Module. So you can get multiple connections if you are using different modules.
If anyone gets errors when they only have 1 rsync running, please let us know so we can investigate.
SWITCHmirror Admins wrote:
Between 12 March 0830 (UTC) and 13 March 0130 (UTC) I got that error message from msync-dvd.centos.org despite our server only had one connection at a time. Our script which initiates the mirroring prevents to start rsync whenever a previous connection for the same package is active, and we have only a single package defined for centos.
Since 13 March 0130 (UTC) I haven't seen that error message.
Regards, Thomas
That was the same case for us as well. We only every start one connection and prevent others till the first is complete. However we were receiving that error message, and now it is gone and I didn't change anything.
Adam
On 03/15/2012 09:04 AM, Adam Ring wrote:
SWITCHmirror Admins wrote:
Between 12 March 0830 (UTC) and 13 March 0130 (UTC) I got that error message from msync-dvd.centos.org despite our server only had one connection at a time. Our script which initiates the mirroring prevents to start rsync whenever a previous connection for the same package is active, and we have only a single package defined for centos.
Since 13 March 0130 (UTC) I haven't seen that error message.
Regards, Thomas
That was the same case for us as well. We only every start one connection and prevent others till the first is complete. However we were receiving that error message, and now it is gone and I didn't change anything.
Adam
I am sure during the transition from the old way to the new way there were some times when there were issues with the plugin. It should be good moving forward.
Dear all,
I feel like I woke up after a year of sleeping... Anyway, I can not find anywhere source rpms. I run find locally over everything on the public mirror I support. I looked into another mirror or two. (I must confess, I didn't need to rebuild/patch,... rpms for quite some time).
I know this question doesn't strictly speaking belong to this list... Still: where are .src.rpm of the CentOS? Is it just me who can't find them, or we indeed are not quite fair with GPL?
Thanks. Valeri
++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++
On Fri, 6 Apr 2012, Valeri Galtsev wrote:
Still: where are .src.rpm of the CentOS? Is it just me who can't find them,
for space reasons, they largely moved to: http://vault.centos.org/ some months ago
-- Russ herrold
Valeri Galtsev kirjoitti:
I know this question doesn't strictly speaking belong to this list... Still: where are .src.rpm of the CentOS? Is it just me who can't find them, or we indeed are not quite fair with GPL?
This question pops up every now and then. Would it make sense to add a Source (6.x) or SRPMS (5.x) directory on the mirrors, with only a readme file directing people to use the vault if they need the sources?
--- The source packages are not available on the mirrors due to space and sync speed constraints. The source packages can be downloaded from http://vault.centos.org/ ---
On 04/06/2012 10:18 PM, Anssi Johansson wrote:
The source packages are not available on the mirrors due to space and sync speed constraints. The source packages can be downloaded from http://vault.centos.org/
yes, and I suppose also adding a [sources] stanza to the relevant yum repo files pointing at the right place. Do you want to go ahead and propose this on the centos-devel list and we can take it from there ?
-
Adam Ring -
Anssi Johansson -
Damjan Sirnik -
Johnny Hughes -
Karanbir Singh -
LWNetwork Mirror -
R P Herrold -
SWITCHmirror Admins -
Valeri Galtsev