MultiTech Developer Resources » Topic: lora-network-server stops

lora-network-server stops

This topic has 8 replies, 2 voices, and was last updated 6 years ago by Ferenc Unghváry.

Viewing 9 posts - 1 through 9 (of 9 total)

Author

Posts

April 13, 2018 at 4:25 am #23088

Ferenc Unghváry

Participant

Dear Support,

we have a multi connect conduit with mLinux.
Today the lora-network-server always stops after a while because of an exception. See the latest some log messages:


9:16:28:973|INFO| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|Parsing 1 packets
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::substr
Logger Level Changed to 100
9:12:38:568|INFO|Setting join delay according to public/private setting
9:12:38:569|INFO|Setting join 5 seconds

Until now the device worked perfectly.
What can cause this error?
What can I do to solve this issue?

April 13, 2018 at 6:43 am #23089

Jason Reiss

Keymaster

What version of mlinux and network server are you running?

# cat /etc/issue
# /opt/lora/lora-network-server –version

Can you increase the logging level to maximum and provide a bit more logging context?

April 13, 2018 at 6:50 am #23090

Ferenc Unghváry

Participant

mLinux 3.2.0 \n \l
MTS Network Server – Version 1.0.43

How can I increase the logging level?

April 13, 2018 at 6:55 am #23091

Jason Reiss

Keymaster

We have new versions of mLinux and network server available
http://www.multitech.net/developer/downloads/

You may want to see if the issue persists after upgrading.

Info for configuring logging:

http://www.multitech.net/developer/software/lora/conduit-mlinux-lora-communication/conduit-mlinux-advance-lora-configuration/


# vi /var/config/lora/lora-network-server.conf

"log": {
    "syslog": false,
    "path": "/var/log/lora-network-server.log",
    "level": 100,
    "console": true
}

April 13, 2018 at 8:35 am #23094

Ferenc Unghváry

Participant

The log level was already set to 100.
Here a longer log:


