Table of Contents

Troubleshoot the gateway

Useful logs

When configuring the gateway or when something unusual happens, most of the time, to understand the behaviour of the gateway it is advised to consult the logs. Here is the list of the most useful logs:

Useful commands

Since Kerlink gateways use a Unix system, most current commands are available (ifconfig, route, ps, iptables, …).

KerOS specific commands:

Bootcause

The bootcount value is counting the number of reboots since the last power cycle. At each power loss the counter is reset to 0. The maximum value of this counter is 65535.
The bootcount value can be checked in the file /tmp/board_info.json:

# grep bootcount /tmp/board_info.json
        "bootcount": 1,

When a gateway is started/restarted, U-Boot displays the boot cause.
The possible reasons are:

This information is transmitted to initrd and to applications with the kernel argument « bootcause ».
The information is then provided in the bootcause parameter in the file /proc/cmdline.
Example:

# cat /proc/cmdline 
console=ttymxc0,115200 bootmode=nominal bootcause=SW bootcount=5 bootfail=0

In case you need assistance to troubleshoot your gateway, Kerlink's support team will help you if:

If the gateway does not satisfy this requirement, please contact sales@kerlink.fr. Our Sales team will make you an offer to get assistance.

Otherwise, contact support@kerlink.fr to get assistance. Our support team will open you an account in Kerlink's ticketing tool.

When contacting the support team, to improve and speed up the resolution of your issue, please provide them:

Automatic log gathering

To simplify the log gathering process, two scripts are available. These scripts generate an archive containing many logs and commands results.

Gathering logs from WebUI since release 5.9

Gathering logs from shell since release 4.2

Gathering logs from shell on older releases

Gathering logs from USB (no commands required)

Helium

This section contains some tips to do the first level of analysis (support level 1) on Helium gateways.
It will help you to investigate before escalate to Kerlink support (level 2).

Please note that there is an existing open wiki for Helium users: Kerlink Helium Hotspot Wiki

Source of info KPI Value Action
Onboarding dashboard Last seen More than 30m ago Gateway is offline. Ask customer to check power/internet.
Less than 30m ago Gateway is online. Check next KPI.
Block height = 0 Gateway is downloading a snapshot.
= 1 Gateway is loading the downloaded snapshot.
Else KPI is ok, check next KPI.
Block age > 30 mn Gateway is syncing, check again in one hour. If it persists, you can open a ticket to Kerlink Support.
< 30 mn Gateway is synced. Check next KPI.
Helium explorer 24h/14d earnings > 0 HNT Seems OK. Confirm with other Explorer KPIs.
Last activity date < 3h Seems OK. Confirm with other Explorer KPIs.
Is there a constructed challenge in the past 24h? Yes Seems OK. Confirm with other Explorer KPIs.
No When gateway is synced, it should challenge. You can open a ticket to Kerlink Support.
Is there a challenged beaconer in the past 24h? Yes Seems OK. Confirm with other Explorer KPIs.
No Gateway might be relayed. If not, you can open a ticket to Kerlink Support.
Is there a witnessed beacon in the past 8-24h? Value depends on density around miner Seems OK. Confirm with other Explorer KPIs.
No You can open a ticket to Kerlink Support.
Is there a “broadcasted beacon” in the past 5d? Yes Seems OK. Confirm with other Explorer KPIs.
No This is random but it seems odd. You can open a ticket to Kerlink Support.

Gateways connected to a WMC

For gateways connected to a WMC, you can use the Remote Command: Remote Access > Command

Due its cryptographic key and to ensure Kerlink Helium Hotspot security, no SSH access can be given to those gateways.

You can use commands below:

Command Awaited result
opkg list
monit status miner Status = OK
monit status lorafwd_helium Status = OK
/etc/init.d/miner status Check Diff

If the result is different than the awaited result, you can open a ticket to Kerlink Support.