Page: 1, 2  Next

Smxi error 34 stops smxi
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 274
Location: South Florida
Reply Quote
I finally installed smxi, when I tried to run it first it stopped at error 100, which is not unusual given that I was using the US mirror, so I changed to Canadian mirror and overcame this issue, but then error 34 stopped me for good, apparently a warning section is missing.
Please help with this.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3882
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
I've said this over and over on these forums, wget had a bug, I don't know which releases of debian have that bug, the solution was and remains to use curl, which must be installed BEFORE running smxi. smxi itself will install it if it's missing.

as for the certificates, that's a debian problem, clearly debian has seriously screwed up their combination of ssl certificate distribution and downloader updates.

There is not, and never has been, anything wrong with smxi in this regard, nor has the 'warnings' file ever not been present. That message means it could not be downloaded, and it could not be downloaded due to either wget errors or certificate errors.

I can't help either of these since they are external to smxi/sgfxi. Note that true first runs of smxi will install curl first, before anything else, which solved the issue in the past.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 274
Location: South Florida
Reply Quote
I can understand your frustration.
All I can tell you is that curl is installed, I don't know if it was installed before smxi or if it was smxi that installed it.
Question is: how should I proceed, reinstall smxi?
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3882
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
It's not frustration so much as wondering why I can't get better debug data. Without that, I can't do anything, since I can't reproduce this issue if it's not the wget thing.

:: Code ::

f=$(curl https://smxi.org/sm/upgrade-data/status);echo "$f"
f=$(curl https://smxi.org/sm/upgrade-data/status_s);echo "$f"
f=$(curl https://smxi.org/sm/upgrade-data/status_t);echo "$f"
f=$(curl https://smxi.org/sm/upgrade-data/alert_message);echo "$f"
f=$(curl https://smxi.org/sm/upgrade-data/alert_message_s);echo "$f"
f=$(curl https://smxi.org/sm/upgrade-data/alert_message_t);echo "$f"

f=$(wget -O - https://smxi.org/sm/upgrade-data/status);echo "$f"
f=$(wget -O - https://smxi.org/sm/upgrade-data/status_s);echo "$f"
f=$(wget -O - https://smxi.org/sm/upgrade-data/status_t);echo "$f"
f=$(wget -O - https://smxi.org/sm/upgrade-data/alert_message);echo "$f"
f=$(wget -O - https://smxi.org/sm/upgrade-data/alert_message_s);echo "$f"
f=$(wget -O - https://smxi.org/sm/upgrade-data/alert_message_t);echo "$f"


what frustrates me is that some people have used this stuff for years yet don't run basic debug scenariors to find out what is wrong.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 274
Location: South Florida
Reply Quote
Please show me how to debug and I will run it for you.
Maybe you want to know that smxi installed fine until hitting the stop point, I could update kernel with it.
Then came errors 100 and 34.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3882
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
I just posted the code to debug, run it, post the output from one of the curl ones and one of the wget ones.

It shouldn't matter which one, since it's all the same type of command.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 274
Location: South Florida
Reply Quote
:: Code ::
ckosloff@crosshair:~$ f=$(curl https://smxi.org/sm/upgrade-data/alert_message);echo "$f"  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   342  100   342    0     0    679      0 --:--:-- --:--:-- --:--:--   679
Alerts Last Modified: 1 June 2017 19:11 (gmt)
------------------------------------------------------------------
1. You may see a strange text item appear during your upgrade. To get this to
close, hit 'q' and the upgrade will continue, or q + enter, or just enter alone.
-----------------------------------------------------------------
ckosloff@crosshair:~$ f=$(wget -O - https://smxi.org/sm/upgrade-data/status_s);echo "$f"
--2018-04-27 19:17:42--  https://smxi.org/sm/upgrade-data/status_s
Resolving smxi.org (smxi.org)... 216.92.31.53
Connecting to smxi.org (smxi.org)|216.92.31.53|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5
Saving to: ‘STDOUT’

-                     100%[=========================>]       5  --.-KB/s    in 0s     

2018-04-27 19:17:42 (13.5 MB/s) - written to stdout [5/5]

alert

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3882
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Astoundingly, there was in fact a bug with curl downloads, that would have caused this error but only on new installs of smxi.

This may or may not be corrected now.

Was missing a key arguments for curl in warnings section.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 274
Location: South Florida
Reply Quote
So you are frustrated.
I will do my best from now on to resist the urge and post as much info as I possibly can.
Thanks for all your efforts.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3882
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
There was a visual cue, or hint, it took me a while to understand where it came from, that was from the bug. It printed out the word 'alert' in front of the ==== line, pushing it to the right. This was pretty obviously wrong, but it was hard to figure out why it happened until I realized I'd missed one argument for curl file download.
Back to top
Display posts from previous:   
Page: 1, 2  Next
All times are GMT - 8 Hours