After update mlinux upto 5.0 I cannot connect thething. Thething status is “not connect”.
Multitech conduit mlinux return:
////////////////////////////// Description (from TTN): Frequency plan (from TTN): IN_865_867
Is the information correct? 1) Yes 2) No #? 1
Stopping existing forwarder
Stopping ttn-packet-forwarder: start-stop-daemon: warning: failed to kill 1350: No such process
killall: mp_pkt_fwd: no process killed
OK
Get up-to-date TTN configuration for packet forwarder
installer.sh: line 822: node: command not found
Starting ttn-packet-forwarder: OK
The installation is now complete.
Check the gateway output using:
tail -f /var/log/lora-pkt-fwd.log
(It might take some minutes for the first output to appear!)
Check the gateways last seen status in the TTN console after
a few minutes to verify the setup is working correctly
///////////////
How was the installer.sh script invoked?
-> sh installler.sh
What command is on line 822?
-> line 822: node /opt/lora/merge.js /var/config/lora/ttn_global_conf.json /var/config/lora/multitech_overrides.json /var/config/lora/global_conf.json
Installing TTN Multi Protocol Packet Forwarder
Collected errors:
open_outer: Failed to open package ‘/tmp/mp-packet-forwarder_3.0.20-r1_arm926ejste.ipk’: Unrecognized archive format
pkg_extract_control_file_to_stream: Failed to extract control.tar.gz from package ‘/tmp/mp-packet-forwarder_3.0.20-r1_arm926ejste.ipk’.
pkg_init_from_file: Failed to extract control file from /tmp/mp-packet-forwarder_3.0.20-r1_arm926ejste.ipk.
Get up-to-date TTN configuration for packet forwarder
./installer.sh: line 822: node: command not found
./installer.sh: line 826: /etc/init.d/ttn-pkt-forwarder: No such file or directory
The installation is now complete.
Check the gateway output using:
tail -f /var/log/lora-pkt-fwd.log
(It might take some minutes for the first output to appear!)
Check the gateways last seen status in the TTN console after
a few minutes to verify the setup is working correctly
I don’t know. I haven’t had time to look at 5.0 yet. I was away on vacation up till yesterday.
Check the MultiTech site and if not clear ask in their forum.
I’ll look into building the software for 5.0 in the next few weeks when I have some spare time.
With 5.0 you should not even try as there seem to be incompatible changes.
Once an update is available you have a choice, use the default one which uses udp or use the installer to get a more reliable connection to the backend.
Hello
After the upgrade my AEP gateway to firmware 5.00 I got all some error message’s from the installer. (You need to run this agian after the upgrade)
Somthing shuld missing and he could not find the radio.
But after run the installer.sh with “sudo installer.sh”
I was going fine and my Multitech Conduit AEP is online with the new firmware.
I think that Multitech has take care more about securitie.