User Tools

Site Tools


Sidebar

Kerlink Wiki Home Page

Home

Setups

General information

Wirnet™ iBTS information

Wirnet™ iFemtoCell information

Wirnet™ iFemtoCell-evolution information

Wirnet™ iStation information

System management

Network management

LoRa Features

KerOS customization

Support and resources



www.kerlink.com

wiki:troubleshoot

This is an old revision of the document!


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:

  • /var/log/messages*: These files are the main logs, they gather the traces of the firmware. They contain the boot traces, the network events, the hardware events, and many other traces.
  • /usr/spf*/var/log/spf2.log*: Theses files contains the traces of the packet forwarder. If you encounter LoRa issues, this is a good way to start.

FIXME : adapt for CPF

  • /tmp/board_info.json: This file contains information about the hardware of the gateway. It is generated at each boot time.

FIXME

  • /tmp/calib_loraloc.json: This file contains the calibration values specific to this gateway. It is generated at boot time.
  • /dev/nmea* (Wirnet iBTS only): These devices receive nmea frames (GPS) every seconds. It can be monitored with the cat command.

Useful commands

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

KerOS specific commands:

  • gsmdiag.py: generates a status of the modem.
  • connmanctl: used to configure/monitor the network manager.
  • opkg list-installed: lists the installed packages.
  • monit status: displays the status of the monitored processes.

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:

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

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

  • POR: Power On Reset (happens when the gateway is powered or after a powerloss).
  • WDOG: Watchdog.
  • SW: Software Reset.
  • HW: Physical reset (RESET button).
  • UNKNOWN: unknown cause.

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:

  • The gateway is still under warranty.
  • The gateway has been bought directly from Kerlink.

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:

  • The serial number of your gateway(s) (the serial number is written on a sticker inside the case with “Wirnet iBTS” written on it or the “Final product ID” on the rear sticker for Wirnet iFemtoCell).
  • A precise description of your problem. “Gateway not working” is not enough to investigate.
  • The list of the actions you took to troubleshoot/investigate your problem.
  • The date of your problem.
  • The version of your firmware.
  • The logs of your gateway (refer to the automatic log gathering section). Without these logs, it is difficult to investigate. If you are able to reproduce the problem, make sure to reproduce it and gather the logs afterward.
  • Any information that would help us understand the context. For example, if the gateway is on the field or in a lab, if a third party program is used, if the gateway was previously working, etc.

Automatic log gathering

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

TODO

  • adapt for CPF logs
  • add result of overlay diff
  • add mount command
  • remove reference to /user/rootfs_rw

Gathering logs from shell

Gathering logs from USB (no commands required)

wiki/troubleshoot.1546958676.txt.gz · Last modified: 2019/01/17 10:01 (external edit)