Downlink Desk Operator's Manual

DMC-DLD-A-30-00-00-00A-400A-AFault isolationIssue 0012026-11-04UnclassifiedQA: UnverifiedApplies to Downlink Desk 0.17.x

Web console – Fault isolation: the console does not open

Fault description

The console address does not open in the browser, or the console says it cannot reach the server.

Preliminary requirements

Required conditions

  • An alert or symptom described above is present.

Required persons

1 × Operator. Estimated time: 10 to 30 minutes.

Support equipment

  • A computer or phone with a web browser, on the same network as the server
  • Terminal access to the server, for example over SSH, for steps on the server

Supplies

None

Spares

None

Safety conditions

None

Isolation procedure

Step 1

Check that your device is on the same network as the server, or connected through the team's private network.

Is your device on the right network?

Yes go to Step 2No go to Result A

Step 2

Check whether a VPN is running on your device.

Is a VPN running?

Yes go to Result BNo go to Step 3

Step 3

Try to connect to the server over SSH, for example ssh yourusername@groundpi.local.

Does the server answer?

Yes go to Step 4No go to Result C

Step 4

On the server, check the console service: systemctl status downlink-desk-web.

Does it show the service as active (running)?

Yes go to Result ENo go to Result D

Results

Result A

Connect your device to the server's network, or to the team's private network, and open the console address again.

Result B

The VPN is probably blocking local traffic. Turn on its option to allow local network access, or disconnect it, and open the console address again.

Result C

The server is off, has lost power or is not on the network. Check its power supply and network connection. A Raspberry Pi needs a proper 5 V, 2.5 A supply; a weak one causes random crashes. After power returns, the console starts by itself within a few minutes.

Result D

Restart the console service: sudo systemctl restart downlink-desk-web. If it does not stay running, read its log with journalctl -u downlink-desk-web -n 50 and report the error to whoever maintains the server.

Result E

The service is running, so the problem is between your device and the server. Check the address and port (8080 by default), and try the server's IP address in place of its name. If an update ran recently, check the About tab once you are in.

Requirements after job completion

  • The cause is found and recorded in the log, or the alert is handed over with notes.