Minor additions to the Gateway Troubleshooting documentation

[ymgupta]

Summary

Add the below errors to the Gateway Troubleshooting documentation:

1. I get a Failed to retrieve TCURI from CUPS: (404) Not Found error in the physical gateway logs, which is configured in Basics Station mode. What do I do?
2. I get an ERROR: [main] failed to start the concentrator error at the beginning of the gateway packet forwarder logs. Why?
3. The downlinks failed with the error invalid fixed paths set in application downlink. Why?

Why do we need this?

To assist users in resolving gateway-related issues on their own.

What is already there? What do you see now?

Troubleshooting Gateways

What is missing? What do you want to see?

Add the errors mentioned in the summary with the resolutions to the Troubleshooting Gateways documentation.

How do you propose to document this?

1. While checking the physical Gateway logs configured in Basics Station, I encountered the error Failed to retrieve TCURI from CUPS: (404) Not Found.

• Cause:
  • The error 404 not found occurs due to the incorrect configuration of the API Key in the LoRa Basics Station LNS Authentication Key field that is available in the General Settings of the Gateway in The Things Stack Console.
• Resolution:

  • Suggest the users to follow the instructions in the Configure CUPS to Send the LNS API Key section from the reference https://www.thethingsindustries.com/docs/gateways/lora-basics-station/cups/#configure-cups-to-send-the-lns-api-key

    2. I see the error ERROR: [main] failed to start the concentrator at the beginning of the Gateway packet forwarder logs.

Insights:

• The error indicates that the gateway failed to start the concentrator, which could be due to a hardware issue at the gateway level and it is recommended to contact the gateway manufacturer for further support in this regard.

  3. The downlink failed with the error invalid fixed paths set in application downlink.

Insights:

• The error invalid fixed paths set in application downlink could occur if the gateway mentioned in the downlink path is not connected or is not available for scheduling a downlink message.
• Users should ensure that the mentioned gateway in the downlink path is connected to The Things Stack.

Can you do this yourself and submit a Pull Request?

No, @nejraselimovic

[KrishnaIyer]

The error 404 not found occurs due to the incorre

That doesn't sound right. If the API Key is incorrect, you should get a 401 Unauthorized.