Hi David, On Tue, Jan 27, 2009 at 11:08:29AM -0600, David C. Rankin wrote:

Listmates,

Prior to six months ago, if a package update or install threw an error because of a mirror time-out or other malady with the mirror system, it was a rare once-a-year occurrence. Lately, I can't even do a simple update without the mirror system blowing up 20 times. Something has got to get fixed. What was a bullet-proof SuSE system of package installs and updates has become so undependable you literally have to baby-sit each and every update.

coincidentally, earlier today I replied to an older mail from you, which you may not have seen yet ("Re: What's up with the mirrors?") where I pointed out exactly what to do: Report the problem! Write to admin@opensuse.org (you will reach me there), or open a bugzilla ticket. If you chose the latter path, using the bugzilla product "openSUSE.org", component "Download infrastructure" will ensure that the issue directly comes to my attention.

That's ridiculous. That's unacceptable.

I'm fully with you. I fully agree that the situation is what it is, and the download client is so fragile. It wouldn't be necessary. We all can be happy when two proposals of mine will finally be implemented: https://features.opensuse.org/305320 Show accessed mirror(s) https://features.opensuse.org/302923 handle redirection to mirrors robustly Until then, there is no way around improvising (and suffering) in dealing with these recurring problems. (Please vote for those features.) ((If you are on 11.1, you can already test a prototype, which is described here: http://en.opensuse.org/Libzypp/Failover It is supposed to fix *all* those plaguing issues.))

I used to kick-off remote updates with ssh host.domain.com 'sudo zypper up -t package' without hesitation, now it looks like the system has gone back to beta status. What is up with the mirror system? If I set up automatic updates in yast to run ... 'automatically'..., I end up with logs full of errors. That never used to happen.

Is there something that can be done to fix this? Moreover, is this something that can be reported to bugzilla? Or, is this just something else that would receive the seemingly obligatory 'CLOSED INVA' response from Novell?

No matter how you look at it something has gone dramatically downhill in the past 6 months to a year that we need to elevate to the proper people so it can get fixed. Christian, Stefan other opensuse guys, what is the proper direction to approach this one? Who is responsible for making sure the mirror system works in a reliable way?

I am responsible to make it work in a reliable way. And I will happily help you (and I can virtually promise that I can). Nevertheless, you are responsible to let me know when you encounter problems, so that I can help you. Which I hope is reasonable. Information that I'll need is the country you are located in, possibly your IP address and the date/time of failing download, possibly certain file that the failure was encountered with. If you fell confident to do so, you can enable zypp debug log and it'll will reveal the failing mirror right away. It is done like this: $ ZYPP_MEDIA_CURL_DEBUG=1 zypper whatever

The most recent time-out calamity follows the signature. It is an update I started 7 hours ago that I am still trying to finish. For single repos, I can see just choosing a mirror and adding that as a source if, for example, the update mirrors are having problems, but I shouldn't have to do that for every repository just to be able to perform update. Let me know who to contact or where to file this so it will get the attention it needs. Thanks.

-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

[04:26 ecstasy:/home/david/tmp] # zypper up -t package Reading installed packages...

The following packages are going to be upgraded: kipi-plugins digikamimageplugins kdiff3 gwenview digikam libkcal2 kitchensync kdewebdev3 kdesdk3-translate kdesdk3-kdecvs kdesdk3 kdepim3-time-management kdepim3-notes kdepim3-kpilot kdepim3 kdenetwork3-news kdenetwork3-IRC kdenetwork3 kdemultimedia3-video-xine kdemultimedia3-video kdemultimedia3-sound kdemultimedia3-mixer kdemultimedia3-midi kdemultimedia3-jukebox kdemultimedia3-extra kdemultimedia3-arts kdemultimedia3-CD kdemultimedia3 kdelibs3-doc kdelibs3-devel kdelibs3-arts kdegraphics3-tex kdegraphics3-scan kdegraphics3-postscript kdegraphics3-pdf kdegraphics3-kamera kdegraphics3-imaging kdegraphics3-fax kdegraphics3-extra kdegames3-board kdegames3 kdebindings3-ruby kdebindings3-javascript-devel kdebindings3-javascript kdebindings3 kdegraphics3 kdebindings3-java kdeartwork3-xscreensaver kdeartwork3-kscreensaver kdeadmin3 kdeaddons3-sound kdeaddons3-konqueror kdeaddons3-kicker kdeaddons3-kate kdeaddons3-games kdeaccessibility3 kdebase3-runtime kdebase3-devel kdebase3 kdelibs3-devel-doc libqt4-x11 libqt4-jambi libqt4-devel libQtWebKit4 libqt4-sql-sqlite libqt4-qt3support ant-javamail

