search

evristzam / ndt

Automatically exported from code.google.com/p/ndt
Other
0 stars 0 forks source link

flash client hangs on "preparing your tests" on desk179 install #172

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
On the installation at http://desk179.internet2.edu:7123/, it seems to be 
hanging in flash on OS X with Chrome and FF.

Original issue reported on code.google.com by AaronMat...@gmail.com on 10 Mar 2015 at 12:59

GoogleCodeExporter commented 9 years ago 
safari too

Original comment by AaronMat...@gmail.com on 10 Mar 2015 at 1:00

GoogleCodeExporter commented 9 years ago

Original comment by AaronMat...@gmail.com on 10 Mar 2015 at 1:25

GoogleCodeExporter commented 9 years ago 
Problem seems to be not related with browser or flash version. Flash console 
outputs:

"Security error on Control socket: [SecurityErrorEvent type="securityError" 
bubbles=false cancelable=false eventPhase=2 text="Error #2048"]"

Could you provide information if this problem occurs only on this specific 
machine with Mac system (I mean if it was tested and worked on another device 
with Mac also) ? Also what http server is being used ?

Original comment by skost...@soldevelo.com on 11 Mar 2015 at 2:02

GoogleCodeExporter commented 9 years ago 
I've not tested with another server. I've seen multiple Macs (the only folks 
who I've had test it had Macs) have seen this issue with this installation.

Original comment by AaronMat...@gmail.com on 12 Mar 2015 at 12:25

GoogleCodeExporter commented 9 years ago

Original comment by skost...@soldevelo.com on 12 Mar 2015 at 2:52

GoogleCodeExporter commented 9 years ago 
It seems like flashpolicy file isn't being returned by server. In order to make 
it work ndt-flashpolicyd daemon needs to be run to listen on port 843. It 
should be installed automatically, however needs to be run as another ndt 
processes need. Could you verify if that is the case? Or tell me how can I 
connect to server using ssh to check it?

Original comment by skost...@soldevelo.com on 12 Mar 2015 at 3:01

GoogleCodeExporter commented 9 years ago 
Ok, I see what the issue was on that host (firewall rules). Is there any way to 
get an actual error message that might tell people what's going on there, 
instead of just hanging?

Original comment by AaronMat...@gmail.com on 12 Mar 2015 at 3:26

GoogleCodeExporter commented 9 years ago 
Currently all errors (if any) occured during flash client execution are stored 
in separated string. However such variable isn't used in java applet. Would it 
be right if JS would check regularly if any error occured and if yes then 
immediately display result view with information that something went wrong 
(with provided error messages)?

Original comment by skost...@soldevelo.com on 12 Mar 2015 at 3:39

GoogleCodeExporter commented 9 years ago 
Yeah. That would be infinitely more useful than hanging :)

Original comment by AaronMat...@gmail.com on 12 Mar 2015 at 3:41

GoogleCodeExporter commented 9 years ago 
I've committed mentioned changes to Issue172 branch. From now if test's 
performing fails then result page is being shown and on Details tab error 
message is visible.

Original comment by skost...@soldevelo.com on 13 Mar 2015 at 11:07

GoogleCodeExporter commented 9 years ago 
Are these changes ok to merge into trunk?

Original comment by skost...@soldevelo.com on 18 Mar 2015 at 5:13

GoogleCodeExporter commented 9 years ago 
What's the error message that you get in the "firewall" scenario?

Original comment by AaronMat...@gmail.com on 19 Mar 2015 at 5:17

GoogleCodeExporter commented 9 years ago 
It's exactly the same mentioned earlier. Flash only recognizes it as general 
security error and from JS I only get this message as is:
"Security error on Control socket: [SecurityErrorEvent type="securityError" 
bubbles=false cancelable=false eventPhase=2 text="Error #2048"] NDT test 
failed. ".

Original comment by skost...@soldevelo.com on 20 Mar 2015 at 8:46

GoogleCodeExporter commented 9 years ago 
That's a rather useless error message. Would it be possible to parse for #2048 
or something, and put up a more useful one?

Original comment by AaronMat...@gmail.com on 20 Mar 2015 at 11:48

GoogleCodeExporter commented 9 years ago 
#2048 error code is related to different kinds of security errors. It's hard to 
recognize what is causing problem exactly only by seeing this message. Should 
we then print only simple message as "Some security error occured" ?

Original comment by skost...@soldevelo.com on 20 Mar 2015 at 11:56

GoogleCodeExporter commented 9 years ago 
I'd imagine the vast majority of cases will be firewall related, so at minimum 
stick something in there like "This error may be caused by firewall issues, 
make sure that port 843 is available on the NDT server, and that you can access 
it".

Original comment by AaronMat...@gmail.com on 20 Mar 2015 at 11:58

GoogleCodeExporter commented 9 years ago 
Ok. Committed changes to Issue172 branch.

Original comment by skost...@soldevelo.com on 20 Mar 2015 at 12:07

GoogleCodeExporter commented 9 years ago 
Seems fine to me. Commit away.

Original comment by AaronMat...@gmail.com on 20 Mar 2015 at 12:15

GoogleCodeExporter commented 9 years ago 
Merged into trunk

Original comment by skost...@soldevelo.com on 20 Mar 2015 at 12:27