Issue 7853 - Synchronization between sf1 and ny1 doesn't work
Summary: Synchronization between sf1 and ny1 doesn't work
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Downloads (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL: http://ny1.mirror.openoffice.org/cont...
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-24 00:06 UTC by stx123
Modified: 2003-12-06 14:52 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2002-09-24 00:06:04 UTC
http://sf1.mirror.openoffice.org/contrib/LinuxPPC/
contains a file OOo_1.0.1_LinuxPPC_install.tar.gz 
This file is not at
http://ny1.mirror.openoffice.org/contrib/LinuxPPC/
Please explain the difference and correct the malfunction.
Comment 1 Unknown 2002-09-24 00:57:18 UTC
Action Plan
1. Open internal ticket to get systems sync'ed.
2. Respond when issue is resolved.
Comment 2 stx123 2002-09-24 00:59:46 UTC
And please add an explanation for the reoccurence and solution for the
problem. Thanks, Stefan.
Comment 3 Unknown 2002-09-24 23:50:31 UTC
The file is back on ny1.  David will have to speak to the reasons for
the cause of this.
Comment 4 Unknown 2002-10-30 01:44:28 UTC
Seems like the issue had to do with rate limiting at the switch rather
than at the machine itself.  We created a patch to enable QoS/shaping
support and applied it to the kernel.  We are hopeful this will
prevent any sunchronization issues going forward.
Comment 5 michael.bemmer 2003-03-24 08:21:15 UTC
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.
Comment 6 michael.bemmer 2003-03-24 08:25:36 UTC
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.