Closed EtienneBourdeau closed 3 years ago
Are you sure the logged error is from starting the packet-forwarder (I've seen sometimes that when processes are logging async, that lines can get mixed).
On my Conduit I have installed according to the instructions you mentioned. After a reboot, I do see that the forwarder is started.
Thank you for your answer.
I will be a little more precise : This morning (Friday August 2nd, ~09h00 AM GMT+1), I have flashed once again the 5.0.0 firmware on my mlinux Gateway (model : MTCDT-LEU1-246L-EU-GB), so I could go all over again from the beginning with a "clean" gateway
Here are the steps I have followed from here :
https://image.noelshack.com/fichiers/2019/31/5/1564730561-capt1.png
https://image.noelshack.com/fichiers/2019/31/5/1564730561-capt2.png
https://www.noelshack.com/2019-31-5-1564730561-capt3.png
Thank you very much for reading this and for caring about this problem, Kind regards,
Etienne
I have received a similar report:
The semtech packet forwarder does not start up if the MT Conduit's cellular interface is enabled and it does not get a signal from the carrier.
One option would be to look into adding Monit as a service monitoring daemon. With the init script it either starts or fails but it will not re-retry. Using Monit (which I'm also using for the LoRa Gateway OS), it will retry if it detects that the process has failed.
Hello !
I have followed the tutorial of this page to install the packet forwarder on my Multitech gateway : https://www.loraserver.io/lora-gateway-bridge/gateway/multitech/
But, while it worked perfectly on older gateways (same model, just older mlinux versions), it happens that on mlinux 5.0.0, after adding the packet forwarder to defaults with update-rc.d and rebooting, an error message appears on startup :
Is there a way to fix this ? By advance, thank you very much !
Kind regards, Etienne