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

Adapter keeps in state green by failure until restart #237

Closed
hkcrainer opened this issue Oct 13, 2023 · 4 comments
Closed

Adapter keeps in state green by failure until restart #237

hkcrainer opened this issue Oct 13, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@hkcrainer
Copy link

Today the Server of Discovergy is broken down.
Discovergy Adapter kept green until reboot, but spams every second in Log.

Adapter Version: 0.5.8
Node.js: 18.17.1
NPM: 9.6.7

Best regards

hkc_rainer

@hkcrainer hkcrainer added the bug Something isn't working label Oct 13, 2023
@Claus1985
Copy link

got the same error

@firebowl
Copy link

Adapter keeps crashing:

discovergy.0 2023-10-17 13:32:25.766 error Unexpected end of JSON input
discovergy.0 2023-10-17 13:32:25.765 error SyntaxError: Unexpected end of JSON input at JSON.parse () at Request._rp_callbackOrig (/opt/iobroker/node_modules/iobroker.discovergy/main.js:154:24) at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:76:39) at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31) at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (node:events:517:28) at Request.emit (node:domain:489:12) at Request. (/opt/iobroker/node_modules/request/request.js:1154:10) at Request.emit (node:events:517:28) at Request.emit (node:domain:489:12)
discovergy.0 2023-10-17 13:32:25.765 error unhandled promise rejection: Unexpected end of JSON input
discovergy.0 2023-10-17 13:32:25.764 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

@DutchmanNL
Copy link
Collaborator

Adapter keeps crashing:

hmm that should not happen as the code is covered in an catch/try blog but log indeed indicate an complete code crash.
Is the adapter restarting after this error or processing other data ?

@DutchmanNL
Copy link
Collaborator

@Claus1985 if the error occurs again, please set adapter log level to debug I added a log line to show API response

dd26794#diff-58417e0f781b6656949d37258c8b9052ed266e2eb7a5163cad7b0863e6b2916aR156

DutchmanNL pushed a commit that referenced this issue Oct 27, 2023
* (DutchmanNL) Error handling improved in cases data processing fails
* (DutchmanNL) Git issues #200 #219 #220 #229 #235 #237 #238 #506 #507 solved
DutchmanNL pushed a commit that referenced this issue Oct 27, 2023
* (DutchmanNL) Error handling improved in cases data processing fails
* (DutchmanNL) Git issues #200 #219 #220 #229 #235 #237 #238 #506 #507 solved
DutchmanNL pushed a commit that referenced this issue Oct 27, 2023
* (DutchmanNL) Error handling improved in cases data processing fails
* (DutchmanNL) Fixes #214 #215 #200 #219 #220 #224 #229 #235 #236 #237 #238 #506 #507
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants