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

uncaught exception... #569

Open
Ilovegym66 opened this issue Feb 16, 2024 · 5 comments
Open

uncaught exception... #569

Ilovegym66 opened this issue Feb 16, 2024 · 5 comments

Comments

@Ilovegym66
Copy link

found this error this morning in the log:

`
2024-02-16 05:01:45.645 - info: tuya.0 (1035) bf3bce1c2235143d3ajws7: Error on Reconnect (1): connection timed out

2024-02-16 05:01:49.344 - info: tuya.0 (1035) bfeeaa29ccb41608a6wp8h: Error on Reconnect (6): connection timed out
2024-02-16 05:01:51.343 - info: tuya.0 (1035) bf51aaad135aa1ced0dhmw: Error on Reconnect (7): connect EHOSTUNREACH 10.1.12.101:6668
2024-02-16 05:01:53.793 - info: tuya.0 (1035) bf51aaad135aa1ced0dhmw: Connect locally to device
2024-02-16 05:01:53.794 - info: tuya.0 (1035) bf51aaad135aa1ced0dhmw Init with IP=10.1.12.101, Key=0e532357ebf0e8a0, Version=3.3
2024-02-16 05:01:54.219 - error: tuya.0 (1035) 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().
2024-02-16 05:01:54.220 - error: tuya.0 (1035) unhandled promise rejection: connection timed out
2024-02-16 05:01:54.223 - error: tuya.0 (1035) Error: connection timed out
at Socket. (/opt/iobroker/node_modules/tuyapi/index.js:599:36)
at Object.onceWrapper (node:events:631:28)
at Socket.emit (node:events:517:28)
at Socket.emit (node:domain:489:12)
at Socket._onTimeout (node:net:598:8)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
2024-02-16 05:01:54.223 - error: tuya.0 (1035) connection timed out
2024-02-16 05:01:54.235 - info: notification-manager.0 (885) New notification on "iobroker" detected
2024-02-16 05:01:54.324 - error: notificationforandroidtv.0 (3439) Notify failed for :10.10.1.56
2024-02-16 05:01:54.349 - warn: tuya.0 (1035) bf51aaad135aa1ced0dhmw: Error on Reconnect (1): connect EHOSTUNREACH 10.1.12.101:6668
2024-02-16 05:01:55.239 - warn: tuya.0 (1035) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-02-16 05:01:55.869 - error: host.iobroker 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:
2024-02-16 05:01:55.870 - error: host.iobroker Caught by controller[1]: Error: connection timed out
2024-02-16 05:01:55.870 - error: host.iobroker Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/tuyapi/index.js:599:36)
2024-02-16 05:01:55.870 - error: host.iobroker Caught by controller[1]: at Object.onceWrapper (node:events:631:28)
2024-02-16 05:01:55.870 - error: host.iobroker Caught by controller[1]: at Socket.emit (node:events:517:28)
2024-02-16 05:01:55.870 - error: host.iobroker Caught by controller[1]: at Socket.emit (node:domain:489:12)
2024-02-16 05:01:55.870 - error: host.iobroker Caught by controller[1]: at Socket._onTimeout (node:net:598:8)
2024-02-16 05:01:55.870 - error: host.iobroker Caught by controller[1]: at listOnTimeout (node:internal/timers:569:17)
2024-02-16 05:01:55.870 - error: host.iobroker Caught by controller[1]: at processTimers (node:internal/timers:512:7)
2024-02-16 05:01:55.870 - error: host.iobroker instance system.adapter.tuya.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-02-16 05:01:55.870 - info: host.iobroker Restart adapter system.adapter.tuya.0 because enabled

`
System:
CPU: 0,2 %
RAM: 21 %
Betriebszeit: 23h
Verfügbar: 5.0.19
Installiert: 5.0.19
Ereignisse: ⇥68 / ↦13
Plattform: docker (official image - v9.0.1)
Betriebssystem: linux
Architektur: x64
CPUs: 8
Geschwindigkeit: 2201 MHz
Modell: Intel(R) Xeon(R) CPU D-1527 @ 2.20GHz
RAM: 62.5 GB
System-Betriebszeit: 33 T. 18:26:50
Node.js: v18.19.1
time: 1708063427260
timeOffset: -60
NPM: 10.2.4
Adapter-Anzahl: 621
Datenträgergröße: 14289.2 GB
Freier Festplattenspeicher: 3425.0 GB
Aktive Instanzen: 64
Pfad: /opt/iobroker/
Betriebszeit: 23:15:05
aktiv: true
_npmNewest: 10.2.4
_nodeNewestNext: 18.19.1
_nodeCurrent: 18.19.1
_npmCurrent: 10.2.4
_npmNewestNext: 10.2.4
_nodeNewest: 18.19.1

@Apollon77
Copy link
Owner

Adapterversion?

@Ilovegym66
Copy link
Author

Sorry, forgot it: 3.15.0

@Apollon77
Copy link
Owner

Ok ... need to check in the underlaying library ...

How often does that happen?

@Ilovegym66
Copy link
Author

Ca. Once a week

@Ilovegym66
Copy link
Author

sometimes every two days. .. very irregular and I don't see any impact from another device or network.. hmpff..

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

2 participants