virtualbox update
|
svmi updated now, thanks
Back to top |
I tried to upgrade virtualbox to 3.0.6 using smxi but it failed.
The script's error message suggests there has been a name change. So perhaps the smxi needs amending. Back to top |
It worked fine for me with the lenny version for non-ose a few days ago
Back to top |
Download tested and works fine. Problem might be in the ISP or something.
:: Code :: HTTP request sent, awaiting response... 200 OK
Length: 43792228 (42M) [application/x-debian-package] Saving to: `virtualbox-3.0_3.0.6-52128_Debian_lenny_i386.deb' 8% [=======> ] 3,741,073 1.78M/s Back to top |
My last post was a little short on info:
My system is 64bit and VBox is the non-ose version. The latter may be the cause of the problem? For me smxi (ver 8.11.23) fails to install VBox and shows a http 404 error. Yet I can leave smxi and download/install VBox manually suggesting that it's not an ISP problem. Also I cannot use smxi to install GuestAdditions (404 error again) but I can install it manually. I have the time to do any tests you may suggest. Back to top |
As noted above, I've recently installed the non-ose version . . . also on a 64 bit box. Is it the lenny or etch version you had problems with?
Back to top |
drb: I don't know. I just let smxi take care of that.
Although I believe smxi goes directly to the VBox URL I did try adding the VBox repository to my sources list (first lenny and then etch) without success. It seems increasingly obvious to me that there is something wrong at my end. But where to start? Back to top |
Try installing it with svmi again, then if it fails, post your /var/log/svmi.log using paste.debian.net to upload the file, and copy in the paste url here.
It can be an ISP or wget issue, that has happened before, and it will happen again, but it's easier to confirm by checking the actual data svmi used. I tested on the non-ose, the ose installs via apt, so there's no wget involved. Back to top |
My apologies techAdmin dI on't know how to paste.debian.net. Please could you tell me how?
In the mean time here is the section of smvi.log surrounding the 404 error:- :: Code :: Function: add_vbox_user - Primary: Start
Using USER_NAME: Resolving dlc-cdn-rd.sun.com... 87.248.211.227, 87.248.210.228 Error: USER_NAME: Resolving dlc-cdn-rd.sun.com... 87.248.211.227, 87.248.210.228 does not exist in /etc/passwd Function: add_vbox_user - Primary: Start Using USER_NAME: Connecting to dlc-cdn-rd.sun.com|87.248.211.227|:80... connected. Error: USER_NAME: Connecting to dlc-cdn-rd.sun.com|87.248.211.227|:80... connected. does not exist in /etc/passwd Function: add_vbox_user - Primary: Start Using USER_NAME: HTTP request sent, awaiting response... 404 Not Found Error: USER_NAME: HTTP request sent, awaiting response... 404 Not Found does not exist in /etc/passwd Function: add_vbox_user - Primary: Start Using USER_NAME: 2009-09-26 01:00:22 ERROR 404: Not Found. Error: USER_NAME: 2009-09-26 01:00:22 ERROR 404: Not Found. does not exist in /etc/passwd Function: add_vbox_user - Primary: Start Function: add_vbox_user - Primary: End Function: add_vbox_user - Primary: End Back to top |
All times are GMT - 8 Hours |