Packet Forwarder Won't Start

[Damian Christie]

I been working on this one for a while with no success. The packet forwarder appears to start but in fact does not.

root@mtcdt:~# /etc/init.d/lora-packet-forwarder start
Found MTAC-LORA-868 with MTAC-LORA-1.0 hardware
Starting lora-packet-forwarder: OK
root@mtcdt:~# /etc/init.d/lora-packet-forwarder stop
Stopping lora-packet-forwarder: start-stop-daemon: warning: failed to kill 851: No such process
OK
root@mtcdt:~#

I’ve verified that global_conf.json is a valid JSON format (i.e. no missing commas). The only thing I changed in this file was the gateway EUI and the server address/ports.

In /etc/default/, lora-network-server is disabled and lora-packet-forwarder is enabled.

The packet forwarder log is not created in /var/log/. I tried creating this before starting the forwarder and the file is unmodified after starting.

I have updated all relevant software to the latest versions:

root@mtcdt:~# cat /etc/mlinux-version
mLinux 3.3.6
Built from branch: (detachedfromf4f803d)
Revision: f4f803d9bdab9aece5b101496cad97710f920246
root@mtcdt:~# opkg list | grep lora
lora-gateway-utils - 4.0.1-r9.0
lora-network-server - 1.0.26-r1.0
lora-packet-forwarder - 3.1.0-r9.0
lora-packet-forwarder-usb - 1.4.1-r10.1
lora-query - 1.0.2-r1.0
root@mtcdt:~# mts-io-sysfs show lora/product-id
MTAC-LORA-868
root@mtcdt:~# mts-io-sysfs show ap1/product-id
MTAC-LORA-868
root@mtcdt:~# mts-io-sysfs show ap2/product-id
cat: can't open '/sys/devices/platform/mts-io/ap2/product-id': No such file or directory

In the system logs I see the following. Does success:0 mean the link is not created?

May 24 05:31:35 mtcdt user.info kernel: [INFO] mts-io:lora_setup:90: created link [lora] to [ap1], success:0

No mention of “pkt” or “fwd” in the system log.
The boot log attempts to start the network server, but no mention of the packet forwarder:

Wed May 24 05:31:37 2017: lora-network-server: disabled in /etc/default

Is there anything else I should be looking at?

[Jason Reiss]

Try this

$ cd /var/run/lora/1
$ ./lora_pkt_fwd

[Jason Reiss]

Are you connected to the internet?

$ nslookup iot.semtech.com

[Damian Christie]

I have no “/var/run/lora/” directory…

[Damian Christie]

Neither lora-packet-forwarder_3.1.0-r9.0_mtcdt.ipk nor lora-packet-forwarder-usb_1.4.1-r10.1_arm926ejste.ipk create this folder or add lora_pkt_fwd.

• This reply was modified 7 years, 10 months ago by Damian Christie.
• This reply was modified 7 years, 10 months ago by Damian Christie.

[Jason Reiss]

That directory should be created by /etc/init.d/lora-packet-forwarder at the beginning of do_start()

However the symlinks do not look like they are being setup correctly.

Try this updated package install. Renable the lora-packet-forwarder in /etc/default after install.

http://www.multitech.net/downloads/lora-packet-forwarder_3.1.0-r9.1_mtcdt.ipk

[Damian Christie]

That worked!! The folders were created when I ran the forwarder after install and the process is staying up. The gateway is now connected to the server. Great, thanks Jason. Was this just an issue with r9.0?

[Damian Christie]

Ok it sort of worked. I can start the packet forwarder manually now but it doesn’t come up after a reboot. The contents of rc5.d are below – no packet forwarder.

root@mtcdt:~# ls -l /etc/rc5.d/
lrwxrwxrwx    1 root     root            20 Mar 20 11:13 S01networking -> ../init.d/networking
lrwxrwxrwx    1 root     root            16 Mar 20 11:13 S02dbus-1 -> ../init.d/dbus-1
lrwxrwxrwx    1 root     root            14 Mar 20 11:12 S09sshd -> ../init.d/sshd
lrwxrwxrwx    1 root     root            14 Mar 20 11:13 S10gpsd -> ../init.d/gpsd
lrwxrwxrwx    1 root     root            21 Mar 20 11:12 S15mountnfs.sh -> ../init.d/mountnfs.sh
lrwxrwxrwx    1 root     root            17 Mar 20 11:13 S20hostapd -> ../init.d/hostapd
lrwxrwxrwx    1 root     root            20 Mar 20 11:13 S20hwclock.sh -> ../init.d/hwclock.sh
lrwxrwxrwx    1 root     root            14 Mar 20 11:13 S20ntpd -> ../init.d/ntpd
lrwxrwxrwx    1 root     root            16 Mar 20 11:12 S20syslog -> ../init.d/syslog
lrwxrwxrwx    1 root     root            20 Mar 20 11:13 S50usb-gadget -> ../init.d/usb-gadget
lrwxrwxrwx    1 root     root            18 Mar 20 11:13 S70lighttpd -> ../init.d/lighttpd
lrwxrwxrwx    1 root     root            19 Mar 20 11:13 S70mosquitto -> ../init.d/mosquitto
lrwxrwxrwx    1 root     root            29 Mar 20 11:12 S80lora-network-server -> ../init.d/lora-network-server
lrwxrwxrwx    1 root     root            15 Mar 20 11:13 S90crond -> ../init.d/crond
lrwxrwxrwx    1 root     root            40 Mar 20 11:12 S95led-status_heartbeat_trigger -> /etc/init.d/led-status_heartbeat_trigger
lrwxrwxrwx    1 root     root            23 Mar 20 11:13 S95reset-handler -> ../init.d/reset-handler
lrwxrwxrwx    1 root     root            15 Mar 20 11:13 S99monit -> ../init.d/monit
lrwxrwxrwx    1 root     root            22 Mar 20 11:12 S99rmnologin.sh -> ../init.d/rmnologin.sh
lrwxrwxrwx    1 root     root            23 Mar 20 11:12 S99stop-bootlogd -> ../init.d/stop-bootlogd
root@mtcdt:~# cat /etc/default/lora-packet-forwarder
# set to "yes" or "no" to control starting on boot
ENABLED="yes"

[Damian Christie]

I just want to bump this so you’re aware of this. I understand this is something easily configured in Linux but I figure you’d want to have the install file do this itself.

Thanks.

[Author]

Posts