NEWS
Emby 1.0.0, startet immer wieder neu...
-
Mangels Umgebung kann ich hier nicht direkt eine Lösung anbieten.
ABER falls ein Entwickler eine Lösung findet und einen PR erstellen kann / will, dann kann ich (nach Rücksprache mit em derzeitigen Maintainer) den Adapter in den Community Bereich transferieren und allfälle Fixes mergen / releasen.
Bitte in diesem Fall mich (ggF auch mehrfach) anpingen.
-
Ich hab mir den Crash lt. Log oen angesehen. Der scheint durch leere Daten ausgelöst zu werden.
Wenn jemand mag, dann kann er eine GITHIUB Version von meinem Fork testen. Ich habe mal blind (d.h. ohne irgendwelche Testmöglichkeit) versucht den Crash zu vermeiden.
Aber wie immer:
Das ist eine ungetestete github version. 'Use at own risk'. One weitere (positive) Rückmeldungen rate ich von einer Installation auf produktiven System eexplizit ab!Technisch ignoriere ich die Antwort ohne Datenteil die anscheinend den Crash auslöst. Ich kann nicht beurteilen, ob damit das Problem gelöst ist oder andere Folgefehler auftreten.
Also wer noch immer mutig ist
https://github.com/mcm1957/ioBroker.emby
P.S: Versionsnummer ist unverändert da keine Release bisher erstellt.
-
@mcm57 hab emby auf meinem testserver neu installiert über github.
da scheint noch was im argen zu sein ...host.iobroker-test 2023-11-15 20:04:40.322 error instance system.adapter.emby.0 terminated with code 6 (UNCAUGHT_EXCEPTION) emby.0 2023-11-15 20:04:39.673 error undefined is not a valid state value emby.0 2023-11-15 20:04:39.673 error Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5448:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5409:21) at W3CWebSocket.webMessage [as onmessage] (/opt/iobroker/node_modules/iobroker.emby/main.js:357:25) at W3CWebSocket._dispatchEvent [as dispatchEvent] (/opt/iobroker/node_modules/yaeti/lib/EventTarget.js:107:17) at W3CWebSocket.onMessage (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:234:14) at WebSocketConnection.<anonymous> (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:205:19) at WebSocketConnection.emit (node:events:517:28) at WebSocketConnection.processFrame (/opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:554:26) at /opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:323:40 emby.0 2023-11-15 20:04:39.672 error unhandled promise rejection: undefined is not a valid state value emby.0 2023-11-15 20:04:39.671 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(). emby.0 2023-11-15 20:04:39.670 error undefined is not a valid state value emby.0 2023-11-15 20:04:39.669 error Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5448:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5409:21) at W3CWebSocket.webMessage [as onmessage] (/opt/iobroker/node_modules/iobroker.emby/main.js:357:25) at W3CWebSocket._dispatchEvent [as dispatchEvent] (/opt/iobroker/node_modules/yaeti/lib/EventTarget.js:107:17) at W3CWebSocket.onMessage (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:234:14) at WebSocketConnection.<anonymous> (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:205:19) at WebSocketConnection.emit (node:events:517:28) at WebSocketConnection.processFrame (/opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:554:26) at /opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:323:40 emby.0 2023-11-15 20:04:39.668 error unhandled promise rejection: undefined is not a valid state value emby.0 2023-11-15 20:04:39.668 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(). emby.0 2023-11-15 20:04:39.667 error undefined is not a valid state value emby.0 2023-11-15 20:04:39.667 error Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5448:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5409:21) at W3CWebSocket.webMessage [as onmessage] (/opt/iobroker/node_modules/iobroker.emby/main.js:357:25) at W3CWebSocket._dispatchEvent [as dispatchEvent] (/opt/iobroker/node_modules/yaeti/lib/EventTarget.js:107:17) at W3CWebSocket.onMessage (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:234:14) at WebSocketConnection.<anonymous> (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:205:19) at WebSocketConnection.emit (node:events:517:28) at WebSocketConnection.processFrame (/opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:554:26) at /opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:323:40 emby.0 2023-11-15 20:04:39.663 error unhandled promise rejection: undefined is not a valid state value emby.0 2023-11-15 20:04:39.663 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(). emby.0 2023-11-15 20:04:08.896 error WebSocket Error. Try Reconnect in 60s emby.0 2023-11-15 20:03:05.827 error WebSocket Error. Try Reconnect in 60s
-
@madison
OK, sorry - muss mir das dann noch mal ansehen. Ist eine andere Stelle als in https://forum.iobroker.net/topic/29700/emby-1-0-0-startet-immer-wieder-neu/32Wenn ich dazu gekommen bin, meld ich mich.
Ansonsten kann ich nur sorry sagen und Hilfe beim Release Anbieten wenn wer den Code fixen kann / will.P.S: Bitte das Log jedenfalls an Issue beim Adapter anhängen wenn noch nicht geschehen
-
@mcm57 kein Problem.
wenn ich was testen soll einfach Bescheid geben.
sonst kann ich leider nicht viel beitragen. -
Der Entwickler hat nachdem ich ein Debug Log geschickt habe, einen ungetesteten Fix bereitgestellt: https://github.com/thewhobox/ioBroker.emby
-
@apachelance habs getestet.
host.iobroker-test 2023-11-17 18:20:17.762 error instance system.adapter.emby.0 terminated with code 6 (UNCAUGHT_EXCEPTION) emby.0 2023-11-17 18:20:17.135 error undefined is not a valid state value emby.0 2023-11-17 18:20:17.134 error Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5448:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5409:21) at W3CWebSocket.webMessage [as onmessage] (/opt/iobroker/node_modules/iobroker.emby/main.js:376:25) at W3CWebSocket._dispatchEvent [as dispatchEvent] (/opt/iobroker/node_modules/yaeti/lib/EventTarget.js:107:17) at W3CWebSocket.onMessage (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:234:14) at WebSocketConnection.<anonymous> (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:205:19) at WebSocketConnection.emit (node:events:517:28) at WebSocketConnection.processFrame (/opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:554:26) at /opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:323:40 emby.0 2023-11-17 18:20:17.134 error unhandled promise rejection: undefined is not a valid state value emby.0 2023-11-17 18:20:17.134 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(). emby.0 2023-11-17 18:20:17.133 error undefined is not a valid state value emby.0 2023-11-17 18:20:17.133 error Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5448:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5409:21) at W3CWebSocket.webMessage [as onmessage] (/opt/iobroker/node_modules/iobroker.emby/main.js:375:25) at W3CWebSocket._dispatchEvent [as dispatchEvent] (/opt/iobroker/node_modules/yaeti/lib/EventTarget.js:107:17) at W3CWebSocket.onMessage (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:234:14) at WebSocketConnection.<anonymous> (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:205:19) at WebSocketConnection.emit (node:events:517:28) at WebSocketConnection.processFrame (/opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:554:26) at /opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:323:40 emby.0 2023-11-17 18:20:17.133 error unhandled promise rejection: undefined is not a valid state value emby.0 2023-11-17 18:20:17.132 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(). emby.0 2023-11-17 18:20:17.131 error undefined is not a valid state value emby.0 2023-11-17 18:20:17.131 error Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5448:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5409:21) at W3CWebSocket.webMessage [as onmessage] (/opt/iobroker/node_modules/iobroker.emby/main.js:372:25) at W3CWebSocket._dispatchEvent [as dispatchEvent] (/opt/iobroker/node_modules/yaeti/lib/EventTarget.js:107:17) at W3CWebSocket.onMessage (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:234:14) at WebSocketConnection.<anonymous> (/opt/iobroker/node_modules/websocket/lib/W3CWebSocket.js:205:19) at WebSocketConnection.emit (node:events:517:28) at WebSocketConnection.processFrame (/opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:554:26) at /opt/iobroker/node_modules/websocket/lib/WebSocketConnection.js:323:40 emby.0 2023-11-17 18:20:17.128 error unhandled promise rejection: undefined is not a valid state value emby.0 2023-11-17 18:20:17.128 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().
-
@madison Sicher, dass du die aktuelle Version hast. Bei mir gibts die Abstürze nicht mehr. Nur noch:
emby.0 2023-11-17 18:25:54.975 warn State "emby.0.b9780d9d3b7bde77c4302e70f3cfe10c.info.userName" has no existing object, this might lead to an error in future versions emby.0 2023-11-17 18:25:54.974 warn State "emby.0.b9780d9d3b7bde77c4302e70f3cfe10c.info.deviceName" has no existing object, this might lead to an error in future versions emby.0 2023-11-17 18:25:54.917 warn This object will not be created in future versions. Please report this to the developer. emby.0 2023-11-17 18:25:54.917 warn Object emby.0.0625f91c9e5aa817d97f3c2df711452c.command.togglemute is invalid: obj.common.type has an invalid value (button) but has to be one of number, string, boolean, array, object, mixed, file, json emby.0 2023-11-17 18:25:54.917 warn This object will not be created in future versions. Please report this to the developer. emby.0 2023-11-17 18:25:54.916 warn Object emby.0.0625f91c9e5aa817d97f3c2df711452c.command.mute is invalid: obj.common.type has an invalid value (button) but has to be one of number, string, boolean, array, object, mixed, file, json
-
@apachelance hab jetzt den Adapter neu installiert, jetzt hab ich die selben Warnings wie du!
-
@madison sagte in Emby 1.0.0, startet immer wieder neu...:
@apachelance hab jetzt den Adapter neu installiert, jetzt hab ich die selben Warnings wie du!
Scheint trotzdem nicht stabil zu sein. Hatte gerade einen Crash:
host.ioBroker 2023-11-17 19:38:50.979 warn Do not restart adapter system.adapter.emby.0 because restart loop detected host.ioBroker 2023-11-17 19:38:50.978 info Restart adapter system.adapter.emby.0 because enabled host.ioBroker 2023-11-17 19:38:50.978 error instance system.adapter.emby.0 terminated with code 6 (UNCAUGHT_EXCEPTION) emby.0 2023-11-17 19:38:50.942 warn get state error: Connection is closed. emby.0 2023-11-17 19:38:50.935 info terminating emby.0 2023-11-17 19:38:50.433 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
-
Ich habe auf Guithub ein Issue erstellt mit der Bitte an den Dev eine neue saubere Release zu erstellen:
https://github.com/thewhobox/ioBroker.emby/issues/24
Derzeit passen die versionsangaben absolut nicht zusammen:
- package.json states 1.0.5
- io-package.json states 1.0.3
- npm lists 1.02
Weiters sollten die Abhängigkeiten aktualisisert werden. Der Adapter verwendet adapter-sore 1.x.x - aktuell ist 3.0.3. Das wird sicher in Zukunft auch zu Problemen führen.
Falls Maintzainer hier mitliest - bitte im Bedarfsfall nachfragen. Ich und andere helfen gern wenn was unkalr ist.
mcm1957
-
@mcm57 Danke.
Hatte ich auch schon: https://github.com/thewhobox/ioBroker.emby/issues/23
Wurde vom Entwickler jedoch heute geschlossen.
-
@apachelance bisher noch kein Absturz bei mir
-
@apachelance
Bei deinem Issue gings um den Crash. Das hat ja zuerst gut ausgesehen.Mein Issue bezieht sich primär mal auf den Releaseablauf. Da der Adapter in latest und stable repository gelistet ist, sollten neue Versionen auch sauber veröffentlicht werden. Würde ungern einen Adapter wegen organisatorischer Abläufe rausnehmen. Daher main Angebot an den Entwickler hier gerne zu helfen, ggF auch mit PR(s).
-
Ich habe den Adapter ioBroker.emby nun in den iobroker-community-adapters Bereich verschoben, die notwendigen Anpassungen vorgenommen und eine neue Release gebaut.
Ab morgen steht 1.1.1 im Latest zur Verfügung.Zum Tester Thread gehts da:
https://forum.iobroker.net/topic/70397/test-adapter-emby-moved-to-community-adaptersDANKE an @thewhobox für seine Fehlerbehebungen und die Freigabe des Adapters sowie das Angebot auch weiterhin bei der Wartung aktiv zu sein soweit es ohne passende Hardwar möglich ist.