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

Deploy Error #24

Closed
GnomiBerlin opened this issue Oct 4, 2018 · 6 comments
Closed

Deploy Error #24

GnomiBerlin opened this issue Oct 4, 2018 · 6 comments
Labels
🐛bug Something isn't working

Comments

@GnomiBerlin
Copy link

Hello, after deploying this error comes from the node:
SyntaxError: Unexpected token in JSON at position 29241

One side effect, which is perhaps not related to this, but since using this node-red-contrib-ccu node the docker is crashing and can not be restarted anymore. I could not see the error, as the terminal window in the Synology Docker environment is too fast away after the crash withing 10 seconds after starting the docker container.

Best Regards,
Joerg

hobbyquaker added a commit that referenced this issue Oct 4, 2018
@hobbyquaker
Copy link
Member

hobbyquaker commented Oct 4, 2018

hopefully the json parse error is fixed with v1.6.11

about the crashes: can't say anything helpful without logs

@hobbyquaker hobbyquaker added the 🐛bug Something isn't working label Oct 4, 2018
@GnomiBerlin
Copy link
Author

I installed v1.6.11 and restarted Node-Red but after deploying now the error comes: SyntaxError: Unexpected token in JSON at position 29266
crashes: you are right. If I have some data, I will add them, but currently I have no usable logs

@hobbyquaker
Copy link
Member

@GnomiBerlin could you retry with the latest version and show me the JSON error message again?

@GnomiBerlin
Copy link
Author

@hobbyquaker I installed 1.6.17 and this is the error output now:
image
hopefully this helps.

hobbyquaker added a commit that referenced this issue Oct 25, 2018
@hobbyquaker
Copy link
Member

Could you please try 1.6.18? This should fix the JSON.parse error.

@GnomiBerlin
Copy link
Author

yes, installed and after deploy the parse error is not seen. This is the current output start...of named data points:
image

more details can be delivered if required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛bug Something isn't working
Development

No branches or pull requests

2 participants