# Node-red-contrib-rfxcom segmentation fault

**URL:** https://discourse.nodered.org/t/node-red-contrib-rfxcom-segmentation-fault/87754
**Category:** General
**Tags:** docker
**Created:** [6 May 2024 14:38 UTC](https://discourse.nodered.org/t/node-red-contrib-rfxcom-segmentation-fault/87754 "2024-05-06T14:38:51Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![cbartetzko](https://avatars.discourse-cdn.com/v4/letter/c/9dc877/32.png) [@cbartetzko](https://discourse.nodered.org/u/cbartetzko)
#### Post date: [6 May 2024 14:38 UTC](https://discourse.nodered.org/t/node-red-contrib-rfxcom-segmentation-fault/87754/1 "2024-05-06T14:38:51Z")

</div>

I've added node-red-contrib-rfxcom 2.13 to my Palette in NodeRed (Docker on Raspberry Pi).  
When trying a simple flow (rfx-sensor to debug) and configuring rfx to /dev/ttyUSB0  
my nodered container instantly crashes when deploying the flow with this error message:

./entrypoint.sh: line 14: 8 Segmentation fault (core dumped) /usr/local/bin/node $NODE\_OPTIONS node\_modules/node-red/red.js --userDir /data $FLOWS "${@}"

The RFXCOM device on /dev/ttyUSB0 works without problems in other smarthome software (e.g. domoticz)  
on this Raspi.

Any idea, what I can do to get it working under nodered ?

---

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [6 May 2024 14:48 UTC](https://discourse.nodered.org/t/node-red-contrib-rfxcom-segmentation-fault/87754/2 "2024-05-06T14:48:12Z")

</div>

It'll be an issue with binaries for serial port. This thread will give you the gist : [https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://github.com/serialport/node-serialport/issues/2438&ved=2ahUKEwj3noDpofmFAxXDQkEAHXFdDR8QFnoECA8QAQ&usg=AOvVaw2uJwlUnMVxU7crV7Xid4V3](https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://github.com/serialport/node-serialport/issues/2438&ved=2ahUKEwj3noDpofmFAxXDQkEAHXFdDR8QFnoECA8QAQ&usg=AOvVaw2uJwlUnMVxU7crV7Xid4V3)

You likely need to rebuild the binaries. You might need the node author to bump latest dependency versions

---

<div class="post-metadata">

### Author: ![cbartetzko](https://avatars.discourse-cdn.com/v4/letter/c/9dc877/32.png) [@cbartetzko](https://discourse.nodered.org/u/cbartetzko)
#### Post date: [6 May 2024 16:02 UTC](https://discourse.nodered.org/t/node-red-contrib-rfxcom-segmentation-fault/87754/3 "2024-05-06T16:02:04Z")

</div>

Thanks @Steve-Mcl  
However sounds (too) complicated for my knowledge.

I've now tried running nodered natively on Raspberry (w/o Docker).  
This is working fine.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [4 August 2024 16:02 UTC](https://discourse.nodered.org/t/node-red-contrib-rfxcom-segmentation-fault/87754/4 "2024-08-04T16:02:28Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.