NODE RED problem on version 4.0.1 about chirpstack-gateway-os HOT 6 CLOSED

What are the minimum steps to reproduce this issue? Could you further explain what this means?

But after 2-3 message transfers connection with NODE RED server was lost again.

What does "message transfers" mean in this case?

from chirpstack-gateway-os.

-We are using a ST Nucleo WL55JC1 as an End Node and ChirpStack Gateway OS on a Raspberry Pi.

-We built the "Echo flow" example from the chirpstack Node-RED documentation.

-The End Node sends a LORAWAN message / 10sec and gateway echoes back the message.

-After 3-4 transactions Node-RED gives the message "server connection has been lost".

We downgrade to version 4.0 and the problem disappears.

from chirpstack-gateway-os.

Thanks, I'm able to reproduce the issue. For some reason, NodeJS is throwing a "Bus error" and terminates.

12 Dec 12:23:22 - [info] Starting flows
12 Dec 12:23:22 - [info] Started flows
12 Dec 12:23:22 - [info] [mqtt-broker:localhost] Connected to broker: mqtt://localhost:1883
Bus error

I'll investigate this further.

from chirpstack-gateway-os.

Quick update, I've tried various things:

• Updating Node-RED
• Updating node-red-contrib-chirpstack package
• Different ways of packaging the above packages
• Installing these packages by hand on the Pi

But this doesn't solve the issue. I'm now trying to update NodeJS to a later version (16.18.1) in the hope that this will resolve the issue 🤞

There have been several reports by other uses (non ChirpStack related), in which case it was either resolved by deleting the node_packages directory and npm install ... everything again or updating NodeJS.

from chirpstack-gateway-os.

Only updating NodeJS did result in the same issue. It looks like the issue was caused by a Yocto recipes update (which I needed because of a newer Rust version). I reverted this update and backported the updated Rust recipes. I no longer see this strange "Bus error" appearing. Tomorrow I'll tidy up all the changes. I expect to release an update in the next couple of days. Thanks again for reporting.

from chirpstack-gateway-os.

@stathisioannides the above commit fixes this issue.

from chirpstack-gateway-os.