Opened 2 years ago

Closed 14 months ago

#2413 closed defect (fixed)

Bandwidth Test always fails in Tokyo, Japan

Reported by: Masayuki Hatta Owned by: sadie
Priority: minor Milestone: 0.9.45
Component: apps/console Version: 0.9.38
Keywords: Cc:
Parent Tickets: Sensitive: no


When I try to run the bandwidth test, it always says:

No results were received. Either the test server is unavailable or network problems are preventing the test from running correctly. Please try again.

The reason seems to be the server it queries is (Tokyo JP), which doesn't work somehow. If I run the test directly from M-Lab's NDT site from the same location, it queries and works. Maybe M-Lab's problem.


Change History (3)

comment:1 Changed 2 years ago by zzz

Interesting. It's a two-stage process where first you ask the name server for the name of the closest test server, then you run the actual test.

One reason for possible difference is that we ask the name server for an SSL test server. I think on the NDT site the default is non-SSL. It took a while to figure out how to do SSL, and it may not be as closely monitored or the infrastructure for it may have bugs. Why Haneda works and Tokyo doesn't, that may be the reason, not sure.

We have a command line you can try with or without the -s argument to try with and without SSL:

java -jar /path/to/routerconsole.jar mlabrunner [-s]

I don't have a way to specify the server on the command line right now. Maybe we need to backoff and retry with non-SSL if SSL fails.

comment:2 Changed 2 years ago by zzz does not respond either for SSL or non-SSL. I don't know if SSL isn't fully supported by their name server, or just a bug. We may have to ask them. We don't retry with non-SSL if SSL fails, maybe we should.

Added support for specifying a server on the mlabrunner CLI, in 10efff13daa5aae7158a6bc4f5d0f6a1dba1b713 0.9.38-1

comment:3 Changed 14 months ago by zzz

Component: installerapps/console
Milestone: 0.9.390.9.45
Owner: set to sadie
Resolution: fixed
Sensitive: unset
Status: newclosed

Several fixes were in 0.9.45. See #2672

Note: See TracTickets for help on using tickets.