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

  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 4.0 jetzt im BETA/LATEST!

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.4k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.5k

js-controller 4.0 jetzt im BETA/LATEST!

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
747 Beiträge 70 Kommentatoren 225.0k Aufrufe 60 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.
  • JB_SullivanJ Offline
    JB_SullivanJ Offline
    JB_Sullivan
    schrieb am zuletzt editiert von
    #375

    Nur mal so für mich als Windows Onkel zur eigenen Beruhigung - die Meldungen sind unkritisch?

    Beim Update non der 3.3 auf 4.0.9hatte ich in der Konsole ja einen ganzen Sack voll (Fehler)Meldungen - siehe weiter oben.

    Jetzt auf die 4.0.10 sind es andere Meldunugen. Da aber alles läuft, scheint das unkritisch zu sein? Das was im Code als REMOVE angegeben ist, kann ich auch gefahrlos löschen?

    > iobroker.js-controller@4.0.10 install C:\iobroker\GLT\node_modules\iobroker.js-controller
    > node iobroker.js setup first
    
    Successfully migrated 22812 objects to Redis Sets
    object _design/system updated
    
    The following notifications happened during sync:
    - Ignoring Directory "heatingcontrol.admin" because officially not created as meta object. Please remove directory!
    - Ignoring Directory "ping.admin" because officially not created as meta object. Please remove directory!
    - Ignoring Directory "vis-test" because officially not created as meta object. Please remove directory!
    
    {
      "defaultPrivate": "-----BEGIN RSA PRIVATE KEY-----Viel Key Code hierzwischen-----END RSA PRIVATE KEY-----\r\n",
    
      "defaultPublic": "-----BEGIN CERTIFICATE-----VIEL Code hier zwischen-----END CERTIFICATE-----\r\n"
    }
    Update certificate defaultPrivate
    The object "system.certificates" was updated successfully.
    Update certificate defaultPublic
    The object "system.certificates" was updated successfully.
    + iobroker.js-controller@4.0.10
    removed 6 packages, updated 23 packages and audited 2522 packages in 67.268s
    
    182 packages are looking for funding
      run `npm fund` for details
    
    found 182 vulnerabilities (18 low, 82 moderate, 76 high, 6 critical)
      run `npm audit fix` to fix them, or `npm audit` for details
    

    ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

    apollon77A 1 Antwort Letzte Antwort
    0
    • apollon77A apollon77

      @crunchip Ja bitte issues wenn es keine gibt. Am Ende ist es so: Wir nutzen das Redis Protokoll zur Kommunikation mit der DB ... egal ob echter oder unserer eigenen DB ...

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

      @apollon77 wie im anderen Thread erwähnt, bleibt meine CPU nun auch oben
      deshalb habe ich nun mal iob gestoppt und die ganze VM neu gestartet
      diesmal kam der nut Adapter noch dazu

      kommen die Host error aufgrund der "fehlerhaften" Adapter, oder durch etwas anderes?

      2022-02-16 11:36:07.841 - info: javascript.0 (14587) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2022-02-16 11:36:08.103 - info: history.0 (14352) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2022-02-16 11:36:08.133 - info: web.0 (16885) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2022-02-16 11:36:08.135 - info: virtualpowermeter.0 (16562) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2022-02-16 11:36:08.135 - info: telegram.1 (14621) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2022-02-16 11:36:08.141 - info: telegram.0 (14602) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2022-02-16 11:36:08.140 - info: zigbee.0 (14934) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2022-02-16 11:36:08.139 - info: text2command.0 (16491) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2022-02-16 11:36:08.137 - info: echarts.0 (15248) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2022-02-16 11:36:08.175 - error: shelly.0 (11928) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      2022-02-16 11:36:08.177 - warn: nut.0 (14949) get state error: Connection is closed.
      2022-02-16 11:36:08.179 - error: nut.0 (14949) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      2022-02-16 11:36:08.177 - error: shelly.0 (11928) unhandled promise rejection: DB closed
      2022-02-16 11:36:08.191 - error: shelly.0 (11928) Error: DB closed
      at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
      at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
      at Object.onceWrapper (events.js:520:26)
      at Socket.emit (events.js:400:28)
      at Socket.emit (domain.js:475:12)
      at TCP. (net.js:686:12)
      2022-02-16 11:36:08.192 - error: shelly.0 (11928) DB closed
      2022-02-16 11:36:08.181 - error: nut.0 (14949) unhandled promise rejection: DB closed
      2022-02-16 11:36:08.448 - error: nut.0 (14949) Error: DB closed
      at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
      at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
      at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)
      at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6485:35)
      2022-02-16 11:36:08.451 - error: nut.0 (14949) DB closed
      2022-02-16 11:36:08.571 - warn: radar2.0 (15633) get state error: Connection is closed.
      2022-02-16 11:36:08.576 - warn: radar2.0 (15633) Error {} is setState for Galaxy-S10Janina._nHere with {"val":51,"ack":true,"from":"system.adapter.radar2.0","user":"system.user.admin"}
      2022-02-16 11:36:10.059 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM
      2022-02-16 11:36:14.590 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM
      2022-02-16 11:36:14.795 - warn: host.IoBroker instance system.adapter.admin.0 terminated due to SIGTERM
      2022-02-16 11:36:14.888 - warn: host.IoBroker instance system.adapter.email.0 terminated due to SIGTERM
      2022-02-16 11:36:14.963 - warn: host.IoBroker instance system.adapter.telegram.0 terminated due to SIGTERM
      2022-02-16 11:36:15.167 - warn: host.IoBroker instance system.adapter.telegram.1 terminated due to SIGTERM
      2022-02-16 11:36:15.581 - warn: host.IoBroker instance system.adapter.sonoff.0 terminated due to SIGTERM
      2022-02-16 11:36:15.642 - warn: host.IoBroker instance system.adapter.tr-064.0 terminated due to SIGTERM
      2022-02-16 11:36:15.649 - warn: host.IoBroker instance system.adapter.javascript.0 terminated due to SIGTERM
      2022-02-16 11:36:15.714 - warn: host.IoBroker instance system.adapter.zigbee.0 terminated due to SIGTERM
      2022-02-16 11:36:15.805 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
      2022-02-16 11:36:15.806 - error: host.IoBroker Caught by controller[0]: Error: DB closed
      2022-02-16 11:36:15.807 - error: host.IoBroker Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
      2022-02-16 11:36:15.807 - error: host.IoBroker Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
      2022-02-16 11:36:15.808 - error: host.IoBroker Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)
      2022-02-16 11:36:15.808 - error: host.IoBroker Caught by controller[0]: at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6485:35)
      2022-02-16 11:36:15.809 - warn: host.IoBroker instance system.adapter.nut.0 terminated due to SIGTERM
      2022-02-16 11:36:15.870 - warn: host.IoBroker instance system.adapter.backitup.0 terminated due to SIGTERM
      2022-02-16 11:36:15.960 - warn: host.IoBroker instance system.adapter.ble.0 terminated due to SIGTERM
      2022-02-16 11:36:16.019 - warn: host.IoBroker instance system.adapter.broadlink2.0 terminated due to SIGTERM
      2022-02-16 11:36:16.118 - warn: host.IoBroker instance system.adapter.chromecast.0 terminated due to SIGTERM
      2022-02-16 11:36:16.281 - warn: host.IoBroker instance system.adapter.echarts.0 terminated due to SIGTERM
      2022-02-16 11:36:16.282 - warn: host.IoBroker instance system.adapter.fully-tablet-control.0 terminated due to SIGTERM
      2022-02-16 11:36:16.385 - warn: host.IoBroker instance system.adapter.info.0 terminated due to SIGTERM
      2022-02-16 11:36:16.452 - warn: host.IoBroker instance system.adapter.iot.0 terminated due to SIGTERM
      2022-02-16 11:36:16.613 - warn: host.IoBroker instance system.adapter.linux-control.0 terminated due to SIGTERM
      2022-02-16 11:36:16.718 - warn: host.IoBroker instance system.adapter.logparser.0 terminated due to SIGTERM
      2022-02-16 11:36:16.818 - warn: host.IoBroker instance system.adapter.mihome.0 terminated due to SIGTERM
      2022-02-16 11:36:16.928 - warn: host.IoBroker instance system.adapter.jarvis.0 terminated due to SIGTERM
      2022-02-16 11:36:17.071 - warn: host.IoBroker instance system.adapter.radar2.0 terminated due to SIGTERM
      2022-02-16 11:36:17.073 - warn: host.IoBroker instance system.adapter.seq.0 terminated due to SIGTERM
      2022-02-16 11:36:17.151 - warn: host.IoBroker instance system.adapter.shuttercontrol.0 terminated due to SIGTERM
      2022-02-16 11:36:17.212 - warn: host.IoBroker instance system.adapter.simple-api.0 terminated due to SIGTERM
      2022-02-16 11:36:17.344 - warn: host.IoBroker instance system.adapter.smartcontrol.0 terminated due to SIGTERM
      2022-02-16 11:36:17.345 - warn: host.IoBroker instance system.adapter.sourceanalytix.0 terminated due to SIGTERM
      2022-02-16 11:36:17.425 - warn: host.IoBroker instance system.adapter.tankerkoenig.0 terminated due to SIGTERM
      2022-02-16 11:36:17.493 - warn: host.IoBroker instance system.adapter.text2command.0 terminated due to SIGTERM
      2022-02-16 11:36:17.570 - warn: host.IoBroker instance system.adapter.trashschedule.0 terminated due to SIGTERM
      2022-02-16 11:36:17.660 - warn: host.IoBroker instance system.adapter.unifi.0 terminated due to SIGTERM
      2022-02-16 11:36:17.716 - warn: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated due to SIGTERM
      2022-02-16 11:36:17.807 - warn: host.IoBroker instance system.adapter.wled.0 terminated due to SIGTERM
      2022-02-16 11:36:17.873 - warn: host.IoBroker instance system.adapter.yeelight-2.0 terminated due to SIGTERM
      2022-02-16 11:36:18.591 - warn: host.IoBroker instance system.adapter.web.0 terminated due to SIGTERM
      2022-02-16 11:36:18.876 - error: host.IoBroker Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
      2022-02-16 11:36:18.877 - error: host.IoBroker Caught by controller[1]: Error: DB closed
      2022-02-16 11:36:18.878 - error: host.IoBroker Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
      2022-02-16 11:36:18.879 - error: host.IoBroker Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
      2022-02-16 11:36:18.879 - error: host.IoBroker Caught by controller[1]: at Object.onceWrapper (events.js:520:26)
      2022-02-16 11:36:18.880 - error: host.IoBroker Caught by controller[1]: at Socket.emit (events.js:400:28)
      2022-02-16 11:36:18.880 - error: host.IoBroker Caught by controller[1]: at Socket.emit (domain.js:475:12)
      2022-02-16 11:36:18.880 - error: host.IoBroker Caught by controller[1]: at TCP. (net.js:686:12)
      2022-02-16 11:36:18.881 - warn: host.IoBroker instance system.adapter.shelly.0 terminated due to SIGTERM
      2022-02-16 11:36:19.226 - warn: host.IoBroker instance system.adapter.wiffi-wz.0 terminated due to SIGTERM
      2022-02-16 11:36:19.272 - warn: host.IoBroker instance system.adapter.socketio.0 terminated due to SIGTERM
      2022-02-16 11:38:26.219 - info: admin.0 (691) starting. Version 5.3.0 in /opt/iobroker/node_modules/iobroker.admin, node: v14.19.0, js-controller: 4.0.10
      2022-02-16 11:38:26.255 - info: admin.0 (691) requesting all states
      2022-02-16 11:38:26.257 - info: admin.0 (691) requesting all objects
      2022-02-16 11:38:30.081 - info: admin.0 (691) received all objects
      2022-02-16 11:38:30.835 - info: email.0 (706) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.email, node: v14.19.0, js-controller: 4.0.10
      2022-02-16 11:38:30.944 - info: admin.0 (691) Request actual repository...
      2022-02-16 11:38:30.957 - info: admin.0 (691) http server listening on port 8081
      

      js-controller hat sich aktuell wieder eingependelt, seit dem Neustart

      umgestiegen von Proxmox auf Unraid

      apollon77A 1 Antwort Letzte Antwort
      0
      • JB_SullivanJ JB_Sullivan

        Nur mal so für mich als Windows Onkel zur eigenen Beruhigung - die Meldungen sind unkritisch?

        Beim Update non der 3.3 auf 4.0.9hatte ich in der Konsole ja einen ganzen Sack voll (Fehler)Meldungen - siehe weiter oben.

        Jetzt auf die 4.0.10 sind es andere Meldunugen. Da aber alles läuft, scheint das unkritisch zu sein? Das was im Code als REMOVE angegeben ist, kann ich auch gefahrlos löschen?

        > iobroker.js-controller@4.0.10 install C:\iobroker\GLT\node_modules\iobroker.js-controller
        > node iobroker.js setup first
        
        Successfully migrated 22812 objects to Redis Sets
        object _design/system updated
        
        The following notifications happened during sync:
        - Ignoring Directory "heatingcontrol.admin" because officially not created as meta object. Please remove directory!
        - Ignoring Directory "ping.admin" because officially not created as meta object. Please remove directory!
        - Ignoring Directory "vis-test" because officially not created as meta object. Please remove directory!
        
        {
          "defaultPrivate": "-----BEGIN RSA PRIVATE KEY-----Viel Key Code hierzwischen-----END RSA PRIVATE KEY-----\r\n",
        
          "defaultPublic": "-----BEGIN CERTIFICATE-----VIEL Code hier zwischen-----END CERTIFICATE-----\r\n"
        }
        Update certificate defaultPrivate
        The object "system.certificates" was updated successfully.
        Update certificate defaultPublic
        The object "system.certificates" was updated successfully.
        + iobroker.js-controller@4.0.10
        removed 6 packages, updated 23 packages and audited 2522 packages in 67.268s
        
        182 packages are looking for funding
          run `npm fund` for details
        
        found 182 vulnerabilities (18 low, 82 moderate, 76 high, 6 critical)
          run `npm audit fix` to fix them, or `npm audit` for details
        
        apollon77A Offline
        apollon77A Offline
        apollon77
        schrieb am zuletzt editiert von
        #377

        @jb_sullivan sagte in js-controller 4.0 jetzt im BETA/LATEST!:

        Nur mal so für mich als Windows Onkel zur eigenen Beruhigung - die Meldungen sind unkritisch?

        Sieht alles ok auch, trotz Windows gg (sorry den haste so gewollt ;-))

        Beim Update non der 3.3 auf 4.0.9hatte ich in der Konsole ja einen ganzen Sack voll (Fehler)Meldungen - siehe weiter oben.

        Ja die kommen nur wenn du von <4 auf 4 kommst. Sobald du auf 4 bist sind die weg.

        Jetzt auf die 4.0.10 sind es andere Meldunugen. Da aber alles läuft, scheint das unkritisch zu sein? Das was im Code als REMOVE angegeben ist, kann ich auch gefahrlos löschen?

        Zu denen gilt: Wenn du die adapter wo er "*.admin" anmeckert noch hast mach mal ein ´iob upload all´ bzw upload von den betroffnen Adaptern ... vis-test müsstest Du wissen obs Weg kann. Es ist ein Verzeichnis im ioBroker storage was das System nicht kennt (Passiert falls DU da mal was manuell hinkopiert hast)

        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
        1 Antwort Letzte Antwort
        0
        • crunchipC crunchip

          @apollon77 wie im anderen Thread erwähnt, bleibt meine CPU nun auch oben
          deshalb habe ich nun mal iob gestoppt und die ganze VM neu gestartet
          diesmal kam der nut Adapter noch dazu

          kommen die Host error aufgrund der "fehlerhaften" Adapter, oder durch etwas anderes?

          2022-02-16 11:36:07.841 - info: javascript.0 (14587) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-02-16 11:36:08.103 - info: history.0 (14352) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-02-16 11:36:08.133 - info: web.0 (16885) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-02-16 11:36:08.135 - info: virtualpowermeter.0 (16562) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-02-16 11:36:08.135 - info: telegram.1 (14621) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-02-16 11:36:08.141 - info: telegram.0 (14602) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-02-16 11:36:08.140 - info: zigbee.0 (14934) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-02-16 11:36:08.139 - info: text2command.0 (16491) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-02-16 11:36:08.137 - info: echarts.0 (15248) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-02-16 11:36:08.175 - error: shelly.0 (11928) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2022-02-16 11:36:08.177 - warn: nut.0 (14949) get state error: Connection is closed.
          2022-02-16 11:36:08.179 - error: nut.0 (14949) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2022-02-16 11:36:08.177 - error: shelly.0 (11928) unhandled promise rejection: DB closed
          2022-02-16 11:36:08.191 - error: shelly.0 (11928) Error: DB closed
          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
          at Object.onceWrapper (events.js:520:26)
          at Socket.emit (events.js:400:28)
          at Socket.emit (domain.js:475:12)
          at TCP. (net.js:686:12)
          2022-02-16 11:36:08.192 - error: shelly.0 (11928) DB closed
          2022-02-16 11:36:08.181 - error: nut.0 (14949) unhandled promise rejection: DB closed
          2022-02-16 11:36:08.448 - error: nut.0 (14949) Error: DB closed
          at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
          at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
          at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)
          at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6485:35)
          2022-02-16 11:36:08.451 - error: nut.0 (14949) DB closed
          2022-02-16 11:36:08.571 - warn: radar2.0 (15633) get state error: Connection is closed.
          2022-02-16 11:36:08.576 - warn: radar2.0 (15633) Error {} is setState for Galaxy-S10Janina._nHere with {"val":51,"ack":true,"from":"system.adapter.radar2.0","user":"system.user.admin"}
          2022-02-16 11:36:10.059 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM
          2022-02-16 11:36:14.590 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM
          2022-02-16 11:36:14.795 - warn: host.IoBroker instance system.adapter.admin.0 terminated due to SIGTERM
          2022-02-16 11:36:14.888 - warn: host.IoBroker instance system.adapter.email.0 terminated due to SIGTERM
          2022-02-16 11:36:14.963 - warn: host.IoBroker instance system.adapter.telegram.0 terminated due to SIGTERM
          2022-02-16 11:36:15.167 - warn: host.IoBroker instance system.adapter.telegram.1 terminated due to SIGTERM
          2022-02-16 11:36:15.581 - warn: host.IoBroker instance system.adapter.sonoff.0 terminated due to SIGTERM
          2022-02-16 11:36:15.642 - warn: host.IoBroker instance system.adapter.tr-064.0 terminated due to SIGTERM
          2022-02-16 11:36:15.649 - warn: host.IoBroker instance system.adapter.javascript.0 terminated due to SIGTERM
          2022-02-16 11:36:15.714 - warn: host.IoBroker instance system.adapter.zigbee.0 terminated due to SIGTERM
          2022-02-16 11:36:15.805 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
          2022-02-16 11:36:15.806 - error: host.IoBroker Caught by controller[0]: Error: DB closed
          2022-02-16 11:36:15.807 - error: host.IoBroker Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
          2022-02-16 11:36:15.807 - error: host.IoBroker Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
          2022-02-16 11:36:15.808 - error: host.IoBroker Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)
          2022-02-16 11:36:15.808 - error: host.IoBroker Caught by controller[0]: at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6485:35)
          2022-02-16 11:36:15.809 - warn: host.IoBroker instance system.adapter.nut.0 terminated due to SIGTERM
          2022-02-16 11:36:15.870 - warn: host.IoBroker instance system.adapter.backitup.0 terminated due to SIGTERM
          2022-02-16 11:36:15.960 - warn: host.IoBroker instance system.adapter.ble.0 terminated due to SIGTERM
          2022-02-16 11:36:16.019 - warn: host.IoBroker instance system.adapter.broadlink2.0 terminated due to SIGTERM
          2022-02-16 11:36:16.118 - warn: host.IoBroker instance system.adapter.chromecast.0 terminated due to SIGTERM
          2022-02-16 11:36:16.281 - warn: host.IoBroker instance system.adapter.echarts.0 terminated due to SIGTERM
          2022-02-16 11:36:16.282 - warn: host.IoBroker instance system.adapter.fully-tablet-control.0 terminated due to SIGTERM
          2022-02-16 11:36:16.385 - warn: host.IoBroker instance system.adapter.info.0 terminated due to SIGTERM
          2022-02-16 11:36:16.452 - warn: host.IoBroker instance system.adapter.iot.0 terminated due to SIGTERM
          2022-02-16 11:36:16.613 - warn: host.IoBroker instance system.adapter.linux-control.0 terminated due to SIGTERM
          2022-02-16 11:36:16.718 - warn: host.IoBroker instance system.adapter.logparser.0 terminated due to SIGTERM
          2022-02-16 11:36:16.818 - warn: host.IoBroker instance system.adapter.mihome.0 terminated due to SIGTERM
          2022-02-16 11:36:16.928 - warn: host.IoBroker instance system.adapter.jarvis.0 terminated due to SIGTERM
          2022-02-16 11:36:17.071 - warn: host.IoBroker instance system.adapter.radar2.0 terminated due to SIGTERM
          2022-02-16 11:36:17.073 - warn: host.IoBroker instance system.adapter.seq.0 terminated due to SIGTERM
          2022-02-16 11:36:17.151 - warn: host.IoBroker instance system.adapter.shuttercontrol.0 terminated due to SIGTERM
          2022-02-16 11:36:17.212 - warn: host.IoBroker instance system.adapter.simple-api.0 terminated due to SIGTERM
          2022-02-16 11:36:17.344 - warn: host.IoBroker instance system.adapter.smartcontrol.0 terminated due to SIGTERM
          2022-02-16 11:36:17.345 - warn: host.IoBroker instance system.adapter.sourceanalytix.0 terminated due to SIGTERM
          2022-02-16 11:36:17.425 - warn: host.IoBroker instance system.adapter.tankerkoenig.0 terminated due to SIGTERM
          2022-02-16 11:36:17.493 - warn: host.IoBroker instance system.adapter.text2command.0 terminated due to SIGTERM
          2022-02-16 11:36:17.570 - warn: host.IoBroker instance system.adapter.trashschedule.0 terminated due to SIGTERM
          2022-02-16 11:36:17.660 - warn: host.IoBroker instance system.adapter.unifi.0 terminated due to SIGTERM
          2022-02-16 11:36:17.716 - warn: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated due to SIGTERM
          2022-02-16 11:36:17.807 - warn: host.IoBroker instance system.adapter.wled.0 terminated due to SIGTERM
          2022-02-16 11:36:17.873 - warn: host.IoBroker instance system.adapter.yeelight-2.0 terminated due to SIGTERM
          2022-02-16 11:36:18.591 - warn: host.IoBroker instance system.adapter.web.0 terminated due to SIGTERM
          2022-02-16 11:36:18.876 - error: host.IoBroker Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
          2022-02-16 11:36:18.877 - error: host.IoBroker Caught by controller[1]: Error: DB closed
          2022-02-16 11:36:18.878 - error: host.IoBroker Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
          2022-02-16 11:36:18.879 - error: host.IoBroker Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
          2022-02-16 11:36:18.879 - error: host.IoBroker Caught by controller[1]: at Object.onceWrapper (events.js:520:26)
          2022-02-16 11:36:18.880 - error: host.IoBroker Caught by controller[1]: at Socket.emit (events.js:400:28)
          2022-02-16 11:36:18.880 - error: host.IoBroker Caught by controller[1]: at Socket.emit (domain.js:475:12)
          2022-02-16 11:36:18.880 - error: host.IoBroker Caught by controller[1]: at TCP. (net.js:686:12)
          2022-02-16 11:36:18.881 - warn: host.IoBroker instance system.adapter.shelly.0 terminated due to SIGTERM
          2022-02-16 11:36:19.226 - warn: host.IoBroker instance system.adapter.wiffi-wz.0 terminated due to SIGTERM
          2022-02-16 11:36:19.272 - warn: host.IoBroker instance system.adapter.socketio.0 terminated due to SIGTERM
          2022-02-16 11:38:26.219 - info: admin.0 (691) starting. Version 5.3.0 in /opt/iobroker/node_modules/iobroker.admin, node: v14.19.0, js-controller: 4.0.10
          2022-02-16 11:38:26.255 - info: admin.0 (691) requesting all states
          2022-02-16 11:38:26.257 - info: admin.0 (691) requesting all objects
          2022-02-16 11:38:30.081 - info: admin.0 (691) received all objects
          2022-02-16 11:38:30.835 - info: email.0 (706) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.email, node: v14.19.0, js-controller: 4.0.10
          2022-02-16 11:38:30.944 - info: admin.0 (691) Request actual repository...
          2022-02-16 11:38:30.957 - info: admin.0 (691) http server listening on port 8081
          

          js-controller hat sich aktuell wieder eingependelt, seit dem Neustart

          apollon77A Offline
          apollon77A Offline
          apollon77
          schrieb am zuletzt editiert von
          #378

          @crunchip sagte in js-controller 4.0 jetzt im BETA/LATEST!:

          kommen die Host error aufgrund der "fehlerhaften" Adapter, oder durch etwas anderes?

          Die Fehler haben mit Viel-CPU-Problemen nichts zu tun!! Das ist ok so, wundert mich ... bzw da mal schauen das auch letzte Versionen installiert sind und ggf issues anlegen wenn ja.

          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
          1 Antwort Letzte Antwort
          0
          • apollon77A apollon77

            hallo,

            mit dem Feedback der letzten tage habe ich heute den js-controller 4.0.10, aka Stable-RC2 für Euch. Enthalten ist:

            4.0.10 (2022-02-15)

            • (foxriver76) Fix module specific rebuild command
            • (foxriver76) allow null for object.states also for extend calls for now
            • (foxriver76) enable sets on migration to redis if allowed
            • (Apollon77) Make sure adapters that are stopped on update are not enabled too early
            • (Apollon77) Optimize some special cases on adapter start

            @crunchip Dein backitup upgrade Problem sollte damit gelöst sein und die Module-spezifischen Rebuilds bei Node-JS updates sollten auch besser tun (na, mag nochmal jemand Node.js upgraden oder so? ;-)) )

            L Offline
            L Offline
            lonsimbt
            schrieb am zuletzt editiert von
            #379

            @apollon77

            Update auf 4.0.10 ist problemlos durchgelaufen!

            Anschließend habe ich Node-JS von v14.19.0 auf v16.14.0 aktualisiert. Der iobroker ist auch danach mit allen Adaptern problemlos gestartet.

            Mir wurde dann ein Update für den hm-rpc-Adapter angeboten. Beim Versuch diesen über den Info-Tab zu aktualisieren, habe ich folgende Fehlermeldungen erhalten:

            host.iobroker  2022-02-16 15:38:47.365  info	iobroker Update hm-rpc from @1.15.5 to @1.15.6
            host.iobroker  2022-02-16 15:38:48.141  info	iobroker NPM version: 8.3.1 Installing iobroker.hm-rpc@1.15.6... (System call)
            host.iobroker  2022-02-16 15:40:09.693	error	iobroker Cannot upgrade: Cannot find view "system"
            host.iobroker  2022-02-16 15:40:09.689	error	iobroker Cannot set system.adapter.hm-rpc: DB closed
            host.iobroker  2022-02-16 15:40:09.663	error	iobroker host.iobroker Cannot install iobroker.hm-rpc@1.15.6: 254
            

            Ein weiterer Aktualisierungsversuch über die Admin-Seite hat dann aber ohne Fehler geklappt. War ich evtl. einfach zu ungeduldig?

            Ansonsten keine Fehlermeldungen oder Auffälligkeiten.

            Gruß Marco

            iobroker im Container (debian Bullseye) unter proxmox 7.1
            debmatic in VM (debian Buster) unter proxmox 7.1 mit HB-RF-USB und RPI-RF-MOD
            40 HomeMatic Geräte, Phillips Hue, Ikea Tradfri, Logitech Harmony Hub, Botvac Connected, Robonect

            apollon77A 1 Antwort Letzte Antwort
            0
            • L lonsimbt

              @apollon77

              Update auf 4.0.10 ist problemlos durchgelaufen!

              Anschließend habe ich Node-JS von v14.19.0 auf v16.14.0 aktualisiert. Der iobroker ist auch danach mit allen Adaptern problemlos gestartet.

              Mir wurde dann ein Update für den hm-rpc-Adapter angeboten. Beim Versuch diesen über den Info-Tab zu aktualisieren, habe ich folgende Fehlermeldungen erhalten:

              host.iobroker  2022-02-16 15:38:47.365  info	iobroker Update hm-rpc from @1.15.5 to @1.15.6
              host.iobroker  2022-02-16 15:38:48.141  info	iobroker NPM version: 8.3.1 Installing iobroker.hm-rpc@1.15.6... (System call)
              host.iobroker  2022-02-16 15:40:09.693	error	iobroker Cannot upgrade: Cannot find view "system"
              host.iobroker  2022-02-16 15:40:09.689	error	iobroker Cannot set system.adapter.hm-rpc: DB closed
              host.iobroker  2022-02-16 15:40:09.663	error	iobroker host.iobroker Cannot install iobroker.hm-rpc@1.15.6: 254
              

              Ein weiterer Aktualisierungsversuch über die Admin-Seite hat dann aber ohne Fehler geklappt. War ich evtl. einfach zu ungeduldig?

              Ansonsten keine Fehlermeldungen oder Auffälligkeiten.

              Gruß Marco

              apollon77A Offline
              apollon77A Offline
              apollon77
              schrieb am zuletzt editiert von
              #380

              @lonsimbt Ist Info aktuell? Es gab mal nen Bug ion info was Adapter-Updates anging ...

              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
              L 1 Antwort Letzte Antwort
              0
              • apollon77A apollon77

                @lonsimbt Ist Info aktuell? Es gab mal nen Bug ion info was Adapter-Updates anging ...

                L Offline
                L Offline
                lonsimbt
                schrieb am zuletzt editiert von
                #381

                @apollon77

                Ich denke schon. Die 1.9.18 wird mir als verfügbar und installiert angezeigt.

                iobroker im Container (debian Bullseye) unter proxmox 7.1
                debmatic in VM (debian Buster) unter proxmox 7.1 mit HB-RF-USB und RPI-RF-MOD
                40 HomeMatic Geräte, Phillips Hue, Ikea Tradfri, Logitech Harmony Hub, Botvac Connected, Robonect

                apollon77A 1 Antwort Letzte Antwort
                0
                • L lonsimbt

                  @apollon77

                  Ich denke schon. Die 1.9.18 wird mir als verfügbar und installiert angezeigt.

                  apollon77A Offline
                  apollon77A Offline
                  apollon77
                  schrieb am zuletzt editiert von
                  #382

                  @lonsimbt Dann bitte nochmal schauen ob ein anderen update (vllt ja noch was offen) auch solche fehler gibt und dann issue bitte anlegen)

                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                  L 1 Antwort Letzte Antwort
                  0
                  • apollon77A apollon77

                    @lonsimbt Dann bitte nochmal schauen ob ein anderen update (vllt ja noch was offen) auch solche fehler gibt und dann issue bitte anlegen)

                    L Offline
                    L Offline
                    lonsimbt
                    schrieb am zuletzt editiert von
                    #383

                    @apollon77

                    Ich habe testweise mal den tr-064-Adapter eine Versionsnummer zurückgesetzt und anschließend über die Info-Seite wieder auf den aktuellen Stand gebracht. Das hat problemlos funktioniert. Ich habe allerdings den Eindruck, dass die Updates recht lange benötigen.

                    Falls der Fehler an anderer Stelle nochmal auftritt, sage ich Bescheid und lege ein issue an.

                    iobroker im Container (debian Bullseye) unter proxmox 7.1
                    debmatic in VM (debian Buster) unter proxmox 7.1 mit HB-RF-USB und RPI-RF-MOD
                    40 HomeMatic Geräte, Phillips Hue, Ikea Tradfri, Logitech Harmony Hub, Botvac Connected, Robonect

                    apollon77A 1 Antwort Letzte Antwort
                    0
                    • L lonsimbt

                      @apollon77

                      Ich habe testweise mal den tr-064-Adapter eine Versionsnummer zurückgesetzt und anschließend über die Info-Seite wieder auf den aktuellen Stand gebracht. Das hat problemlos funktioniert. Ich habe allerdings den Eindruck, dass die Updates recht lange benötigen.

                      Falls der Fehler an anderer Stelle nochmal auftritt, sage ich Bescheid und lege ein issue an.

                      apollon77A Offline
                      apollon77A Offline
                      apollon77
                      schrieb am zuletzt editiert von
                      #384

                      @lonsimbt sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                      Ich habe allerdings den Eindruck, dass die Updates recht lange benötigen.

                      Denke da musst du npm fragen :-)

                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                      1 Antwort Letzte Antwort
                      1
                      • DolomitiD Offline
                        DolomitiD Offline
                        Dolomiti
                        schrieb am zuletzt editiert von
                        #385

                        Habe jetzt auch mal 4.0.10 installiert. System war uptodate
                        Node.js ist auch richtig

                        /usr/bin/nodejs
                        /usr/bin/node
                        /usr/bin/npm
                        v14.19.0
                        v14.19.0
                        6.14.16
                        

                        Bekomme aber folgende Meldungen am Anfang

                        schlippe@ioBroker-Test:~$ iobroker upgrade self
                        Update js-controller from @3.3.22 to @4.0.10
                        NPM version: 6.14.16
                        npm install iobroker.js-controller@4.0.10 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                        In file included from ../src/binding.cc:1:
                        /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:43: warning: cast between incompatible function types from 'void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' {aka '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.19.0/include/node/node.h:827:3: note: in expansion of macro 'NODE_MODULE_X'
                          NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                          ^~~~~~~~~~~~~
                        ../src/binding.cc:153:1: note: in expansion of macro 'NODE_MODULE'
                        NODE_MODULE(cpufeatures, init)
                        ^~~~~~~~~~~
                        In file included from ../src/unix_dgram.cc:5:
                        ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                        ../../nan/nan.h:2298:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                            , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                                                     ^
                        In file included from ../../nan/nan.h:54,
                                        from ../src/unix_dgram.cc:5:
                        ../src/unix_dgram.cc: At global scope:
                        /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793: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.19.0/include/node/node.h:827: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)
                        ^~~~~~~~~~~
                        Server Objects 127.0.0.1:32802 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
                        Server States 127.0.0.1:38042 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
                        Server Objects 127.0.0.1:32802 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
                        Server States 127.0.0.1:38044 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                        Server Objects 127.0.0.1:32802 Error from InMemDB: Error: Unknown LUA script load
                        Server Objects 127.0.0.1:32802 Error from InMemDB: Error: Unknown LUA script load
                        Server Objects 127.0.0.1:32802 Error from InMemDB: Error: Unknown LUA script load
                        (node:14970) Warning: Accessing non-existent property 'count' of module exports inside circular dependency
                        (Use `node --trace-warnings ...` to show where the warning was created)
                        (node:14970) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
                        (node:14970) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
                        (node:14970) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
                        Server Objects 127.0.0.1:32802 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                        Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                        schlippe@ioBroker-Test:~$ iobroker start
                        


                        System startet dann auch und bei beim status kommt folgende Warnung. Kann ich das ignorieren?

                        schlippe@ioBroker-Test:~$ iobroker status
                        (node:15326) Warning: Accessing non-existent property 'count' of module exports inside circular dependency
                        (Use `node --trace-warnings ...` to show where the warning was created)
                        (node:15326) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
                        (node:15326) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
                        (node:15326) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
                        iobroker is running on this host.
                        
                        
                        Objects type: jsonl
                        States  type: jsonl
                        
                        

                        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                        Intel N100 (32GB,256GB SSD), Proxmox -> Debian 12 in VM (Master) + Debian 12 in CT (Test) + Debmatic, HM-Aktoren, Wago 750-880, Shelly, Zigbee

                        crunchipC apollon77A 2 Antworten Letzte Antwort
                        0
                        • JB_SullivanJ Offline
                          JB_SullivanJ Offline
                          JB_Sullivan
                          schrieb am zuletzt editiert von
                          #386

                          Ich habe eben nochmal ein Win10 Update gemacht und dann den Broker automatisch neu starten lassen. Dabei poppte die folgende Meldung auf - hatte ich in der Form noch nie und auch die Einstellung 60 Sekunden ließ sich nicht einstellen. Dabei kam die Meldung am unteren Bildrand.

                          Habe dann Abrechen gedrückt, da ich in der Form eigentlich noch nie Probleme hatte. Waren wohl noch ein paar andere Windows Prozesse im Hintergrund am starten, oder so.....

                          Das nur mal am Rande.

                          34060dc7-6e2d-45bb-931a-2bc94c3389e0-image.png

                          ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                          apollon77A 1 Antwort Letzte Antwort
                          0
                          • FeuersturmF Online
                            FeuersturmF Online
                            Feuersturm
                            schrieb am zuletzt editiert von Feuersturm
                            #387

                            @apollon77
                            Edit: Sehe gerade im ersten Beitrag, dass die Errors gewollt / ok sind.

                            Ich hab gerade einmal mein Produktivsystem von js-controller 3.3.22 auf 4.0.10 aktualisiert und folgende Ausgabe erhalten:

                            proxmox@ioBroker:~$ iob stop
                            proxmox@ioBroker:~$ iob upgrade self
                            Update js-controller from @3.3.22 to @4.0.10
                            NPM version: 6.14.15
                            npm install iobroker.js-controller@4.0.10 --loglevel error --unsafe-perm --prefi                                                                                                                     x "/opt/iobroker" (System call)
                            In file included from ../src/unix_dgram.cc:5:
                            ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                            ../../nan/nan.h:2294:62: warning: cast between incompatible function types from                                                                                                                      'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka '                                                                                                                     void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                             2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                  |                                                              ^
                            In file included from ../../nan/nan.h:56,
                                             from ../src/unix_dgram.cc:5:
                            ../src/unix_dgram.cc: At global scope:
                            /home/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:787: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::V                                                                                                                     alue>, void*)'} [-Wcast-function-type]
                              787 |       (node::addon_register_func) (regfunc),                          \
                                  |                                           ^
                            /home/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:821:3: note: in expan                                                                                                                     sion of macro 'NODE_MODULE_X'
                              821 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_                                                                                                                     usage)
                                  |   ^~~~~~~~~~~~~
                            ../src/unix_dgram.cc:404:1: note: in expansion of macro 'NODE_MODULE'
                              404 | NODE_MODULE(unix_dgram, Initialize)
                                  | ^~~~~~~~~~~
                            Server Objects 127.0.0.1:59728 Error from InMemDB: Error: GET-UNSUPPORTED for na                                                                                                                     mespace cfg.: Data=["meta.objects.features.useSets"]
                            Server States 127.0.0.1:34856 Error from InMemDB: Error: GET-UNSUPPORTED for nam                                                                                                                     espace meta.: Data=["meta.states.protocolVersion"]
                            Server Objects 127.0.0.1:59728 Error from InMemDB: Error: GET-UNSUPPORTED for na                                                                                                                     mespace cfg.: Data=["meta.objects.protocolVersion"]
                            Server States 127.0.0.1:34858 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED                                                                                                                      for namespace meta.: Data=["meta.*"]
                            Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa                                                                                                                     d
                            Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa                                                                                                                     d
                            Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa                                                                                                                     d
                            Server Objects 127.0.0.1:59728 Error from InMemDB: Error: SET-UNSUPPORTED for na                                                                                                                     mespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]                                                                                                                     }]
                            Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for names                                                                                                                     pace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                            proxmox@ioBroker:~$
                            
                            

                            Nach dem Update ergibt iob status folgendes:

                            proxmox@ioBroker:~$ iob status
                            iobroker is not running on this host.
                            
                            Objects type: jsonl
                            States  type: jsonl
                            
                            proxmox@ioBroker:~$ node -v && nodejs -v && npm -v
                            v14.18.2
                            v14.18.2
                            6.14.15
                            
                            
                            crunchipC apollon77A 2 Antworten Letzte Antwort
                            0
                            • DolomitiD Dolomiti

                              Habe jetzt auch mal 4.0.10 installiert. System war uptodate
                              Node.js ist auch richtig

                              /usr/bin/nodejs
                              /usr/bin/node
                              /usr/bin/npm
                              v14.19.0
                              v14.19.0
                              6.14.16
                              

                              Bekomme aber folgende Meldungen am Anfang

                              schlippe@ioBroker-Test:~$ iobroker upgrade self
                              Update js-controller from @3.3.22 to @4.0.10
                              NPM version: 6.14.16
                              npm install iobroker.js-controller@4.0.10 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                              In file included from ../src/binding.cc:1:
                              /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:43: warning: cast between incompatible function types from 'void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' {aka '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.19.0/include/node/node.h:827:3: note: in expansion of macro 'NODE_MODULE_X'
                                NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                                ^~~~~~~~~~~~~
                              ../src/binding.cc:153:1: note: in expansion of macro 'NODE_MODULE'
                              NODE_MODULE(cpufeatures, init)
                              ^~~~~~~~~~~
                              In file included from ../src/unix_dgram.cc:5:
                              ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                              ../../nan/nan.h:2298:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                                  , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                                                           ^
                              In file included from ../../nan/nan.h:54,
                                              from ../src/unix_dgram.cc:5:
                              ../src/unix_dgram.cc: At global scope:
                              /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793: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.19.0/include/node/node.h:827: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)
                              ^~~~~~~~~~~
                              Server Objects 127.0.0.1:32802 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
                              Server States 127.0.0.1:38042 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
                              Server Objects 127.0.0.1:32802 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
                              Server States 127.0.0.1:38044 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                              Server Objects 127.0.0.1:32802 Error from InMemDB: Error: Unknown LUA script load
                              Server Objects 127.0.0.1:32802 Error from InMemDB: Error: Unknown LUA script load
                              Server Objects 127.0.0.1:32802 Error from InMemDB: Error: Unknown LUA script load
                              (node:14970) Warning: Accessing non-existent property 'count' of module exports inside circular dependency
                              (Use `node --trace-warnings ...` to show where the warning was created)
                              (node:14970) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
                              (node:14970) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
                              (node:14970) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
                              Server Objects 127.0.0.1:32802 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                              Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                              schlippe@ioBroker-Test:~$ iobroker start
                              


                              System startet dann auch und bei beim status kommt folgende Warnung. Kann ich das ignorieren?

                              schlippe@ioBroker-Test:~$ iobroker status
                              (node:15326) Warning: Accessing non-existent property 'count' of module exports inside circular dependency
                              (Use `node --trace-warnings ...` to show where the warning was created)
                              (node:15326) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
                              (node:15326) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
                              (node:15326) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
                              iobroker is running on this host.
                              
                              
                              Objects type: jsonl
                              States  type: jsonl
                              
                              
                              crunchipC Abwesend
                              crunchipC Abwesend
                              crunchip
                              Forum Testing Most Active
                              schrieb am zuletzt editiert von
                              #388

                              @dolomiti bei mir war es mongodb,, die zur gleichen Ausgabe führte

                              umgestiegen von Proxmox auf Unraid

                              1 Antwort Letzte Antwort
                              0
                              • FeuersturmF Feuersturm

                                @apollon77
                                Edit: Sehe gerade im ersten Beitrag, dass die Errors gewollt / ok sind.

                                Ich hab gerade einmal mein Produktivsystem von js-controller 3.3.22 auf 4.0.10 aktualisiert und folgende Ausgabe erhalten:

                                proxmox@ioBroker:~$ iob stop
                                proxmox@ioBroker:~$ iob upgrade self
                                Update js-controller from @3.3.22 to @4.0.10
                                NPM version: 6.14.15
                                npm install iobroker.js-controller@4.0.10 --loglevel error --unsafe-perm --prefi                                                                                                                     x "/opt/iobroker" (System call)
                                In file included from ../src/unix_dgram.cc:5:
                                ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                                ../../nan/nan.h:2294:62: warning: cast between incompatible function types from                                                                                                                      'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka '                                                                                                                     void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                                 2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                      |                                                              ^
                                In file included from ../../nan/nan.h:56,
                                                 from ../src/unix_dgram.cc:5:
                                ../src/unix_dgram.cc: At global scope:
                                /home/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:787: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::V                                                                                                                     alue>, void*)'} [-Wcast-function-type]
                                  787 |       (node::addon_register_func) (regfunc),                          \
                                      |                                           ^
                                /home/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:821:3: note: in expan                                                                                                                     sion of macro 'NODE_MODULE_X'
                                  821 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_                                                                                                                     usage)
                                      |   ^~~~~~~~~~~~~
                                ../src/unix_dgram.cc:404:1: note: in expansion of macro 'NODE_MODULE'
                                  404 | NODE_MODULE(unix_dgram, Initialize)
                                      | ^~~~~~~~~~~
                                Server Objects 127.0.0.1:59728 Error from InMemDB: Error: GET-UNSUPPORTED for na                                                                                                                     mespace cfg.: Data=["meta.objects.features.useSets"]
                                Server States 127.0.0.1:34856 Error from InMemDB: Error: GET-UNSUPPORTED for nam                                                                                                                     espace meta.: Data=["meta.states.protocolVersion"]
                                Server Objects 127.0.0.1:59728 Error from InMemDB: Error: GET-UNSUPPORTED for na                                                                                                                     mespace cfg.: Data=["meta.objects.protocolVersion"]
                                Server States 127.0.0.1:34858 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED                                                                                                                      for namespace meta.: Data=["meta.*"]
                                Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa                                                                                                                     d
                                Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa                                                                                                                     d
                                Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa                                                                                                                     d
                                Server Objects 127.0.0.1:59728 Error from InMemDB: Error: SET-UNSUPPORTED for na                                                                                                                     mespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]                                                                                                                     }]
                                Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for names                                                                                                                     pace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                                proxmox@ioBroker:~$
                                
                                

                                Nach dem Update ergibt iob status folgendes:

                                proxmox@ioBroker:~$ iob status
                                iobroker is not running on this host.
                                
                                Objects type: jsonl
                                States  type: jsonl
                                
                                proxmox@ioBroker:~$ node -v && nodejs -v && npm -v
                                v14.18.2
                                v14.18.2
                                6.14.15
                                
                                
                                crunchipC Abwesend
                                crunchipC Abwesend
                                crunchip
                                Forum Testing Most Active
                                schrieb am zuletzt editiert von
                                #389

                                @feuersturm sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                folgende Ausgabe erhalten:

                                Wäre da nicht nach dem iob stop ein iob update angebracht gewesen?

                                umgestiegen von Proxmox auf Unraid

                                FeuersturmF 1 Antwort Letzte Antwort
                                0
                                • DolomitiD Dolomiti

                                  Habe jetzt auch mal 4.0.10 installiert. System war uptodate
                                  Node.js ist auch richtig

                                  /usr/bin/nodejs
                                  /usr/bin/node
                                  /usr/bin/npm
                                  v14.19.0
                                  v14.19.0
                                  6.14.16
                                  

                                  Bekomme aber folgende Meldungen am Anfang

                                  schlippe@ioBroker-Test:~$ iobroker upgrade self
                                  Update js-controller from @3.3.22 to @4.0.10
                                  NPM version: 6.14.16
                                  npm install iobroker.js-controller@4.0.10 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                                  In file included from ../src/binding.cc:1:
                                  /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:43: warning: cast between incompatible function types from 'void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' {aka '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.19.0/include/node/node.h:827:3: note: in expansion of macro 'NODE_MODULE_X'
                                    NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                                    ^~~~~~~~~~~~~
                                  ../src/binding.cc:153:1: note: in expansion of macro 'NODE_MODULE'
                                  NODE_MODULE(cpufeatures, init)
                                  ^~~~~~~~~~~
                                  In file included from ../src/unix_dgram.cc:5:
                                  ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                                  ../../nan/nan.h:2298:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                                      , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                                                               ^
                                  In file included from ../../nan/nan.h:54,
                                                  from ../src/unix_dgram.cc:5:
                                  ../src/unix_dgram.cc: At global scope:
                                  /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793: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.19.0/include/node/node.h:827: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)
                                  ^~~~~~~~~~~
                                  Server Objects 127.0.0.1:32802 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
                                  Server States 127.0.0.1:38042 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
                                  Server Objects 127.0.0.1:32802 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
                                  Server States 127.0.0.1:38044 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                                  Server Objects 127.0.0.1:32802 Error from InMemDB: Error: Unknown LUA script load
                                  Server Objects 127.0.0.1:32802 Error from InMemDB: Error: Unknown LUA script load
                                  Server Objects 127.0.0.1:32802 Error from InMemDB: Error: Unknown LUA script load
                                  (node:14970) Warning: Accessing non-existent property 'count' of module exports inside circular dependency
                                  (Use `node --trace-warnings ...` to show where the warning was created)
                                  (node:14970) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
                                  (node:14970) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
                                  (node:14970) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
                                  Server Objects 127.0.0.1:32802 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                                  Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                                  schlippe@ioBroker-Test:~$ iobroker start
                                  


                                  System startet dann auch und bei beim status kommt folgende Warnung. Kann ich das ignorieren?

                                  schlippe@ioBroker-Test:~$ iobroker status
                                  (node:15326) Warning: Accessing non-existent property 'count' of module exports inside circular dependency
                                  (Use `node --trace-warnings ...` to show where the warning was created)
                                  (node:15326) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
                                  (node:15326) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
                                  (node:15326) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
                                  iobroker is running on this host.
                                  
                                  
                                  Objects type: jsonl
                                  States  type: jsonl
                                  
                                  
                                  apollon77A Offline
                                  apollon77A Offline
                                  apollon77
                                  schrieb am zuletzt editiert von
                                  #390

                                  @dolomiti Das hat nichts mit dem Controller zu tun. Das liegt an Nodejs 14 und scheinbar einer "alten" version von node-red der eine buggy mongodb version enthalten hat und diese verursacht diese Fejhler. ALso bitte node-red aktualisieren

                                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                  DolomitiD 1 Antwort Letzte Antwort
                                  0
                                  • JB_SullivanJ JB_Sullivan

                                    Ich habe eben nochmal ein Win10 Update gemacht und dann den Broker automatisch neu starten lassen. Dabei poppte die folgende Meldung auf - hatte ich in der Form noch nie und auch die Einstellung 60 Sekunden ließ sich nicht einstellen. Dabei kam die Meldung am unteren Bildrand.

                                    Habe dann Abrechen gedrückt, da ich in der Form eigentlich noch nie Probleme hatte. Waren wohl noch ein paar andere Windows Prozesse im Hintergrund am starten, oder so.....

                                    Das nur mal am Rande.

                                    34060dc7-6e2d-45bb-931a-2bc94c3389e0-image.png

                                    apollon77A Offline
                                    apollon77A Offline
                                    apollon77
                                    schrieb am zuletzt editiert von
                                    #391

                                    @jb_sullivan Diese Meldung kommt vom Admin wenn nicht innerhalb einer definierten Wartezeit Daten kommen. Ja das passiert ggf wenn gerade viele Adapter starten und somit das System unter Last steht.

                                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                    1 Antwort Letzte Antwort
                                    0
                                    • crunchipC crunchip

                                      @feuersturm sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                      folgende Ausgabe erhalten:

                                      Wäre da nicht nach dem iob stop ein iob update angebracht gewesen?

                                      FeuersturmF Online
                                      FeuersturmF Online
                                      Feuersturm
                                      schrieb am zuletzt editiert von
                                      #392

                                      @crunchip sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                      @feuersturm sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                      folgende Ausgabe erhalten:

                                      Wäre da nicht nach dem iob stop ein iob update angebracht gewesen?

                                      iob update wurde vor dem iob stop ausgeführt.

                                      1 Antwort Letzte Antwort
                                      1
                                      • FeuersturmF Feuersturm

                                        @apollon77
                                        Edit: Sehe gerade im ersten Beitrag, dass die Errors gewollt / ok sind.

                                        Ich hab gerade einmal mein Produktivsystem von js-controller 3.3.22 auf 4.0.10 aktualisiert und folgende Ausgabe erhalten:

                                        proxmox@ioBroker:~$ iob stop
                                        proxmox@ioBroker:~$ iob upgrade self
                                        Update js-controller from @3.3.22 to @4.0.10
                                        NPM version: 6.14.15
                                        npm install iobroker.js-controller@4.0.10 --loglevel error --unsafe-perm --prefi                                                                                                                     x "/opt/iobroker" (System call)
                                        In file included from ../src/unix_dgram.cc:5:
                                        ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                                        ../../nan/nan.h:2294:62: warning: cast between incompatible function types from                                                                                                                      'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka '                                                                                                                     void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                                         2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                              |                                                              ^
                                        In file included from ../../nan/nan.h:56,
                                                         from ../src/unix_dgram.cc:5:
                                        ../src/unix_dgram.cc: At global scope:
                                        /home/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:787: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::V                                                                                                                     alue>, void*)'} [-Wcast-function-type]
                                          787 |       (node::addon_register_func) (regfunc),                          \
                                              |                                           ^
                                        /home/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:821:3: note: in expan                                                                                                                     sion of macro 'NODE_MODULE_X'
                                          821 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_                                                                                                                     usage)
                                              |   ^~~~~~~~~~~~~
                                        ../src/unix_dgram.cc:404:1: note: in expansion of macro 'NODE_MODULE'
                                          404 | NODE_MODULE(unix_dgram, Initialize)
                                              | ^~~~~~~~~~~
                                        Server Objects 127.0.0.1:59728 Error from InMemDB: Error: GET-UNSUPPORTED for na                                                                                                                     mespace cfg.: Data=["meta.objects.features.useSets"]
                                        Server States 127.0.0.1:34856 Error from InMemDB: Error: GET-UNSUPPORTED for nam                                                                                                                     espace meta.: Data=["meta.states.protocolVersion"]
                                        Server Objects 127.0.0.1:59728 Error from InMemDB: Error: GET-UNSUPPORTED for na                                                                                                                     mespace cfg.: Data=["meta.objects.protocolVersion"]
                                        Server States 127.0.0.1:34858 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED                                                                                                                      for namespace meta.: Data=["meta.*"]
                                        Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa                                                                                                                     d
                                        Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa                                                                                                                     d
                                        Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa                                                                                                                     d
                                        Server Objects 127.0.0.1:59728 Error from InMemDB: Error: SET-UNSUPPORTED for na                                                                                                                     mespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]                                                                                                                     }]
                                        Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for names                                                                                                                     pace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                                        proxmox@ioBroker:~$
                                        
                                        

                                        Nach dem Update ergibt iob status folgendes:

                                        proxmox@ioBroker:~$ iob status
                                        iobroker is not running on this host.
                                        
                                        Objects type: jsonl
                                        States  type: jsonl
                                        
                                        proxmox@ioBroker:~$ node -v && nodejs -v && npm -v
                                        v14.18.2
                                        v14.18.2
                                        6.14.15
                                        
                                        
                                        apollon77A Offline
                                        apollon77A Offline
                                        apollon77
                                        schrieb am zuletzt editiert von
                                        #393

                                        @feuersturm Sieht alles korrekt aus. Sind die üblichen Compile Warnungen und die oben beschriebenen "einmaligen Not supported "Meldungen. Alles so wie es soll :-)

                                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                        1 Antwort Letzte Antwort
                                        0
                                        • DiginixD Offline
                                          DiginixD Offline
                                          Diginix
                                          schrieb am zuletzt editiert von Diginix
                                          #394

                                          @apollon77 Habe eben unter 4.0.10 5 Adapter aktualisiert (shelly von 5.1.3 auf 5.2.0, text2command von 2.1.2 auf 2.1.6, socketio von 4.1.2 auf 4.1.4, ws von 1.1.4 auf 1.1.6, web von 4.1.4 auf 4.1.5). Als letztes den web und dann kam mal wieder der OOM Killer obwohl die VM nun 6GB hat und nicht über 5 GB belegt hatte:

                                          Feb 17 11:17:27 iobroker kernel: [185572.752465] CPU: 1 PID: 707 Comm: gmain Not tainted 5.4.0-99-generic #112-Ubuntu
                                          Feb 17 11:17:27 iobroker kernel: [185572.752466] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
                                          Feb 17 11:17:27 iobroker kernel: [185572.752469] Call Trace:
                                          Feb 17 11:17:27 iobroker kernel: [185572.752486]  dump_stack+0x6d/0x8b
                                          Feb 17 11:17:27 iobroker kernel: [185572.752489]  dump_header+0x4f/0x1eb
                                          Feb 17 11:17:27 iobroker kernel: [185572.752491]  oom_kill_process.cold+0xb/0x10
                                          Feb 17 11:17:27 iobroker kernel: [185572.752494]  out_of_memory+0x1cf/0x4d0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752497]  __alloc_pages_slowpath+0xd5e/0xe50
                                          Feb 17 11:17:27 iobroker kernel: [185572.752502]  __alloc_pages_nodemask+0x2d0/0x320
                                          Feb 17 11:17:27 iobroker kernel: [185572.752504]  alloc_pages_current+0x87/0xe0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752511]  __page_cache_alloc+0x72/0x90
                                          Feb 17 11:17:27 iobroker kernel: [185572.752514]  pagecache_get_page+0xbf/0x300
                                          Feb 17 11:17:27 iobroker kernel: [185572.752516]  filemap_fault+0x6b2/0xa50
                                          Feb 17 11:17:27 iobroker kernel: [185572.752519]  ? unlock_page_memcg+0x12/0x20
                                          Feb 17 11:17:27 iobroker kernel: [185572.752521]  ? page_add_file_rmap+0xff/0x1a0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752524]  ? xas_load+0xd/0x80
                                          Feb 17 11:17:27 iobroker kernel: [185572.752526]  ? xas_find+0x17f/0x1c0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752532]  ? filemap_map_pages+0x24c/0x380
                                          Feb 17 11:17:27 iobroker kernel: [185572.752535]  ext4_filemap_fault+0x32/0x50
                                          Feb 17 11:17:27 iobroker kernel: [185572.752538]  __do_fault+0x3c/0x130
                                          Feb 17 11:17:27 iobroker kernel: [185572.752540]  do_fault+0x24b/0x640
                                          Feb 17 11:17:27 iobroker kernel: [185572.752542]  __handle_mm_fault+0x4c5/0x7a0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752545]  handle_mm_fault+0xca/0x200
                                          Feb 17 11:17:27 iobroker kernel: [185572.752548]  do_user_addr_fault+0x1f9/0x450
                                          Feb 17 11:17:27 iobroker kernel: [185572.752551]  __do_page_fault+0x58/0x90
                                          Feb 17 11:17:27 iobroker kernel: [185572.752553]  do_page_fault+0x2c/0xe0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752556]  do_async_page_fault+0x39/0x70
                                          Feb 17 11:17:27 iobroker kernel: [185572.752558]  async_page_fault+0x34/0x40
                                          Feb 17 11:17:27 iobroker kernel: [185572.752569] RIP: 0033:0x7fdd6c4e54d0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752575] Code: Bad RIP value.
                                          Feb 17 11:17:27 iobroker kernel: [185572.752576] RSP: 002b:00007fdd6bbe0c58 EFLAGS: 00010246
                                          Feb 17 11:17:27 iobroker kernel: [185572.752578] RAX: 0000000000000000 RBX: 00005653fef41350 RCX: 0000000000000002
                                          Feb 17 11:17:27 iobroker kernel: [185572.752579] RDX: 00005653fef41350 RSI: 000000007fffffff RDI: 00005653fef43e90
                                          Feb 17 11:17:27 iobroker kernel: [185572.752580] RBP: 00005653fef43e90 R08: 0000000000000000 R09: 0000000000000000
                                          Feb 17 11:17:27 iobroker kernel: [185572.752581] R10: 00005653fef5e870 R11: 0000000000000000 R12: 0000000000000002
                                          Feb 17 11:17:27 iobroker kernel: [185572.752582] R13: 000000007fffffff R14: 0000000000000002 R15: 00005653fef43e90
                                          Feb 17 11:17:27 iobroker kernel: [185572.752596] Mem-Info:
                                          Feb 17 11:17:27 iobroker kernel: [185572.752608] active_anon:1417365 inactive_anon:49 isolated_anon:0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752608]  active_file:105 inactive_file:33 isolated_file:0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752608]  unevictable:4618 dirty:0 writeback:0 unstable:0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752608]  slab_reclaimable:10079 slab_unreclaimable:24210
                                          Feb 17 11:17:27 iobroker kernel: [185572.752608]  mapped:2683 shmem:288 pagetables:14758 bounce:0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752608]  free:23741 free_pcp:1412 free_cma:0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752616] Node 0 active_anon:5669460kB inactive_anon:196kB active_file:420kB inactive_file:132kB unevictable:18472kB isolated(anon):0kB isolated(file):0kB mapped:10732kB dirty:0kB writeback:0kB shmem:1152kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
                                          Feb 17 11:17:27 iobroker kernel: [185572.752617] Node 0 DMA free:15900kB min:176kB low:220kB high:264kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
                                          Feb 17 11:17:27 iobroker kernel: [185572.752621] lowmem_reserve[]: 0 2875 5837 5837 5837
                                          Feb 17 11:17:27 iobroker kernel: [185572.752624] Node 0 DMA32 free:45028kB min:33196kB low:41492kB high:49788kB active_anon:2910612kB inactive_anon:64kB active_file:968kB inactive_file:420kB unevictable:0kB writepending:0kB present:3129176kB managed:3034304kB mlocked:0kB kernel_stack:2384kB pagetables:17240kB bounce:0kB free_pcp:3220kB local_pcp:548kB free_cma:0kB
                                          Feb 17 11:17:27 iobroker kernel: [185572.752634] lowmem_reserve[]: 0 0 2962 2962 2962
                                          Feb 17 11:17:27 iobroker kernel: [185572.752637] Node 0 Normal free:34036kB min:34204kB low:42752kB high:51300kB active_anon:2758848kB inactive_anon:132kB active_file:240kB inactive_file:276kB unevictable:18472kB writepending:0kB present:3145728kB managed:3033552kB mlocked:18472kB kernel_stack:7696kB pagetables:41792kB bounce:0kB free_pcp:2436kB local_pcp:288kB free_cma:0kB
                                          Feb 17 11:17:27 iobroker kernel: [185572.752640] lowmem_reserve[]: 0 0 0 0 0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752643] Node 0 DMA: 1*4kB (U) 1*8kB (U) 1*16kB (U) 0*32kB 2*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15900kB
                                          Feb 17 11:17:27 iobroker kernel: [185572.752651] Node 0 DMA32: 1299*4kB (UME) 956*8kB (UME) 540*16kB (UME) 259*32kB (UME) 130*64kB (UME) 41*128kB (UME) 6*256kB (UME) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 44876kB
                                          Feb 17 11:17:27 iobroker kernel: [185572.752660] Node 0 Normal: 880*4kB (UMH) 1532*8kB (UMEH) 734*16kB (UEH) 227*32kB (UE) 1*64kB (H) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 34848kB
                                          Feb 17 11:17:27 iobroker kernel: [185572.752679] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
                                          Feb 17 11:17:27 iobroker kernel: [185572.752679] 2460 total pagecache pages
                                          Feb 17 11:17:27 iobroker kernel: [185572.752681] 0 pages in swap cache
                                          Feb 17 11:17:27 iobroker kernel: [185572.752682] Swap cache stats: add 0, delete 0, find 0/0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752683] Free swap  = 0kB
                                          Feb 17 11:17:27 iobroker kernel: [185572.752683] Total swap = 0kB
                                          Feb 17 11:17:27 iobroker kernel: [185572.752684] 1572724 pages RAM
                                          Feb 17 11:17:27 iobroker kernel: [185572.752685] 0 pages HighMem/MovableOnly
                                          Feb 17 11:17:27 iobroker kernel: [185572.752686] 51783 pages reserved
                                          Feb 17 11:17:27 iobroker kernel: [185572.752689] 0 pages cma reserved
                                          Feb 17 11:17:27 iobroker kernel: [185572.752690] 0 pages hwpoisoned
                                          Feb 17 11:17:27 iobroker kernel: [185572.752691] Tasks state (memory values in pages):
                                          Feb 17 11:17:27 iobroker kernel: [185572.752691] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
                                          Feb 17 11:17:27 iobroker kernel: [185572.752700] [    377]     0   377    35296      683   282624        0          -250 systemd-journal
                                          Feb 17 11:17:27 iobroker kernel: [185572.752703] [    411]     0   411     5347      827    73728        0         -1000 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752706] [    599]     0   599    70036     4487    98304        0         -1000 multipathd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752709] [    653]   112   653     1776      733    49152        0             0 rpcbind
                                          Feb 17 11:17:27 iobroker kernel: [185572.752712] [    657]   102   657    22558      662    81920        0             0 systemd-timesyn
                                          Feb 17 11:17:27 iobroker kernel: [185572.752714] [    688]   100   688     6653      713    73728        0             0 systemd-network
                                          Feb 17 11:17:27 iobroker kernel: [185572.752716] [    690]   101   690     6040     1489    90112        0             0 systemd-resolve
                                          Feb 17 11:17:27 iobroker kernel: [185572.752718] [    702]     0   702    58871     1060    90112        0             0 accounts-daemon
                                          Feb 17 11:17:27 iobroker kernel: [185572.752720] [    705]     0   705     2357      814    61440        0             0 bluetoothd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752722] [    710]     0   710     1392      601    49152        0             0 cron
                                          Feb 17 11:17:27 iobroker kernel: [185572.752724] [    711]   103   711     1949      805    53248        0          -900 dbus-daemon
                                          Feb 17 11:17:27 iobroker kernel: [185572.752726] [    717]     0   717    20474      689    61440        0             0 irqbalance
                                          Feb 17 11:17:27 iobroker kernel: [185572.752728] [    718]     0   718     6656     2681    90112        0             0 networkd-dispat
                                          Feb 17 11:17:27 iobroker kernel: [185572.752731] [    719]     0   719     1637      544    49152        0             0 qemu-ga
                                          Feb 17 11:17:27 iobroker kernel: [185572.752733] [    720]   104   720    56087      624    81920        0             0 rsyslogd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752735] [    732]     0   732     4213      941    73728        0             0 systemd-logind
                                          Feb 17 11:17:27 iobroker kernel: [185572.752737] [    734]     0   734    98140     1267   122880        0             0 udisksd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752739] [    735]     0   735      948      491    49152        0             0 atd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752741] [    745]     0   745     3044      929    65536        0         -1000 sshd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752743] [    758]     0   758      715      388    45056        0             0 agetty
                                          Feb 17 11:17:27 iobroker kernel: [185572.752745] [    773]     0   773    26287     2668   102400        0             0 unattended-upgr
                                          Feb 17 11:17:27 iobroker kernel: [185572.752747] [    795]     0   795    58179      794    86016        0             0 polkitd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752750] [  55466]     0 55466    62066      476    98304        0             0 upowerd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752753] [ 154992]     0 154992   292215     4229   286720        0          -900 snapd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752755] [ 179634]  1000 179634  1016283   803799 13590528        0             0 iobroker.js-con
                                          Feb 17 11:17:27 iobroker kernel: [185572.752758] [ 179664]  1000 179664   274516    62398  4775936        0             0 io.admin.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752760] [ 179688]  1000 179688   167893     8967  2334720        0             0 io.email.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752762] [ 179705]  1000 179705   170907    14589  2367488        0             0 io.history.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752764] [ 179720]  1000 179720   277563    55508  5705728        0             0 io.javascript.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752766] [ 179752]  1000 179752   172560    15417  2478080        0             0 io.influxdb.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752769] [ 179807]  1000 179807   235550    11930  2543616        0             0 io.alexa2.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752771] [ 179830]  1000 179830   260645    21474  2674688        0             0 io.mihome-vacuu
                                          Feb 17 11:17:27 iobroker kernel: [185572.752773] [ 179843]  1000 179843   234206     9900  2486272        0             0 io.alexa2.1
                                          Feb 17 11:17:27 iobroker kernel: [185572.752775] [ 179862]  1000 179862   170010    11804  2420736        0             0 io.modbus.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752777] [ 179877]  1000 179877   170662    12442  2703360        0             0 io.mqtt.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752779] [ 179892]  1000 179892   238326    15902  2600960        0             0 io.telegram.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752781] [ 179901]  1000 179901   167782     9130  2396160        0             0 io.onkyo.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752783] [ 179926]  1000 179926   168992    10349  2473984        0             0 io.ping.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752788] [ 179977]  1000 179977   205085    47412  3014656        0             0 io.sonoff.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752791] [ 180033]  1000 180033   236423    12055  2510848        0             0 io.backitup.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752793] [ 180097]  1000 180097   229752    12323  1814528        0             0 io.info.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752795] [ 180454]  1000 180454   186182    11257  2637824        0             0 io.iot.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752798] [ 180574]  1000 180574   218574    11282  2678784        0             0 io.iot.1
                                          Feb 17 11:17:27 iobroker kernel: [185572.752800] [ 180589]  1000 180589   236003    13396  2514944        0             0 io.jarvis.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752802] [ 180610]  1000 180610   173911    23431  2682880        0             0 io.lupusec.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752804] [ 180660]  1000 180660   234680    11490  2596864        0             0 io.parser.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752807] [ 180701]  1000 180701   235683    13335  2441216        0             0 io.plenticore.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752809] [ 180724]  1000 180724   170176    14529  2662400        0             0 io.radar2.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752811] [ 180763]  1000 180763   167700     8939  2379776        0             0 io.samsung.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752813] [ 180783]  1000 180783   232943     9789  2342912        0             0 io.simple-api.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752815] [ 180800]  1000 180800   172168    13773  2330624        0             0 io.statistics.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752817] [ 180979]  1000 180979   234641    10296  2514944        0             0 io.tankerkoenig
                                          Feb 17 11:17:27 iobroker kernel: [185572.752819] [ 180986]  1000 180986   235595    10738  2523136        0             0 io.bring.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752821] [ 181009]  1000 181009   169962    12869  2412544        0             0 io.proxmox.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752823] [ 181031]  1000 181031   170411    14387  2232320        0             0 io.bydbatt.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752832] [ 181042]  1000 181042   232850     8750  2375680        0             0 io.pvforecast.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752835] [ 331158]     0 331158     3482     1022    65536        0             0 sshd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752837] [ 331169]  1000 331169     4591     1119    86016        0             0 systemd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752839] [ 331182]  1000 331182    42506     1175   102400        0             0 (sd-pam)
                                          Feb 17 11:17:27 iobroker kernel: [185572.752842] [ 331304]  1000 331304     3516      837    65536        0             0 sshd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752844] [ 331305]  1000 331305     1465      534    53248        0             0 bash
                                          Feb 17 11:17:27 iobroker kernel: [185572.752847] [ 336178]  1000 336178   170475    12467  2805760        0             0 io.tr-064.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752849] [ 355290]  1000 355290   164702     6762  2220032        0             0 io.frontier_sil
                                          Feb 17 11:17:27 iobroker kernel: [185572.752851] [ 356236]     0 356236     3482     1021    65536        0             0 sshd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752854] [ 356241]     0 356241     3482     1004    73728        0             0 sshd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752856] [ 356376]  1000 356376     3516      759    73728        0             0 sshd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752859] [ 356387]  1000 356387     1465      505    53248        0             0 bash
                                          Feb 17 11:17:27 iobroker kernel: [185572.752861] [ 356417]  1000 356417     3516      721    65536        0             0 sshd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752863] [ 356420]  1000 356420     1465      422    53248        0             0 bash
                                          Feb 17 11:17:27 iobroker kernel: [185572.752865] [ 356570]  1000 356570   164244     6600  2162688        0             0 io.yeelight-2.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752868] [ 356834]  1000 356834   171308    13942  2818048        0             0 io.shelly.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752870] [ 357162]  1000 357162   164403     6264  2195456        0             0 io.mihome.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752872] [ 357217]     0 357217     3482      988    69632        0             0 sshd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752875] [ 357316]  1000 357316     3516      812    69632        0             0 sshd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752877] [ 357317]  1000 357317     1465      528    57344        0             0 bash
                                          Feb 17 11:17:27 iobroker kernel: [185572.752879] [ 357404]  1000 357404   164225     6370  2170880        0             0 io.text2command
                                          Feb 17 11:17:27 iobroker kernel: [185572.752882] [ 357964]  1000 357964   237010    13544  2936832        0             0 io.web.0
                                          Feb 17 11:17:27 iobroker kernel: [185572.752885] [ 357974]  1000 357974   191386    16792  3194880        0             0 io.web.1
                                          Feb 17 11:17:27 iobroker kernel: [185572.752887] [ 358127]     0 358127     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752889] [ 358128]     0 358128     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752895] [ 358129]     0 358129     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752897] [ 358130]     0 358130     5347      419    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752899] [ 358131]     0 358131     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752901] [ 358132]     0 358132     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752903] [ 358133]     0 358133     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752905] [ 358134]     0 358134     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752907] [ 358135]     0 358135     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752908] [ 358136]     0 358136     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752910] [ 358137]     0 358137     5347      659    65536        0             0 systemd-udevd
                                          Feb 17 11:17:27 iobroker kernel: [185572.752912] [ 358142]  1000 358142      652      104    40960        0             0 sh
                                          Feb 17 11:17:27 iobroker kernel: [185572.752915] [ 358143]  1000 358143     1237      919    49152        0             0 arp-scan
                                          Feb 17 11:17:27 iobroker kernel: [185572.752916] [ 358144]  1000 358144     1469      520    49152        0             0 ping
                                          Feb 17 11:17:27 iobroker kernel: [185572.752918] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/iobroker.service,task=iobroker.js-con,pid=179634,uid=1000
                                          Feb 17 11:17:27 iobroker kernel: [185572.752962] Out of memory: Killed process 179634 (iobroker.js-con) total-vm:4065132kB, anon-rss:3213752kB, file-rss:1444kB, shmem-rss:0kB, UID:1000 pgtables:13272kB oom_score_adj:0
                                          Feb 17 11:17:27 iobroker kernel: [185572.946819] oom_reaper: reaped process 179634 (iobroker.js-con), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
                                          Feb 17 11:17:27 iobroker kernel: [185573.010658] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
                                          Feb 17 11:17:27 iobroker kernel: [185573.011690] debugfs: File 'le_max_key_size' in directory 'hci0' already present!
                                          Feb 17 11:17:27 iobroker systemd[1]: iobroker.service: Main process exited, code=killed, status=9/KILL
                                          Feb 17 11:17:27 iobroker kernel: [185573.133563] device ens18 left promiscuous mode
                                          Feb 17 11:17:36 iobroker systemd[1]: Started Session 91 of user iobroker.
                                          Feb 17 11:17:56 iobroker systemd[1]: iobroker.service: Failed with result 'signal'.
                                          Feb 17 11:17:56 iobroker systemd[1]: Stopped ioBroker Server.
                                          

                                          77ad152b-ee30-4370-b670-4c127b3d6c46-image.png

                                          Also hab ich ein iob stop gemacht und danach ein iob start. Dann kam es zu dem Fall dass Instanzen loopten:

                                          2022-02-17 11:19:11.550 - error: admin.0 (358368) admin.0 already running
                                          2022-02-17 11:19:11.551 - warn: admin.0 (358368) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:12.152 - error: host.iobroker instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:15.139 - error: email.0 (358380) email.0 already running
                                          2022-02-17 11:19:15.140 - warn: email.0 (358380) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:15.739 - error: host.iobroker instance system.adapter.email.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:19.206 - error: history.0 (358393) history.0 already running
                                          2022-02-17 11:19:19.208 - warn: history.0 (358393) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:19.803 - error: host.iobroker instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:24.000 - error: javascript.0 (358405) javascript.0 already running
                                          2022-02-17 11:19:24.002 - warn: javascript.0 (358405) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:24.607 - error: host.iobroker instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:27.671 - error: telegram.0 (358417) telegram.0 already running
                                          2022-02-17 11:19:27.673 - warn: telegram.0 (358417) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:28.277 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:31.374 - error: influxdb.0 (358432) influxdb.0 already running
                                          2022-02-17 11:19:31.375 - warn: influxdb.0 (358432) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:31.974 - error: host.iobroker instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:35.248 - error: alexa2.0 (358444) alexa2.0 already running
                                          2022-02-17 11:19:35.249 - warn: alexa2.0 (358444) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:35.848 - error: host.iobroker instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:39.215 - error: alexa2.1 (358457) alexa2.1 already running
                                          2022-02-17 11:19:39.217 - warn: alexa2.1 (358457) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:39.810 - error: host.iobroker instance system.adapter.alexa2.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:43.691 - info: admin.0 (358468) starting. Version 5.3.0 in /opt/iobroker/node_modules/iobroker.admin, node: v14.19.0, js-controller: 4.0.10
                                          2022-02-17 11:19:43.783 - info: admin.0 (358468) requesting all states
                                          2022-02-17 11:19:43.784 - info: admin.0 (358468) requesting all objects
                                          2022-02-17 11:19:44.134 - info: admin.0 (358468) Request actual repository...
                                          2022-02-17 11:19:45.330 - info: admin.0 (358468) received all objects
                                          2022-02-17 11:19:45.538 - info: admin.0 (358468) https server listening on port 8081
                                          2022-02-17 11:19:45.539 - info: admin.0 (358468) Use link "https://localhost:8081" to configure.
                                          2022-02-17 11:19:46.828 - info: admin.0 (358468) Repository received successfully.
                                          2022-02-17 11:19:47.323 - info: email.0 (358500) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.email, node: v14.19.0, js-controller: 4.0.10
                                          2022-02-17 11:19:47.838 - error: mihome-vacuum.0 (358511) mihome-vacuum.0 already running
                                          2022-02-17 11:19:47.839 - warn: mihome-vacuum.0 (358511) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:48.428 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:48.971 - error: admin.0 (358468) error
                                          2022-02-17 11:19:51.615 - error: modbus.0 (358539) modbus.0 already running
                                          2022-02-17 11:19:51.617 - warn: modbus.0 (358539) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:52.210 - error: host.iobroker instance system.adapter.modbus.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          2022-02-17 11:19:55.302 - error: mqtt.0 (358555) mqtt.0 already running
                                          2022-02-17 11:19:55.303 - warn: mqtt.0 (358555) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          2022-02-17 11:19:55.938 - error: host.iobroker instance system.adapter.mqtt.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          

                                          Also noch mal iob stop, mit ps auxww | grep io geschaut dass nichts mehr läuft und nochmal iob start.
                                          Nun läuft er wieder. Aber dass mit dem OOM Killer seit js-controller 4.x ist schon "interessant".

                                          ..:: So long! Tom ::..

                                          NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                                          apollon77A 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
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          853

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          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