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

Get hundreds of error messges filling the syslog. What should I do? #19

Open
mrohner opened this issue Sep 1, 2017 · 2 comments
Open

Comments

@mrohner
Copy link

mrohner commented Sep 1, 2017

Error appeared when coding first blynk write note. I obviously did a mistake defining the websocket in the node as it cannot get connected.
The error close messages repeat 16 times per second filling the syslog and making node-red loosing connection too.

31 Aug 11:39:24 - [info] Node-RED version: v0.17.2
31 Aug 11:39:24 - [info] Node.js version: v6.11.2
31 Aug 11:39:24 - [info] Linux 3.4.113-sun8i arm LE
31 Aug 11:39:26 - [info] Loading palette nodes
31 Aug 11:39:38 - [info] Dashboard up and running
31 Aug 11:39:43 - [info] Dashboard version 2.4.1 started at /ui
31 Aug 11:39:45 - [warn] ------------------------------------------------------
31 Aug 11:39:45 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
31 Aug 11:39:45 - [warn] ------------------------------------------------------
31 Aug 11:39:45 - [info] Settings file : /home/pi/.node-red/settings.js
31 Aug 11:39:45 - [info] User directory : /home/pi/.node-red
31 Aug 11:39:45 - [info] Flows file : /home/pi/.node-red/flows_mosquitto.json
31 Aug 11:39:46 - [info] Server now running at http://127.0.0.1:1880/
31 Aug 11:39:46 - [info] Starting flows
31 Aug 11:39:49 - [info] Started flows
error
close
31 Aug 11:39:49 - [info] [mqtt-broker:8e79b041.968cc] Connected to broker: mqtt://192.168.178.59:8 883
error
close
error
close
error
close
error
close
error
close
error
close
error
close
error
close
error
close
error
close
error
close
error
close
error
close
error
close

@tzapu
Copy link
Owner

tzapu commented Sep 1, 2017 via email

@jmikerq
Copy link

jmikerq commented Nov 20, 2017

@mrohner I am trying to fix this issue, but I cannot seem to reproduce this error consistently. Can you show me your setup when you see this error?

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