The following NEW package is going to be installed: kipi-plugins-lang

The following package is going to change vendor: ant-javamail

Overall download size: 134.1 M. After the operation, additional 11.4 M will be used. Continue? [YES/no]: yes Downloading package gwenview-1.4.2-121.2.x86_64 (1/68), 560.0 K (2.0 M unpacked) Downloading: gwenview-1.4.2-121.2.x86_64.rpm [done (97.2 K/s)] Installing: gwenview-1.4.2-121.2 [done] Downloading package digikam-0.9.4-54.2.x86_64 (2/68), 6.4 M (27.9 M unpacked) Downloading: digikam-0.9.4-54.2.x86_64.rpm [error] Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/Backports/openSUSE_11.0/x86_6...': Error code: User abort Error message: Connection time-out

Abort, retry, ignore? [A/r/i]: r Downloading: digikam-0.9.4-54.2.x86_64.rpm [error] Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/Backports/openSUSE_11.0/x86_6...': Error code: User abort Error message: Connection time-out

Abort, retry, ignore? [A/r/i]: r Downloading: digikam-0.9.4-54.2.x86_64.rpm [done (133.5 K/s)] Installing: digikam-0.9.4-54.2 [done] Downloading package libkcal2-3.5.10-19.5.x86_64 (3/68), 391.0 K (1.4 M unpacked) Downloading: libkcal2-3.5.10-19.5.x86_64.rpm [done (97.5 K/s)] Installing: libkcal2-3.5.10-19.5 [done] Downloading package kdewebdev3-3.5.10-15.30.x86_64 (4/68), 1.6 M (4.3 M unpacked) Downloading: kdewebdev3-3.5.10-15.30.x86_64.rpm [done (119.0 K/s)] Installing: kdewebdev3-3.5.10-15.30 [done] Downloading package kdesdk3-translate-3.5.10-2.33.x86_64 (5/68), 1.6 M (5.6 M unpacked) Downloading: kdesdk3-translate-3.5.10-2.33.x86_64.rpm [done (126.2 K/s)] Installing: kdesdk3-translate-3.5.10-2.33 [done] Downloading package kdesdk3-3.5.10-2.33.x86_64 (6/68), 3.4 M (10.1 M unpacked) Downloading: kdesdk3-3.5.10-2.33.x86_64.rpm [done (127.8 K/s)] Installing: kdesdk3-3.5.10-2.33 [done] Downloading package kdenetwork3-news-3.5.10-15.6.x86_64 (7/68), 234.0 K (998.0 K unpacked) Downloading: kdenetwork3-news-3.5.10-15.6.x86_64.rpm [done (60.7 K/s)] Installing: kdenetwork3-news-3.5.10-15.6 [done] Downloading package kdenetwork3-IRC-3.5.10-15.6.x86_64 (8/68), 605.0 K (2.0 M unpacked) Downloading: kdenetwork3-IRC-3.5.10-15.6.x86_64.rpm [error] Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/x86_64/kde...': Error code: User abort Error message: Connection time-out

Abort, retry, ignore? [A/r/i]: r Downloading: kdenetwork3-IRC-3.5.10-15.6.x86_64.rpm [done (114.7 K/s)] Installing: kdenetwork3-IRC-3.5.10-15.6 [done] Downloading package kdenetwork3-3.5.10-15.6.x86_64 (9/68), 1.2 M (4.0 M unpacked) Downloading: kdenetwork3-3.5.10-15.6.x86_64.rpm [done (115.9 K/s)] Installing: kdenetwork3-3.5.10-15.6 [done] Downloading package kdemultimedia3-video-xine-3.5.10-5.26.x86_64 (10/68), 71.0 K (531.0 K unpacked) Downloading: kdemultimedia3-video-xine-3.5.10-5.26.x86_64.rpm [error] Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/x86_64/kde...': Error code: User abort Error message: Connection time-out

