Neues YouTube-Video: Visualisierung im Devices-Adapter

[Happyuser20]

Hallo zusammen

Mein Iobroker im Synology docker will nach einem abgebrochenen Update des Js Controllers von 7.2.1 auf 7.2.2.nicht mehr starten.

Uncaught Rejection: Error: Could not determine controller directory

    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1854:11)

    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1327:37)

    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3324:30)

    at runNextTicks (node:internal/process/task_queues:64:5)

    at processImmediate (node:internal/timers:452:9)

Could not determine controller directory

Error: Could not determine controller directory

    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1854:11)

    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1327:37)

    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3324:30)

    at runNextTicks (node:internal/process/task_queues:64:5)

    at processImmediate (node:internal/timers:452:9)

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:

Error: Could not determine controller directory

    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1854:11)

    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1327:37)

    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3324:30)

    at runNextTicks (node:internal/process/task_queues:64:5)

    at processImmediate (node:internal/timers:452:9)

wie kann ich das reparieren?

Gruß
HappyUser20

[Ro75]

@Happyuser20 sagte:

Update des Js Controllers von 7.21 auf 7.22.

wo holst du diese Version her? Aktuell ist 7.1.2. Bist du BETA-Tester?

Ro75.

[skvarel]

@Ro75 .. die 7.2.2 ist Stable

EDIT:
Helfen kann ich aber leider nicht. Hier läuft es mir der Version einwandfrei

[Happyuser20]

@skvarel sagte:

@Ro75 .. die 7.2.2 ist Stable

EDIT:
Helfen kann ich aber leider nicht. Hier läuft es mir der Version einwandfrei

Die wars.

[skvarel]

@Happyuser20 .. den Punkt bei der Version falsch gesetzt. Bitte berichtigen.

Die Versionen lauten:
7.2.1 und 7.2.2

Das verwirrt sonst nur.

[mcm1957]

@Happyuser20 sagte:

Hallo zusammen

Mein Iobroker im Synology docker will nach einem abgebrochenen Update des Js Controllers von 7.2.1 auf 7.2.2.nicht mehr starten.

Uncaught Rejection: Error: Could not determine controller directory

    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1854:11)

    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1327:37)

    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3324:30)

    at runNextTicks (node:internal/process/task_queues:64:5)

    at processImmediate (node:internal/timers:452:9)

Could not determine controller directory

Error: Could not determine controller directory

    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1854:11)

    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1327:37)

    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3324:30)

    at runNextTicks (node:internal/process/task_queues:64:5)

    at processImmediate (node:internal/timers:452:9)

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:

Error: Could not determine controller directory

    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1854:11)

    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1327:37)

    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3324:30)

    at runNextTicks (node:internal/process/task_queues:64:5)

    at processImmediate (node:internal/timers:452:9)

wie kann ich das reparieren?

Gruß
HappyUser20

Welche node.js Version verwendet du?

[Happyuser20]

@mcm1957 sagte:

@Happyuser20 sagte:

Hallo zusammen

Mein Iobroker im Synology docker will nach einem abgebrochenen Update des Js Controllers von 7.2.1 auf 7.2.2.nicht mehr starten.

Uncaught Rejection: Error: Could not determine controller directory

    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1854:11)

    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1327:37)

    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3324:30)

    at runNextTicks (node:internal/process/task_queues:64:5)

    at processImmediate (node:internal/timers:452:9)

Could not determine controller directory

Error: Could not determine controller directory

    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1854:11)

    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1327:37)

    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3324:30)

    at runNextTicks (node:internal/process/task_queues:64:5)

    at processImmediate (node:internal/timers:452:9)

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:

Error: Could not determine controller directory

    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1854:11)

    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1327:37)

    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3324:30)

    at runNextTicks (node:internal/process/task_queues:64:5)

    at processImmediate (node:internal/timers:452:9)

wie kann ich das reparieren?

Gruß
HappyUser20

Welche node.js Version verwendet du?

soweit ich das noch im Kopf habe, v22.22.3 ?

[Marc Berg]

@Happyuser20 sagte:

wie kann ich das reparieren?

Versuch's mal so:

cd /opt/iobroker
npm install iobroker.js-controller

• Container Neustart

[mcm1957]

nach einem abgebrochenen Update des Js Controllers

Was hat den Abbruch ausgelöst? Ein Fehler im Updateprozess selbst oder ein Bedienungsfehler, Stromausfall, ...
Geht nur drum zu beobachten ob ein generelles Problem vorliegen könnte.