Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. ioBroker startet nach Update nicht mehr

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    16
    1
    363

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    4.8k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.3k

ioBroker startet nach Update nicht mehr

Geplant Angeheftet Gesperrt Verschoben Error/Bug
update error
36 Beiträge 5 Kommentatoren 932 Aufrufe 4 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • O Olli-S
    Systemdata Bitte Ausfüllen
    Hardwaresystem: Pi4
    Arbeitsspeicher: 4GB
    Festplattenart: SD-Karte
    Betriebssystem: Debian
    Node-Version: v10.16.3
    Nodejs-Version: v10.16.3
    NPM-Version: 6.9.0
    Installationsart: Manuell
    Image genutzt: Nein
    Ort/Name der Imagedatei: Link

    Hallo zusammen,

    nachdem ich heute ioBroker aktualisiert habe, bekomme ich ihn nicht mehr gestartet.
    Alle Fehlerlösungen welche mir in der Vergangenheit halfen, bringen leider auch nichts...

    Ich stelle mal wieder fest (wie immer wenn der ioBroker mal streikt), dass ich mich viel zu wenig mit Linux auseinandersetze...
    Kann sich bitte mal jemand von den Spezis mein letztes Log anschauen, und mich in die richtige Richtung schubsen?

    Vielen Dank im Voraus und besten Gruß
    Olli

    Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l
    
    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.
    
    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.
    Last login: Mon Jun  6 16:10:44 2022 from 192.168.99.44
    pi@raspberrypi:~ $ cd /opt/iobroker
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ Iobroker start admin
    -bash: Iobroker: command not found
    pi@raspberrypi:/opt/iobroker $ iobroker start admin
    internal/modules/cjs/loader.js:638
        throw err;
        ^
    
    Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
        at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
        at Function.Module._load (internal/modules/cjs/loader.js:562:25)
        at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
        at startup (internal/bootstrap/node.js:283:19)
        at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    -bash: Error:: command not found
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ sudo chmod 777 * -R
    pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.js-controller –production
    npm ERR! code EINVALIDTAGNAME
    npm ERR! Invalid tag name "–production": Tags may not have any characters that encodeURIComponent encodes.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /root/.npm/_logs/2022-06-06T15_37_41_466Z-debug.log
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.js-controller
    
    > iobroker.js-controller@2.2.10 preinstall /opt/iobroker/node_modules/iobroker.js-controller
    > node lib/preinstallCheck.js
    
    NPM version: 6.9.0
    
    > @serialport/bindings-cpp@10.7.0 install /opt/iobroker/node_modules/@serialport/bindings-cpp
    > node-gyp-build
    
    gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/10.16.3"
    gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    gyp ERR! configure error
    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/@serialport/bindings-cpp/build'
    gyp ERR! System Linux 4.19.66-v7l+
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node                                                    -gyp.js" "rebuild"
    gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings-cpp
    gyp ERR! node -v v10.16.3
    gyp ERR! node-gyp -v v3.8.0
    gyp ERR! not ok
    
    > canvas@2.9.1 install /opt/iobroker/node_modules/canvas
    > node-pre-gyp install --fallback-to-build
    
    node-pre-gyp WARN Pre-built binaries not installable for canvas@2.9.1 and node@10.16.3 (no                                                    de-v64 ABI, glibc) (falling back to source compile with node-gyp)
    node-pre-gyp WARN Hit error ENOENT: no such file or directory, mkdir
    gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy                                                    p/10.16.3"
    gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    gyp ERR! configure error
    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/canvas/                                                    build'
    gyp ERR! System Linux 4.19.66-v7l+
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node                                                    -gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/bui                                                    ld/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/c                                                    anvas/build/Release" "--napi_version=4" "--node_abi_napi=napi" "--napi_build_version=0" "-                                                    -node_napi_label=node-v64"
    gyp ERR! cwd /opt/iobroker/node_modules/canvas
    gyp ERR! node -v v10.16.3
    gyp ERR! node-gyp -v v3.8.0
    gyp ERR! not ok
    node-pre-gyp ERR! build error
    node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/                                                    node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker                                                    /node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iob                                                    roker/node_modules/canvas/build/Release --napi_version=4 --node_abi_napi=napi --napi_build                                                    _version=0 --node_napi_label=node-v64' (1)
    node-pre-gyp ERR! stack     at ChildProcess.cmd.on (/opt/iobroker/node_modules/@mapbox/nod                                                    e-pre-gyp/lib/util/compile.js:89:23)
    node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
    node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)
    node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process                                                    .js:259:5)
    node-pre-gyp ERR! System Linux 4.19.66-v7l+
    node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "                                                    install" "--fallback-to-build"
    node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas
    node-pre-gyp ERR! node -v v10.16.3
    node-pre-gyp ERR! node-pre-gyp -v v1.0.9
    node-pre-gyp ERR! not ok
    Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-                                                    gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Rele                                                    ase/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build                                                    /Release --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=no                                                    de-v64' (1)
    
    > unix-dgram@2.0.4 install /opt/iobroker/node_modules/unix-dgram
    > node-gyp rebuild
    
    gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy                                                    p/10.16.3"
    gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    gyp ERR! configure error
    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/unix-dg                                                    ram/build'
    gyp ERR! System Linux 4.19.66-v7l+
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node                                                    -gyp.js" "rebuild"
    gyp ERR! cwd /opt/iobroker/node_modules/unix-dgram
    gyp ERR! node -v v10.16.3
    gyp ERR! node-gyp -v v3.8.0
    gyp ERR! not ok
    
    > iobroker.js-controller@2.2.10 install /opt/iobroker/node_modules/iobroker.js-controller
    > node iobroker.js setup first
    
    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/                                                    node_modules/iobroker.js-controller/lib/setup/../../_service_iobroker.bat'
    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/                                                    node_modules/iobroker.js-controller/lib/setup/../../iobroker.bat'
    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/                                                    node_modules/iobroker.js-controller/lib/setup/../../iob.bat'
    fs.js:114
        throw err;
        ^
    
    Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller                                                    /lib/setup/../../tmp'
        at Object.mkdirSync (fs.js:757:3)
        at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup                                                    .js:690:58)
        at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:238:                                                    23)
        at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/li                                                    b/setup.js:2472:5)
        at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1                                                    :24)
        at Module._compile (internal/modules/cjs/loader.js:778:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
        at Module.load (internal/modules/cjs/loader.js:653:32)
        at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
        at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/nod                                                    e_modules/fsevents):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wan                                                    ted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_module                                                    s/iobroker.info/node_modules/osx-temperature-sensor):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sen                                                    sor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/alexa-                                                    remote2/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gaxios                                                    /package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/google                                                    -auth-library/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gtoken                                                    /package.json'
    npm WARN ws@7.4.3 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    npm WARN ws@7.4.3 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    npm WARN node-fetch@2.6.7 requires a peer of encoding@^0.1.0 but none is installed. You mu                                                    st install peer dependencies yourself.
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @serialport/bindings-cpp@10.7.0 (node_modu                                                    les/@serialport/bindings-cpp):
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @serialport/bindings-cpp@10.7.0 install: `                                                    node-gyp-build`
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.9.1 (node_modules/canvas):
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.9.1 install: `node-pre-gyp instal                                                    l --fallback-to-build`
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.4 (node_modules/unix-dgram)                                                    :
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.4 install: `node-gyp rebuil                                                    d`
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! iobroker.js-controller@2.2.10 install: `node iobroker.js setup first`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the iobroker.js-controller@2.2.10 install script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging outpu                                                    t above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /root/.npm/_logs/2022-06-06T15_41_26_133Z-debug.log
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ iobroker start admin
    internal/modules/cjs/loader.js:638
        throw err;
        ^
    
    Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
        at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
        at Function.Module._load (internal/modules/cjs/loader.js:562:25)
        at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
        at startup (internal/bootstrap/node.js:283:19)
        at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller
    npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/le-acme-core/node_modu                                           les
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules                                           /fsevents):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os"                                           :"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroke                                           r.info/node_modules/osx-temperature-sensor):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7                                           : wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/alexa-remote2/p                                           ackage.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gaxios/package.                                           json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/google-auth-lib                                           rary/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gtoken/package.                                           json'
    npm WARN ws@7.4.3 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    npm WARN ws@7.4.3 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    npm WARN node-fetch@2.6.7 requires a peer of encoding@^0.1.0 but none is installed. You must instal                                           l peer dependencies yourself.
    
    npm ERR! path /opt/iobroker/node_modules/le-acme-core/node_modules
    npm ERR! code EACCES
    npm ERR! errno -13
    npm ERR! syscall access
    npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/node_mod                                           ules'
    npm ERR!  { [Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/node                                           _modules']
    npm ERR!   stack:
    npm ERR!    'Error: EACCES: permission denied, access \'/opt/iobroker/node_modules/le-acme-core/nod                                           e_modules\'',
    npm ERR!   errno: -13,
    npm ERR!   code: 'EACCES',
    npm ERR!   syscall: 'access',
    npm ERR!   path: '/opt/iobroker/node_modules/le-acme-core/node_modules' }
    npm ERR!
    npm ERR! The operation was rejected by your operating system.
    npm ERR! It is likely you do not have the permissions to access this file as the current user
    npm ERR!
    npm ERR! If you believe this might be a permissions issue, please double-check the
    npm ERR! permissions of the file and its containing directories, or try running
    npm ERR! the command again as root/Administrator (though this is not recommended).
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /home/iobroker/.npm/_logs/2022-06-06T15_47_12_538Z-debug.log
    pi@raspberrypi:/opt/iobroker $ iobroker start admin
    internal/modules/cjs/loader.js:638
        throw err;
        ^
    
    Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
        at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
        at Function.Module._load (internal/modules/cjs/loader.js:562:25)
        at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
        at startup (internal/bootstrap/node.js:283:19)
        at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ iobroker fix
    library: loaded
    Library version=2022-06-03
    ioBroker is not installed in /opt/iobroker! Cannot fix anything...
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ node -v
    v10.16.3
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ nodejs -v
    v10.16.3
    pi@raspberrypi:/opt/iobroker $ npm -v
    6.9.0
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ : pi
    pi@raspberrypi:/opt/iobroker $ pi@192.168.99.38's password:
    > Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l
    >
    o> The programs included with the Debian GNU/Linux system are free software;
    > the exact distribution terms for each program are described in the
    > individual files in /usr/share/doc/*/copyright.
    >
     > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    > permitted by applicable law.
    > Last login: Mon Jun  6 16:10:44 2022 from 192.168.99.44
    > pi@raspberrypi:~ $ cd /opt/iobroker
    > pi@raspberrypi:/opt/iobroker $ iobroker start
    > pi@raspberrypi:/opt/iobroker $ Iobroker start admin
    > -bash: Iobroker: command not found
    > pi@raspberrypi:/opt/iobroker $ iobroker start admin
    > internal/modules/cjs/loader.js:638
    >     throw err;
    >     ^
    >
    > Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iob                                                              roker.js'
    >     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    >     at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    >     at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    >     at startup (internal/bootstrap/node.js:283:19)
    >     at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    > pi@raspberrypi:/opt/iobroker $ iobroker start
    > pi@raspberrypi:/opt/iobroker $ ^C
    > pi@raspberrypi:/opt/iobroker $ ^C
    > pi@raspberrypi:/opt/iobroker $ Error: Cannot find module '/opt/iobroker/node_mod                                                              ules/iobroker.js-controller/iobroker.js'
    > -bash: Error:: command not found
    > pi@raspberrypi:/opt/iobroker $ ^C
    > pi@raspberrypi:/opt/iobroker $ sudo chmod 777 * -R
    > pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.js-controller –producti                                                              on
    > npm ERR! code EINVALIDTAGNAME
    > npm ERR! Invalid tag name "–production": Tags may not have any characters that encodeURICo                                                    mponent encodes.
    >
    p> npm ERR! A complete log of this run can be found in:
    > npm ERR!     /root/.npm/_logs/2022-06-06T15_37_41_466Z-debug.log
    > pi@raspberrypi:/opt/iobroker $ iobroker start
    > pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.js-controller
    >
    > > iobroker.js-controller@2.2.10 preinstall /opt/iobroker/node_modules/iobroker.js-controll                                                    er
    > > node lib/preinstallCheck.js
    >
    > NPM version: 6.9.0
    >
    > > @serialport/bindings-cpp@10.7.0 install /opt/iobroker/node_modules/@serialport/bindings-                                                    cpp
    > > node-gyp-build
    >
    > gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy                                                    p/10.16.3"
    > gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    > gyp ERR! configure error
    > gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/@serial                                                    port/bindings-cpp/build'
    > gyp ERR! System Linux 4.19.66-v7l+
    > gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node                                                    -gyp.js" "rebuild"
    > gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings-cpp
    > gyp ERR! node -v v10.16.3
    > gyp ERR! node-gyp -v v3.8.0
    > gyp ERR! not ok
    >
    m> > canvas@2.9.1 install /opt/iobroker/node_modules/canvas
    > > node-pre-gyp install --fallback-to-build
    >
    p> node-pre-gyp WARN Pre-built binaries not installable for canvas@2.9.1 and node@10.16.3 (no                                                    de-v64 ABI, glibc) (falling back to source compile with node-gyp)
    > node-pre-gyp WARN Hit error ENOENT: no such file or directory, mkdir
    > gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy                                                    p/10.16.3"
    > gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    > gyp ERR! configure error
    > gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/canvas/                                                    build'
    > gyp ERR! System Linux 4.19.66-v7l+
    > gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node                                                    -gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/bui                                                    ld/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/c                                                    anvas/build/Release" "--napi_version=4" "--node_abi_napi=napi" "--napi_build_version=0" "-                                                    -node_napi_label=node-v64"
    > gyp ERR! cwd /opt/iobroker/node_modules/canvas
    > gyp ERR! node -v v10.16.3
    > gyp ERR! node-gyp -v v3.8.0
    > gyp ERR! not ok
    > node-pre-gyp ERR! build error
    > node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/                                                    node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker                                                    /node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iob                                                    roker/node_modules/canvas/build/Release --napi_version=4 --node_abi_napi=napi --napi_build                                                    _version=0 --node_napi_label=node-v64' (1)
    > node-pre-gyp ERR! stack     at ChildProcess.cmd.on (/opt/iobroker/node_modules/@mapbox/nod                                                    e-pre-gyp/lib/util/compile.js:89:23)
    > node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
    > node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)
    > node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process                                                    .js:259:5)
    > node-pre-gyp ERR! System Linux 4.19.66-v7l+
    > node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "                                                    install" "--fallback-to-build"
    > node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas
    > node-pre-gyp ERR! node -v v10.16.3
    > node-pre-gyp ERR! node-pre-gyp -v v1.0.9
    > node-pre-gyp ERR! not ok
    > Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-                                                    gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Rele                                                    ase/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build                                                    /Release --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=no                                                    de-v64' (1)
    >
    > > unix-dgram@2.0.4 install /opt/iobroker/node_modules/unix-dgram
    > > node-gyp rebuild
    >
    > gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy                                                    p/10.16.3"
    > gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    > gyp ERR! configure error
    > gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/unix-dg                                                    ram/build'
    > gyp ERR! System Linux 4.19.66-v7l+
    > gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node                                                    -gyp.js" "rebuild"
    > gyp ERR! cwd /opt/iobroker/node_modules/unix-dgram
    > gyp ERR! node -v v10.16.3
    > gyp ERR! node-gyp -v v3.8.0
    > gyp ERR! not ok
    >
     > > iobroker.js-controller@2.2.10 install /opt/iobroker/node_modules/iobroker.js-controller
    > > node iobroker.js setup first
    >
    > Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/                                                    node_modules/iobroker.js-controller/lib/setup/../../_service_iobroker.bat'
    > Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/                                                    node_modules/iobroker.js-controller/lib/setup/../../iobroker.bat'
    > Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/                                                    node_modules/iobroker.js-controller/lib/setup/../../iob.bat'
    > fs.js:114
    >     throw err;
    >     ^
    >
    > Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller                                                    /lib/setup/../../tmp'
    >     at Object.mkdirSync (fs.js:757:3)
    >     at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup                                                    .js:690:58)
    >     at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:238:                                                    23)
    >     at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/li                                                    b/setup.js:2472:5)
    >     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1                                                    :24)
    >     at Module._compile (internal/modules/cjs/loader.js:778:30)
    >     at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    >     at Module.load (internal/modules/cjs/loader.js:653:32)
    >     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    >     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/nod                                                    e_modules/fsevents):
    > npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wan                                                    ted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_module                                                    s/iobroker.info/node_modules/osx-temperature-sensor):
    > npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sen                                                    sor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    > npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/alexa-                                                    remote2/package.json'
    > npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gaxios                                                    /package.json'
    > npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/google                                                    -auth-library/package.json'
    > npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gtoken                                                    /package.json'
    > npm WARN ws@7.4.3 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    > npm WARN ws@7.4.3 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    > npm WARN ws@7.3.0 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    > npm WARN ws@7.3.0 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    > npm WARN ws@8.4.2 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    > npm WARN ws@8.4.2 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins                                                    tall peer dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must                                                     install peer dependencies yourself.
    > npm WARN node-fetch@2.6.7 requires a peer of encoding@^0.1.0 but none is installed. You mu                                                    st install peer dependencies yourself.
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @serialport/bindings-cpp@10.7.0 (node_modu                                                    les/@serialport/bindings-cpp):
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @serialport/bindings-cpp@10.7.0 install: `                                                    node-gyp-build`
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.9.1 (node_modules/canvas):
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.9.1 install: `node-pre-gyp instal                                                    l --fallback-to-build`
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.4 (node_modules/unix-dgram)                                                    :
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.4 install: `node-gyp rebuil                                                    d`
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    >
    b> npm ERR! code ELIFECYCLE
    > npm ERR! errno 1
    > npm ERR! iobroker.js-controller@2.2.10 install: `node iobroker.js setup first`
    > npm ERR! Exit status 1
    > npm ERR!
    > npm ERR! Failed at the iobroker.js-controller@2.2.10 install script.
    > npm ERR! This is probably not a problem with npm. There is likely additional logging outpu                                                    t above.
    >
    d> npm ERR! A complete log of this run can be found in:
    > npm ERR!     /root/.npm/_logs/2022-06-06T15_41_26_133Z-debug.log
    > pi@raspberrypi:/opt/iobroker $ iobroker start
    > pi@raspberrypi:/opt/iobroker $ iobroker start admin
    > internal/modules/cjs/loader.js:638
    >     throw err;
    >     ^
    >
    > Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    >     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    >     at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    >     at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    >     at startup (internal/bootstrap/node.js:283:19)
    >     at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    > pi@raspberrypi:/opt/iobroker $ ^C
    > pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller
    > npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/le-acme-core/node_modu                                           les
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules                                           /fsevents):
    > npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os"                                           :"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    > npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroke                                           r.info/node_modules/osx-temperature-sensor):
    > npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7                                           : wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    > npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/alexa-remote2/p                                           ackage.json'
    > npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gaxios/package.                                           json'
    > npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/google-auth-lib                                           rary/package.json'
    > npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gtoken/package.                                           json'
    > npm WARN ws@7.4.3 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    > npm WARN ws@7.4.3 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    > npm WARN ws@7.3.0 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    > npm WARN ws@7.3.0 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    > npm WARN ws@8.4.2 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    > npm WARN ws@8.4.2 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer                                            dependencies yourself.
    > npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install                                            peer dependencies yourself.
    > npm WARN node-fetch@2.6.7 requires a peer of encoding@^0.1.0 but none is installed. You must instal                                           l peer dependencies yourself.
    >
    > npm ERR! path /opt/iobroker/node_modules/le-acme-core/node_modules
    > npm ERR! code EACCES
    > npm ERR! errno -13
    > npm ERR! syscall access
    > npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/node_mod                                           ules'
    > npm ERR!  { [Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/node                                           _modules']
    > npm ERR!   stack:
    > npm ERR!    'Error: EACCES: permission denied, access \'/opt/iobroker/node_modules/le-acme-core/nod                                           e_modules\'',
    > npm ERR!   errno: -13,
    > npm ERR!   code: 'EACCES',
    > npm ERR!   syscall: 'access',
    > npm ERR!   path: '/opt/iobroker/node_modules/le-acme-core/node_modules' }
    > npm ERR!
    > npm ERR! The operation was rejected by your operating system.
    > npm ERR! It is likely you do not have the permissions to access this file as the current user
    > npm ERR!
    > npm ERR! If you believe this might be a permissions issue, please double-check the
    > npm ERR! permissions of the file and its containing directories, or try running
    > npm ERR! the command again as root/Administrator (though this is not recommended).
    >
    > npm ERR! A complete log of this run can be found in:
    > npm ERR!     /home/iobroker/.npm/_logs/2022-06-06T15_47_12_538Z-debug.log
    > pi@raspberrypi:/opt/iobroker $ iobroker start admin
    > internal/modules/cjs/loader.js:638
    >     throw err;
    >     ^
    >
    > Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    >     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    >     at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    >     at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    >     at startup (internal/bootstrap/node.js:283:19)
    >     at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    
    ```|Systemdata| Bitte Ausfüllen|
    |--|--|
    |Hardwaresystem:| NUC&#x2F;Pi3&#x2F;etc.|
    |Arbeitsspeicher:| 1GB |
    |Festplattenart:| SD-Karte&#x2F;SSD&#x2F;HDD |
    |Betriebssystem:| Ubuntu&#x2F;Windows&#x2F;Mac |
    |Node-Version:| 10.x.x |
    |Nodejs-Version:| 10.x.x |
    |NPM-Version:| 6.x.x |
    |Installationsart:| Skript&#x2F;Manuell |
    |Image genutzt:| Ja&#x2F;Nein |
    |Ort&#x2F;Name der Imagedatei:| Link ||Systemdata| Bitte Ausfüllen|
    |--|--|
    |Hardwaresystem:| Pi4|
    |Arbeitsspeicher:| 4GB |
    |Festplattenart:| SD-Karte |
    |Betriebssystem:| Debian |
    |Node-Version:| v10.16.3 |
    |Nodejs-Version:| v10.16.3 |
    |NPM-Version:| 6.9.0 |
    |Installationsart:| Manuell |
    |Image genutzt:| Nein |
    |Ort&#x2F;Name der Imagedatei:| Link |
    
    
    Hallo zusammen,
    
    nachdem ich heute ioBroker aktualisiert habe, bekomme ich ihn nicht mehr gestartet.
    Alle Fehlerlösungen welche mir in der Vergangenheit halfen, bringen leider auch nichts...
    
    Ich stelle mal wieder fest (wie immer wenn der ioBroker mal streikt), dass ich mich viel zu wenig mit Linux auseinandersetze...
    Kann sich bitte mal jemand von den Spezis mein letztes Log anschauen, und mich in die richtige Richtung schubsen?
    
    Vielen Dank im Voraus und besten Gruß
    Olli
     
    
    

    Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.
    Last login: Mon Jun 6 16:10:44 2022 from 192.168.99.44
    pi@raspberrypi:~ $ cd /opt/iobroker
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ Iobroker start admin
    -bash: Iobroker: command not found
    pi@raspberrypi:/opt/iobroker $ iobroker start admin
    internal/modules/cjs/loader.js:638
    throw err;
    ^

    Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    -bash: Error:: command not found
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ sudo chmod 777 * -R
    pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.js-controller –production
    npm ERR! code EINVALIDTAGNAME
    npm ERR! Invalid tag name "–production": Tags may not have any characters that encodeURIComponent encodes.

    npm ERR! A complete log of this run can be found in:
    npm ERR! /root/.npm/_logs/2022-06-06T15_37_41_466Z-debug.log
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.js-controller

    iobroker.js-controller@2.2.10 preinstall /opt/iobroker/node_modules/iobroker.js-controller
    node lib/preinstallCheck.js

    NPM version: 6.9.0

    @serialport/bindings-cpp@10.7.0 install /opt/iobroker/node_modules/@serialport/bindings-cpp
    node-gyp-build

    gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/10.16.3"
    gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    gyp ERR! configure error
    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/@serialport/bindings-cpp/build'
    gyp ERR! System Linux 4.19.66-v7l+
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node -gyp.js" "rebuild"
    gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings-cpp
    gyp ERR! node -v v10.16.3
    gyp ERR! node-gyp -v v3.8.0
    gyp ERR! not ok

    canvas@2.9.1 install /opt/iobroker/node_modules/canvas
    node-pre-gyp install --fallback-to-build

    node-pre-gyp WARN Pre-built binaries not installable for canvas@2.9.1 and node@10.16.3 (no de-v64 ABI, glibc) (falling back to source compile with node-gyp)
    node-pre-gyp WARN Hit error ENOENT: no such file or directory, mkdir
    gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy p/10.16.3"
    gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    gyp ERR! configure error
    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/canvas/ build'
    gyp ERR! System Linux 4.19.66-v7l+
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node -gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/bui ld/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/c anvas/build/Release" "--napi_version=4" "--node_abi_napi=napi" "--napi_build_version=0" "- -node_napi_label=node-v64"
    gyp ERR! cwd /opt/iobroker/node_modules/canvas
    gyp ERR! node -v v10.16.3
    gyp ERR! node-gyp -v v3.8.0
    gyp ERR! not ok
    node-pre-gyp ERR! build error
    node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/ node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker /node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iob roker/node_modules/canvas/build/Release --napi_version=4 --node_abi_napi=napi --napi_build _version=0 --node_napi_label=node-v64' (1)
    node-pre-gyp ERR! stack at ChildProcess.cmd.on (/opt/iobroker/node_modules/@mapbox/nod e-pre-gyp/lib/util/compile.js:89:23)
    node-pre-gyp ERR! stack at ChildProcess.emit (events.js:198:13)
    node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:982:16)
    node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process .js:259:5)
    node-pre-gyp ERR! System Linux 4.19.66-v7l+
    node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" " install" "--fallback-to-build"
    node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas
    node-pre-gyp ERR! node -v v10.16.3
    node-pre-gyp ERR! node-pre-gyp -v v1.0.9
    node-pre-gyp ERR! not ok
    Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node- gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Rele ase/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build /Release --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=no de-v64' (1)

    unix-dgram@2.0.4 install /opt/iobroker/node_modules/unix-dgram
    node-gyp rebuild

    gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy p/10.16.3"
    gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    gyp ERR! configure error
    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/unix-dg ram/build'
    gyp ERR! System Linux 4.19.66-v7l+
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node -gyp.js" "rebuild"
    gyp ERR! cwd /opt/iobroker/node_modules/unix-dgram
    gyp ERR! node -v v10.16.3
    gyp ERR! node-gyp -v v3.8.0
    gyp ERR! not ok

    iobroker.js-controller@2.2.10 install /opt/iobroker/node_modules/iobroker.js-controller
    node iobroker.js setup first

    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/ node_modules/iobroker.js-controller/lib/setup/../../_service_iobroker.bat'
    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/ node_modules/iobroker.js-controller/lib/setup/../../iobroker.bat'
    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/ node_modules/iobroker.js-controller/lib/setup/../../iob.bat'
    fs.js:114
    throw err;
    ^

    Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller /lib/setup/../../tmp'
    at Object.mkdirSync (fs.js:757:3)
    at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup .js:690:58)
    at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:238: 23)
    at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/li b/setup.js:2472:5)
    at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1 :24)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/nod e_modules/fsevents):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wan ted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_module s/iobroker.info/node_modules/osx-temperature-sensor):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sen sor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/alexa- remote2/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gaxios /package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/google -auth-library/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gtoken /package.json'
    npm WARN ws@7.4.3 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.4.3 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN node-fetch@2.6.7 requires a peer of encoding@^0.1.0 but none is installed. You mu st install peer dependencies yourself.
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @serialport/bindings-cpp@10.7.0 (node_modu les/@serialport/bindings-cpp):
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @serialport/bindings-cpp@10.7.0 install: node-gyp-build
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.9.1 (node_modules/canvas):
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.9.1 install: node-pre-gyp instal l --fallback-to-build
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.4 (node_modules/unix-dgram) :
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.4 install: node-gyp rebuil d
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! iobroker.js-controller@2.2.10 install: node iobroker.js setup first
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the iobroker.js-controller@2.2.10 install script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging outpu t above.

    npm ERR! A complete log of this run can be found in:
    npm ERR! /root/.npm/_logs/2022-06-06T15_41_26_133Z-debug.log
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ iobroker start admin
    internal/modules/cjs/loader.js:638
    throw err;
    ^

    Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller
    npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/le-acme-core/node_modu les
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules /fsevents):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os" :"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroke r.info/node_modules/osx-temperature-sensor):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7 : wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/alexa-remote2/p ackage.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gaxios/package. json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/google-auth-lib rary/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gtoken/package. json'
    npm WARN ws@7.4.3 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.3 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN node-fetch@2.6.7 requires a peer of encoding@^0.1.0 but none is installed. You must instal l peer dependencies yourself.

    npm ERR! path /opt/iobroker/node_modules/le-acme-core/node_modules
    npm ERR! code EACCES
    npm ERR! errno -13
    npm ERR! syscall access
    npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/node_mod ules'
    npm ERR! { [Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/node _modules']
    npm ERR! stack:
    npm ERR! 'Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/nod e_modules'',
    npm ERR! errno: -13,
    npm ERR! code: 'EACCES',
    npm ERR! syscall: 'access',
    npm ERR! path: '/opt/iobroker/node_modules/le-acme-core/node_modules' }
    npm ERR!
    npm ERR! The operation was rejected by your operating system.
    npm ERR! It is likely you do not have the permissions to access this file as the current user
    npm ERR!
    npm ERR! If you believe this might be a permissions issue, please double-check the
    npm ERR! permissions of the file and its containing directories, or try running
    npm ERR! the command again as root/Administrator (though this is not recommended).

    npm ERR! A complete log of this run can be found in:
    npm ERR! /home/iobroker/.npm/_logs/2022-06-06T15_47_12_538Z-debug.log
    pi@raspberrypi:/opt/iobroker $ iobroker start admin
    internal/modules/cjs/loader.js:638
    throw err;
    ^

    Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ iobroker fix
    library: loaded
    Library version=2022-06-03
    ioBroker is not installed in /opt/iobroker! Cannot fix anything...
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ node -v
    v10.16.3
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ nodejs -v
    v10.16.3
    pi@raspberrypi:/opt/iobroker $ npm -v
    6.9.0
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ : pi
    pi@raspberrypi:/opt/iobroker $ pi@192.168.99.38's password:

    Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l

    o> The programs included with the Debian GNU/Linux system are free software;

    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.
    Last login: Mon Jun 6 16:10:44 2022 from 192.168.99.44
    pi@raspberrypi:~ $ cd /opt/iobroker
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ Iobroker start admin
    -bash: Iobroker: command not found
    pi@raspberrypi:/opt/iobroker $ iobroker start admin
    internal/modules/cjs/loader.js:638
    throw err;
    ^

    Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iob roker.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ Error: Cannot find module '/opt/iobroker/node_mod ules/iobroker.js-controller/iobroker.js'
    -bash: Error:: command not found
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ sudo chmod 777 * -R
    pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.js-controller –producti on
    npm ERR! code EINVALIDTAGNAME
    npm ERR! Invalid tag name "–production": Tags may not have any characters that encodeURICo mponent encodes.

    p> npm ERR! A complete log of this run can be found in:

    npm ERR! /root/.npm/_logs/2022-06-06T15_37_41_466Z-debug.log
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.js-controller

    iobroker.js-controller@2.2.10 preinstall /opt/iobroker/node_modules/iobroker.js-controll er
    node lib/preinstallCheck.js

    NPM version: 6.9.0

    @serialport/bindings-cpp@10.7.0 install /opt/iobroker/node_modules/@serialport/bindings- cpp
    node-gyp-build

    gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy p/10.16.3"
    gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    gyp ERR! configure error
    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/@serial port/bindings-cpp/build'
    gyp ERR! System Linux 4.19.66-v7l+
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node -gyp.js" "rebuild"
    gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings-cpp
    gyp ERR! node -v v10.16.3
    gyp ERR! node-gyp -v v3.8.0
    gyp ERR! not ok

    m> > canvas@2.9.1 install /opt/iobroker/node_modules/canvas

    node-pre-gyp install --fallback-to-build

    p> node-pre-gyp WARN Pre-built binaries not installable for canvas@2.9.1 and node@10.16.3 (no de-v64 ABI, glibc) (falling back to source compile with node-gyp)

    node-pre-gyp WARN Hit error ENOENT: no such file or directory, mkdir
    gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy p/10.16.3"
    gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    gyp ERR! configure error
    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/canvas/ build'
    gyp ERR! System Linux 4.19.66-v7l+
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node -gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/bui ld/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/c anvas/build/Release" "--napi_version=4" "--node_abi_napi=napi" "--napi_build_version=0" "- -node_napi_label=node-v64"
    gyp ERR! cwd /opt/iobroker/node_modules/canvas
    gyp ERR! node -v v10.16.3
    gyp ERR! node-gyp -v v3.8.0
    gyp ERR! not ok
    node-pre-gyp ERR! build error
    node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/ node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker /node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iob roker/node_modules/canvas/build/Release --napi_version=4 --node_abi_napi=napi --napi_build _version=0 --node_napi_label=node-v64' (1)
    node-pre-gyp ERR! stack at ChildProcess.cmd.on (/opt/iobroker/node_modules/@mapbox/nod e-pre-gyp/lib/util/compile.js:89:23)
    node-pre-gyp ERR! stack at ChildProcess.emit (events.js:198:13)
    node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:982:16)
    node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process .js:259:5)
    node-pre-gyp ERR! System Linux 4.19.66-v7l+
    node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" " install" "--fallback-to-build"
    node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas
    node-pre-gyp ERR! node -v v10.16.3
    node-pre-gyp ERR! node-pre-gyp -v v1.0.9
    node-pre-gyp ERR! not ok
    Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node- gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Rele ase/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build /Release --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=no de-v64' (1)

    unix-dgram@2.0.4 install /opt/iobroker/node_modules/unix-dgram
    node-gyp rebuild

    gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gy p/10.16.3"
    gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
    gyp ERR! configure error
    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/unix-dg ram/build'
    gyp ERR! System Linux 4.19.66-v7l+
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node -gyp.js" "rebuild"
    gyp ERR! cwd /opt/iobroker/node_modules/unix-dgram
    gyp ERR! node -v v10.16.3
    gyp ERR! node-gyp -v v3.8.0
    gyp ERR! not ok

    iobroker.js-controller@2.2.10 install /opt/iobroker/node_modules/iobroker.js-controller
    node iobroker.js setup first

    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/ node_modules/iobroker.js-controller/lib/setup/../../_service_iobroker.bat'
    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/ node_modules/iobroker.js-controller/lib/setup/../../iobroker.bat'
    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/ node_modules/iobroker.js-controller/lib/setup/../../iob.bat'
    fs.js:114
    throw err;
    ^

    Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller /lib/setup/../../tmp'
    at Object.mkdirSync (fs.js:757:3)
    at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup .js:690:58)
    at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:238: 23)
    at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/li b/setup.js:2472:5)
    at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1 :24)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/nod e_modules/fsevents):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wan ted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_module s/iobroker.info/node_modules/osx-temperature-sensor):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sen sor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/alexa- remote2/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gaxios /package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/google -auth-library/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gtoken /package.json'
    npm WARN ws@7.4.3 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.4.3 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must ins tall peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN node-fetch@2.6.7 requires a peer of encoding@^0.1.0 but none is installed. You mu st install peer dependencies yourself.
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @serialport/bindings-cpp@10.7.0 (node_modu les/@serialport/bindings-cpp):
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @serialport/bindings-cpp@10.7.0 install: node-gyp-build
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.9.1 (node_modules/canvas):
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.9.1 install: node-pre-gyp instal l --fallback-to-build
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.4 (node_modules/unix-dgram) :
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.4 install: node-gyp rebuil d
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

    b> npm ERR! code ELIFECYCLE

    npm ERR! errno 1
    npm ERR! iobroker.js-controller@2.2.10 install: node iobroker.js setup first
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the iobroker.js-controller@2.2.10 install script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging outpu t above.

    d> npm ERR! A complete log of this run can be found in:

    npm ERR! /root/.npm/_logs/2022-06-06T15_41_26_133Z-debug.log
    pi@raspberrypi:/opt/iobroker $ iobroker start
    pi@raspberrypi:/opt/iobroker $ iobroker start admin
    internal/modules/cjs/loader.js:638
    throw err;
    ^

    Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller
    npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/le-acme-core/node_modu les
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules /fsevents):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os" :"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroke r.info/node_modules/osx-temperature-sensor):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7 : wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/alexa-remote2/p ackage.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gaxios/package. json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/google-auth-lib rary/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/gtoken/package. json'
    npm WARN ws@7.4.3 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.3 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.3.0 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@8.4.2 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
    npm WARN ws@7.4.5 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
    npm WARN node-fetch@2.6.7 requires a peer of encoding@^0.1.0 but none is installed. You must instal l peer dependencies yourself.

    npm ERR! path /opt/iobroker/node_modules/le-acme-core/node_modules
    npm ERR! code EACCES
    npm ERR! errno -13
    npm ERR! syscall access
    npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/node_mod ules'
    npm ERR! { [Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/node _modules']
    npm ERR! stack:
    npm ERR! 'Error: EACCES: permission denied, access '/opt/iobroker/node_modules/le-acme-core/nod e_modules'',
    npm ERR! errno: -13,
    npm ERR! code: 'EACCES',
    npm ERR! syscall: 'access',
    npm ERR! path: '/opt/iobroker/node_modules/le-acme-core/node_modules' }
    npm ERR!
    npm ERR! The operation was rejected by your operating system.
    npm ERR! It is likely you do not have the permissions to access this file as the current user
    npm ERR!
    npm ERR! If you believe this might be a permissions issue, please double-check the
    npm ERR! permissions of the file and its containing directories, or try running
    npm ERR! the command again as root/Administrator (though this is not recommended).

    npm ERR! A complete log of this run can be found in:
    npm ERR! /home/iobroker/.npm/_logs/2022-06-06T15_47_12_538Z-debug.log
    pi@raspberrypi:/opt/iobroker $ iobroker start admin
    internal/modules/cjs/loader.js:638
    throw err;
    ^

    Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

    GlasfaserG Offline
    GlasfaserG Offline
    Glasfaser
    schrieb am zuletzt editiert von
    #6

    @Thomas-Braun

    @olli-s sagte in ioBroker startet nach Update nicht mehr:
    pi@raspberrypi:/opt/iobroker $ node -v
    v10.16.3
    pi@raspberrypi:/opt/iobroker $ ^C
    pi@raspberrypi:/opt/iobroker $ nodejs -v
    v10.16.3
    pi@raspberrypi:/opt/iobroker $ npm -v
    6.9.0

    Ich habe so eine Befürchtung ... er hat kein Backup ... nach dem Stand seines Log´s

    Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • GlasfaserG Glasfaser

      @Thomas-Braun

      @olli-s sagte in ioBroker startet nach Update nicht mehr:
      pi@raspberrypi:/opt/iobroker $ node -v
      v10.16.3
      pi@raspberrypi:/opt/iobroker $ ^C
      pi@raspberrypi:/opt/iobroker $ nodejs -v
      v10.16.3
      pi@raspberrypi:/opt/iobroker $ npm -v
      6.9.0

      Ich habe so eine Befürchtung ... er hat kein Backup ... nach dem Stand seines Log´s

      Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      schrieb am zuletzt editiert von
      #7

      @glasfaser sagte in ioBroker startet nach Update nicht mehr:

      Ich habe so eine Befürchtung ... er hat kein Backup ... nach dem Stand seines Log´s

      Zumindest ist das System vermutlich von schon reichlich angegammelt. Node10 ist ja auch längst tot. Und auf die krumme Basis setzt dann die windschief zusammengekloppte ioBroker-Installation auf.
      Das Ding ist kernschrott...

      Linux-Werkzeugkasten:
      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
      NodeJS Fixer Skript:
      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

      1 Antwort Letzte Antwort
      0
      • O Offline
        O Offline
        Olli-S
        schrieb am zuletzt editiert von
        #8

        Danke erstmal für eure Antworten.

        Die Installation ist schon etwas älter, und frei nach dem Motto "never touch a running system" auch nicht sonderlich oft aktualisiert.
        Ich wollte die Installation eigentlich schon längst auf nen Lenovo-Tiny mit SSD migriert haben, (der hier seit nem Jahr rumliegt) leider hat das beim letzten Anlauf nicht richtig funktioniert. Irgendwie hat er das damalige Backup nicht ordentlich übernommen. Aus Zeitmangel hab ich es dann wieder liegengelassen, der Pi lief ja noch.

        Nen Update mit Backitup war eigentlich konfiguriert, und sollte somit auf der SD-Karte schlummern.
        Vielleicht wäre das der richtige Zeitpunkt die Migration endlich durchzuziehen...
        Leider fehlt mir grad mal wieder die Zeit.
        Habt ihr noch ne Idee ob ich die alte Installation nochmal für ne Woche reanimieren kann, um die Migration dann in Ruhe zu machen?

        Vielen Dank im Voraus und VG

        GlasfaserG Thomas BraunT 2 Antworten Letzte Antwort
        0
        • O Olli-S

          Danke erstmal für eure Antworten.

          Die Installation ist schon etwas älter, und frei nach dem Motto "never touch a running system" auch nicht sonderlich oft aktualisiert.
          Ich wollte die Installation eigentlich schon längst auf nen Lenovo-Tiny mit SSD migriert haben, (der hier seit nem Jahr rumliegt) leider hat das beim letzten Anlauf nicht richtig funktioniert. Irgendwie hat er das damalige Backup nicht ordentlich übernommen. Aus Zeitmangel hab ich es dann wieder liegengelassen, der Pi lief ja noch.

          Nen Update mit Backitup war eigentlich konfiguriert, und sollte somit auf der SD-Karte schlummern.
          Vielleicht wäre das der richtige Zeitpunkt die Migration endlich durchzuziehen...
          Leider fehlt mir grad mal wieder die Zeit.
          Habt ihr noch ne Idee ob ich die alte Installation nochmal für ne Woche reanimieren kann, um die Migration dann in Ruhe zu machen?

          Vielen Dank im Voraus und VG

          GlasfaserG Offline
          GlasfaserG Offline
          Glasfaser
          schrieb am zuletzt editiert von
          #9

          @olli-s sagte in ioBroker startet nach Update nicht mehr:

          Die Installation ist schon etwas älter, und frei nach dem Motto "never touch a running system"

          Niemals so denken !

          Leider fehlt mir grad mal wieder die Zeit.

          Das ist nicht mal eben .... in zwei , drei Befehlen zu reparieren ...

          Dann Warte die Woche und mache es Ordentlich .

          Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

          O 1 Antwort Letzte Antwort
          0
          • O Olli-S

            Danke erstmal für eure Antworten.

            Die Installation ist schon etwas älter, und frei nach dem Motto "never touch a running system" auch nicht sonderlich oft aktualisiert.
            Ich wollte die Installation eigentlich schon längst auf nen Lenovo-Tiny mit SSD migriert haben, (der hier seit nem Jahr rumliegt) leider hat das beim letzten Anlauf nicht richtig funktioniert. Irgendwie hat er das damalige Backup nicht ordentlich übernommen. Aus Zeitmangel hab ich es dann wieder liegengelassen, der Pi lief ja noch.

            Nen Update mit Backitup war eigentlich konfiguriert, und sollte somit auf der SD-Karte schlummern.
            Vielleicht wäre das der richtige Zeitpunkt die Migration endlich durchzuziehen...
            Leider fehlt mir grad mal wieder die Zeit.
            Habt ihr noch ne Idee ob ich die alte Installation nochmal für ne Woche reanimieren kann, um die Migration dann in Ruhe zu machen?

            Vielen Dank im Voraus und VG

            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            schrieb am zuletzt editiert von
            #10

            @olli-s sagte in ioBroker startet nach Update nicht mehr:

            Nen Update mit Backitup war eigentlich konfiguriert, und sollte somit auf der SD-Karte schlummern.

            Ein Backup auf dem gleichen Datenträger ist keins.

            Linux-Werkzeugkasten:
            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
            NodeJS Fixer Skript:
            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

            O 1 Antwort Letzte Antwort
            1
            • GlasfaserG Glasfaser

              @olli-s sagte in ioBroker startet nach Update nicht mehr:

              Die Installation ist schon etwas älter, und frei nach dem Motto "never touch a running system"

              Niemals so denken !

              Leider fehlt mir grad mal wieder die Zeit.

              Das ist nicht mal eben .... in zwei , drei Befehlen zu reparieren ...

              Dann Warte die Woche und mache es Ordentlich .

              O Offline
              O Offline
              Olli-S
              schrieb am zuletzt editiert von
              #11

              @glasfaser

              Das ist mal wieder der Beweis, "der Schuster hat die schlechtesten Schuhe".
              Ich schlage mich mich ansonsten täglich mit nem 100 User Windwos-Netzwerk, mit allem drum und dran, rum.
              Da bleibt leider zu häufig die Muße bei den eigenen Systemen auf der Strecke ;)

              Ok, wie könnte ich überprüfen ob ich nen aktuelles Backup habe?

              VG

              Thomas BraunT 2 Antworten Letzte Antwort
              -1
              • Thomas BraunT Thomas Braun

                @olli-s sagte in ioBroker startet nach Update nicht mehr:

                Nen Update mit Backitup war eigentlich konfiguriert, und sollte somit auf der SD-Karte schlummern.

                Ein Backup auf dem gleichen Datenträger ist keins.

                O Offline
                O Offline
                Olli-S
                schrieb am zuletzt editiert von
                #12

                @thomas-braun
                Oh damn, das wäre echt suboptimal...

                O 1 Antwort Letzte Antwort
                0
                • O Olli-S

                  @glasfaser

                  Das ist mal wieder der Beweis, "der Schuster hat die schlechtesten Schuhe".
                  Ich schlage mich mich ansonsten täglich mit nem 100 User Windwos-Netzwerk, mit allem drum und dran, rum.
                  Da bleibt leider zu häufig die Muße bei den eigenen Systemen auf der Strecke ;)

                  Ok, wie könnte ich überprüfen ob ich nen aktuelles Backup habe?

                  VG

                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb am zuletzt editiert von
                  #13

                  @olli-s sagte in ioBroker startet nach Update nicht mehr:

                  Ich schlage mich mich ansonsten täglich mit nem 100 User Windwos-Netzwerk, mit allem drum und dran, rum.

                  Auch mit dem Denkfehler 'Never change a running system'?

                  Linux-Werkzeugkasten:
                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                  NodeJS Fixer Skript:
                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                  1 Antwort Letzte Antwort
                  1
                  • O Olli-S

                    @glasfaser

                    Das ist mal wieder der Beweis, "der Schuster hat die schlechtesten Schuhe".
                    Ich schlage mich mich ansonsten täglich mit nem 100 User Windwos-Netzwerk, mit allem drum und dran, rum.
                    Da bleibt leider zu häufig die Muße bei den eigenen Systemen auf der Strecke ;)

                    Ok, wie könnte ich überprüfen ob ich nen aktuelles Backup habe?

                    VG

                    Thomas BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    schrieb am zuletzt editiert von Thomas Braun
                    #14

                    @olli-s sagte in ioBroker startet nach Update nicht mehr:

                    Ok, wie könnte ich überprüfen ob ich nen aktuelles Backup habe?

                    System neuinstallieren, ioBroker neuinstallieren, Backup einspielen, schauen ob das Backup nicht auch schon Murks im Bauch hatte.

                    Linux-Werkzeugkasten:
                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                    NodeJS Fixer Skript:
                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                    1 Antwort Letzte Antwort
                    0
                    • O Olli-S

                      @thomas-braun
                      Oh damn, das wäre echt suboptimal...

                      O Offline
                      O Offline
                      Olli-S
                      schrieb am zuletzt editiert von
                      #15

                      Ich hab grad nochmal geschaut.
                      Habe hier noch vom letzten Migrationsversuch ne Backup "2020_11_19-13_47_34_backupiobroker.tar.gz"
                      Die ist zwar schon älter, aber seit dem hat sich jetzt auch nicht so viel verändert.

                      Aber das ist natürlich dann auch wieder der alte Schrunz.
                      Wahrscheinlich wär es doch sinnvoller das Ganze auf der grünen Wiese aufzusetzen, und keine Altlasten mitzuschleppen, oder?

                      Thomas BraunT 2 Antworten Letzte Antwort
                      0
                      • O Olli-S

                        Ich hab grad nochmal geschaut.
                        Habe hier noch vom letzten Migrationsversuch ne Backup "2020_11_19-13_47_34_backupiobroker.tar.gz"
                        Die ist zwar schon älter, aber seit dem hat sich jetzt auch nicht so viel verändert.

                        Aber das ist natürlich dann auch wieder der alte Schrunz.
                        Wahrscheinlich wär es doch sinnvoller das Ganze auf der grünen Wiese aufzusetzen, und keine Altlasten mitzuschleppen, oder?

                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #16

                        @olli-s sagte in ioBroker startet nach Update nicht mehr:

                        2020_11

                        Kannst du vergessen.

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        1 Antwort Letzte Antwort
                        0
                        • O Olli-S

                          Ich hab grad nochmal geschaut.
                          Habe hier noch vom letzten Migrationsversuch ne Backup "2020_11_19-13_47_34_backupiobroker.tar.gz"
                          Die ist zwar schon älter, aber seit dem hat sich jetzt auch nicht so viel verändert.

                          Aber das ist natürlich dann auch wieder der alte Schrunz.
                          Wahrscheinlich wär es doch sinnvoller das Ganze auf der grünen Wiese aufzusetzen, und keine Altlasten mitzuschleppen, oder?

                          Thomas BraunT Online
                          Thomas BraunT Online
                          Thomas Braun
                          Most Active
                          schrieb am zuletzt editiert von Thomas Braun
                          #17

                          @olli-s sagte in ioBroker startet nach Update nicht mehr:

                          aber seit dem hat sich jetzt auch nicht so viel verändert.

                          NodeJS-Version, das Datenbankformat, der js-controller, der Admin usw.
                          Aber sonst nix, stimmt.

                          Linux-Werkzeugkasten:
                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                          NodeJS Fixer Skript:
                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                          O 1 Antwort Letzte Antwort
                          0
                          • Thomas BraunT Thomas Braun

                            @olli-s sagte in ioBroker startet nach Update nicht mehr:

                            aber seit dem hat sich jetzt auch nicht so viel verändert.

                            NodeJS-Version, das Datenbankformat, der js-controller, der Admin usw.
                            Aber sonst nix, stimmt.

                            O Offline
                            O Offline
                            Olli-S
                            schrieb am zuletzt editiert von Olli-S
                            #18

                            @thomas-braun said in ioBroker startet nach Update nicht mehr:

                            Auch mit dem Denkfehler 'Never change a running system'?
                            Ganz sicher nicht, das ist Job, und nicht Hobby ^^

                            @olli-s sagte in ioBroker startet nach Update nicht mehr:

                            aber seit dem hat sich jetzt auch nicht so viel verändert.

                            NodeJS-Version, das Datenbankformat usw.
                            Aber sonst nix, stimmt.

                            Ich meinte nur dass sich nicht so viel in meiner Installation verändert hatte.
                            Dass sich ioBroker weiterentwickelt hat ist mir schon klar...

                            Thomas BraunT 1 Antwort Letzte Antwort
                            0
                            • O Olli-S

                              @thomas-braun said in ioBroker startet nach Update nicht mehr:

                              Auch mit dem Denkfehler 'Never change a running system'?
                              Ganz sicher nicht, das ist Job, und nicht Hobby ^^

                              @olli-s sagte in ioBroker startet nach Update nicht mehr:

                              aber seit dem hat sich jetzt auch nicht so viel verändert.

                              NodeJS-Version, das Datenbankformat usw.
                              Aber sonst nix, stimmt.

                              Ich meinte nur dass sich nicht so viel in meiner Installation verändert hatte.
                              Dass sich ioBroker weiterentwickelt hat ist mir schon klar...

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von Thomas Braun
                              #19

                              @olli-s

                              Das (ich setze es mal in Anführungszeichen) "Backup" wirst du nicht in eine frische Neuinstallation des ioBrokers einfach reinbekommen.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              O 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @olli-s

                                Das (ich setze es mal in Anführungszeichen) "Backup" wirst du nicht in eine frische Neuinstallation des ioBrokers einfach reinbekommen.

                                O Offline
                                O Offline
                                Olli-S
                                schrieb am zuletzt editiert von
                                #20

                                @thomas-braun said in ioBroker startet nach Update nicht mehr:

                                @olli-s

                                Das Backup wirst du nicht in eine frische Neuinstallation des ioBrokers einfach reinbekommen.

                                Das wird schon das Problem bei der letzten Migration gewesen sein.

                                Thomas BraunT 1 Antwort Letzte Antwort
                                0
                                • O Olli-S

                                  @thomas-braun said in ioBroker startet nach Update nicht mehr:

                                  @olli-s

                                  Das Backup wirst du nicht in eine frische Neuinstallation des ioBrokers einfach reinbekommen.

                                  Das wird schon das Problem bei der letzten Migration gewesen sein.

                                  Thomas BraunT Online
                                  Thomas BraunT Online
                                  Thomas Braun
                                  Most Active
                                  schrieb am zuletzt editiert von Thomas Braun
                                  #21

                                  @olli-s

                                  Das Ding ist ein klassischer Fall von 'Fahrlässige Tötung von Computersystemen durch Unterlassung von Updates'

                                  Das Rumgemurkse mit den Rechten hat dem Ding dann nur noch den Rest gegeben.

                                  Linux-Werkzeugkasten:
                                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                  NodeJS Fixer Skript:
                                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                  1 Antwort Letzte Antwort
                                  1
                                  • O Offline
                                    O Offline
                                    Olli-S
                                    schrieb am zuletzt editiert von
                                    #22

                                    @thomas-braun
                                    Ok, dann erstmal Danke für deine Zeit, und vor allem für die schnelle Reaktion.
                                    Dann lese ich mich "mal wieder" frisch ein (wenn du sagst dass sich substanziell in ioBroker soviel verändert hat), und überdenke ob ich weiterhin auf iBroker setze oder vielleicht mal was Neues probiere, wenn ich eh ganz von vorne anfangen muss.

                                    Ich muss gestehen dass mich der Updateprozess (zwingend über die Kommandezeile) beim ioBroker etwas abnervt.
                                    Wenn dabei was schief läuft, ist man als "Nicht-Linuxspezi" erstmal im Ansatz überfordert.

                                    Dann geh´s los:
                                    Durch zig Forenposts lesen, Sachen finden, bewerten und ggf. testen, um dann festzustellen dass diese schon wieder völlig outdated sind, man genau das Falsche gemacht hat, und damit dem System noch den Rest gegeben hat.
                                    Ich möchte gar nicht wissen wie das denen geht die gar keinen technischen Background haben....

                                    Auch wenn ich in der Vergangenheit immer auf ioBroker geschworen habe, bin ich grad etwas resigniert.

                                    Ich muss da mal drüber schlafen.
                                    Euch erstmal vielen Dank, noch nen schönen Restabend und viele Grüße.

                                    Thomas BraunT HomoranH 3 Antworten Letzte Antwort
                                    0
                                    • O Olli-S

                                      @thomas-braun
                                      Ok, dann erstmal Danke für deine Zeit, und vor allem für die schnelle Reaktion.
                                      Dann lese ich mich "mal wieder" frisch ein (wenn du sagst dass sich substanziell in ioBroker soviel verändert hat), und überdenke ob ich weiterhin auf iBroker setze oder vielleicht mal was Neues probiere, wenn ich eh ganz von vorne anfangen muss.

                                      Ich muss gestehen dass mich der Updateprozess (zwingend über die Kommandezeile) beim ioBroker etwas abnervt.
                                      Wenn dabei was schief läuft, ist man als "Nicht-Linuxspezi" erstmal im Ansatz überfordert.

                                      Dann geh´s los:
                                      Durch zig Forenposts lesen, Sachen finden, bewerten und ggf. testen, um dann festzustellen dass diese schon wieder völlig outdated sind, man genau das Falsche gemacht hat, und damit dem System noch den Rest gegeben hat.
                                      Ich möchte gar nicht wissen wie das denen geht die gar keinen technischen Background haben....

                                      Auch wenn ich in der Vergangenheit immer auf ioBroker geschworen habe, bin ich grad etwas resigniert.

                                      Ich muss da mal drüber schlafen.
                                      Euch erstmal vielen Dank, noch nen schönen Restabend und viele Grüße.

                                      Thomas BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      schrieb am zuletzt editiert von
                                      #23

                                      @olli-s sagte in ioBroker startet nach Update nicht mehr:

                                      (zwingend über die Kommandezeile) beim ioBroker etwas abnervt.

                                      Ist nicht zwingend über die Kommandozeile. Aber über die Kommandozeile ist es einfacher. Ein Desktop läuft ja auf einem Server eh nicht, da kann man auch die 5 Befehle die es dafür braucht benutzen.

                                      Linux-Werkzeugkasten:
                                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                      NodeJS Fixer Skript:
                                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                      1 Antwort Letzte Antwort
                                      0
                                      • O Olli-S

                                        @thomas-braun
                                        Ok, dann erstmal Danke für deine Zeit, und vor allem für die schnelle Reaktion.
                                        Dann lese ich mich "mal wieder" frisch ein (wenn du sagst dass sich substanziell in ioBroker soviel verändert hat), und überdenke ob ich weiterhin auf iBroker setze oder vielleicht mal was Neues probiere, wenn ich eh ganz von vorne anfangen muss.

                                        Ich muss gestehen dass mich der Updateprozess (zwingend über die Kommandezeile) beim ioBroker etwas abnervt.
                                        Wenn dabei was schief läuft, ist man als "Nicht-Linuxspezi" erstmal im Ansatz überfordert.

                                        Dann geh´s los:
                                        Durch zig Forenposts lesen, Sachen finden, bewerten und ggf. testen, um dann festzustellen dass diese schon wieder völlig outdated sind, man genau das Falsche gemacht hat, und damit dem System noch den Rest gegeben hat.
                                        Ich möchte gar nicht wissen wie das denen geht die gar keinen technischen Background haben....

                                        Auch wenn ich in der Vergangenheit immer auf ioBroker geschworen habe, bin ich grad etwas resigniert.

                                        Ich muss da mal drüber schlafen.
                                        Euch erstmal vielen Dank, noch nen schönen Restabend und viele Grüße.

                                        Thomas BraunT Online
                                        Thomas BraunT Online
                                        Thomas Braun
                                        Most Active
                                        schrieb am zuletzt editiert von
                                        #24

                                        @olli-s sagte in ioBroker startet nach Update nicht mehr:

                                        Durch zig Forenposts lesen, Sachen finden, bewerten und ggf. testen, um dann festzustellen dass diese schon wieder völlig outdated sind, man genau das Falsche gemacht hat, und damit dem System noch den Rest gegeben hat.

                                        Wenn man regelmäßig dabei bleibt, sein System auf stable fährt usw. ist es auch überhaupt kein Hexenwerk sich dann in die verbliebenen Änderungen reinzufuchsen.

                                        Linux-Werkzeugkasten:
                                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                        NodeJS Fixer Skript:
                                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                        1 Antwort Letzte Antwort
                                        0
                                        • O Olli-S

                                          @thomas-braun
                                          Ok, dann erstmal Danke für deine Zeit, und vor allem für die schnelle Reaktion.
                                          Dann lese ich mich "mal wieder" frisch ein (wenn du sagst dass sich substanziell in ioBroker soviel verändert hat), und überdenke ob ich weiterhin auf iBroker setze oder vielleicht mal was Neues probiere, wenn ich eh ganz von vorne anfangen muss.

                                          Ich muss gestehen dass mich der Updateprozess (zwingend über die Kommandezeile) beim ioBroker etwas abnervt.
                                          Wenn dabei was schief läuft, ist man als "Nicht-Linuxspezi" erstmal im Ansatz überfordert.

                                          Dann geh´s los:
                                          Durch zig Forenposts lesen, Sachen finden, bewerten und ggf. testen, um dann festzustellen dass diese schon wieder völlig outdated sind, man genau das Falsche gemacht hat, und damit dem System noch den Rest gegeben hat.
                                          Ich möchte gar nicht wissen wie das denen geht die gar keinen technischen Background haben....

                                          Auch wenn ich in der Vergangenheit immer auf ioBroker geschworen habe, bin ich grad etwas resigniert.

                                          Ich muss da mal drüber schlafen.
                                          Euch erstmal vielen Dank, noch nen schönen Restabend und viele Grüße.

                                          HomoranH Nicht stören
                                          HomoranH Nicht stören
                                          Homoran
                                          Global Moderator Administrators
                                          schrieb am zuletzt editiert von
                                          #25

                                          @olli-s sagte in ioBroker startet nach Update nicht mehr:

                                          Ich muss gestehen dass mich der Updateprozess (zwingend über die Kommandezeile) beim ioBroker etwas abnervt.

                                          wieso Zwingend?
                                          Backitup ist ein Adapter der im Admin konfiguriert wird.

                                          kein Support per PN! - Fragen im Forum stellen -
                                          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                                          Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                                          der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                                          Thomas BraunT 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          591

                                          Online

                                          32.7k

                                          Benutzer

                                          82.5k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe