Nodered is abruptly terminate while connecting with cratedb and fetching data from it

Hi all,
i am trying to connect nodered with cratedb node and fetching data from it.
But nodered is abruptly terminated.
Below is the logs:
2 Feb 17:04:00 - [red] Uncaught Exception:
2 Feb 17:04:00 - Error: connect EINVAL - Local (
at internalConnect (net.js:882:16)
at defaultTriggerAsyncIdScope (internal/async_hooks.js:294:19)
at GetAddrInfoReqWrap.emitLookup [as callback] (net.js:1029:9)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)
npm ERR! errno 1
npm ERR! node-red@1.0.3 start: node packages/node_modules/node-red/red.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red@1.0.3 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-02-02T11_34_00_544Z-debug.log.

Below is the nodered flow

[{"id":"4f0c52d3.bb3f0c","type":"tab","label":"Flow 8","disabled":false,"info":""},{"id":"4c75de04.47a5c","type":"crate in","z":"4f0c52d3.bb3f0c","name":"crate","database":"43d9b0e8.ac4ef","x":260,"y":160,"wires":[["6c9c35de.5141ac"]]},{"id":"c3fe9791.a3ea68","type":"inject","z":"4f0c52d3.bb3f0c","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":true,"onceDelay":0.1,"x":90,"y":80,"wires":[["dbfcc7c.01b0738"]]},{"id":"6c9c35de.5141ac","type":"debug","z":"4f0c52d3.bb3f0c","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":560,"y":220,"wires":[]},{"id":"dbfcc7c.01b0738","type":"function","z":"4f0c52d3.bb3f0c","name":"","func":"msg.query=\"SELECT * FROM doc.etairqualityobserved LIMIT 100 where text like ?;\"\nmsg.args=['%moderate%']\nreturn msg;","outputs":1,"noerr":0,"x":450,"y":60,"wires":[["4c75de04.47a5c"]]},{"id":"43d9b0e8.ac4ef","type":"crate","z":"","url":"","name":"etairqualityobserved"}]

port 4200 looks like cratedb. As it's an async error we can't do anything sensibly apart from exit cleanly. That node need to handle that error - so best to contact the author and ask for help (if the issue has not already been raised)

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