8 Feb 18:35:55 - [info] Welcome to Node-RED =================== 8 Feb 18:35:55 - [info] Node-RED version: v0.19.4 8 Feb 18:35:55 - [info] Node.js version: v8.9.4 8 Feb 18:35:55 - [info] Windows_NT 10.0.17134 x64 LE 8 Feb 18:35:56 - [info] Loading palette nodes 8 Feb 18:35:57 - [debug] Module: node-red-contrib-timed-counter 0.0.1 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-timed-counter 8 Feb 18:35:57 - [debug] Module: node-red-contrib-credentials 0.2.1 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-credentials 8 Feb 18:35:57 - [debug] Module: node-red-contrib-mssql 0.0.7 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-mssql 8 Feb 18:35:57 - [debug] Module: node-red-contrib-multipart-stream-decoder 0.0.3 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-multipart-stream-decoder 8 Feb 18:35:57 - [debug] Module: node-red-contrib-nora 0.0.17 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-nora 8 Feb 18:35:57 - [debug] Module: node-red-contrib-norelite 2.6.1 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-norelite 8 Feb 18:35:57 - [debug] Module: node-red-contrib-os 0.1.7 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-os 8 Feb 18:35:57 - [debug] Module: node-red-contrib-soap-filesupport 0.1.2 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-soap-filesupport 8 Feb 18:35:57 - [debug] Module: node-red-contrib-mqtt-broker 0.2.4 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-mqtt-broker 8 Feb 18:35:57 - [debug] Module: node-red-contrib-web-worldmap 1.5.21 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-contrib-web-worldmap 8 Feb 18:35:57 - [debug] Module: node-red-dashboard 2.13.2 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-dashboard 8 Feb 18:35:57 - [debug] Module: node-red-node-base64 0.1.3 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-node-base64 8 Feb 18:35:57 - [debug] Module: node-red-node-email 1.0.7 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-node-email 8 Feb 18:35:57 - [debug] Module: node-red-node-twitter 1.1.4 8 Feb 18:35:57 - [debug] \Users\Demo\.node-red\node_modules\node-red-node-twitter 8 Feb 18:35:57 - [debug] Module: node-red-node-feedparser 0.1.14 8 Feb 18:35:57 - [debug] C:\Users\Demo\AppData\Roaming\npm\node_modules\node-red\node_modules\node-red-node-feedparser 8 Feb 18:35:57 - [debug] Module: node-red-node-rbe 0.2.3 8 Feb 18:35:57 - [debug] C:\Users\Demo\AppData\Roaming\npm\node_modules\node-red\node_modules\node-red-node-rbe 8 Feb 18:35:57 - [debug] Module: node-red-node-twitter 1.1.3 *ignored due to local copy* 8 Feb 18:35:57 - [debug] C:\Users\Demo\AppData\Roaming\npm\node_modules\node-red\node_modules\node-red-node-twitter 8 Feb 18:35:57 - [warn] rpi-gpio : Raspberry Pi specific node set inactive 8 Feb 18:35:58 - [info] Worldmap version 1.5.21 8 Feb 18:35:58 - [info] Dashboard version 2.13.2 started at /ui 8 Feb 18:35:59 - [warn] ------------------------------------------------------ 8 Feb 18:35:59 - [warn] [node-red/tail] Not currently supported on Windows. 8 Feb 18:35:59 - [warn] ------------------------------------------------------ 8 Feb 18:35:59 - [info] Settings file : \Users\Demo\.node-red\settings.js 8 Feb 18:35:59 - [info] HTTP Static : C:\Users\Demo\.node-red\static 8 Feb 18:35:59 - [info] Context store : 'default' [module=memory] 8 Feb 18:35:59 - [info] User directory : \Users\Demo\.node-red 8 Feb 18:35:59 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable 8 Feb 18:35:59 - [info] Flows file : \Users\Demo\.node-red\flows_JMT-Node-RED.json 8 Feb 18:35:59 - [info] Server now running at http://127.0.0.1:1880/ 8 Feb 18:35:59 - [debug] loaded flow revision: 0b8858fcbc22e731049eec3fcdea0b54 8 Feb 18:35:59 - [debug] red/runtime/nodes/credentials.load : no user key present 8 Feb 18:35:59 - [debug] red/runtime/nodes/credentials.load : using default key 8 Feb 18:35:59 - [debug] red/runtime/nodes/credentials.load : keyType=system 8 Feb 18:35:59 - [warn] --------------------------------------------------------------------- Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials file will not be recoverable, you will have to delete it and re-enter your credentials. You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change. --------------------------------------------------------------------- 8 Feb 18:35:59 - [trace] runtime event: {"id":"runtime-state","retain":true} 8 Feb 18:35:59 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"0b8858fcbc22e731049eec3fcdea0b54"},"retain":true} 8 Feb 18:35:59 - [info] Starting flows 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : global 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : 9fa0534b.ecb568 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : ca18d17c.b1d018 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : 2b8ed3ea.d539ac 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : bf9508b3.bf87a8 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : 760c2358.b1be0c 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : 2ab8a64.df6a25a 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : 7c8b0597.511384 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : f3213584.06ef78 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : e43b4c87.0a32d 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : 3cf6e240.060fae 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : c2fc9c80.1e55 8 Feb 18:35:59 - [debug] red/nodes/flows.start : starting flow : 2cff21f2.29af7e 8 Feb 18:35:59 - [error] [twitter in:e1a0493f.dfe9] missing twitter credentials 8 Feb 18:35:59 - [info] [mosca in:9013b902.1e6eb8] Binding mosca mqtt server on port: 1883 8 Feb 18:35:59 - [info] [tcp out:d003c65e.82583] connecting to jmt-xpco:9090 8 Feb 18:35:59 - [info] [tcp out:3244fabe.a590ce] connecting to jmt-xpco:9090 8 Feb 18:35:59 - [info] [tcp out:XProtect Corporate Event Server] connecting to jmt-xpco:9090 8 Feb 18:35:59 - [info] [worldmap:fe7bb0e0.bed5c] started at /worldmap 8 Feb 18:35:59 - [info] [tcp out:a800ce7a.0fd9b] connecting to 192.168.97.247:1234 8 Feb 18:35:59 - [info] [tcp out:46936cb9.a68544] connecting to 192.168.97.247:1234 8 Feb 18:35:59 - [info] [tcp out:2b427efc.37cfa2] connecting to 192.168.97.247:1234 8 Feb 18:35:59 - [trace] runtime event: {"id":"runtime-state","retain":true} 8 Feb 18:35:59 - [info] Started flows 8 Feb 18:35:59 - [info] [tcp out:c090d056.0ce428] listening on port 8001 8 Feb 18:35:59 - [error] [tcp out:331124b8.1cebd4] unable to listen on port 8001, error: Error: listen EADDRINUSE :::8001 8 Feb 18:35:59 - [info] [tcp in:221dab6b.9d6bf4] listening on port 1234 8 Feb 18:35:59 - [info] [tcp in:c919aa48.9d7868] listening on port 22335 8 Feb 18:35:59 - [info] [tcp in:1521c40.1218e3c] listening on port 22336 8 Feb 18:35:59 - [info] [tcp in:f890f482.793428] listening on port 22337 8 Feb 18:35:59 - [info] [tcp out:a800ce7a.0fd9b] connected to 192.168.97.247:1234 8 Feb 18:35:59 - [info] [tcp out:46936cb9.a68544] connected to 192.168.97.247:1234 8 Feb 18:35:59 - [info] [tcp out:2b427efc.37cfa2] connected to 192.168.97.247:1234 8 Feb 18:35:59 - [info] [tcp out:3244fabe.a590ce] connected to jmt-xpco:9090 8 Feb 18:35:59 - [info] [tcp out:d003c65e.82583] connected to jmt-xpco:9090 8 Feb 18:35:59 - [info] [tcp out:XProtect Corporate Event Server] connected to jmt-xpco:9090 8 Feb 18:35:59 - [info] [mqtt-broker:cf06dcbf.be106] Connected to broker: mqtt://localhost:1883 8 Feb 18:36:07 - [info] [tcp out:3244fabe.a590ce] connection lost to jmt-xpco:9090 8 Feb 18:36:07 - [info] [tcp out:d003c65e.82583] connection lost to jmt-xpco:9090 8 Feb 18:36:07 - [info] [tcp out:XProtect Corporate Event Server] connection lost to jmt-xpco:9090 8 Feb 18:36:17 - [info] [tcp out:3244fabe.a590ce] connecting to jmt-xpco:9090 8 Feb 18:36:17 - [info] [tcp out:d003c65e.82583] connecting to jmt-xpco:9090 8 Feb 18:36:17 - [info] [tcp out:d003c65e.82583] connected to jmt-xpco:9090 8 Feb 18:36:17 - [info] [tcp out:3244fabe.a590ce] connected to jmt-xpco:9090 8 Feb 18:36:17 - [info] [tcp out:XProtect Corporate Event Server] connecting to jmt-xpco:9090 8 Feb 18:36:17 - [info] [tcp out:XProtect Corporate Event Server] connected to jmt-xpco:9090 8 Feb 18:36:25 - [info] [tcp out:d003c65e.82583] connection lost to jmt-xpco:9090 8 Feb 18:36:25 - [info] [tcp out:3244fabe.a590ce] connection lost to jmt-xpco:9090 8 Feb 18:36:25 - [info] [tcp out:XProtect Corporate Event Server] connection lost to jmt-xpco:9090