Online upgrade stuck on retrieving a package.

I’m upgrading another machine which is stuck for an hour on trying to retrieve one of the packages, on 3793 out of 4679 or something, that’s after about four-five hours of downloading.

Currently the tty says “retrieving …name of the package etc… starting”.

What are my options? Ideally, I would like to bring “retry/abort/ignore” prompt and continue. Or exit zypper and restart the upgrade but I don’t want to redownload all 3792 packages again. Is it possible to save them so that zypper picks up from where it left?

Are there any shortcuts that would do something like this in tty or should it be managed from shell in GUI?

On Wed 04 Feb 2015 03:16:01 PM CST, Stan Ice wrote:

I’m upgrading another machine which is stuck for an hour on trying to
retrieve one of the packages, on 3793 out of 4679 or something, that’s
after about four-five hours of downloading.

Currently the tty says “retrieving …name of the package etc…
starting”.

What are my options? Ideally, I would like to bring “retry/abort/ignore”
prompt and continue. Or exit zypper and restart the upgrade but I don’t
want to redownload all 3792 packages again. Is it possible to save them
so that zypper picks up from where it left?

Are there any shortcuts that would do something like this in tty or
should it be managed from shell in GUI?

Hi
Press ctrl+c and restart the update, zypper caches and starts where it
left off (well on 13.2 it does…). It happens from time to time if
something breaks in the ether…


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.2 (Harlequin) (x86_64) GNOME 3.14.0 Kernel 3.16.7-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

It magically resumed itself, still about 700 packages to go so anything can happen.

Ctrl-C doesn’t work in tty, should it be Ctrl-Z or Ctrl-?

It’s good to know that zypper would resume where it left off, but does it keep cache over a reboot?

I’ve also had a lot of errors that prompted for retry/abort/ignore, is there a away to to tell zypper to automatically retry without waiting for me to check on it?

On Wed 04 Feb 2015 03:36:01 PM CST, Stan Ice wrote:

It magically resumed itself, still about 700 packages to go so anything
can happen.

Ctrl-C doesn’t work in tty, should it be Ctrl-Z or Ctrl-?

It’s good to know that zypper would resume where it left off, but does
it keep cache over a reboot?

I’ve also had a lot of errors that prompted for retry/abort/ignore, is
there a away to to tell zypper to automatically retry without waiting
for me to check on it?

Hi
Nope, same in a tty, hold the ctrl key and press c a few times it will
abort.

It appears they may be having issues on the network anyway, or maybe
the mirror your accessing.


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.2 (Harlequin) (x86_64) GNOME 3.14.0 Kernel 3.16.7-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

Nope, didn’t go as expected at all.

Perhaps zypper did eventually react to Ctrl-C, I don’t know, but somehow it quit after it retrieved all 4000+ packages.

I run the same command again, zypper dup --download “in-advance”, hoping that it would read downloaded packages from cache but it started downloading the whole thing all over again. I canceled it and tried simple “zypper dup” thinking that --download option might have forced downloading but with no luck.

The other thing I did in between was to disable kde:extra repository that was on during my first attempt at upgrade.

Right now it’s downloading package 64/4673. God knows how many hours until it’s done, and I have to monitor it for download errors, too.

Why not just download the Full Install DVD - one download;
then use it to upgrade machines?

I always have trouble with network based updates in my area (dropouts,
restarts, etc); they end up taking much longer than downloading the DVD one time.

Perhaps you are right.

I have one 32-bit and two 64-bit machines. 32-bit upgrade went smoothly so I thought I would try one of the 64-bit machines. Last year I upgraded them to 13.1 without any problems. I also have one Ubuntu install and it had probably three or four online upgrades.

I’ll let it run for now but download a DVD on the one I"m using now.

Just checked on it - it’s actually installing packages already, apparently it downloaded only a few missing in the beginning and then read the rest from cache. Now there’s no turning back.

The full install DVD also contains the “Rescue System”.
This comes in quite handy when trying to recover a broken system.

In any case, I find it most convenient to download the full dvd,
then us it to install my two machines.

for what it might be worse (to others)

i had decided to do the upgrade from 12.3 to 13.2 - upgraded the URLs of the repositories - sorted out some problems YAST flagged (one of which may well have involved rtkit) and started the (release) upgrade.
finally after over an hour i had to shutdown my computer by holding down the power button 4 sec
was surprised that the boot menu included 13.2 (as default) as the kernel had already been installed but ended up at INIT 3 :-{
doing an


zypper up

finished the upgrade and after another reboot i’m happily posting this from openSUSE 13.2 :slight_smile:

had tried

 systemctl daemon-reexec 
  • kill yast processes

but ended up with a stuck system (hard reset)

You realize that 12.3 to 13.2 is not really the best idea??

It may in theory be possible that if you have a deep understanding of the system you maybe can do it bit you will haev huge problems. Install clean new. You can keep your home partition if you have one

Also it is better if you are trying to jump that many versions to use the full DVD upgrade method and not try an online. Too many things can go wrong.

On 2015-04-23 03:26, claudebucher wrote:
>
> for what it might be worse (to others)
>
> i had decided to do the upgrade from 12.3 to 13.2 - upgraded the URLs of
> the repositories - sorted out some problems YAST flagged (one of which
> may well have involved rtkit) and started the (release) upgrade.

You know, don’t you (it is written in the online distribution upgrade
instructions) that jumping over a release is not supported. That is, you
have to go from 12.3 to 13.1, and after it completes and reboots and you
iron the kinks, you go 13.1 to 13.2.

> but ended up with a stuck system (hard reset)

No surprise.

Suggestion: download the full 13.2 DVD, and attempt an offline upgrade
instead. Sometimes it works.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))