Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with Docker Node-Red #132

Closed
vampywiz17 opened this issue May 28, 2023 · 5 comments
Closed

Problem with Docker Node-Red #132

vampywiz17 opened this issue May 28, 2023 · 5 comments

Comments

@vampywiz17
Copy link

vampywiz17 commented May 28, 2023

Hello there,

I try to migrate my local Node-RED install to Docker, but if this node is active, the Node-RED can not start...

Seems the problem is connect this (the error message is same):

serialport/node-serialport#2438

28 May 10:54:17 - [info] 
Welcome to Node-RED
===================
28 May 10:54:17 - [info] Node-RED version: v3.0.2
28 May 10:54:17 - [info] Node.js  version: v16.20.0
28 May 10:54:17 - [info] Linux 6.2.0-20-generic x64 LE
28 May 10:54:17 - [info] Loading palette nodes
28 May 10:54:19 - [info] Settings file  : /data/settings.js
28 May 10:54:19 - [info] Context store  : 'default' [module=memory]
28 May 10:54:19 - [info] User directory : /data
28 May 10:54:19 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 May 10:54:19 - [info] Flows file     : /data/flows_ubuntu.json
28 May 10:54:19 - [info] Server now running at http://127.0.0.1:1880/
28 May 10:54:19 - [info] Starting flows
28 May 10:54:19 - [info] Started flows
./entrypoint.sh: line 14:     7 Segmentation fault      (core dumped) /usr/local/bin/node $NODE_OPTIONS node_modules/node-red/red.js --userDir /data $FLOWS "${@}"
@maxwellhadley
Copy link
Owner

That looks like a segmentation fault coming from NodeJS itself - not seen that before. In theory, that should never happen, no matter how messed up the JavaScript is. I suspect it's something to do with serialport, which node-red-contrib-rfxcom depends on, as I have seen a lot of (different) issues arising with the serialport/Docker combination recently.

It might be worth checking for NodeJS bug reports, too

@vampywiz17
Copy link
Author

vampywiz17 commented May 29, 2023

@maxwellhadley

serial node do similar segmentation fault. It cause a specific version of serial port pre-compiled binary. This commit will try to fix it.

node-red/node-red-nodes#999

node-red/node-red-nodes#894

it help you a bit?

@hardillb
Copy link

hardillb commented Jun 6, 2023

node-serialport v11 should include the fix, you will need to kick/poke upstream dependencies to pick it up

@vampywiz17
Copy link
Author

Hello @maxwellhadley

What do you think, it possible to fix this problem?

@maxwellhadley
Copy link
Owner

Version 2.13.0 now published to npm uses serialport 11.x.x, to retain compatibility with NodeJS v14. This should fix your issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants