500 server error upgrading wolfram-engine

[RedBullet]

I am in the process of doing a dist-upgrade. Looks like everything downloaded OK with the exception of the wolfram-engine

I keep getting server error 500 or really slow response which just stops after a number of retries.

Should I just keep trying? Or is there some other fix for this?

[ShiftPlusOne]

How long ago was this? I believe the issue has been resolved about half an hour ago.

[RedBullet]

Just now, been trying for maybe an hour?

Here's what I see:

500 Internal Server Error [IP: 93.93.128.230 80]
E: Failed to fetch http://archive.raspberrypi.org/debian/p ... _armhf.deb 500 Internal Server Error [IP: 93.93.128.230 80]

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

[ShiftPlusOne]

Thanks, forwarded the problem on and it's being looked into.

[RedBullet]

Thanks, please let me know when I should try again. Should I try to wget and install manually? Or just sit tight?

[ShiftPlusOne]

I am told it should be resolved now.

[RedBullet]

Sort of. Not getting server error 500 anymore but it seems like the connection timesout and I see repeated gets:

The following packages will be upgraded:
wolfram-engine
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 236 MB of archives.
After this operation, 198 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.raspberrypi.org/debian/ jessie/main wolfram-engine armhf 10.3.1+2016012407 [236 MB]
Get:2 http://archive.raspberrypi.org/debian/ jessie/main wolfram-engine armhf 10.3.1+2016012407 [236 MB]
Get:3 http://archive.raspberrypi.org/debian/ jessie/main wolfram-engine armhf 10.3.1+2016012407 [236 MB]
77% [3 wolfram-engine 182 MB/236 MB 77%]

[RedBullet]

On get #23 currently at 79%

[ShiftPlusOne]

Apologies. The servers hosting the repo haven't seen quite this much traffic before. It should be back to normal when things quiet down a bit and then we'll be looking at ways to cope with the traffic a little better in the future.

[RedBullet]

Sure, totally understand.

I was able to get the package via wget from a different machine, and I pushed it to my Pi^2.

I assume I can just do a dpkg -i <file> and install it that way for now?

[ShiftPlusOne]

Yes, that should work. Although it may make sense to uninstall it and forget about it, if you don't use it.

[simongrey]

Hi All, I'm new to this so apologies for any faux pas.
I'm writing because about 90 minutes ago I started a dist-upgrade on a Pi-2 that originally had Wheezy but had subsequently been upgraded to Jessie. All this time later, the upgrade has stalled at get 202 - jessie/main wolfram-engine .... it has been very slow since it hit the wolfram bit. A little googling shows this has been an issue for at least 18 months. The Pi is a plaything for me so I can (and will) just leave it and see what it looks like in the morning. This post is just to let the powers that be know that there is very much still an issue of some kind.
I am on BT with usual download speeds around 16Mbs/sec.
Cheers
Simon
PS Moved on to get 205 in the time it took to write this.

[DougieLawson]

Wolfram is an enormous package and it even takes a RPi3B a long time to run the sha1sums to ensure that apt-get/dpkg has got a good copy. That's before it takes a long time (and lots of SDCard space) to unpack it.

[simongrey]

Thanks for the response - and if that means that what I am seeing is normal, then fair enough. I certainly was not aware that all that was going on. Live and learn !