13:4:5:474|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PULL-DATA|192.168.63.103:46804
13:4:5:607|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PUSH-DATA|192.168.63.103:34877
13:4:5:608|INFO| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|Parsing 1 packets
13:4:5:609|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|DATA: 400500000000bff00333ed531db33dd5a2525762607404181c206432bf520201b41a0341d8980326d8b2
13:4:5:609|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|FREQ: 868.500000 MHz DR5 RSSI: -46 dB SNR: 70 cB
13:4:5:610|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|TYPE: Unconfirmed Up
13:4:5:610|DEBUG| GW:00:80:00:00:00:00:c1:ca|PACKET-RX|ADDR: 00:00:00:05 FCnt:f0bf
13:4:5:611|INFO| ED:00-01-02-03-04-05-06-0b|CHECK-PKT|FCNT: 0002f0bf LAST-FCNT: 0002f0be Duplicate: no
13:4:5:612|INFO| ED:00-01-02-03-04-05-06-0b|CHECK-MIC|ADDR: 00:00:00:05 passed
13:4:5:612|INFO| ED:00-01-02-03-04-05-06-0b|PER|0.247831%
13:4:5:613|DEBUG| ED:00-01-02-03-04-05-06-0b|PACKET-RX|GW:00:80:00:00:00:00:c1:ca Time_us:1058586931
13:4:5:613|DEBUG| ED:00-01-02-03-04-05-06-0b|PACKET-RX|Downlink Packets Queued: 0
13:4:5:613|INFO| ED:00-01-02-03-04-05-06-0b|FCTRL|ADR:0 ADRACK:0 ACK:0 CLASS:A OPTS:0
13:4:5:625|TRACE| Schedule DC band: 1 available: 36000 duration: 56 freq: 868500000
13:4:5:625|INFO| ED:00-01-02-03-04-05-06-0b|SCHED-TX|Use RX1 TOA:56 ms
13:4:5:626|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|JSON: {"chan":2,"codr":"4/5","data":"QAUAAAAAv/ADM+1THbM91aJSV2JgdAQYHCBkMr9SAgG0GgNB2JgDJtiy","datr":"SF7BW125","freq":868.5,"lsnr":7,"modu":"LORA","rfch":1,"rssi":-46,"size":42,"stat":1,"time":"2018-04-13T13:03:50.608672Z","tmst":1058586931}
13:4:5:633|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PUSH-DATA|127.0.0.1:41926
13:4:5:635|INFO| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|Parsing 1 packets
13:4:5:636|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|DATA: 400500000000bff00333ed531db33dd5a2525762607404181c206432bf520201b41a0341d8980326d8b2
13:4:5:636|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|FREQ: 868.500000 MHz DR5 RSSI: -83 dB SNR: 72 cB
13:4:5:636|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|TYPE: Unconfirmed Up
13:4:5:637|DEBUG| GW:00:80:00:00:00:00:c1:ca|PACKET-RX|ADDR: 00:00:00:05 FCnt:f0bf
13:4:5:638|TRACE| Test authentication of duplicate frame
13:4:5:639|INFO| ED:00-01-02-03-04-05-06-0b|CHECK-PKT|FCNT: beea6094 LAST-FCNT: 0002f0bf Duplicate: yes
13:4:5:639|INFO| ED:00-01-02-03-04-05-06-0b|CHECK-MIC|ADDR: 00:00:00:05 passed
13:4:5:640|INFO| ED:00-01-02-03-04-05-06-0b|PER|0.247525%
13:4:5:640|DEBUG| ED:00-01-02-03-04-05-06-0b|PACKET-RX|GW:00:80:00:00:00:00:c1:ca Time_us:3671254707
13:4:5:640|DEBUG| ED:00-01-02-03-04-05-06-0b|PACKET-RX|Downlink Packets Queued: 0
13:4:5:641|INFO| ED:00-01-02-03-04-05-06-0b|FCTRL|ADR:0 ADRACK:0 ACK:0 CLASS:A OPTS:0
13:4:5:643|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|JSON: {"chan":2,"codr":"4/5","data":"QAUAAAAAv/ADM+1THbM91aJSV2JgdAQYHCBkMr9SAgG0GgNB2JgDJtiy","datr":"SF7BW125","freq":868.5,"lsnr":7.2000000000000002,"modu":"LORA","rfch":0,"rssi":-83,"size":42,"stat":1,"time":"2018-04-13T13:04:05.632249Z","tmst":3671254707}
13:4:6:379|INFO| ED:00-01-02-03-04-05-06-0b|FRAME-TX|Nothing to transmit
13:4:15:234|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PULL-DATA|127.0.0.1:45199
13:4:15:674|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PULL-DATA|192.168.63.103:46804
13:4:19:865|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PUSH-DATA|127.0.0.1:41926
13:4:19:866|INFO| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|Parsing 1 packets
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::substr
Logger Level Changed to 100
9:39:41:806|INFO|Setting join delay according to public/private setting
9:39:41:807|INFO|Setting join 5 seconds

April 13, 2018 at 8:43 am #23095

Jason Reiss

Keymaster

Thanks for the extended logging.

I see you have remote gateways in packet forwarder mode.

An upgrade to the v2.0.19 network server has better support for a network configured with central network server and packet forwarding gateways.

There may an issue using the v1.0.43 network server in this setup as the feature was not fully tested at that point.

April 13, 2018 at 8:51 am #23096

Ferenc Unghváry

Participant

Do I have to upgrade mLinux, lora-network-server and lora-packet-forwarder on both multiConnect Conduit devices?

April 13, 2018 at 9:05 am #23097

Jason Reiss

Keymaster

I would upgrade both if possible.
At least the Conduit running the network server should definitely be upgraded.
The packet forwarder unit, if used with a USB card, has had a patch removed so it will exit if the MTAC card gets in a bad state and attempts to report invalid packet fields for datarate and size.
Otherwise a Conduit with an SPI card may not need updating.

Both Conduits should use have a monit configured to ensure the network server and packet forwarder process are restarted in case of unexpected exit.

AEP firmware includes an angel process that handles this feature. mLinux does not provide this out of the box, monit should be used.

April 17, 2018 at 1:17 am #23128

Ferenc Unghváry

Participant

Last Friday there was a powerbreak for a short time.
On Monday I could not login to the conduit. The conduit responses for ping but it does not response for SSH.

The conduit is built on the roof of the building.
It gets power via PoE. I unplugged the Ethernet cable and reconnected after a while. But it did not help.

What can we do?
How can we do a factory reset?

Author

Posts

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.

lora-network-server stops

User

Sitemap

Pages

Forums