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 crashes after update to 1.13.0 #120

Closed
peer69 opened this issue May 18, 2020 · 18 comments
Closed

Adapter crashes after update to 1.13.0 #120

peer69 opened this issue May 18, 2020 · 18 comments

Comments

@peer69
Copy link

peer69 commented May 18, 2020

After upgrading to 1.13.0 my adapter crashed on startup, going back to 1.12.5 fixes the error:

sql.0 | 2020-05-18 17:29:22.910 | error | (3871) adapter disabled

sql.0 | 2020-05-18 17:28:51.628 | info | (3123) Terminated (NO_ERROR): Without reason

sql.0 | 2020-05-18 17:28:51.628 | info | (3123) terminating

sql.0 | 2020-05-18 17:28:51.123 | error | at processTicksAndRejections (internal/process/task_queues.js:97:5)

sql.0 | 2020-05-18 17:28:51.123 | error | at _0x30230c._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115328)

sql.0 | 2020-05-18 17:28:51.123 | error | at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1482:21

sql.0 | 2020-05-18 17:28:51.123 | error | at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:7066:26

sql.0 | 2020-05-18 17:28:51.123 | error | at Array.map (<anonymous>)

sql.0 | 2020-05-18 17:28:51.123 | error | at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:7066:39

sql.0 | 2020-05-18 17:28:51.123 | error | (3123) TypeError: Cannot read property 'startsWith' of undefined

sql.0 | 2020-05-18 17:28:51.118 | error | (3123) unhandled promise rejection: Cannot read property 'startsWith' of undefined

sql.0 | 2020-05-18 17:28:51.048 | info | (3123) enabled logging of zwave.0.NODE6.METER.Electric_-_W_1, Alias=false, 16 points now activated
@Apollon77
Copy link
Contributor

which js-controller version?

@peer69
Copy link
Author

peer69 commented May 18, 2020

3.1.4

@Apollon77
Copy link
Contributor

interesting ...
@ioBroker/developers

reason is a subscribeForeignState with an array where one element is undefined

@Apollon77
Copy link
Contributor

@Apollon77
Copy link
Contributor

PS: was also buggy before because on undefined entries it simply subscribed * ... but now we throw an error

@Superwuzy
Copy link

I've experienced the same problem since updated to 1.13.0 (js-controller 3.1.4).

@LJSven
Copy link

LJSven commented May 18, 2020

Same here

@kugelkopf123
Copy link

Same here!
Always restarting...

2020-05-18 21:55:24.988  - �[31merror�[39m: sql.0 (32736) Error: ER_CON_COUNT_ERROR: Too many connections
2020-05-18 21:55:24.994  - �[31merror�[39m: sql.0 (32736) Error: ER_CON_COUNT_ERROR: Too many connections
2020-05-18 21:55:25.000  - �[31merror�[39m: sql.0 (32736) Error: ER_CON_COUNT_ERROR: Too many connections
2020-05-18 21:55:25.014  - �[31merror�[39m: sql.0 (32736) Error: ER_CON_COUNT_ERROR: Too many connections
2020-05-18 21:55:25.133  - �[33mwarn�[39m: sql.0 (32736) Terminated (UNCAUGHT_EXCEPTION): Without reason
2020-05-18 21:55:25.541  - �[32minfo�[39m: sql.0 (32736) terminating
2020-05-18 21:55:25.545  - �[32minfo�[39m: sql.0 (32736) terminating with timeout
2020-05-18 21:55:25.618  - �[31merror�[39m: sql.0 (32736) Error: ER_CON_COUNT_ERROR: Too many connections
2020-05-18 21:55:27.706  - �[31merror�[39m: host.raspi4 Caught by controller[0]: 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(). The promise rejected with the reason:
2020-05-18 21:55:27.709  - �[31merror�[39m: host.raspi4 Caught by controller[1]: TypeError: Cannot read property 'startsWith' of undefined
2020-05-18 21:55:27.710  - �[31merror�[39m: host.raspi4 Caught by controller[1]:     at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:7066:39
2020-05-18 21:55:27.711  - �[31merror�[39m: host.raspi4 Caught by controller[1]:     at Array.map (<anonymous>)
2020-05-18 21:55:27.711  - �[31merror�[39m: host.raspi4 Caught by controller[1]:     at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:7066:26
2020-05-18 21:55:27.712  - �[31merror�[39m: host.raspi4 Caught by controller[1]:     at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1482:21
2020-05-18 21:55:27.713  - �[31merror�[39m: host.raspi4 Caught by controller[1]:     at _0x30230c._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115328)
2020-05-18 21:55:27.714  - �[31merror�[39m: host.raspi4 Caught by controller[1]:     at runMicrotasks (<anonymous>)
2020-05-18 21:55:27.716  - �[31merror�[39m: host.raspi4 Caught by controller[1]:     at processTicksAndRejections (internal/process/task_queues.js:97:5)
2020-05-18 21:55:27.720  - �[31merror�[39m: host.raspi4 instance system.adapter.sql.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2020-05-18 21:55:27.721  - �[32minfo�[39m: host.raspi4 Restart adapter system.adapter.sql.0 because enabled

JS Controller 3.1.4
nodejs: 12.16.3
npm: 6.14.4

@sbormann
Copy link

+1

1 similar comment
@Xsev1
Copy link

Xsev1 commented May 18, 2020

+1

@Apollon77
Copy link
Contributor

Please go back to latest 1.12.x till fix is done hopefully later today

@m-s-b
Copy link

m-s-b commented May 19, 2020

Got the same error after installing 1.13.0. After downgrade to 1.12.5:
sql.0 2020-05-19 07:34:49.602 info (4756) No Data sql.0 2020-05-19 07:34:24.964 error (4756) Error: Packets out of order. Got: 1 Expected: 0
Actually I´m not able to connect to SQL database.
Edit:
After downgrade @1.9.4 and upgrade @1.12.5 SQL is connected.

@jens-maus
Copy link

same problem here with 1.13.0. After downgrade to 1.12.5 everything works again.

@Apollon77
Copy link
Contributor

on my list for today

@Apollon77
Copy link
Contributor

please check 1.13.1!!

@m-s-b
Copy link

m-s-b commented May 20, 2020

Adapter ist grün und Daten werden auch gespeichert.
Allerdings wie in issue #122 Warnungen "no Real ID" für diverse Datenpunkte von linkeddevices und sourceanalytics.
Zusätzlich nach jedem Adapterstart ~ 20 mal die Warnung "No connection to database" obwohl der Test in der Adapterkonfiguration funktioniert.

@Apollon77
Copy link
Contributor

Bitte auch hier wie in #122 abgefragt mal schauen was exakt das für states sind die er da anmeckert ... alle Details helfen weil wir es bisher nicht nachstellen können. Wir haben de crash grund jetzt verhindert - aber verstehen Ihn noch nicht.

"No connection to database" ... Logs? Am besten mal debug log bitte aber in ein eigenes issue

@Apollon77
Copy link
Contributor

weiter in #122

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

9 participants