Page: 1, 2, 3, 4, 5, 6, 7  Next

Trouble installling smxi in a fresh install of Debian testing
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 274
Location: South Florida
Reply Quote
After launching smxi, with wired connection detected, I get error:
DOwnload error: smxi component sm-versions could not be accessed...
The download failed with wget error: The site may be down.
Selecting n after that just brings more similar errors.
All files are present in /usr/local/bin.
Please help
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 a networking issue on your end, I've seen that before, it's nothing that I can resolve for you. Could be in your router, could be your isp, but where it is not, is in smxi.

I used to see this more when smxi had heavy use, there's certain ISP/router combinations that generate that failure.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 274
Location: South Florida
Reply Quote
I don't understand how it is complaining about downloading when files are in same directory.
IMy backup computer doesn't have the issue, it is connected to same router, same ISP, same Debian testing kernel 13.0.1, I believe.
Dunno where to start.
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 a specific networking issue, I've seen it before. the issue is rapid requests, repeated, which somewhere along the chain is ignored. smxi can't fix this issue.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 274
Location: South Florida
Reply Quote
I don't understand how it can be networking issue, if the files are present in same directory, why does smxi fail t to find them?
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
Whether or not you understand this issue doesn't make it a non issue, as I said, I used to see this issue all the time, relatively speaking, not like, constantly,, but it would pop enough to where I recognize it immediately.

It can be a router defect, a bad ISP filter, defective hardware, it can be lots of things, but never once did anyone actually figure out the exact sequence of events that would cause it. Could be router firmware in upstream switches from your house, could be how the modem chats with the ISP, it could be any one of many things, but it is certainly something.

At rare almost not worth thinking about instances, it could be the smxi.org server temporarily missing a request, but that would resolve the next time you tried smxi in almost all cases.

Networking is a very complex area to debug issues in, I've had my ISP take over a week to figure out a networking issue that I was the first to detect, because I do development I recognized it before anyone else on my network node for example. That case was a failing Outbound switch several steps up from my local connection, that's those big industrial networking switches.

Your case however is usually not a failing switch, it's something else, but nobody ever could figure it out.
Back to top
dacorsa
Status: New User - Welcome
Joined: 04 Dec 2016
Posts: 3
Reply Quote
i've the same problem with debian sid....never seen before but now i have this problem. I use smxi till 2005

Maybe a strange update of debian?

best regards
Back to top
smxi not starting anymore
raila
Status: Curious
Joined: 06 Aug 2009
Posts: 5
Reply Quote
same problem here since some days.
"sm-versions could not be accessed - site may be down"
In my case i did not install it new, it is an about three years old install...
A normal apt-get update after trying smxi to start always works!

best regards
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
Just to be make sure there might not be some wget type issue, I updated smxi/sgfxi to use the new https://smxi.org ssl domain explicitly. Note that should not make any difference.

You can verify this on your own systems by these two commands:

:: Code ::
wget -O - smxi.org/sm/sm-versions


which should redirect with a 301 to the https version, like so:

:: Code ::
wget -O - smxi.org/sm/sm-versions
--2017-11-03 08:11:35--  http://smxi.org/sm/sm-versions
Resolving smxi.org (smxi.org)... 216.92.31.53
Connecting to smxi.org (smxi.org)|216.92.31.53|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://smxi.org/sm/sm-versions [following]
--2017-11-03 08:11:36--  https://smxi.org/sm/sm-versions
Connecting to smxi.org (smxi.org)|216.92.31.53|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1009
Saving to: ‘STDOUT’
-                               0%[                                                ]       0  --.-KB/s               
smxi=8.15.23:2017-11-03
sm-lib-apt-tools=1.23.42:2015-06-23
sm-lib-clean-up=2.10.15:2012-02-08
......


If that is what you see, then networking issues is the cause. If it is not what you see, then the https was the cause.

You can further test:

:: Code ::
wget -O - https://smxi.org/sm/sm-versions


which should result in:

:: Code ::
wget -O - https://smxi.org/sm/sm-versions
--2017-11-03 08:15:39--  https://smxi.org/sm/sm-versions
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: 1009
Saving to: ‘STDOUT’

-                               0%[                                                ]       0  --.-KB/s               
smxi=8.15.23:2017-11-03
sm-lib-apt-tools=1.23.42:2015-06-23
sm-lib-clean-up=2.10.15:2012-02-08
sm-lib-distro-conversion=3.3.17:2014-03-29
sm-lib-du-fixes=1.4.12:2015-11-16
sm-lib-graphics=2.6.2:2014-12-19
sm-lib-kde4-updater=0.7.39:2013-11-19
sm-lib-kernel=2.6.86:2017-05-19
sm-lib-kernel-install=2.12.14:2016-05-12
sm-lib-misc-tweaks=1.24.6:2015-03-11
sm-lib-package-install=3.4.38:2016-11-01
sm-lib-package-removal=1.4.2:2011-02-10
sm-lib-warning=2.0.2:2009-04-15
sm-lib-2006-fixes=1.2.2:2008-06-08
sm-lib-2007-fixes=1.3.20:2008-11-17
sm-lib-2008-fixes=1.4.2:2008-12-26
sm-lib-2008-fixes-s=1.0.1:2008-11-17
sm-lib-2008-fixes-t=1.0.2:2008-11-18
sm-lib-2009-fixes=1.1.25:2010-09-16
sm-lib-2009-fixes-s=1.0.1:2009-04-07
sm-lib-2009-fixes-t=1.1.19:2009-12-02
sm-lib-2011-fixes=1.1.0:2011-07-14
sm-lib-2011-fixes-s=1.0.0:2011-02-10
sm-lib-2011-fixes-t=1.1.0:2011-07-14
sgfxi=4.24.18:2017-11-03
svmi=2.8.72:2017-07-27
inxi=2.3.43:2017-10-31
rbxi=2.7.4:2016-12-20
sm-main-version=8.41.58:2017-11-03

###**EOF**###
-                             100%[===============================================>]    1009  --.-KB/s    in 0s     

2017-11-03 08:15:39 (28.9 MB/s) - written to stdout [1009/1009]


If that is what you see, then networking issues are the cause.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 274
Location: South Florida
Reply Quote
In order to run these commands as root, in what directory should I be?
Back to top
Display posts from previous:   
Page: 1, 2, 3, 4, 5, 6, 7  Next
All times are GMT - 8 Hours