openSUSE online updates suck beyond belief. What the heck is the problem. I finally got them to work, but I believe it is because the repositories started working about 8:00 PM. Read on before you decide to ditch Windows or another distro for openSUSE. openSUSE rocks without the update and software management problems. But, heck without software management, what good is it.
I finally got my Dell T300 with openSUSE 11.1 Server to update using yast via ssh. Once I removed all the repositories and then reinstalled them, I was able to perform online updates. I did have to remove the “/” at the end of the url’s. Even so, I had to perform 53 retries during about 80 updates over a period of nearly two hours. That doesn’t include 6 hours of fooling with yast, not yast2. At the 50% download which was at 8:00 PM Central Time, the updates progressed quickly without any additional retries required. I believe the problem is with the repositories.
Below is a description of my trials and tribulations with openSUSE Online Updates.
This is the list of default repositories, after I had removed the last “/” from them about 2 weeks ago. Notice the two identical update repositories. One was named “Update” and the other “Updates”:
cd:///?devices=/dev/sr0
Index of /debug/distribution/11.1/repo/oss yast
Index of /distribution/11.1/repo/non-oss yast
Index of /distribution/11.1/repo/oss yast
Index of /source/distribution/11.1/repo/oss yast
Index of /update/11.1 yum
Index of /update/11.1 yum
Here’s what you can do to duplicate my efforts:
ssh to the server and log in
open a terminal and resize the terminal window larger either now or later after starting yast.
su -
password
Start yast, select Software in the Yast Control Center if it is not already selected. Then hit tab or right arrow to get to the right window. Then use the down arrow to select Software Repositories and hit enter to go to “Configured Software Repositories”.
If you haven’t already done so, resize the terminal window after getting to the repository window, so that you can see the entire url of the repository when the repository is selected, and also so that you can see the OK button in the bottom right. Otherwise you will not be able to save the configuration without the OK button as the F (function) keys often don’t work via ssh. The contents of Yast will expand in the enlarged terminal window as soon as you tab or click the up or down arrow.
At this point I disabled repositories and autorefresh, planning to just re-add them in case they consisted of invisible characters, etc. However, it appeared that they still tried to refresh when I added the new ones by copying and pasting from the repository web pages. So, I just remove all of them, except the DVD drive.
Go to Package Repositories - openSUSE
Midway down page are the Official Repositories for 11.1, 11.0 and 10.3 for Oss, Non-oss, Update, Src-oss, Src-non-oss, Debug, Contrib, KDE, GNOME, JAVA. I went to each page in a browser and then copied the url from the address bar.
In Configured Software Repositories, tab to add,
Select http
Uncheck “Download repository description files”. I had problems until I unchecked this.
Tab to [Next] and press enter
On “Server and Directory” page, tab to “Edit Complete URL” and press space bar.
Tab to “URL of the Repository” and then copy and paste the URL from the browser on the local machine.
Tab back and name the repository the same as the last directory in the URL such as “Oss” I tested with and without the end “/” and determined that it should be removed.
Click next.
I would often get “Cannot access installation media.” at this point. I then clicked “retry” several times. When this doesn’t work, which was often, I’d click “Abort”. Oddly, this occasionally worked, or at least the repository was added to the list. Clicking “Details” will show something like “Download (curl) error for 'http://download.opens”. You will not be able to see the entire url via ssh and yast. The next line will be “Error code: Connection failed” and a third line “Error message: Couldn’t resolve host 'download.o” Clicking “Abort” will bring up a “downloading” window just like the “retry”. It is as if “abort” does exactly the same a “retry”. If you have to click on “Skip”, the repository will show up in the Yast list of repositories in the “Configure Software Repositories”
I had no problem with the “Contrib” repository, but I did with the others.
After installing all the repositories I wanted, I enabled all of them. I then set one to autorefresh and then tabbed to refresh and selected “Refresh all autorefreshed”. This way I was only refreshing one repository at a time, making it easier to troubleshoot. I then “retried” until the refresh appeared to be successful. I then disabled Autorefresh for the successfully refreshed repository, set another repository to Autorefresh and then tabbed to “refresh” and again selected “Refresh all autorefreshed”
After each repository gets added properly, exit yast so it gets saved. If yast is aborted while adding addition repositories and you haven’t exited since adding previous repositories, the previous repositories will not be saved and will be lost.
Uncheck enable and Automatically Refresh of the most recently added repository before adding another repository because the previous repositories will try to refresh which is time consuming.
After all repositories were added and refreshed individually, I set them all to enable and to “not” autorefresh.
I then ran “Online updates”. There were about 80 of them. I had to retry numerous times, but each time the percent went up. Had to retry several times for these two"
Downloading: http://download.opensuse.org/.../descr/packages.gz
Downloading: http://download.opensuse.org/source/.../oss/media.1/media
I then had problems with many retries: Each entry below includes the number of reties:
6 - Downloading delta RPM ./rpm/x86_64/python-satsolver-0.13.0_0.13.7-3.3_0.1.1.x86_64.delta.rpm
9 - Downloading delta RPM ./rpm/x86_64/libzypp-5.24.5_5.30.3-1.1_0.1.1.x86_64.delta.rpm
Then got the message: “Packages for package management were updated. Finishing and restarting now.” Click ok.
Then got the message: “At least one of the updates installed requires restart of the session. Relogin into your system as soon as possible.”
Restarted and updated again - about 70 more updates or only 10 of previous updated.
9 retries for various updates
8 - Downloading delta RPM ./rpm/x86_64/libtalloc1-3.2.4_3.2.7-5.2_11.3.2.x86─
6 - Downloading delta RPM ./rpm/x86_64/xorg-x11-libxcb-7.4-1.28_1.29.1.x86_6─
5
43 retries at 28%
8
At 47% updates proceeded quickly from about 8:30PM Central Time to 8:36 (6 min) without any further retries. Started about 7:00
Message: “At least one of the updates installed requires a system reboot to function properly. Reboot the system.”
Finally the following worked which didn’t about 10:00 AM today:
yast -i ncurses-devel
Now I can try a kernel rebuild after a whole day. Note the time of this post 10:20 PM compared to my starting post this morning.
I have a very good Internet connection. Software downloads are flawless and fast including many ISO downloads. One variable, I have a wireless bridge between the server and the access point. I have had no problems with other distro software management on this multboot server.