Abort, retry, ignore? [A/r/i]: r Downloading: kdemultimedia3-video-xine-3.5.10-5.26.x86_64.rpm [done] Installing: kdemultimedia3-video-xine-3.5.10-5.26 [done] Downloading package kdemultimedia3-sound-3.5.10-5.26.x86_64 (11/68), 1.2 M (10.5 M unpacked) Downloading: kdemultimedia3-sound-3.5.10-5.26.x86_64.rpm [done (122.1 K/s)] Installing: kdemultimedia3-sound-3.5.10-5.26 [done] Downloading package kdemultimedia3-mixer-3.5.10-5.26.x86_64 (12/68), 319.0 K (1.1 M unpacked) Downloading: kdemultimedia3-mixer-3.5.10-5.26.x86_64.rpm [error] Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/x86_64/kde...': Error code: User abort Error message: Connection time-out

Abort, retry, ignore? [A/r/i]: r Downloading: kdemultimedia3-mixer-3.5.10-5.26.x86_64.rpm [error] Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/x86_64/kde...': Error code: User abort Error message: Connection time-out

Abort, retry, ignore? [A/r/i]: r Downloading: kdemultimedia3-mixer-3.5.10-5.26.x86_64.rpm [done (87.1 K/s)] Installing: kdemultimedia3-mixer-3.5.10-5.26 [done] Downloading package kdemultimedia3-midi-3.5.10-5.26.x86_64 (13/68), 199.0 K (635.0 K unpacked) Downloading: kdemultimedia3-midi-3.5.10-5.26.x86_64.rpm [done (45.8 K/s)] Installing: kdemultimedia3-midi-3.5.10-5.26 [done] Downloading package kdemultimedia3-CD-3.5.10-5.26.x86_64 (14/68), 1.1 M (2.2 M unpacked) Downloading: kdemultimedia3-CD-3.5.10-5.26.x86_64.rpm [done (112.8 K/s)] Installing: kdemultimedia3-CD-3.5.10-5.26 [done] Downloading package kdemultimedia3-3.5.10-5.26.x86_64 (15/68), 229.0 K (634.0 K unpacked) Downloading: kdemultimedia3-3.5.10-5.26.x86_64.rpm [done (74.9 K/s)] Installing: kdemultimedia3-3.5.10-5.26 [done] Downloading package kdelibs3-doc-3.5.10-33.3.x86_64 (16/68), 842.0 K (5.7 M unpacked) Downloading: kdelibs3-doc-3.5.10-33.3.x86_64.rpm [done (119.3 K/s)] Installing: kdelibs3-doc-3.5.10-33.3 [done] Downloading package kdelibs3-arts-3.5.10-33.3.x86_64 (17/68), 114.0 K (568.0 K unpacked) Downloading: kdelibs3-arts-3.5.10-33.3.x86_64.rpm [error] Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/x86_64/kde...': Error code: User abort Error message: Connection time-out

Abort, retry, ignore? [A/r/i]: r Downloading: kdelibs3-arts-3.5.10-33.3.x86_64.rpm [done (40.2 K/s)] Installing: kdelibs3-arts-3.5.10-33.3 [done] Downloading package kdegraphics3-scan-3.5.10-2.36.x86_64 (18/68), 824.0 K (1.5 M unpacked) Downloading: kdegraphics3-scan-3.5.10-2.36.x86_64.rpm [done (112.3 K/s)] Installing: kdegraphics3-scan-3.5.10-2.36 [done] Downloading package kdegraphics3-postscript-3.5.10-2.36.x86_64 (19/68), 195.0 K (635.0 K unpacked) Downloading: kdegraphics3-postscript-3.5.10-2.36.x86_64.rpm [done (57.0 K/s)] Installing: kdegraphics3-postscript-3.5.10-2.36 [done] Downloading package kdegraphics3-pdf-3.5.10-2.36.x86_64 (20/68), 711.0 K (2.4 M unpacked) Downloading: kdegraphics3-pdf-3.5.10-2.36.x86_64.rpm [done (111.2 K/s)] Installing: kdegraphics3-pdf-3.5.10-2.36 [done] Downloading package kdegraphics3-kamera-3.5.10-2.36.x86_64 (21/68), 69.0 K (211.0 K unpacked) Downloading: kdegraphics3-kamera-3.5.10-2.36.x86_64.rpm [done] Installing: kdegraphics3-kamera-3.5.10-2.36 [done] Downloading package kdegraphics3-imaging-3.5.10-2.36.x86_64 (22/68), 1.8 M (4.0 M unpacked) Downloading: kdegraphics3-imaging-3.5.10-2.36.x86_64.rpm [done (124.2 K/s)] Installing: kdegraphics3-imaging-3.5.10-2.36 [done] Downloading package kdegraphics3-extra-3.5.10-2.36.x86_64 (23/68), 117.0 K (363.0 K unpacked) Downloading: kdegraphics3-extra-3.5.10-2.36.x86_64.rpm [error] Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/x86_64/kde...': Error code: User abort Error message: Connection time-out

Abort, retry, ignore? [A/r/i]:

AARRGGHHHH! #$$%&*ERGSF&#$%^&

Don't despair :-) Please help to find the broken mirror. For the benefit of your own sanity, and for the benefit of thousands of affected other users. So please provide the information I mentioned above, and we'll solve it. Thanks, Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi, On Mon, Feb 02, 2009 at 12:18:45PM +0800, Low Kian Seong wrote:

On Wed, Jan 28, 2009 at 1:55 AM, Peter Poeml wrote:

...

Hi David,

On Tue, Jan 27, 2009 at 11:08:29AM -0600, David C. Rankin wrote:

...

Listmates,

Prior to six months ago, if a package update or install threw an error because of a mirror time-out or other malady with the mirror system, it was a rare once-a-year occurrence. Lately, I can't even do a simple update without the mirror system blowing up 20 times. Something has got to get fixed. What was a bullet-proof SuSE system of package installs and updates has become so undependable you literally have to baby-sit each and every update.

coincidentally, earlier today I replied to an older mail from you, which you may not have seen yet ("Re: What's up with the mirrors?") where I pointed out exactly what to do:

Report the problem!

Write to admin@opensuse.org (you will reach me there), or open a bugzilla ticket. If you chose the latter path, using the bugzilla product "openSUSE.org", component "Download infrastructure" will ensure that the issue directly comes to my attention.

...

That's ridiculous. That's unacceptable.

I'm fully with you. I fully agree that the situation is what it is, and the download client is so fragile. It wouldn't be necessary. We all can be happy when two proposals of mine will finally be implemented:

https://features.opensuse.org/305320 Show accessed mirror(s) https://features.opensuse.org/302923 handle redirection to mirrors robustly

Until then, there is no way around improvising (and suffering) in dealing with these recurring problems.

(Please vote for those features.)

((If you are on 11.1, you can already test a prototype, which is described here: http://en.opensuse.org/Libzypp/Failover It is supposed to fix *all* those plaguing issues.))

Please help me understand correctly. Is the Failover already part of the zypper that comes with opensuse 11.1?

It is part of openSUSE 11.1 in the way that it can be activated by setting an environmental variable before starting zypper/YaST. It is not active by default. There is known bug (https://bugzilla.novell.com/show_bug.cgi?id=471016): adding/removing repositories does not work. But download and updates of packages seems to work great already. How to activate the new behaviour is described here: http://en.opensuse.org/Libzypp/Failover#openSUSE_11.1

...

...

I used to kick-off remote updates with ssh host.domain.com 'sudo zypper up -t package' without hesitation, now it looks like the system has gone back to beta status. What is up with the mirror system? If I set up automatic updates in yast to run ... 'automatically'..., I end up with logs full of errors. That never used to happen.

Is there something that can be done to fix this? Moreover, is this something that can be reported to bugzilla? Or, is this just something else that would receive the seemingly obligatory 'CLOSED INVA' response from Novell?

No matter how you look at it something has gone dramatically downhill in the past 6 months to a year that we need to elevate to the proper people so it can get fixed. Christian, Stefan other opensuse guys, what is the proper direction to approach this one? Who is responsible for making sure the mirror system works in a reliable way?

I am responsible to make it work in a reliable way. And I will happily help you (and I can virtually promise that I can). Nevertheless, you are responsible to let me know when you encounter problems, so that I can help you. Which I hope is reasonable.

Information that I'll need is the country you are located in, possibly your IP address and the date/time of failing download, possibly certain file that the failure was encountered with.

If you fell confident to do so, you can enable zypp debug log and it'll will reveal the failing mirror right away. It is done like this: $ ZYPP_MEDIA_CURL_DEBUG=1 zypper whatever

...

The most recent time-out calamity follows the signature. It is an update I started 7 hours ago that I am still trying to finish. For single repos, I can see just choosing a mirror and adding that as a source if, for example, the update mirrors are having problems, but I shouldn't have to do that for every repository just to be able to perform update. Let me know who to contact or where to file this so it will get the attention it needs. Thanks.

Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org