Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • 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. ioBroker Allgemein
  4. [gelöst]Zigbee startet nach Update nicht mehr

NEWS

  • Neues YouTube-Video: Visualisierung im Devices-Adapter
    BluefoxB
    Bluefox
    11
    1
    322

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    1.9k

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    11
    1
    791

[gelöst]Zigbee startet nach Update nicht mehr

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
zigbee adpater
22 Beiträge 4 Kommentatoren 992 Aufrufe 4 Beobachtet
  • Ä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.
  • Thomas BraunT Thomas Braun

    @amg_666
    Man meldet sich auch nicht als root an.

    crunchipC Abwesend
    crunchipC Abwesend
    crunchip
    Forum Testing Most Active Developer
    schrieb am zuletzt editiert von
    #10

    @thomas-braun ist wahrscheinlich im proxmox terminal

    Ist es nicht noch ratsam den npm cache zu löschen?

    umgestiegen von Proxmox auf Unraid

    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • crunchipC crunchip

      @thomas-braun ist wahrscheinlich im proxmox terminal

      Ist es nicht noch ratsam den npm cache zu löschen?

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

      @crunchip

      Bei proxmox wäre der host anders, oder?

      Klar, npm cache kann man auch mal löschen.

      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
      • amg_666A Offline
        amg_666A Offline
        amg_666
        schrieb am zuletzt editiert von
        #12

        @thomas-braun ich geb heute abend mal ein update, npm cache clean probier ich aus.

        iobroker auf proxmox container

        1 Antwort Letzte Antwort
        0
        • amg_666A Offline
          amg_666A Offline
          amg_666
          schrieb am zuletzt editiert von
          #13

          @amg_666 Also, nochmal angemeldet, nicht über proxmox Konsole sondern über PuTTY und mit einem "normalen" user, nicht root.
          iobroker fixer:

          andreas@iobroker:/opt/iobroker$ curl -sL https://iobroker.net/fix.sh | bash -
          library: loaded
          Library version=2021-04-07
          
          ==========================================================================
          
              Welcome to the ioBroker installation fixer!
              Script version: 2021-04-07
          
              You might need to enter your password a couple of times.
          
          ==========================================================================
          
          
          ==========================================================================
              Installing prerequisites (1/3)
          ==========================================================================
          
          [sudo] password for andreas:
          Hit:1 http://security.debian.org buster/updates InRelease
          Hit:2 http://ftp.debian.org/debian buster InRelease
          Hit:3 http://ftp.debian.org/debian buster-updates InRelease
          Hit:4 https://deb.nodesource.com/node_14.x buster InRelease
          Reading package lists... Done
          Installed gcc-c++
          
          ==========================================================================
              Checking ioBroker user and directory permissions (2/3)
          ==========================================================================
          
          Created /etc/sudoers.d/iobroker
          Fixing directory permissions...
          
          ==========================================================================
              Checking autostart (3/3)
          ==========================================================================
          
          Enabling autostart...
          Autostart enabled!
          
          ==========================================================================
          
              Your installation was fixed successfully
              Run iobroker start to start ioBroker again!
          
          ==========================================================================
          
          andreas@iobroker:/opt/iobroker$ iobroker start
          
          

          npm cache clean habe ich nicht gemacht, weil er am meckern war dass das nicht notwendig ist:

          andreas@iobroker:/opt/iobroker$ npm cache clean
          npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data e                                                                                                                                                             xtracted from the cache is guaranteed to be valid. If you want to make sure ever                                                                                                                                                             ything is consistent, use 'npm cache verify' instead. On the other hand, if you'                                                                                                                                                             re debugging an issue with the installer, you can use `npm install --cache /tmp/                                                                                                                                                             empty-cache` to use a temporary cache instead of nuking the actual one.
          npm ERR!
          npm ERR! If you're sure you want to delete the entire cache, rerun this command                                                                                                                                                              with --force.
          
          npm ERR! A complete log of this run can be found in:
          npm ERR!     /home/andreas/.npm/_logs/2021-04-16T11_16_38_943Z-debug.log
          andreas@iobroker:/opt/iobroker$ npm cache clean
          npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one.
          npm ERR!
          npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
          
          npm ERR! A complete log of this run can be found in:
          npm ERR!     /home/andreas/.npm/_logs/2021-04-16T11_17_02_316Z-debug.log
          
          

          npm cache verifiy liefert

          andreas@iobroker:/opt/iobroker$ npm cache verify
          Cache verified and compressed (~/.npm/_cacache):
          Content verified: 1 (1535980 bytes)
          Content garbage-collected: 1 (1535980 bytes)
          Index entries: 1
          Finished in 0.129s
          

          Update des Adapters aus der Adminoberfläche liefert wieder den Fehler

          Fertig mit Fehler: internal/modules/cjs/loader.js:883 throw err; ^Error: Cannot find module 'mime'Require stack:- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js- /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15) at Function.Module._load (internal/modules/cjs/loader.js:725:27) at Module.require (internal/modules/cjs/loader.js:952:19) at require (internal/modules/cjs/helpers.js:88:18) at Upload.uploadAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js:525:24) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:225:28 at installNpm (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2557:9) at finishUpgrade (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:205:13) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:419:21 at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupInstall.js:223:55 { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ]}
          

          log bringt danach Fehler auch bei anderen Adaptern:

          host.iobroker	2021-04-16 13:48:01.038	error	Please consider running the installation fixer when on Linux.
          host.iobroker	2021-04-16 13:48:01.037	error	could not store process id list in /opt/iobroker/node_modules/iobroker.js-controller/pids.txt! Please check permissions and user ownership of this file. Was ioBroker started as a different user? Pleas
          host.iobroker	2021-04-16 13:48:00.154	error	instance system.adapter.daswetter.0 terminated with code 10 (CANNOT_FIND_ADAPTER_DIR)
          host.iobroker	2021-04-16 13:48:00.036	info	instance system.adapter.daswetter.0 started with pid 4600
          host.iobroker	2021-04-16 13:45:33.904	info	iobroker exit 1
          host.iobroker	2021-04-16 13:45:33.894	error	iobroker internal/modules/cjs/loader.js:883 throw err; ^Error: Cannot find module 'mime'Require stack:- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js- /opt/iobroker/node
          host.iobroker	2021-04-16 13:45:01.042	error	Please consider running the installation fixer when on Linux.
          host.iobroker	2021-04-16 13:45:01.041	error	could not store process id list in /opt/iobroker/node_modules/iobroker.js-controller/pids.txt! Please check permissions and user ownership of this file. Was ioBroker started as a different user? Pleas
          host.iobroker	2021-04-16 13:45:00.238	error	instance system.adapter.ical.3 terminated with code 10 (CANNOT_FIND_ADAPTER_DIR)
          host.iobroker	2021-04-16 13:45:00.040	info	instance system.adapter.ical.3 started with pid 4593
          smartmeter.0	2021-04-16 13:44:42.876	info	(13972) Received 10 values, 5 updated
          javascript.0	2021-04-16 13:44:09.934	info	(3766) script.js.common.Statusanzeige_gross: request: http://192.168.2.82/cm?cmnd=Led11 0,0,0
          web.0	2021-04-16 13:44:08.366	info	(3962) ==>Connected system.user.admin from ::ffff:192.168.2.105
          web.0	2021-04-16 13:44:08.298	info	(3962) <==Disconnect system.user.admin from ::ffff:192.168.2.105 flot
          host.iobroker	2021-04-16 13:43:47.278	info	iobroker info sharp Using cached /home/iobroker/.npm/_libvips/libvips-8.10.0-linux-x64.tar.br
          host.iobroker	2021-04-16 13:40:09.986	info	instance system.adapter.ical.2 terminated with code 0 (NO_ERROR)
          ical.2	2021-04-16 13:40:09.408	info	(4261) Terminated (NO_ERROR): Without reason
          ical.2	2021-04-16 13:40:04.076	info	(4261) processing URL: Geburtstag https://calendar.google.com/calendar/ical/lqbnk2mjfq76g1pq1mg0v962q4%40group.calendar.google.com/private-3381bd6686823f0e378489decbeb2378/basic.ics
          host.iobroker	2021-04-16 13:40:03.751	info	instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          host.iobroker	2021-04-16 13:40:03.490	info	iobroker NPM version: 6.14.12npm install iobroker.zigbee@1.5.1 --loglevel error --prefix "/opt/iobroker" (System call)
          ical.2	2021-04-16 13:40:03.097	info	(4261) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.ical, node: v14.16.1, js-controller: 3.2.16
          zigbee.0	2021-04-16 13:40:03.118	info	(3977) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          zigbee.0	2021-04-16 13:40:03.117	info	(3977) terminating
          zigbee.0	2021-04-16 13:40:02.783	info	(3977) Zigbee: disabling joining new devices.
          zigbee.0	2021-04-16 13:40:02.781	info	(3977) cleaned everything up...
          zigbee.0	2021-04-16 13:40:02.780	info	(3977) Got terminate signal TERMINATE_YOURSELF
          host.iobroker	2021-04-16 13:40:02.820	info	stopInstance system.adapter.zigbee.0 send kill signal
          host.iobroker	2021-04-16 13:40:02.763	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
          host.iobroker	2021-04-16 13:40:02.762	info	"system.adapter.zigbee.0" disabled
          host.iobroker	2021-04-16 13:40:02.709	info	iobroker host.iobroker Adapter "system.adapter.zigbee.0" is stopped.
          host.iobroker	2021-04-16 13:40:02.637	info	iobroker Update zigbee from @1.4.4 to @1.5.1
          host.iobroker	2021-04-16 13:40:00.449	info	instance system.adapter.ical.2 started with pid 4261
          host.iobroker	2021-04-16 13:40:00.203	info	iobroker upgrade zigbee
          

          iobroker auf proxmox container

          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • amg_666A amg_666

            @amg_666 Also, nochmal angemeldet, nicht über proxmox Konsole sondern über PuTTY und mit einem "normalen" user, nicht root.
            iobroker fixer:

            andreas@iobroker:/opt/iobroker$ curl -sL https://iobroker.net/fix.sh | bash -
            library: loaded
            Library version=2021-04-07
            
            ==========================================================================
            
                Welcome to the ioBroker installation fixer!
                Script version: 2021-04-07
            
                You might need to enter your password a couple of times.
            
            ==========================================================================
            
            
            ==========================================================================
                Installing prerequisites (1/3)
            ==========================================================================
            
            [sudo] password for andreas:
            Hit:1 http://security.debian.org buster/updates InRelease
            Hit:2 http://ftp.debian.org/debian buster InRelease
            Hit:3 http://ftp.debian.org/debian buster-updates InRelease
            Hit:4 https://deb.nodesource.com/node_14.x buster InRelease
            Reading package lists... Done
            Installed gcc-c++
            
            ==========================================================================
                Checking ioBroker user and directory permissions (2/3)
            ==========================================================================
            
            Created /etc/sudoers.d/iobroker
            Fixing directory permissions...
            
            ==========================================================================
                Checking autostart (3/3)
            ==========================================================================
            
            Enabling autostart...
            Autostart enabled!
            
            ==========================================================================
            
                Your installation was fixed successfully
                Run iobroker start to start ioBroker again!
            
            ==========================================================================
            
            andreas@iobroker:/opt/iobroker$ iobroker start
            
            

            npm cache clean habe ich nicht gemacht, weil er am meckern war dass das nicht notwendig ist:

            andreas@iobroker:/opt/iobroker$ npm cache clean
            npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data e                                                                                                                                                             xtracted from the cache is guaranteed to be valid. If you want to make sure ever                                                                                                                                                             ything is consistent, use 'npm cache verify' instead. On the other hand, if you'                                                                                                                                                             re debugging an issue with the installer, you can use `npm install --cache /tmp/                                                                                                                                                             empty-cache` to use a temporary cache instead of nuking the actual one.
            npm ERR!
            npm ERR! If you're sure you want to delete the entire cache, rerun this command                                                                                                                                                              with --force.
            
            npm ERR! A complete log of this run can be found in:
            npm ERR!     /home/andreas/.npm/_logs/2021-04-16T11_16_38_943Z-debug.log
            andreas@iobroker:/opt/iobroker$ npm cache clean
            npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one.
            npm ERR!
            npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
            
            npm ERR! A complete log of this run can be found in:
            npm ERR!     /home/andreas/.npm/_logs/2021-04-16T11_17_02_316Z-debug.log
            
            

            npm cache verifiy liefert

            andreas@iobroker:/opt/iobroker$ npm cache verify
            Cache verified and compressed (~/.npm/_cacache):
            Content verified: 1 (1535980 bytes)
            Content garbage-collected: 1 (1535980 bytes)
            Index entries: 1
            Finished in 0.129s
            

            Update des Adapters aus der Adminoberfläche liefert wieder den Fehler

            Fertig mit Fehler: internal/modules/cjs/loader.js:883 throw err; ^Error: Cannot find module 'mime'Require stack:- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js- /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15) at Function.Module._load (internal/modules/cjs/loader.js:725:27) at Module.require (internal/modules/cjs/loader.js:952:19) at require (internal/modules/cjs/helpers.js:88:18) at Upload.uploadAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js:525:24) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:225:28 at installNpm (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2557:9) at finishUpgrade (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:205:13) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:419:21 at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupInstall.js:223:55 { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ]}
            

            log bringt danach Fehler auch bei anderen Adaptern:

            host.iobroker	2021-04-16 13:48:01.038	error	Please consider running the installation fixer when on Linux.
            host.iobroker	2021-04-16 13:48:01.037	error	could not store process id list in /opt/iobroker/node_modules/iobroker.js-controller/pids.txt! Please check permissions and user ownership of this file. Was ioBroker started as a different user? Pleas
            host.iobroker	2021-04-16 13:48:00.154	error	instance system.adapter.daswetter.0 terminated with code 10 (CANNOT_FIND_ADAPTER_DIR)
            host.iobroker	2021-04-16 13:48:00.036	info	instance system.adapter.daswetter.0 started with pid 4600
            host.iobroker	2021-04-16 13:45:33.904	info	iobroker exit 1
            host.iobroker	2021-04-16 13:45:33.894	error	iobroker internal/modules/cjs/loader.js:883 throw err; ^Error: Cannot find module 'mime'Require stack:- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js- /opt/iobroker/node
            host.iobroker	2021-04-16 13:45:01.042	error	Please consider running the installation fixer when on Linux.
            host.iobroker	2021-04-16 13:45:01.041	error	could not store process id list in /opt/iobroker/node_modules/iobroker.js-controller/pids.txt! Please check permissions and user ownership of this file. Was ioBroker started as a different user? Pleas
            host.iobroker	2021-04-16 13:45:00.238	error	instance system.adapter.ical.3 terminated with code 10 (CANNOT_FIND_ADAPTER_DIR)
            host.iobroker	2021-04-16 13:45:00.040	info	instance system.adapter.ical.3 started with pid 4593
            smartmeter.0	2021-04-16 13:44:42.876	info	(13972) Received 10 values, 5 updated
            javascript.0	2021-04-16 13:44:09.934	info	(3766) script.js.common.Statusanzeige_gross: request: http://192.168.2.82/cm?cmnd=Led11 0,0,0
            web.0	2021-04-16 13:44:08.366	info	(3962) ==>Connected system.user.admin from ::ffff:192.168.2.105
            web.0	2021-04-16 13:44:08.298	info	(3962) <==Disconnect system.user.admin from ::ffff:192.168.2.105 flot
            host.iobroker	2021-04-16 13:43:47.278	info	iobroker info sharp Using cached /home/iobroker/.npm/_libvips/libvips-8.10.0-linux-x64.tar.br
            host.iobroker	2021-04-16 13:40:09.986	info	instance system.adapter.ical.2 terminated with code 0 (NO_ERROR)
            ical.2	2021-04-16 13:40:09.408	info	(4261) Terminated (NO_ERROR): Without reason
            ical.2	2021-04-16 13:40:04.076	info	(4261) processing URL: Geburtstag https://calendar.google.com/calendar/ical/lqbnk2mjfq76g1pq1mg0v962q4%40group.calendar.google.com/private-3381bd6686823f0e378489decbeb2378/basic.ics
            host.iobroker	2021-04-16 13:40:03.751	info	instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
            host.iobroker	2021-04-16 13:40:03.490	info	iobroker NPM version: 6.14.12npm install iobroker.zigbee@1.5.1 --loglevel error --prefix "/opt/iobroker" (System call)
            ical.2	2021-04-16 13:40:03.097	info	(4261) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.ical, node: v14.16.1, js-controller: 3.2.16
            zigbee.0	2021-04-16 13:40:03.118	info	(3977) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
            zigbee.0	2021-04-16 13:40:03.117	info	(3977) terminating
            zigbee.0	2021-04-16 13:40:02.783	info	(3977) Zigbee: disabling joining new devices.
            zigbee.0	2021-04-16 13:40:02.781	info	(3977) cleaned everything up...
            zigbee.0	2021-04-16 13:40:02.780	info	(3977) Got terminate signal TERMINATE_YOURSELF
            host.iobroker	2021-04-16 13:40:02.820	info	stopInstance system.adapter.zigbee.0 send kill signal
            host.iobroker	2021-04-16 13:40:02.763	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
            host.iobroker	2021-04-16 13:40:02.762	info	"system.adapter.zigbee.0" disabled
            host.iobroker	2021-04-16 13:40:02.709	info	iobroker host.iobroker Adapter "system.adapter.zigbee.0" is stopped.
            host.iobroker	2021-04-16 13:40:02.637	info	iobroker Update zigbee from @1.4.4 to @1.5.1
            host.iobroker	2021-04-16 13:40:00.449	info	instance system.adapter.ical.2 started with pid 4261
            host.iobroker	2021-04-16 13:40:00.203	info	iobroker upgrade zigbee
            
            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            schrieb am zuletzt editiert von
            #14

            @amg_666 sagte in Zigbee startet nach Update nicht mehr:

            Please check permissions and user ownership of this file. Was ioBroker started as a different user?

            Und?
            Das kann vom root-login kommen. Damit kann man sich ganz wunderbar das System zerfriemeln. Deswegen nutzt man den halt auch nicht.

            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

            amg_666A 1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @amg_666 sagte in Zigbee startet nach Update nicht mehr:

              Please check permissions and user ownership of this file. Was ioBroker started as a different user?

              Und?
              Das kann vom root-login kommen. Damit kann man sich ganz wunderbar das System zerfriemeln. Deswegen nutzt man den halt auch nicht.

              amg_666A Offline
              amg_666A Offline
              amg_666
              schrieb am zuletzt editiert von
              #15

              @thomas-braun Also neu aufsetzen und dann ein Backup einspielen, oder?

              iobroker auf proxmox container

              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • amg_666A amg_666

                @thomas-braun Also neu aufsetzen und dann ein Backup einspielen, oder?

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

                @amg_666
                Keine Ahnung. Musst du wissen, was du machen willst oder musst.

                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
                • amg_666A Offline
                  amg_666A Offline
                  amg_666
                  schrieb am zuletzt editiert von
                  #17

                  @thomas-braun sagte in Zigbee startet nach Update nicht mehr:

                  Musst du wissen, was du machen willst oder musst.

                  Wenn ich das wüsste, dann würde ich die Frage ja nicht posten :-)
                  Aber mal im Ernst: Durch Root kann ich mir diverse Rechte "zerschießen" und ich dachte dass das doch genau ein Thema ist, was derr Fixer korrigiert (?)

                  iobroker auf proxmox container

                  Thomas BraunT 1 Antwort Letzte Antwort
                  0
                  • amg_666A amg_666

                    @thomas-braun sagte in Zigbee startet nach Update nicht mehr:

                    Musst du wissen, was du machen willst oder musst.

                    Wenn ich das wüsste, dann würde ich die Frage ja nicht posten :-)
                    Aber mal im Ernst: Durch Root kann ich mir diverse Rechte "zerschießen" und ich dachte dass das doch genau ein Thema ist, was derr Fixer korrigiert (?)

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

                    @amg_666

                    Der Fixer ist aber auch nicht der Wunderheiler für verbogene Systeme. Das kann funktionieren, muss aber nicht. Kommt halt darauf an was da genau verfummelt wurde.
                    Besser halt erst gar nicht per unnötigem root-login das System kaputt machen.

                    Wenn du nicht weißt wo da anzusetzen ist: Installier es neu.

                    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
                    • amg_666A Offline
                      amg_666A Offline
                      amg_666
                      schrieb am zuletzt editiert von
                      #19

                      @thomas-braun Ich setz es auf gelöst :-)

                      1. Bei den fehlerhaften Installationen hat er ja maßgeblich js-controller Module angemeckert die angeblich nicht vorhanden sind. Ich habe jetzt mit
                      npm install iobroker.js-controller
                      

                      den js-controller neu installiert und da kamen dann einige Unstimmigkeiten (unkompatible Funktionstypen, falsche lockfile Versionen etc)
                      Nach Installation ließ sich iobroker nicht starten , also nochmal fixer und jetzt läuft es und auch der zigbee ging ohne Probleme auf die neue Version.

                      npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@                                                                                                                                              1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my                                                                                                                                                              best with it!
                      
                      > iobroker.js-controller@3.2.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller
                      > node lib/preinstallCheck.js
                      
                      NPM version: 6.14.12
                      
                      > epoll@2.0.10 install /opt/iobroker/node_modules/epoll
                      > node-gyp rebuild
                      
                      make: Entering directory '/opt/iobroker/node_modules/epoll/build'
                        CXX(target) Release/obj.target/epoll/src/epoll.o
                        SOLINK_MODULE(target) Release/obj.target/epoll.node
                        COPY Release/epoll.node
                      make: Leaving directory '/opt/iobroker/node_modules/epoll/build'
                      
                      > bufferutil@4.0.3 install /opt/iobroker/node_modules/bufferutil
                      > node-gyp-build
                      
                      
                      > unix-dgram@2.0.3 install /opt/iobroker/node_modules/unix-dgram
                      > node-gyp rebuild
                      
                      make: Entering directory '/opt/iobroker/node_modules/unix-dgram/build'
                        CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o
                      In file included from ../../nan/nan.h:56,
                                       from ../src/unix_dgram.cc:5:
                      /home/iobroker/.cache/node-gyp/14.16.1/include/node/node.h:758:43: warning: cast between incompatible function types from 'void (*)(v8::Local<v8::Object>)' to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
                             (node::addon_register_func) (regfunc),                          \
                                                                 ^
                      /home/iobroker/.cache/node-gyp/14.16.1/include/node/node.h:792:3: note: in expansion of macro 'NODE_MODULE_X'
                         NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                         ^~~~~~~~~~~~~
                      ../src/unix_dgram.cc:404:1: note: in expansion of macro 'NODE_MODULE'
                       NODE_MODULE(unix_dgram, Initialize)
                       ^~~~~~~~~~~
                        SOLINK_MODULE(target) Release/obj.target/unix_dgram.node
                        COPY Release/unix_dgram.node
                      make: Leaving directory '/opt/iobroker/node_modules/unix-dgram/build'
                      
                      > ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional
                      > node rebuild.js
                      
                      ursaNative bindings compilation fail. This is not an issue. Modules that depend on it will use fallbacks.
                      
                      > utf-8-validate@5.0.4 install /opt/iobroker/node_modules/utf-8-validate
                      > node-gyp-build
                      
                      
                      > canvas@2.7.0 install /opt/iobroker/node_modules/canvas
                      > node-pre-gyp install --fallback-to-build
                      
                      node-pre-gyp WARN Using request for node-pre-gyp https download
                      [canvas] Success: "/opt/iobroker/node_modules/canvas/build/Release/canvas.node" is installed via remote
                      
                      > @serialport/bindings@9.0.7 install /opt/iobroker/node_modules/@serialport/bindings
                      > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
                      
                      
                      > sharp@0.26.2 install /opt/iobroker/node_modules/sharp
                      > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
                      
                      info sharp Using cached /home/iobroker/.npm/_libvips/libvips-8.10.0-linux-x64.tar.br
                      
                      > @serialport/bindings@9.0.4 install /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                      > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
                      
                      
                      > @serialport/bindings@9.0.4 install /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                      > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
                      
                      
                      > diskusage@1.1.3 install /opt/iobroker/node_modules/diskusage
                      > node-gyp rebuild
                      
                      make: Entering directory '/opt/iobroker/node_modules/diskusage/build'
                        CXX(target) Release/obj.target/diskusage/src/main.o
                      In file included from ../../nan/nan.h:56,
                                       from ../src/main.cpp:3:
                      /home/iobroker/.cache/node-gyp/14.16.1/include/node/node.h:758:43: warning: cast between incompatible function types from 'void (*)(v8::Local<v8::Object>)' to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
                             (node::addon_register_func) (regfunc),                          \
                                                                 ^
                      /home/iobroker/.cache/node-gyp/14.16.1/include/node/node.h:792:3: note: in expansion of macro 'NODE_MODULE_X'
                         NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                         ^~~~~~~~~~~~~
                      ../src/main.cpp:42:1: note: in expansion of macro 'NODE_MODULE'
                       NODE_MODULE(diskusage, Init)
                       ^~~~~~~~~~~
                        CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o
                        SOLINK_MODULE(target) Release/obj.target/diskusage.node
                        COPY Release/diskusage.node
                      make: Leaving directory '/opt/iobroker/node_modules/diskusage/build'
                      
                      > iobroker.vis@1.3.8 install /opt/iobroker/node_modules/iobroker.vis
                      > node main.js --install
                      
                      
                      > iobroker.js-controller@3.2.16 install /opt/iobroker/node_modules/iobroker.js-controller
                      > node iobroker.js setup first
                      
                      object _design/system updated
                      
                      The following notifications happened during sync:
                      - Ignoring Directory "hm-rega" because officially not created as meta object. Please remove directory!
                      
                      ioBroker configuration updated
                      
                      > @root/acme@3.1.0 postinstall /opt/iobroker/node_modules/@root/acme
                      > node scripts/postinstall
                      
                      
                      > core-js@3.10.0 postinstall /opt/iobroker/node_modules/core-js
                      > node -e "try{require('./postinstall')}catch(e){}"
                      
                      Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
                      
                      The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
                      > https://opencollective.com/core-js
                      > https://www.patreon.com/zloirock
                      
                      Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
                      
                      
                      > serialport@9.0.6 postinstall /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/serialport
                      > node thank-you.js
                      
                      Thank you for using serialport!
                      If you rely on this package, please consider supporting our open collective:
                      > https://opencollective.com/serialport/donate
                      
                      
                      
                      > serialport@9.0.6 postinstall /opt/iobroker/node_modules/zigbee-herdsman/node_modules/serialport
                      > node thank-you.js
                      
                      Thank you for using serialport!
                      If you rely on this package, please consider supporting our open collective:
                      > https://opencollective.com/serialport/donate
                      
                      
                      
                      > iobroker.javascript@5.1.3 postinstall /opt/iobroker/node_modules/iobroker.javascript
                      > node ./install/installTypings.js
                      
                      Installing NodeJS typings...
                      latest @types: 14, installed node: 14
                      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (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":"x64"})
                      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/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":"x64"})
                      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/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":"x64"})
                      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/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":"x64"})
                      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (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":"x64"})
                      
                      + iobroker.js-controller@3.2.16
                      added 2480 packages from 458 contributors, removed 5 packages and updated 1628 packages in 296.338s
                      
                      137 packages are looking for funding
                        run `npm fund` for details
                      
                      

                      iobroker auf proxmox container

                      Thomas BraunT 1 Antwort Letzte Antwort
                      0
                      • amg_666A amg_666

                        @thomas-braun Ich setz es auf gelöst :-)

                        1. Bei den fehlerhaften Installationen hat er ja maßgeblich js-controller Module angemeckert die angeblich nicht vorhanden sind. Ich habe jetzt mit
                        npm install iobroker.js-controller
                        

                        den js-controller neu installiert und da kamen dann einige Unstimmigkeiten (unkompatible Funktionstypen, falsche lockfile Versionen etc)
                        Nach Installation ließ sich iobroker nicht starten , also nochmal fixer und jetzt läuft es und auch der zigbee ging ohne Probleme auf die neue Version.

                        npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@                                                                                                                                              1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my                                                                                                                                                              best with it!
                        
                        > iobroker.js-controller@3.2.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller
                        > node lib/preinstallCheck.js
                        
                        NPM version: 6.14.12
                        
                        > epoll@2.0.10 install /opt/iobroker/node_modules/epoll
                        > node-gyp rebuild
                        
                        make: Entering directory '/opt/iobroker/node_modules/epoll/build'
                          CXX(target) Release/obj.target/epoll/src/epoll.o
                          SOLINK_MODULE(target) Release/obj.target/epoll.node
                          COPY Release/epoll.node
                        make: Leaving directory '/opt/iobroker/node_modules/epoll/build'
                        
                        > bufferutil@4.0.3 install /opt/iobroker/node_modules/bufferutil
                        > node-gyp-build
                        
                        
                        > unix-dgram@2.0.3 install /opt/iobroker/node_modules/unix-dgram
                        > node-gyp rebuild
                        
                        make: Entering directory '/opt/iobroker/node_modules/unix-dgram/build'
                          CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o
                        In file included from ../../nan/nan.h:56,
                                         from ../src/unix_dgram.cc:5:
                        /home/iobroker/.cache/node-gyp/14.16.1/include/node/node.h:758:43: warning: cast between incompatible function types from 'void (*)(v8::Local<v8::Object>)' to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
                               (node::addon_register_func) (regfunc),                          \
                                                                   ^
                        /home/iobroker/.cache/node-gyp/14.16.1/include/node/node.h:792:3: note: in expansion of macro 'NODE_MODULE_X'
                           NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                           ^~~~~~~~~~~~~
                        ../src/unix_dgram.cc:404:1: note: in expansion of macro 'NODE_MODULE'
                         NODE_MODULE(unix_dgram, Initialize)
                         ^~~~~~~~~~~
                          SOLINK_MODULE(target) Release/obj.target/unix_dgram.node
                          COPY Release/unix_dgram.node
                        make: Leaving directory '/opt/iobroker/node_modules/unix-dgram/build'
                        
                        > ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional
                        > node rebuild.js
                        
                        ursaNative bindings compilation fail. This is not an issue. Modules that depend on it will use fallbacks.
                        
                        > utf-8-validate@5.0.4 install /opt/iobroker/node_modules/utf-8-validate
                        > node-gyp-build
                        
                        
                        > canvas@2.7.0 install /opt/iobroker/node_modules/canvas
                        > node-pre-gyp install --fallback-to-build
                        
                        node-pre-gyp WARN Using request for node-pre-gyp https download
                        [canvas] Success: "/opt/iobroker/node_modules/canvas/build/Release/canvas.node" is installed via remote
                        
                        > @serialport/bindings@9.0.7 install /opt/iobroker/node_modules/@serialport/bindings
                        > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
                        
                        
                        > sharp@0.26.2 install /opt/iobroker/node_modules/sharp
                        > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
                        
                        info sharp Using cached /home/iobroker/.npm/_libvips/libvips-8.10.0-linux-x64.tar.br
                        
                        > @serialport/bindings@9.0.4 install /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                        > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
                        
                        
                        > @serialport/bindings@9.0.4 install /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                        > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
                        
                        
                        > diskusage@1.1.3 install /opt/iobroker/node_modules/diskusage
                        > node-gyp rebuild
                        
                        make: Entering directory '/opt/iobroker/node_modules/diskusage/build'
                          CXX(target) Release/obj.target/diskusage/src/main.o
                        In file included from ../../nan/nan.h:56,
                                         from ../src/main.cpp:3:
                        /home/iobroker/.cache/node-gyp/14.16.1/include/node/node.h:758:43: warning: cast between incompatible function types from 'void (*)(v8::Local<v8::Object>)' to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
                               (node::addon_register_func) (regfunc),                          \
                                                                   ^
                        /home/iobroker/.cache/node-gyp/14.16.1/include/node/node.h:792:3: note: in expansion of macro 'NODE_MODULE_X'
                           NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                           ^~~~~~~~~~~~~
                        ../src/main.cpp:42:1: note: in expansion of macro 'NODE_MODULE'
                         NODE_MODULE(diskusage, Init)
                         ^~~~~~~~~~~
                          CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o
                          SOLINK_MODULE(target) Release/obj.target/diskusage.node
                          COPY Release/diskusage.node
                        make: Leaving directory '/opt/iobroker/node_modules/diskusage/build'
                        
                        > iobroker.vis@1.3.8 install /opt/iobroker/node_modules/iobroker.vis
                        > node main.js --install
                        
                        
                        > iobroker.js-controller@3.2.16 install /opt/iobroker/node_modules/iobroker.js-controller
                        > node iobroker.js setup first
                        
                        object _design/system updated
                        
                        The following notifications happened during sync:
                        - Ignoring Directory "hm-rega" because officially not created as meta object. Please remove directory!
                        
                        ioBroker configuration updated
                        
                        > @root/acme@3.1.0 postinstall /opt/iobroker/node_modules/@root/acme
                        > node scripts/postinstall
                        
                        
                        > core-js@3.10.0 postinstall /opt/iobroker/node_modules/core-js
                        > node -e "try{require('./postinstall')}catch(e){}"
                        
                        Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
                        
                        The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
                        > https://opencollective.com/core-js
                        > https://www.patreon.com/zloirock
                        
                        Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
                        
                        
                        > serialport@9.0.6 postinstall /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/serialport
                        > node thank-you.js
                        
                        Thank you for using serialport!
                        If you rely on this package, please consider supporting our open collective:
                        > https://opencollective.com/serialport/donate
                        
                        
                        
                        > serialport@9.0.6 postinstall /opt/iobroker/node_modules/zigbee-herdsman/node_modules/serialport
                        > node thank-you.js
                        
                        Thank you for using serialport!
                        If you rely on this package, please consider supporting our open collective:
                        > https://opencollective.com/serialport/donate
                        
                        
                        
                        > iobroker.javascript@5.1.3 postinstall /opt/iobroker/node_modules/iobroker.javascript
                        > node ./install/installTypings.js
                        
                        Installing NodeJS typings...
                        latest @types: 14, installed node: 14
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (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":"x64"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/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":"x64"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/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":"x64"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/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":"x64"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (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":"x64"})
                        
                        + iobroker.js-controller@3.2.16
                        added 2480 packages from 458 contributors, removed 5 packages and updated 1628 packages in 296.338s
                        
                        137 packages are looking for funding
                          run `npm fund` for details
                        
                        
                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von Thomas Braun
                        #20

                        @amg_666
                        Über npm installiert man das ja auch anders:

                        cd /opt/iobroker
                        sudo -H -u iobroker npm install iobroker.js-controller
                        

                        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
                        • amg_666A Offline
                          amg_666A Offline
                          amg_666
                          schrieb am zuletzt editiert von
                          #21

                          @thomas-braun im how-to steht unter Punkt 3 d) nur npm install..., da hatte ich das her.
                          Aber jetzt läufts ja, insofern ist es für mich ok.

                          iobroker auf proxmox container

                          Thomas BraunT 1 Antwort Letzte Antwort
                          0
                          • amg_666A amg_666

                            @thomas-braun im how-to steht unter Punkt 3 d) nur npm install..., da hatte ich das her.
                            Aber jetzt läufts ja, insofern ist es für mich ok.

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

                            @amg_666 Mal geschaut von wann das HowTo ist?

                            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

                            Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

                            Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

                            Mit deinem Input könnte dieser Beitrag noch besser werden 💗

                            Registrieren Anmelden
                            Antworten
                            • In einem neuen Thema antworten
                            Anmelden zum Antworten
                            • Älteste zuerst
                            • Neuste zuerst
                            • Meiste Stimmen


                            Support us

                            ioBroker
                            Community Adapters
                            Donate
                            FAQ Cloud / IOT
                            HowTo: Node.js-Update
                            HowTo: Backup/Restore
                            Downloads
                            BLOG

                            557

                            Online

                            32.9k

                            Benutzer

                            83.0k

                            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