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. Tester
  4. Test js-controller v2.0.x (GitHub)

NEWS

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

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

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

Test js-controller v2.0.x (GitHub)

Geplant Angeheftet Gesperrt Verschoben Tester
js-controller
1.0k Beiträge 48 Kommentatoren 313.7k Aufrufe 35 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.
  • apollon77A apollon77

    Und weils so schön ist 2.0.34 auf GitHub ;-)

    Die 2.0.33 hatte ein Problem "custom" state Settings (History und so) bei nutzung von "file" für Objekte wieder zu deaktivieren ;-)

    D Offline
    D Offline
    darkiop
    Most Active
    schrieb am zuletzt editiert von darkiop
    #831

    @apollon77 sagte in [Aufruf] js-controller 2.0 Beta Test:

    Die 2.0.33 hatte ein Problem "custom" state Settings (History und so) bei nutzung von "file" für Objekte wieder zu deaktivieren

    Alla Hopp, dann werf ich mal die Skripte zum Updaten an :)

    Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

    1 Antwort Letzte Antwort
    1
    • apollon77A apollon77

      Und weils so schön ist 2.0.34 auf GitHub ;-)

      Die 2.0.33 hatte ein Problem "custom" state Settings (History und so) bei nutzung von "file" für Objekte wieder zu deaktivieren ;-)

      sigi234S Online
      sigi234S Online
      sigi234
      Forum Testing Most Active
      schrieb am zuletzt editiert von sigi234
      #832

      @apollon77 sagte in [Aufruf] js-controller 2.0 Beta Test:

      Und weils so schön ist 2.0.34 auf GitHub ;-)

      Die 2.0.33 hatte ein Problem "custom" state Settings (History und so) bei nutzung von "file" für Objekte wieder zu deaktivieren ;-)

      Host "Medion(Test)" is up to date ?
      Edit:
      Dauerte ein wenig.

      Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
      Immer Daten sichern!

      1 Antwort Letzte Antwort
      0
      • smartboartS Offline
        smartboartS Offline
        smartboart
        schrieb am zuletzt editiert von smartboart
        #833

        hi, hab immer mal wieder nen System Restart. Bemerke ich nur wegen der Telegramm Meldung & iobroker started telegramm. Hier der log dazu..
        Alle Versionen latest und Aktuell...Jemand ne idee


        2019-10-18 14:16:40.126 - info: host.ioBroker-Rock iobroker.js-controller version 2.0.34 js-controller starting
        2019-10-18 14:16:40.144 - info: host.ioBroker-Rock Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
        2019-10-18 14:16:40.146 - info: host.ioBroker-Rock hostname: ioBroker-Rock, node: v10.16.3
        2019-10-18 14:16:40.150 - info: host.ioBroker-Rock ip addresses: fe80::e118:30d6:9c4:76da
        2019-10-18 14:16:40.368 - info: host.ioBroker-Rock connected to Objects and States
        2019-10-18 14:16:40.457 - error: host.ioBroker-Rock uncaught exception: addMembership ENODEV
        2019-10-18 14:16:40.459 - error: host.ioBroker-Rock Error: addMembership ENODEV
        at Socket.addMembership (dgram.js:581:11)
        at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/multihostServer.js:258:20)
        at Socket.emit (events.js:198:13)
        at startListening (dgram.js:128:10)
        at state.handle.lookup (dgram.js:249:7)
        at process._tickCallback (internal/process/next_tick.js:63:19)
        2019-10-18 14:16:40.473 - info: host.ioBroker-Rock iobroker _restart
        2019-10-18 14:16:41.696 - info: host.ioBroker-Rock 38 instances found
        2019-10-18 14:16:41.857 - info: host.ioBroker-Rock starting 26 instances
        2019-10-18 14:16:41.945 - info: host.ioBroker-Rock instance system.adapter.admin.0 started with pid 1333
        2019-10-18 14:16:41.952 - info: host.ioBroker-Rock terminated
        2019-10-18 14:16:43.868 - info: host.ioBroker-Rock iobroker.js-controller version 2.0.34 js-controller starting
        2019-10-18 14:16:43.884 - info: host.ioBroker-Rock Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
        2019-10-18 14:16:43.886 - info: host.ioBroker-Rock hostname: ioBroker-Rock, node: v10.16.3
        2019-10-18 14:16:43.890 - info: host.ioBroker-Rock ip addresses: fe80::e118:30d6:9c4:76da
        2019-10-18 14:16:44.067 - info: host.ioBroker-Rock connected to Objects and States
        2019-10-18 14:16:44.148 - error: host.ioBroker-Rock uncaught exception: addMembership ENODEV
        2019-10-18 14:16:44.150 - error: host.ioBroker-Rock Error: addMembership ENODEV
        at Socket.addMembership (dgram.js:581:11)
        at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/multihostServer.js:258:20)
        at Socket.emit (events.js:198:13)
        at startListening (dgram.js:128:10)
        at state.handle.lookup (dgram.js:249:7)
        at process._tickCallback (internal/process/next_tick.js:63:19)
        2019-10-18 14:16:44.163 - info: host.ioBroker-Rock iobroker _restart
        2019-10-18 14:16:45.442 - info: host.ioBroker-Rock 38 instances found
        2019-10-18 14:16:45.543 - info: host.ioBroker-Rock starting 26 instances
        2019-10-18 14:16:45.598 - info: host.ioBroker-Rock instance system.adapter.admin.0 started with pid 1537
        2019-10-18 14:16:45.604 - info: host.ioBroker-Rock terminated
        2019-10-18 14:16:45.616 - info: host.ioBroker-Rock iobroker Starting node restart.js
        2019-10-18 14:16:47.422 - info: host.ioBroker-Rock iobroker.js-controller version 2.0.34 js-controller starting
        2019-10-18 14:16:47.437 - info: host.ioBroker-Rock Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
        2019-10-18 14:16:47.439 - info: host.ioBroker-Rock hostname: ioBroker-Rock, node: v10.16.3
        2019-10-18 14:16:47.443 - info: host.ioBroker-Rock ip addresses: 192.168.1.42 fe80::e118:30d6:9c4:76da
        2019-10-18 14:16:47.622 - info: host.ioBroker-Rock connected to Objects and States
        2019-10-18 14:16:47.702 - warn: host.ioBroker-Rock Multihost discovery server: service started on 0.0.0.0:50005
        2019-10-18 14:16:48.815 - info: host.ioBroker-Rock 38 instances found
        2019-10-18 14:16:48.907 - info: host.ioBroker-Rock starting 26 instances
        2019-10-18 14:16:48.980 - info: host.ioBroker-Rock instance system.adapter.admin.0 started with pid 1566
        2019-10-18 14:17:10.510 - info: host.ioBroker-Rock instance system.adapter.backitup.0 started with pid 1581
        2019-10-18 14:17:14.503 - info: host.ioBroker-Rock instance system.adapter.broadlink2.0 started with pid 1589
        2019-10-18 14:17:18.499 - info: host.ioBroker-Rock instance system.adapter.email.0 started with pid 1612
        2019-10-18 14:17:22.498 - info: host.ioBroker-Rock instance system.adapter.fritzbox.0 started with pid 1635
        2019-10-18 14:17:24.752 - warn: broadlink2.0 (1589) sendT1Packed error 'socket not created/bound or closed or waiting!'
        2019-10-18 14:17:24.768 - warn: broadlink2.0 (1589) sendT1Packed error 'socket not created/bound or closed or waiting!'
        2019-10-18 14:17:26.500 - info: host.ioBroker-Rock instance system.adapter.fullybrowser.0 started with pid 1653
        2019-10-18 14:17:30.501 - info: host.ioBroker-Rock instance system.adapter.gruenbeck.0 started with pid 1668
        2019-10-18 14:17:34.499 - info: host.ioBroker-Rock instance system.adapter.history.0 started with pid 1683
        2019-10-18 14:17:38.502 - info: host.ioBroker-Rock instance system.adapter.hm-rega.0 started with pid 1698
        2019-10-18 14:17:42.501 - info: host.ioBroker-Rock instance system.adapter.hm-rpc.0 started with pid 1713
        2019-10-18 14:17:46.503 - info: host.ioBroker-Rock instance system.adapter.info.0 started with pid 1728
        2019-10-18 14:17:50.511 - info: host.ioBroker-Rock instance system.adapter.javascript.0 started with pid 1747
        2019-10-18 14:17:54.501 - info: host.ioBroker-Rock instance system.adapter.modbus.0 started with pid 2169
        2019-10-18 14:17:57.657 - info: javascript.0 (1747) starting. Version 4.3.1 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.16.3
        2019-10-18 14:17:57.765 - info: javascript.0 (1747) requesting all states
        2019-10-18 14:17:57.770 - info: javascript.0 (1747) requesting all objects
        2019-10-18 14:17:58.501 - info: host.ioBroker-Rock instance system.adapter.socketio.0 started with pid 2197
        2019-10-18 14:17:59.579 - info: javascript.0 (1747) received all states
        2019-10-18 14:18:00.749 - info: javascript.0 (1747) received all objects
        2019-10-18 14:18:02.510 - info: host.ioBroker-Rock instance system.adapter.sonoff.0 started with pid 2401
        2019-10-18 14:18:06.501 - info: host.ioBroker-Rock instance system.adapter.statistics.0 started with pid 2421
        2019-10-18 14:18:10.565 - info: host.ioBroker-Rock instance system.adapter.telegram.0 started with pid 2621
        2019-10-18 14:18:12.356 - info: javascript.0 (1747) Start javascript script.js.common.Alarmanlage.Alarm_output

        apollon77A 1 Antwort Letzte Antwort
        0
        • smartboartS smartboart

          hi, hab immer mal wieder nen System Restart. Bemerke ich nur wegen der Telegramm Meldung & iobroker started telegramm. Hier der log dazu..
          Alle Versionen latest und Aktuell...Jemand ne idee


          2019-10-18 14:16:40.126 - info: host.ioBroker-Rock iobroker.js-controller version 2.0.34 js-controller starting
          2019-10-18 14:16:40.144 - info: host.ioBroker-Rock Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
          2019-10-18 14:16:40.146 - info: host.ioBroker-Rock hostname: ioBroker-Rock, node: v10.16.3
          2019-10-18 14:16:40.150 - info: host.ioBroker-Rock ip addresses: fe80::e118:30d6:9c4:76da
          2019-10-18 14:16:40.368 - info: host.ioBroker-Rock connected to Objects and States
          2019-10-18 14:16:40.457 - error: host.ioBroker-Rock uncaught exception: addMembership ENODEV
          2019-10-18 14:16:40.459 - error: host.ioBroker-Rock Error: addMembership ENODEV
          at Socket.addMembership (dgram.js:581:11)
          at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/multihostServer.js:258:20)
          at Socket.emit (events.js:198:13)
          at startListening (dgram.js:128:10)
          at state.handle.lookup (dgram.js:249:7)
          at process._tickCallback (internal/process/next_tick.js:63:19)
          2019-10-18 14:16:40.473 - info: host.ioBroker-Rock iobroker _restart
          2019-10-18 14:16:41.696 - info: host.ioBroker-Rock 38 instances found
          2019-10-18 14:16:41.857 - info: host.ioBroker-Rock starting 26 instances
          2019-10-18 14:16:41.945 - info: host.ioBroker-Rock instance system.adapter.admin.0 started with pid 1333
          2019-10-18 14:16:41.952 - info: host.ioBroker-Rock terminated
          2019-10-18 14:16:43.868 - info: host.ioBroker-Rock iobroker.js-controller version 2.0.34 js-controller starting
          2019-10-18 14:16:43.884 - info: host.ioBroker-Rock Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
          2019-10-18 14:16:43.886 - info: host.ioBroker-Rock hostname: ioBroker-Rock, node: v10.16.3
          2019-10-18 14:16:43.890 - info: host.ioBroker-Rock ip addresses: fe80::e118:30d6:9c4:76da
          2019-10-18 14:16:44.067 - info: host.ioBroker-Rock connected to Objects and States
          2019-10-18 14:16:44.148 - error: host.ioBroker-Rock uncaught exception: addMembership ENODEV
          2019-10-18 14:16:44.150 - error: host.ioBroker-Rock Error: addMembership ENODEV
          at Socket.addMembership (dgram.js:581:11)
          at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/multihostServer.js:258:20)
          at Socket.emit (events.js:198:13)
          at startListening (dgram.js:128:10)
          at state.handle.lookup (dgram.js:249:7)
          at process._tickCallback (internal/process/next_tick.js:63:19)
          2019-10-18 14:16:44.163 - info: host.ioBroker-Rock iobroker _restart
          2019-10-18 14:16:45.442 - info: host.ioBroker-Rock 38 instances found
          2019-10-18 14:16:45.543 - info: host.ioBroker-Rock starting 26 instances
          2019-10-18 14:16:45.598 - info: host.ioBroker-Rock instance system.adapter.admin.0 started with pid 1537
          2019-10-18 14:16:45.604 - info: host.ioBroker-Rock terminated
          2019-10-18 14:16:45.616 - info: host.ioBroker-Rock iobroker Starting node restart.js
          2019-10-18 14:16:47.422 - info: host.ioBroker-Rock iobroker.js-controller version 2.0.34 js-controller starting
          2019-10-18 14:16:47.437 - info: host.ioBroker-Rock Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
          2019-10-18 14:16:47.439 - info: host.ioBroker-Rock hostname: ioBroker-Rock, node: v10.16.3
          2019-10-18 14:16:47.443 - info: host.ioBroker-Rock ip addresses: 192.168.1.42 fe80::e118:30d6:9c4:76da
          2019-10-18 14:16:47.622 - info: host.ioBroker-Rock connected to Objects and States
          2019-10-18 14:16:47.702 - warn: host.ioBroker-Rock Multihost discovery server: service started on 0.0.0.0:50005
          2019-10-18 14:16:48.815 - info: host.ioBroker-Rock 38 instances found
          2019-10-18 14:16:48.907 - info: host.ioBroker-Rock starting 26 instances
          2019-10-18 14:16:48.980 - info: host.ioBroker-Rock instance system.adapter.admin.0 started with pid 1566
          2019-10-18 14:17:10.510 - info: host.ioBroker-Rock instance system.adapter.backitup.0 started with pid 1581
          2019-10-18 14:17:14.503 - info: host.ioBroker-Rock instance system.adapter.broadlink2.0 started with pid 1589
          2019-10-18 14:17:18.499 - info: host.ioBroker-Rock instance system.adapter.email.0 started with pid 1612
          2019-10-18 14:17:22.498 - info: host.ioBroker-Rock instance system.adapter.fritzbox.0 started with pid 1635
          2019-10-18 14:17:24.752 - warn: broadlink2.0 (1589) sendT1Packed error 'socket not created/bound or closed or waiting!'
          2019-10-18 14:17:24.768 - warn: broadlink2.0 (1589) sendT1Packed error 'socket not created/bound or closed or waiting!'
          2019-10-18 14:17:26.500 - info: host.ioBroker-Rock instance system.adapter.fullybrowser.0 started with pid 1653
          2019-10-18 14:17:30.501 - info: host.ioBroker-Rock instance system.adapter.gruenbeck.0 started with pid 1668
          2019-10-18 14:17:34.499 - info: host.ioBroker-Rock instance system.adapter.history.0 started with pid 1683
          2019-10-18 14:17:38.502 - info: host.ioBroker-Rock instance system.adapter.hm-rega.0 started with pid 1698
          2019-10-18 14:17:42.501 - info: host.ioBroker-Rock instance system.adapter.hm-rpc.0 started with pid 1713
          2019-10-18 14:17:46.503 - info: host.ioBroker-Rock instance system.adapter.info.0 started with pid 1728
          2019-10-18 14:17:50.511 - info: host.ioBroker-Rock instance system.adapter.javascript.0 started with pid 1747
          2019-10-18 14:17:54.501 - info: host.ioBroker-Rock instance system.adapter.modbus.0 started with pid 2169
          2019-10-18 14:17:57.657 - info: javascript.0 (1747) starting. Version 4.3.1 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.16.3
          2019-10-18 14:17:57.765 - info: javascript.0 (1747) requesting all states
          2019-10-18 14:17:57.770 - info: javascript.0 (1747) requesting all objects
          2019-10-18 14:17:58.501 - info: host.ioBroker-Rock instance system.adapter.socketio.0 started with pid 2197
          2019-10-18 14:17:59.579 - info: javascript.0 (1747) received all states
          2019-10-18 14:18:00.749 - info: javascript.0 (1747) received all objects
          2019-10-18 14:18:02.510 - info: host.ioBroker-Rock instance system.adapter.sonoff.0 started with pid 2401
          2019-10-18 14:18:06.501 - info: host.ioBroker-Rock instance system.adapter.statistics.0 started with pid 2421
          2019-10-18 14:18:10.565 - info: host.ioBroker-Rock instance system.adapter.telegram.0 started with pid 2621
          2019-10-18 14:18:12.356 - info: javascript.0 (1747) Start javascript script.js.common.Alarmanlage.Alarm_output

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

          @smartboart ENODEV heisst Error NO DEVice und das ganze auf Netzwerkebene ... Was ist das für ein System? Scheinbar war Netzwerk-Device weg? Netzteil ausreichend dimensioniert?

          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
          smartboartS 1 Antwort Letzte Antwort
          0
          • apollon77A apollon77

            @smartboart ENODEV heisst Error NO DEVice und das ganze auf Netzwerkebene ... Was ist das für ein System? Scheinbar war Netzwerk-Device weg? Netzteil ausreichend dimensioniert?

            smartboartS Offline
            smartboartS Offline
            smartboart
            schrieb am zuletzt editiert von smartboart
            #835

            @apollon77 Ist ein Multihostsystem mit Redis auf dem Master. file und states. Beide SBC haengen jeweils mittels netzwerkkabel an jeweils 1GB Anschluß des selben Router.
            Versorgt werden beide SBC als auch die Fritte ueber eine DC Ups 12v 5A .
            Die SBC bekommen davon jeweils mittels 12V auf 5V 3A Umsetzer ihre 5 V.
            Spannung wuerde ich ausschliessen. Die DC Ups hat bei angehängter Last eine Autonomie von 30min. Hardware SBC siehe unten. Auslastung > noch Luft nach oben...

            apollon77A 1 Antwort Letzte Antwort
            0
            • smartboartS smartboart

              @apollon77 Ist ein Multihostsystem mit Redis auf dem Master. file und states. Beide SBC haengen jeweils mittels netzwerkkabel an jeweils 1GB Anschluß des selben Router.
              Versorgt werden beide SBC als auch die Fritte ueber eine DC Ups 12v 5A .
              Die SBC bekommen davon jeweils mittels 12V auf 5V 3A Umsetzer ihre 5 V.
              Spannung wuerde ich ausschliessen. Die DC Ups hat bei angehängter Last eine Autonomie von 30min. Hardware SBC siehe unten. Auslastung > noch Luft nach oben...

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

              @smartboart Naja ... angenommen allein ein Raspi braucht ggf bis zu 2+A und du hast 3 solche Geräte an 5A hängen ... Ich weiss das ein Raspi in Unterversorgungs-Situationen Chips abschaltet die u.a. Ethernet, WLAN und USB bereistetllen weil ich nicht wie das bei anderen geräten ist.

              Schau mal in /var/log/syslog ob zu den Zeitpunkten da was zu sehen ist bitte

              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
              smartboartS 1 Antwort Letzte Antwort
              0
              • apollon77A apollon77

                @smartboart Naja ... angenommen allein ein Raspi braucht ggf bis zu 2+A und du hast 3 solche Geräte an 5A hängen ... Ich weiss das ein Raspi in Unterversorgungs-Situationen Chips abschaltet die u.a. Ethernet, WLAN und USB bereistetllen weil ich nicht wie das bei anderen geräten ist.

                Schau mal in /var/log/syslog ob zu den Zeitpunkten da was zu sehen ist bitte

                smartboartS Offline
                smartboartS Offline
                smartboart
                schrieb am zuletzt editiert von
                #837

                @apollon77 Nur 2 Geraete mit 5V 3A...entspricht 30W. Ups mit 12V 5A entspricht 60Watt. Glaube nicht dass die Fritte mehr wie 30 Watt zieht.. Ausserdem wuerde das die Ups melden / Ueberlast...Den Tipp werde ich trotzdem Beherzigen und mal ein Messgeraet dran haengen. Den Syslog schaue ich mir an...

                apollon77A 1 Antwort Letzte Antwort
                0
                • smartboartS smartboart

                  @apollon77 Nur 2 Geraete mit 5V 3A...entspricht 30W. Ups mit 12V 5A entspricht 60Watt. Glaube nicht dass die Fritte mehr wie 30 Watt zieht.. Ausserdem wuerde das die Ups melden / Ueberlast...Den Tipp werde ich trotzdem Beherzigen und mal ein Messgeraet dran haengen. Den Syslog schaue ich mir an...

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

                  @smartboart Sagen wir es so: Ich hab schon viele komische Dinge erlebt die nach Tausch oder "upgrade" eines Netzteils plötzlich weg waren :-) Und vor allem komische Effekte wie "netzwerk plötzlich weg" hatten wir zumindestens bei Systemen wir Raspis nicht nur einmal. Teilweise sind es Lastspitzen die plötzlich auftreten why ever ... Aber /var/log/syslog sollte sowas zeigen

                  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
                  smartboartS 2 Antworten Letzte Antwort
                  0
                  • apollon77A apollon77

                    @smartboart Sagen wir es so: Ich hab schon viele komische Dinge erlebt die nach Tausch oder "upgrade" eines Netzteils plötzlich weg waren :-) Und vor allem komische Effekte wie "netzwerk plötzlich weg" hatten wir zumindestens bei Systemen wir Raspis nicht nur einmal. Teilweise sind es Lastspitzen die plötzlich auftreten why ever ... Aber /var/log/syslog sollte sowas zeigen

                    smartboartS Offline
                    smartboartS Offline
                    smartboart
                    schrieb am zuletzt editiert von smartboart
                    #839

                    @apollon77
                    Im Raspy Slave ist um die Uhrzeit kein Eintrag gemacht worden. Im Master startet diese genau mit dem neustart...schaue gerade nur über vpn mit handy (nano /var/log/syslog) wenn ich zu hause bin lade ich die datei mal hoch...

                    1 Antwort Letzte Antwort
                    0
                    • apollon77A apollon77

                      @smartboart Sagen wir es so: Ich hab schon viele komische Dinge erlebt die nach Tausch oder "upgrade" eines Netzteils plötzlich weg waren :-) Und vor allem komische Effekte wie "netzwerk plötzlich weg" hatten wir zumindestens bei Systemen wir Raspis nicht nur einmal. Teilweise sind es Lastspitzen die plötzlich auftreten why ever ... Aber /var/log/syslog sollte sowas zeigen

                      smartboartS Offline
                      smartboartS Offline
                      smartboart
                      schrieb am zuletzt editiert von smartboart
                      #840

                      @apollon77
                      so hier der syslog..

                      hier mal ein Auszug..Tauchen Sachen mit Spannungswerten auf...kann es aber nicht wirklich deuten. Google spuckt jede Menge dieser Einträge im Zusammenhang mit dem Rock64 aus.

                      Oct 18 14:16:35 localhost kernel: [ 1.495918] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: debug
                      Oct 18 14:16:35 localhost kernel: [ 1.495942] vcc_sd: unable to resolve supply
                      Oct 18 14:16:35 localhost kernel: [ 1.495958] vcc_sd: 3300 mV
                      Oct 18 14:16:35 localhost kernel: [ 1.496208] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                      Oct 18 14:16:35 localhost kernel: [ 1.496233] vcc_sd: regulator get failed, ret=-517
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: dpkg.log
                      Oct 18 14:16:35 localhost kernel: [ 1.496250] reg-fixed-voltage sdmmc-regulator:

                      syslog


                      Oct 18 14:16:35 localhost fake-hwclock[246]: Current system time: 2019-10-18 12:16:33
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Booting Linux on physical CPU 0x0
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuacct
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Linux version 4.4.192-rockchip64 (root@builder) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02) ) #1 SMP Tue Oct 8 18:39:24 CEST 2019
                      Oct 18 14:16:35 localhost fake-hwclock[246]: fake-hwclock saved clock information is in the past: 2019-10-18 11:17:01
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Boot CPU: AArch64 Processor [410fd034]
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] earlycon: Early serial console at MMIO32 0xff130000 (options '')
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] bootconsole [uart0] enabled
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] On node 0 totalpages: 1043968
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] DMA zone: 16312 pages used for memmap
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] DMA zone: 0 pages reserved
                      Oct 18 14:16:35 localhost fake-hwclock[246]: To set system time to this saved clock anyway, use "force"
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] DMA zone: 1043968 pages, LIFO batch:31
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] psci: probing for conduit method from DT.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] psci: PSCIv1.0 detected in firmware.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] psci: Using standard PSCI v0.2 function IDs
                      Oct 18 14:16:35 localhost resolvconf[309]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] PERCPU: Embedded 21 pages/cpu @ffffffc0fef1f000 s46312 r8192 d31512 u86016
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] pcpu-alloc: s46312 r8192 d31512 u86016 alloc=21*4096
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
                      Oct 18 14:16:35 localhost systemd[1]: Started Create Static Device Nodes in /dev.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Detected VIPT I-cache on CPU0
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] CPU features: enabling workaround for ARM erratum 845719
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1027656
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Kernel command line: earlycon=uart8250,mmio32,0xff130000 swiotlb=1 kpti=0 no_console_suspend=1 usbcore.autosuspend=-1 root=UUID=37725f38-d37c-429c-89a6-9fc49158dcfe rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=b275bf8f-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
                      Oct 18 14:16:35 localhost systemd[1]: Starting udev Kernel Device Manager...
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] software IO TLB: mapped [mem 0xfeed7000-0xfef17000] (0MB)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Memory: 4078868K/4175872K available (11518K kernel code, 1488K rwdata, 4160K rodata, 1216K init, 699K bss, 97004K reserved, 0K cma-reserved)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Virtual kernel memory layout:
                      Oct 18 14:16:35 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] modules : 0xffffff8000000000 - 0xffffff8008000000 ( 128 MB)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] vmalloc : 0xffffff8008000000 - 0xffffffbdbfff0000 ( 246 GB)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] .init : 0xffffff8008fe0000 - 0xffffff8009110000 ( 1216 KB)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] .text : 0xffffff8008080000 - 0xffffff8008bc0000 ( 11520 KB)
                      Oct 18 14:16:35 localhost systemd[1]: Started Flush Journal to Persistent Storage.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] .rodata : 0xffffff8008bc0000 - 0xffffff8008fe0000 ( 4224 KB)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] .data : 0xffffff8009110000 - 0xffffff8009284008 ( 1489 KB)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] vmemmap : 0xffffffbdc0000000 - 0xffffffbfc0000000 ( 8 GB maximum)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] 0xffffffbdc0008000 - 0xffffffbdc3fc0000 ( 63 MB actual)
                      Oct 18 14:16:35 localhost systemd[1]: Started udev Kernel Device Manager.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] fixed : 0xffffffbffe7fb000 - 0xffffffbffec00000 ( 4116 KB)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] PCI I/O : 0xffffffbffee00000 - 0xffffffbfffe00000 ( 16 MB)
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] memory : 0xffffffc000200000 - 0xffffffc0ff000000 ( 4078 MB)
                      Oct 18 14:16:35 localhost systemd[1]: Started Set the console keyboard layout.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Hierarchical RCU implementation.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Build-time adjustment of leaf fanout to 64.
                      Oct 18 14:16:35 localhost systemd[1]: Reached target Local File Systems (Pre).
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] NR_IRQS:64 nr_irqs:64 0
                      Oct 18 14:16:35 localhost systemd[1]: Mounting /tmp...
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] GIC: Using split EOI/Deactivate mode
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                      Oct 18 14:16:35 localhost systemd[1]: Mounted /tmp.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] Architected cp15 timer(s) running at 24.00MHz (phys).
                      Oct 18 14:16:35 localhost systemd[1]: Reached target Local File Systems.
                      Oct 18 14:16:35 localhost kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
                      Oct 18 14:16:35 localhost kernel: [ 0.000007] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
                      Oct 18 14:16:35 localhost kernel: [ 0.001143] Console: colour dummy device 80x25
                      Oct 18 14:16:35 localhost systemd[1]: Starting Preprocess NFS configuration...
                      Oct 18 14:16:35 localhost kernel: [ 0.001159] console [tty1] enabled
                      Oct 18 14:16:35 localhost kernel: [ 0.001170] bootconsole [uart0] disabled
                      Oct 18 14:16:35 localhost kernel: [ 0.001195] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
                      Oct 18 14:16:35 localhost kernel: [ 0.001213] pid_max: default: 32768 minimum: 301
                      Oct 18 14:16:35 localhost systemd[1]: Starting Armbian ZRAM config...
                      Oct 18 14:16:35 localhost kernel: [ 0.001349] Security Framework initialized
                      Oct 18 14:16:35 localhost kernel: [ 0.001362] Yama: becoming mindful.
                      Oct 18 14:16:35 localhost kernel: [ 0.001387] AppArmor: AppArmor disabled by boot time parameter
                      Oct 18 14:16:35 localhost systemd[1]: Starting Set console font and keymap...
                      Oct 18 14:16:35 localhost kernel: [ 0.001451] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
                      Oct 18 14:16:35 localhost kernel: [ 0.001467] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
                      Oct 18 14:16:35 localhost kernel: [ 0.002397] Initializing cgroup subsys io
                      Oct 18 14:16:35 localhost kernel: [ 0.002421] Initializing cgroup subsys memory
                      Oct 18 14:16:35 localhost kernel: [ 0.002458] Initializing cgroup subsys devices
                      Oct 18 14:16:35 localhost kernel: [ 0.002476] Initializing cgroup subsys freezer
                      Oct 18 14:16:35 localhost kernel: [ 0.002493] Initializing cgroup subsys net_cls
                      Oct 18 14:16:35 localhost systemd[1]: Starting Create Volatile Files and Directories...
                      Oct 18 14:16:35 localhost kernel: [ 0.002513] Initializing cgroup subsys perf_event
                      Oct 18 14:16:35 localhost kernel: [ 0.002531] Initializing cgroup subsys net_prio
                      Oct 18 14:16:35 localhost kernel: [ 0.002551] Initializing cgroup subsys hugetlb
                      Oct 18 14:16:35 localhost kernel: [ 0.002565] Initializing cgroup subsys pids
                      Oct 18 14:16:35 localhost systemd[1]: Starting Raise network interfaces...
                      Oct 18 14:16:35 localhost kernel: [ 0.002619] ftrace: allocating 43805 entries in 172 pages
                      Oct 18 14:16:35 localhost kernel: [ 0.134714] sched-energy: CPU device node has no sched-energy-costs
                      Oct 18 14:16:35 localhost kernel: [ 0.134736] Invalid sched_group_energy for CPU0
                      Oct 18 14:16:35 localhost kernel: [ 0.134746] CPU0: update cpu_capacity 1024
                      Oct 18 14:16:35 localhost systemd[1]: Started Preprocess NFS configuration.
                      Oct 18 14:16:35 localhost kernel: [ 0.134809] ASID allocator initialised with 32768 entries
                      Oct 18 14:16:35 localhost kernel: [ 0.137693] Detected VIPT I-cache on CPU1
                      Oct 18 14:16:35 localhost systemd[1]: Reached target NFS client services.
                      Oct 18 14:16:35 localhost kernel: [ 0.137751] Invalid sched_group_energy for CPU1
                      Oct 18 14:16:35 localhost kernel: [ 0.137757] CPU1: update cpu_capacity 1024
                      Oct 18 14:16:35 localhost kernel: [ 0.137762] CPU1: Booted secondary processor [410fd034]
                      Oct 18 14:16:35 localhost systemd[1]: Started Set console font and keymap.
                      Oct 18 14:16:35 localhost kernel: [ 0.138511] Detected VIPT I-cache on CPU2
                      Oct 18 14:16:35 localhost kernel: [ 0.138558] Invalid sched_group_energy for CPU2
                      Oct 18 14:16:35 localhost kernel: [ 0.138563] CPU2: update cpu_capacity 1024
                      Oct 18 14:16:35 localhost systemd[1]: Started udev Coldplug all Devices.
                      Oct 18 14:16:35 localhost kernel: [ 0.138569] CPU2: Booted secondary processor [410fd034]
                      Oct 18 14:16:35 localhost kernel: [ 0.139246] Detected VIPT I-cache on CPU3
                      Oct 18 14:16:35 localhost kernel: [ 0.139291] Invalid sched_group_energy for CPU3
                      Oct 18 14:16:35 localhost systemd[1]: Started Create Volatile Files and Directories.
                      Oct 18 14:16:35 localhost kernel: [ 0.139297] CPU3: update cpu_capacity 1024
                      Oct 18 14:16:35 localhost kernel: [ 0.139302] CPU3: Booted secondary processor [410fd034]
                      Oct 18 14:16:35 localhost kernel: [ 0.139403] Brought up 4 CPUs
                      Oct 18 14:16:35 localhost kernel: [ 0.139467] SMP: Total of 4 processors activated.
                      Oct 18 14:16:35 localhost systemd[1]: Starting RPC bind portmap service...
                      Oct 18 14:16:35 localhost kernel: [ 0.139482] CPU features: kernel page table isolation forced OFF by command line option
                      Oct 18 14:16:35 localhost kernel: [ 0.139493] CPU features: detected feature: 32-bit EL0 Support
                      Oct 18 14:16:35 localhost kernel: [ 0.139508] CPU: All CPU(s) started at EL2
                      Oct 18 14:16:35 localhost kernel: [ 0.139547] alternatives: patching kernel code
                      Oct 18 14:16:35 localhost systemd[1]: Reached target System Time Synchronized.
                      Oct 18 14:16:35 localhost kernel: [ 0.139794] Invalid sched_group_energy for CPU3
                      Oct 18 14:16:35 localhost kernel: [ 0.139808] Invalid sched_group_energy for Cluster3
                      Oct 18 14:16:35 localhost kernel: [ 0.139817] Invalid sched_group_energy for CPU2
                      Oct 18 14:16:35 localhost systemd[1]: Started Entropy daemon using the HAVEGE algorithm.
                      Oct 18 14:16:35 localhost kernel: [ 0.139827] Invalid sched_group_energy for Cluster2
                      Oct 18 14:16:35 localhost kernel: [ 0.139837] Invalid sched_group_energy for CPU1
                      Oct 18 14:16:35 localhost kernel: [ 0.139847] Invalid sched_group_energy for Cluster1
                      Oct 18 14:16:35 localhost kernel: [ 0.139857] Invalid sched_group_energy for CPU0
                      Oct 18 14:16:35 localhost systemd[1]: Starting Update UTMP about System Boot/Shutdown...
                      Oct 18 14:16:35 localhost kernel: [ 0.139867] Invalid sched_group_energy for Cluster0
                      Oct 18 14:16:35 localhost kernel: [ 0.140633] devtmpfs: initialized
                      Oct 18 14:16:35 localhost kernel: [ 0.164712] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
                      Oct 18 14:16:35 localhost kernel: [ 0.164749] futex hash table entries: 1024 (order: 4, 65536 bytes)
                      Oct 18 14:16:35 localhost systemd-udevd[382]: Process '/sbin/iwconfig wlan0 power off' failed with exit code 250.
                      Oct 18 14:16:35 localhost kernel: [ 0.165346] xor: measuring software checksum speed
                      Oct 18 14:16:35 localhost kernel: [ 0.202627] 8regs : 1080.000 MB/sec
                      Oct 18 14:16:35 localhost kernel: [ 0.242708] 8regs_prefetch: 968.000 MB/sec
                      Oct 18 14:16:35 localhost kernel: [ 0.282796] 32regs : 1458.000 MB/sec
                      Oct 18 14:16:35 localhost systemd-udevd[380]: Process '/bin/mount -t fusectl fusectl /sys/fs/fuse/connections' failed with exit code 32.
                      Oct 18 14:16:35 localhost kernel: [ 0.322881] 32regs_prefetch: 1224.000 MB/sec
                      Oct 18 14:16:35 localhost kernel: [ 0.322893] xor: using function: 32regs (1458.000 MB/sec)
                      Oct 18 14:16:35 localhost kernel: [ 0.322933] pinctrl core: initialized pinctrl subsystem
                      Oct 18 14:16:35 localhost systemd[1]: Started Update UTMP about System Boot/Shutdown.
                      Oct 18 14:16:35 localhost systemd[1]: Started RPC bind portmap service.
                      Oct 18 14:16:35 localhost systemd[1]: Reached target RPC Port Mapper.
                      Oct 18 14:16:35 localhost systemd[1]: Reached target Remote File Systems (Pre).
                      Oct 18 14:16:35 localhost systemd[1]: Reached target Remote File Systems.
                      Oct 18 14:16:35 localhost systemd[1]: Found device /dev/ttyS2.
                      Oct 18 14:16:35 localhost armbian-zram-config[390]: Setting up swapspace version 1, size = 1024 MiB (1073737728 bytes)
                      Oct 18 14:16:35 localhost armbian-zram-config[390]: no label, UUID=81bcee6b-4a7b-463d-8d7d-1fae520194a8
                      Oct 18 14:16:35 localhost systemd-udevd[369]: link_config: could not get ethtool features for eth0
                      Oct 18 14:16:35 localhost systemd-udevd[369]: Could not set offload features of eth0: Device or resource busy
                      Oct 18 14:16:35 localhost systemd[1]: Reached target Sound Card.
                      Oct 18 14:16:35 localhost systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
                      Oct 18 14:16:35 localhost armbian-zram-config[390]: mke2fs 1.43.4 (31-Jan-2017)
                      Oct 18 14:16:35 localhost armbian-zram-config[390]: Geräteblöcke werden verworfen: 4096/12800#010#010#010#010#010#010#010#010#010#010#010 #010#010#010#010#010#010#010#010#010#010#010erledigt
                      Oct 18 14:16:35 localhost armbian-zram-config[390]: Ein Dateisystems mit 12800 (4k) Blöcken und 12800 Inodes wird erzeugt.
                      Oct 18 14:16:35 localhost armbian-zram-config[390]: beim Anfordern von Speicher für die Gruppentabellen: 0/1#010#010#010 #010#010#010erledigt
                      Oct 18 14:16:35 localhost armbian-zram-config[390]: Inode-Tabellen werden geschrieben: 0/1#010#010#010 #010#010#010erledigt
                      Oct 18 14:16:35 localhost armbian-zram-config[390]: Die Superblöcke und die Informationen über die Dateisystemnutzung werden
                      Oct 18 14:16:35 localhost armbian-zram-config[390]: geschrieben: 0/1#010#010#010 #010#010#010erledigt
                      Oct 18 14:16:35 localhost systemd[1]: Started Armbian ZRAM config.
                      Oct 18 14:16:35 localhost systemd[1]: Starting Armbian memory supported logging...
                      Oct 18 14:16:35 localhost kernel: [ 0.323289] regulator-dummy: no parameters
                      Oct 18 14:16:35 localhost systemd[1]: Started Raise network interfaces.
                      Oct 18 14:16:35 localhost kernel: [ 0.324240] NET: Registered protocol family 16
                      Oct 18 14:16:35 localhost kernel: [ 0.334966] cpuidle: using governor ladder
                      Oct 18 14:16:35 localhost kernel: [ 0.342065] cpuidle: using governor menu
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: Mounting /dev/zram0 as /var/log/
                      Oct 18 14:16:35 localhost kernel: [ 0.342107] Registered FIQ tty driver
                      Oct 18 14:16:35 localhost kernel: [ 0.343018] vdso: 2 pages (1 code @ ffffff8008bc6000, 1 data @ ffffff8009114000)
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: Fr 18. Okt 14:16:34 CEST 2019: Loading logs from storage
                      Oct 18 14:16:35 localhost kernel: [ 0.343059] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
                      Oct 18 14:16:35 localhost kernel: [ 0.343921] DMA: preallocated 2048 KiB pool for atomic allocations
                      Oct 18 14:16:35 localhost kernel: [ 0.362887] gpiochip_add_data: registered GPIOs 0 to 31 on device: gpio0
                      Oct 18 14:16:35 localhost kernel: [ 0.363026] gpiochip_add_data: registered GPIOs 32 to 63 on device: gpio1
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: sending incremental file list
                      Oct 18 14:16:35 localhost kernel: [ 0.363156] gpiochip_add_data: registered GPIOs 64 to 95 on device: gpio2
                      Oct 18 14:16:35 localhost kernel: [ 0.363295] gpiochip_add_data: registered GPIOs 96 to 127 on device: gpio3
                      Oct 18 14:16:35 localhost kernel: [ 0.471410] raid6: int64x1 gen() 203 MB/s
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: ./
                      Oct 18 14:16:35 localhost kernel: [ 0.539448] raid6: int64x1 xor() 190 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 0.607456] raid6: int64x2 gen() 328 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 0.675648] raid6: int64x2 xor() 261 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 0.743744] raid6: int64x4 gen() 482 MB/s
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: alternatives.log
                      Oct 18 14:16:35 localhost kernel: [ 0.811802] raid6: int64x4 xor() 329 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 0.880052] raid6: int64x8 gen() 388 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 0.948069] raid6: int64x8 xor() 304 MB/s
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: armbian-hardware-monitor.log
                      Oct 18 14:16:35 localhost kernel: [ 1.016227] raid6: neonx1 gen() 364 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 1.084334] raid6: neonx1 xor() 341 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 1.152458] raid6: neonx2 gen() 552 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 1.220574] raid6: neonx2 xor() 500 MB/s
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: auth.log
                      Oct 18 14:16:35 localhost kernel: [ 1.288724] raid6: neonx4 gen() 749 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 1.356781] raid6: neonx4 xor() 563 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 1.424942] raid6: neonx8 gen() 766 MB/s
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: bootstrap.log
                      Oct 18 14:16:35 localhost kernel: [ 1.493006] raid6: neonx8 xor() 579 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 1.493018] raid6: using algorithm neonx8 gen() 766 MB/s
                      Oct 18 14:16:35 localhost kernel: [ 1.493027] raid6: .... xor() 579 MB/s, rmw enabled
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: btmp
                      Oct 18 14:16:35 localhost kernel: [ 1.493036] raid6: using intx1 recovery algorithm
                      Oct 18 14:16:35 localhost kernel: [ 1.493532] mpp venc_srv: mpp_probe enter
                      Oct 18 14:16:35 localhost kernel: [ 1.493568] mpp venc_srv: init success
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: daemon.log
                      Oct 18 14:16:35 localhost kernel: [ 1.494392] rockchip-pm rockchip-suspend: not set wakeup-config
                      Oct 18 14:16:35 localhost kernel: [ 1.494409] rockchip-pm rockchip-suspend: not set pwm-regulator-config
                      Oct 18 14:16:35 localhost kernel: [ 1.495844] of_get_named_gpiod_flags: parsed 'gpio' property of node '/sdmmc-regulator[0]' - status (0)
                      Oct 18 14:16:35 localhost kernel: [ 1.495918] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: debug
                      Oct 18 14:16:35 localhost kernel: [ 1.495942] vcc_sd: unable to resolve supply
                      Oct 18 14:16:35 localhost kernel: [ 1.495958] vcc_sd: 3300 mV
                      Oct 18 14:16:35 localhost kernel: [ 1.496208] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                      Oct 18 14:16:35 localhost kernel: [ 1.496233] vcc_sd: regulator get failed, ret=-517
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: dpkg.log
                      Oct 18 14:16:35 localhost kernel: [ 1.496250] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                      Oct 18 14:16:35 localhost kernel: [ 1.496269] vcc_sd: unable to resolve supply
                      Oct 18 14:16:35 localhost kernel: [ 1.496286] reg-fixed-voltage sdmmc-regulator: vcc_sd supplying 3300000uV
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: faillog
                      Oct 18 14:16:35 localhost kernel: [ 1.496544] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc-host-5v-regulator[0]' - status (0)
                      Oct 18 14:16:35 localhost kernel: [ 1.496605] reg-fixed-voltage vcc-host-5v-regulator: Looking up vin-supply from device tree
                      Oct 18 14:16:35 localhost kernel: [ 1.496665] vcc_host_5v: unable to resolve supply
                      Oct 18 14:16:35 localhost armbian-ramlog[613]: kern.log
                      Oct 18 14:16:35 localhost kernel: [ 1.496687] vcc_host_5v: no parameters
                      Oct 18 14:16:35 localhost kernel: [ 1.496964] reg-fixed-voltage vcc-host-5v-regulator: Looking up vin-supply from device tree
                      Oct 18 14:16:35 localhost kernel: [ 1.497028] vcc_host_5v: regulator get failed, ret=-517

                      apollon77A 1 Antwort Letzte Antwort
                      0
                      • smartboartS smartboart

                        @apollon77
                        so hier der syslog..

                        hier mal ein Auszug..Tauchen Sachen mit Spannungswerten auf...kann es aber nicht wirklich deuten. Google spuckt jede Menge dieser Einträge im Zusammenhang mit dem Rock64 aus.

                        Oct 18 14:16:35 localhost kernel: [ 1.495918] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: debug
                        Oct 18 14:16:35 localhost kernel: [ 1.495942] vcc_sd: unable to resolve supply
                        Oct 18 14:16:35 localhost kernel: [ 1.495958] vcc_sd: 3300 mV
                        Oct 18 14:16:35 localhost kernel: [ 1.496208] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                        Oct 18 14:16:35 localhost kernel: [ 1.496233] vcc_sd: regulator get failed, ret=-517
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: dpkg.log
                        Oct 18 14:16:35 localhost kernel: [ 1.496250] reg-fixed-voltage sdmmc-regulator:

                        syslog


                        Oct 18 14:16:35 localhost fake-hwclock[246]: Current system time: 2019-10-18 12:16:33
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Booting Linux on physical CPU 0x0
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuacct
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Linux version 4.4.192-rockchip64 (root@builder) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02) ) #1 SMP Tue Oct 8 18:39:24 CEST 2019
                        Oct 18 14:16:35 localhost fake-hwclock[246]: fake-hwclock saved clock information is in the past: 2019-10-18 11:17:01
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Boot CPU: AArch64 Processor [410fd034]
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] earlycon: Early serial console at MMIO32 0xff130000 (options '')
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] bootconsole [uart0] enabled
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] On node 0 totalpages: 1043968
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] DMA zone: 16312 pages used for memmap
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] DMA zone: 0 pages reserved
                        Oct 18 14:16:35 localhost fake-hwclock[246]: To set system time to this saved clock anyway, use "force"
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] DMA zone: 1043968 pages, LIFO batch:31
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] psci: probing for conduit method from DT.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] psci: PSCIv1.0 detected in firmware.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] psci: Using standard PSCI v0.2 function IDs
                        Oct 18 14:16:35 localhost resolvconf[309]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] PERCPU: Embedded 21 pages/cpu @ffffffc0fef1f000 s46312 r8192 d31512 u86016
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] pcpu-alloc: s46312 r8192 d31512 u86016 alloc=21*4096
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
                        Oct 18 14:16:35 localhost systemd[1]: Started Create Static Device Nodes in /dev.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Detected VIPT I-cache on CPU0
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] CPU features: enabling workaround for ARM erratum 845719
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1027656
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Kernel command line: earlycon=uart8250,mmio32,0xff130000 swiotlb=1 kpti=0 no_console_suspend=1 usbcore.autosuspend=-1 root=UUID=37725f38-d37c-429c-89a6-9fc49158dcfe rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=b275bf8f-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
                        Oct 18 14:16:35 localhost systemd[1]: Starting udev Kernel Device Manager...
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] software IO TLB: mapped [mem 0xfeed7000-0xfef17000] (0MB)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Memory: 4078868K/4175872K available (11518K kernel code, 1488K rwdata, 4160K rodata, 1216K init, 699K bss, 97004K reserved, 0K cma-reserved)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Virtual kernel memory layout:
                        Oct 18 14:16:35 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] modules : 0xffffff8000000000 - 0xffffff8008000000 ( 128 MB)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] vmalloc : 0xffffff8008000000 - 0xffffffbdbfff0000 ( 246 GB)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] .init : 0xffffff8008fe0000 - 0xffffff8009110000 ( 1216 KB)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] .text : 0xffffff8008080000 - 0xffffff8008bc0000 ( 11520 KB)
                        Oct 18 14:16:35 localhost systemd[1]: Started Flush Journal to Persistent Storage.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] .rodata : 0xffffff8008bc0000 - 0xffffff8008fe0000 ( 4224 KB)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] .data : 0xffffff8009110000 - 0xffffff8009284008 ( 1489 KB)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] vmemmap : 0xffffffbdc0000000 - 0xffffffbfc0000000 ( 8 GB maximum)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] 0xffffffbdc0008000 - 0xffffffbdc3fc0000 ( 63 MB actual)
                        Oct 18 14:16:35 localhost systemd[1]: Started udev Kernel Device Manager.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] fixed : 0xffffffbffe7fb000 - 0xffffffbffec00000 ( 4116 KB)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] PCI I/O : 0xffffffbffee00000 - 0xffffffbfffe00000 ( 16 MB)
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] memory : 0xffffffc000200000 - 0xffffffc0ff000000 ( 4078 MB)
                        Oct 18 14:16:35 localhost systemd[1]: Started Set the console keyboard layout.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Hierarchical RCU implementation.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Build-time adjustment of leaf fanout to 64.
                        Oct 18 14:16:35 localhost systemd[1]: Reached target Local File Systems (Pre).
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] NR_IRQS:64 nr_irqs:64 0
                        Oct 18 14:16:35 localhost systemd[1]: Mounting /tmp...
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] GIC: Using split EOI/Deactivate mode
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                        Oct 18 14:16:35 localhost systemd[1]: Mounted /tmp.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] Architected cp15 timer(s) running at 24.00MHz (phys).
                        Oct 18 14:16:35 localhost systemd[1]: Reached target Local File Systems.
                        Oct 18 14:16:35 localhost kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
                        Oct 18 14:16:35 localhost kernel: [ 0.000007] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
                        Oct 18 14:16:35 localhost kernel: [ 0.001143] Console: colour dummy device 80x25
                        Oct 18 14:16:35 localhost systemd[1]: Starting Preprocess NFS configuration...
                        Oct 18 14:16:35 localhost kernel: [ 0.001159] console [tty1] enabled
                        Oct 18 14:16:35 localhost kernel: [ 0.001170] bootconsole [uart0] disabled
                        Oct 18 14:16:35 localhost kernel: [ 0.001195] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
                        Oct 18 14:16:35 localhost kernel: [ 0.001213] pid_max: default: 32768 minimum: 301
                        Oct 18 14:16:35 localhost systemd[1]: Starting Armbian ZRAM config...
                        Oct 18 14:16:35 localhost kernel: [ 0.001349] Security Framework initialized
                        Oct 18 14:16:35 localhost kernel: [ 0.001362] Yama: becoming mindful.
                        Oct 18 14:16:35 localhost kernel: [ 0.001387] AppArmor: AppArmor disabled by boot time parameter
                        Oct 18 14:16:35 localhost systemd[1]: Starting Set console font and keymap...
                        Oct 18 14:16:35 localhost kernel: [ 0.001451] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
                        Oct 18 14:16:35 localhost kernel: [ 0.001467] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
                        Oct 18 14:16:35 localhost kernel: [ 0.002397] Initializing cgroup subsys io
                        Oct 18 14:16:35 localhost kernel: [ 0.002421] Initializing cgroup subsys memory
                        Oct 18 14:16:35 localhost kernel: [ 0.002458] Initializing cgroup subsys devices
                        Oct 18 14:16:35 localhost kernel: [ 0.002476] Initializing cgroup subsys freezer
                        Oct 18 14:16:35 localhost kernel: [ 0.002493] Initializing cgroup subsys net_cls
                        Oct 18 14:16:35 localhost systemd[1]: Starting Create Volatile Files and Directories...
                        Oct 18 14:16:35 localhost kernel: [ 0.002513] Initializing cgroup subsys perf_event
                        Oct 18 14:16:35 localhost kernel: [ 0.002531] Initializing cgroup subsys net_prio
                        Oct 18 14:16:35 localhost kernel: [ 0.002551] Initializing cgroup subsys hugetlb
                        Oct 18 14:16:35 localhost kernel: [ 0.002565] Initializing cgroup subsys pids
                        Oct 18 14:16:35 localhost systemd[1]: Starting Raise network interfaces...
                        Oct 18 14:16:35 localhost kernel: [ 0.002619] ftrace: allocating 43805 entries in 172 pages
                        Oct 18 14:16:35 localhost kernel: [ 0.134714] sched-energy: CPU device node has no sched-energy-costs
                        Oct 18 14:16:35 localhost kernel: [ 0.134736] Invalid sched_group_energy for CPU0
                        Oct 18 14:16:35 localhost kernel: [ 0.134746] CPU0: update cpu_capacity 1024
                        Oct 18 14:16:35 localhost systemd[1]: Started Preprocess NFS configuration.
                        Oct 18 14:16:35 localhost kernel: [ 0.134809] ASID allocator initialised with 32768 entries
                        Oct 18 14:16:35 localhost kernel: [ 0.137693] Detected VIPT I-cache on CPU1
                        Oct 18 14:16:35 localhost systemd[1]: Reached target NFS client services.
                        Oct 18 14:16:35 localhost kernel: [ 0.137751] Invalid sched_group_energy for CPU1
                        Oct 18 14:16:35 localhost kernel: [ 0.137757] CPU1: update cpu_capacity 1024
                        Oct 18 14:16:35 localhost kernel: [ 0.137762] CPU1: Booted secondary processor [410fd034]
                        Oct 18 14:16:35 localhost systemd[1]: Started Set console font and keymap.
                        Oct 18 14:16:35 localhost kernel: [ 0.138511] Detected VIPT I-cache on CPU2
                        Oct 18 14:16:35 localhost kernel: [ 0.138558] Invalid sched_group_energy for CPU2
                        Oct 18 14:16:35 localhost kernel: [ 0.138563] CPU2: update cpu_capacity 1024
                        Oct 18 14:16:35 localhost systemd[1]: Started udev Coldplug all Devices.
                        Oct 18 14:16:35 localhost kernel: [ 0.138569] CPU2: Booted secondary processor [410fd034]
                        Oct 18 14:16:35 localhost kernel: [ 0.139246] Detected VIPT I-cache on CPU3
                        Oct 18 14:16:35 localhost kernel: [ 0.139291] Invalid sched_group_energy for CPU3
                        Oct 18 14:16:35 localhost systemd[1]: Started Create Volatile Files and Directories.
                        Oct 18 14:16:35 localhost kernel: [ 0.139297] CPU3: update cpu_capacity 1024
                        Oct 18 14:16:35 localhost kernel: [ 0.139302] CPU3: Booted secondary processor [410fd034]
                        Oct 18 14:16:35 localhost kernel: [ 0.139403] Brought up 4 CPUs
                        Oct 18 14:16:35 localhost kernel: [ 0.139467] SMP: Total of 4 processors activated.
                        Oct 18 14:16:35 localhost systemd[1]: Starting RPC bind portmap service...
                        Oct 18 14:16:35 localhost kernel: [ 0.139482] CPU features: kernel page table isolation forced OFF by command line option
                        Oct 18 14:16:35 localhost kernel: [ 0.139493] CPU features: detected feature: 32-bit EL0 Support
                        Oct 18 14:16:35 localhost kernel: [ 0.139508] CPU: All CPU(s) started at EL2
                        Oct 18 14:16:35 localhost kernel: [ 0.139547] alternatives: patching kernel code
                        Oct 18 14:16:35 localhost systemd[1]: Reached target System Time Synchronized.
                        Oct 18 14:16:35 localhost kernel: [ 0.139794] Invalid sched_group_energy for CPU3
                        Oct 18 14:16:35 localhost kernel: [ 0.139808] Invalid sched_group_energy for Cluster3
                        Oct 18 14:16:35 localhost kernel: [ 0.139817] Invalid sched_group_energy for CPU2
                        Oct 18 14:16:35 localhost systemd[1]: Started Entropy daemon using the HAVEGE algorithm.
                        Oct 18 14:16:35 localhost kernel: [ 0.139827] Invalid sched_group_energy for Cluster2
                        Oct 18 14:16:35 localhost kernel: [ 0.139837] Invalid sched_group_energy for CPU1
                        Oct 18 14:16:35 localhost kernel: [ 0.139847] Invalid sched_group_energy for Cluster1
                        Oct 18 14:16:35 localhost kernel: [ 0.139857] Invalid sched_group_energy for CPU0
                        Oct 18 14:16:35 localhost systemd[1]: Starting Update UTMP about System Boot/Shutdown...
                        Oct 18 14:16:35 localhost kernel: [ 0.139867] Invalid sched_group_energy for Cluster0
                        Oct 18 14:16:35 localhost kernel: [ 0.140633] devtmpfs: initialized
                        Oct 18 14:16:35 localhost kernel: [ 0.164712] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
                        Oct 18 14:16:35 localhost kernel: [ 0.164749] futex hash table entries: 1024 (order: 4, 65536 bytes)
                        Oct 18 14:16:35 localhost systemd-udevd[382]: Process '/sbin/iwconfig wlan0 power off' failed with exit code 250.
                        Oct 18 14:16:35 localhost kernel: [ 0.165346] xor: measuring software checksum speed
                        Oct 18 14:16:35 localhost kernel: [ 0.202627] 8regs : 1080.000 MB/sec
                        Oct 18 14:16:35 localhost kernel: [ 0.242708] 8regs_prefetch: 968.000 MB/sec
                        Oct 18 14:16:35 localhost kernel: [ 0.282796] 32regs : 1458.000 MB/sec
                        Oct 18 14:16:35 localhost systemd-udevd[380]: Process '/bin/mount -t fusectl fusectl /sys/fs/fuse/connections' failed with exit code 32.
                        Oct 18 14:16:35 localhost kernel: [ 0.322881] 32regs_prefetch: 1224.000 MB/sec
                        Oct 18 14:16:35 localhost kernel: [ 0.322893] xor: using function: 32regs (1458.000 MB/sec)
                        Oct 18 14:16:35 localhost kernel: [ 0.322933] pinctrl core: initialized pinctrl subsystem
                        Oct 18 14:16:35 localhost systemd[1]: Started Update UTMP about System Boot/Shutdown.
                        Oct 18 14:16:35 localhost systemd[1]: Started RPC bind portmap service.
                        Oct 18 14:16:35 localhost systemd[1]: Reached target RPC Port Mapper.
                        Oct 18 14:16:35 localhost systemd[1]: Reached target Remote File Systems (Pre).
                        Oct 18 14:16:35 localhost systemd[1]: Reached target Remote File Systems.
                        Oct 18 14:16:35 localhost systemd[1]: Found device /dev/ttyS2.
                        Oct 18 14:16:35 localhost armbian-zram-config[390]: Setting up swapspace version 1, size = 1024 MiB (1073737728 bytes)
                        Oct 18 14:16:35 localhost armbian-zram-config[390]: no label, UUID=81bcee6b-4a7b-463d-8d7d-1fae520194a8
                        Oct 18 14:16:35 localhost systemd-udevd[369]: link_config: could not get ethtool features for eth0
                        Oct 18 14:16:35 localhost systemd-udevd[369]: Could not set offload features of eth0: Device or resource busy
                        Oct 18 14:16:35 localhost systemd[1]: Reached target Sound Card.
                        Oct 18 14:16:35 localhost systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
                        Oct 18 14:16:35 localhost armbian-zram-config[390]: mke2fs 1.43.4 (31-Jan-2017)
                        Oct 18 14:16:35 localhost armbian-zram-config[390]: Geräteblöcke werden verworfen: 4096/12800#010#010#010#010#010#010#010#010#010#010#010 #010#010#010#010#010#010#010#010#010#010#010erledigt
                        Oct 18 14:16:35 localhost armbian-zram-config[390]: Ein Dateisystems mit 12800 (4k) Blöcken und 12800 Inodes wird erzeugt.
                        Oct 18 14:16:35 localhost armbian-zram-config[390]: beim Anfordern von Speicher für die Gruppentabellen: 0/1#010#010#010 #010#010#010erledigt
                        Oct 18 14:16:35 localhost armbian-zram-config[390]: Inode-Tabellen werden geschrieben: 0/1#010#010#010 #010#010#010erledigt
                        Oct 18 14:16:35 localhost armbian-zram-config[390]: Die Superblöcke und die Informationen über die Dateisystemnutzung werden
                        Oct 18 14:16:35 localhost armbian-zram-config[390]: geschrieben: 0/1#010#010#010 #010#010#010erledigt
                        Oct 18 14:16:35 localhost systemd[1]: Started Armbian ZRAM config.
                        Oct 18 14:16:35 localhost systemd[1]: Starting Armbian memory supported logging...
                        Oct 18 14:16:35 localhost kernel: [ 0.323289] regulator-dummy: no parameters
                        Oct 18 14:16:35 localhost systemd[1]: Started Raise network interfaces.
                        Oct 18 14:16:35 localhost kernel: [ 0.324240] NET: Registered protocol family 16
                        Oct 18 14:16:35 localhost kernel: [ 0.334966] cpuidle: using governor ladder
                        Oct 18 14:16:35 localhost kernel: [ 0.342065] cpuidle: using governor menu
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: Mounting /dev/zram0 as /var/log/
                        Oct 18 14:16:35 localhost kernel: [ 0.342107] Registered FIQ tty driver
                        Oct 18 14:16:35 localhost kernel: [ 0.343018] vdso: 2 pages (1 code @ ffffff8008bc6000, 1 data @ ffffff8009114000)
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: Fr 18. Okt 14:16:34 CEST 2019: Loading logs from storage
                        Oct 18 14:16:35 localhost kernel: [ 0.343059] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
                        Oct 18 14:16:35 localhost kernel: [ 0.343921] DMA: preallocated 2048 KiB pool for atomic allocations
                        Oct 18 14:16:35 localhost kernel: [ 0.362887] gpiochip_add_data: registered GPIOs 0 to 31 on device: gpio0
                        Oct 18 14:16:35 localhost kernel: [ 0.363026] gpiochip_add_data: registered GPIOs 32 to 63 on device: gpio1
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: sending incremental file list
                        Oct 18 14:16:35 localhost kernel: [ 0.363156] gpiochip_add_data: registered GPIOs 64 to 95 on device: gpio2
                        Oct 18 14:16:35 localhost kernel: [ 0.363295] gpiochip_add_data: registered GPIOs 96 to 127 on device: gpio3
                        Oct 18 14:16:35 localhost kernel: [ 0.471410] raid6: int64x1 gen() 203 MB/s
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: ./
                        Oct 18 14:16:35 localhost kernel: [ 0.539448] raid6: int64x1 xor() 190 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 0.607456] raid6: int64x2 gen() 328 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 0.675648] raid6: int64x2 xor() 261 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 0.743744] raid6: int64x4 gen() 482 MB/s
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: alternatives.log
                        Oct 18 14:16:35 localhost kernel: [ 0.811802] raid6: int64x4 xor() 329 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 0.880052] raid6: int64x8 gen() 388 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 0.948069] raid6: int64x8 xor() 304 MB/s
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: armbian-hardware-monitor.log
                        Oct 18 14:16:35 localhost kernel: [ 1.016227] raid6: neonx1 gen() 364 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 1.084334] raid6: neonx1 xor() 341 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 1.152458] raid6: neonx2 gen() 552 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 1.220574] raid6: neonx2 xor() 500 MB/s
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: auth.log
                        Oct 18 14:16:35 localhost kernel: [ 1.288724] raid6: neonx4 gen() 749 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 1.356781] raid6: neonx4 xor() 563 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 1.424942] raid6: neonx8 gen() 766 MB/s
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: bootstrap.log
                        Oct 18 14:16:35 localhost kernel: [ 1.493006] raid6: neonx8 xor() 579 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 1.493018] raid6: using algorithm neonx8 gen() 766 MB/s
                        Oct 18 14:16:35 localhost kernel: [ 1.493027] raid6: .... xor() 579 MB/s, rmw enabled
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: btmp
                        Oct 18 14:16:35 localhost kernel: [ 1.493036] raid6: using intx1 recovery algorithm
                        Oct 18 14:16:35 localhost kernel: [ 1.493532] mpp venc_srv: mpp_probe enter
                        Oct 18 14:16:35 localhost kernel: [ 1.493568] mpp venc_srv: init success
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: daemon.log
                        Oct 18 14:16:35 localhost kernel: [ 1.494392] rockchip-pm rockchip-suspend: not set wakeup-config
                        Oct 18 14:16:35 localhost kernel: [ 1.494409] rockchip-pm rockchip-suspend: not set pwm-regulator-config
                        Oct 18 14:16:35 localhost kernel: [ 1.495844] of_get_named_gpiod_flags: parsed 'gpio' property of node '/sdmmc-regulator[0]' - status (0)
                        Oct 18 14:16:35 localhost kernel: [ 1.495918] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: debug
                        Oct 18 14:16:35 localhost kernel: [ 1.495942] vcc_sd: unable to resolve supply
                        Oct 18 14:16:35 localhost kernel: [ 1.495958] vcc_sd: 3300 mV
                        Oct 18 14:16:35 localhost kernel: [ 1.496208] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                        Oct 18 14:16:35 localhost kernel: [ 1.496233] vcc_sd: regulator get failed, ret=-517
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: dpkg.log
                        Oct 18 14:16:35 localhost kernel: [ 1.496250] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree
                        Oct 18 14:16:35 localhost kernel: [ 1.496269] vcc_sd: unable to resolve supply
                        Oct 18 14:16:35 localhost kernel: [ 1.496286] reg-fixed-voltage sdmmc-regulator: vcc_sd supplying 3300000uV
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: faillog
                        Oct 18 14:16:35 localhost kernel: [ 1.496544] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc-host-5v-regulator[0]' - status (0)
                        Oct 18 14:16:35 localhost kernel: [ 1.496605] reg-fixed-voltage vcc-host-5v-regulator: Looking up vin-supply from device tree
                        Oct 18 14:16:35 localhost kernel: [ 1.496665] vcc_host_5v: unable to resolve supply
                        Oct 18 14:16:35 localhost armbian-ramlog[613]: kern.log
                        Oct 18 14:16:35 localhost kernel: [ 1.496687] vcc_host_5v: no parameters
                        Oct 18 14:16:35 localhost kernel: [ 1.496964] reg-fixed-voltage vcc-host-5v-regulator: Looking up vin-supply from device tree
                        Oct 18 14:16:35 localhost kernel: [ 1.497028] vcc_host_5v: regulator get failed, ret=-517

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

                        @smartboart ohne da jetzt mega tief rein zu schauen klinge das doch mal interessant das irgendwas mit power war und damit kann es exakt das sein das die Netzwerk Hardware mal kurz weg war.

                        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
                        smartboartS 2 Antworten Letzte Antwort
                        0
                        • apollon77A apollon77

                          @smartboart ohne da jetzt mega tief rein zu schauen klinge das doch mal interessant das irgendwas mit power war und damit kann es exakt das sein das die Netzwerk Hardware mal kurz weg war.

                          smartboartS Offline
                          smartboartS Offline
                          smartboart
                          schrieb am zuletzt editiert von
                          #842

                          @apollon77 ja vielen Dank für den Hinweis... Behalte das mal im Auge.. Dachte es hat mit dem neuen Controller zutun weil ich es vorher nicht hatte... Wie gesagt bekomme das ja durch die telegramm meldung mit wenn was neu startet..hänge mal ein Messgeraet / logger dran...

                          1 Antwort Letzte Antwort
                          0
                          • J Offline
                            J Offline
                            Jan1
                            schrieb am zuletzt editiert von
                            #843

                            @apollon77
                            ich habe ein paar Kleinigkeiten im Log nach einem iobroker restart und weiß nicht ob's vom controller kommt, oder von den Adaptern. Schaus mal bitte kurz an, laufen tut ja alles.

                            history.0	2019-10-19 09:34:48.241	error	(COMPACT) Cannot find view "system" for search "instance" : Error: Connection is closed.
                            alexa2.0	2019-10-19 09:34:48.244	info	(COMPACT) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            web.0	2019-10-19 09:34:48.243	info	(COMPACT) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            history.0	2019-10-19 09:34:48.240	error	(COMPACT) Cannot find view "system" for search "instance" : Error: Connection is closed.
                            iot.0	2019-10-19 09:34:48.239	warn	(COMPACT) get state Error: Connection is closed.
                            
                            apollon77A 1 Antwort Letzte Antwort
                            0
                            • J Jan1

                              @apollon77
                              ich habe ein paar Kleinigkeiten im Log nach einem iobroker restart und weiß nicht ob's vom controller kommt, oder von den Adaptern. Schaus mal bitte kurz an, laufen tut ja alles.

                              history.0	2019-10-19 09:34:48.241	error	(COMPACT) Cannot find view "system" for search "instance" : Error: Connection is closed.
                              alexa2.0	2019-10-19 09:34:48.244	info	(COMPACT) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              web.0	2019-10-19 09:34:48.243	info	(COMPACT) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              history.0	2019-10-19 09:34:48.240	error	(COMPACT) Cannot find view "system" for search "instance" : Error: Connection is closed.
                              iot.0	2019-10-19 09:34:48.239	warn	(COMPACT) get state Error: Connection is closed.
                              
                              apollon77A Offline
                              apollon77A Offline
                              apollon77
                              schrieb am zuletzt editiert von
                              #844

                              @Jan1 Diese Meldungen kommen wenn ein Adapter sich beendet aber die Verbindung zur DB weg ist - der will dann noch ein paar Dinge aufräumen, schaffts aber nicht weil er die Daten nicht bekommt. Von daher in dem Fall ok

                              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
                              J 1 Antwort Letzte Antwort
                              0
                              • apollon77A apollon77

                                @Jan1 Diese Meldungen kommen wenn ein Adapter sich beendet aber die Verbindung zur DB weg ist - der will dann noch ein paar Dinge aufräumen, schaffts aber nicht weil er die Daten nicht bekommt. Von daher in dem Fall ok

                                J Offline
                                J Offline
                                Jan1
                                schrieb am zuletzt editiert von
                                #845

                                @apollon77
                                Alles klar, ist ja auch sonst nix negatives aufgefallen.
                                IOBroker rennt bei mir derzeit richtig gut, schnell und ohne irgendwelche Auffälligkeiten, saubere Arbeit.

                                1 Antwort Letzte Antwort
                                1
                                • FredFF Online
                                  FredFF Online
                                  FredF
                                  Most Active Forum Testing
                                  schrieb am zuletzt editiert von
                                  #846

                                  @apollon77
                                  Bin jetzt auch auf 2.0.34 und kann nur das was @Jan1 schreibt bestätigen.
                                  Läuft wie schmitz katz.
                                  Ich sage mal Danke für deinen unermüdlichen Einsatz

                                  apollon77A 1 Antwort Letzte Antwort
                                  0
                                  • FredFF FredF

                                    @apollon77
                                    Bin jetzt auch auf 2.0.34 und kann nur das was @Jan1 schreibt bestätigen.
                                    Läuft wie schmitz katz.
                                    Ich sage mal Danke für deinen unermüdlichen Einsatz

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

                                    @FredF danke. Wir werkeln gerade noch an drei Themen. Zwei sind schon done (noch ein alias fix und die Hänger bei Updates von 1.5. auf 2.0). Das dritte sind die permission Fehler bei files bzw vis ... das ist noch offen. Das kann ich noch nicht nachstellen :-( aber wir sind dran.

                                    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 Offline
                                      apollon77A Offline
                                      apollon77
                                      schrieb am zuletzt editiert von
                                      #848

                                      Hi All,

                                      Auf Github gibt es die 2.0.35 die heute Abend vorauss. ins Latest kommt.

                                      Fixes:

                                      • (Apollon77) Allow to use Redis password as "pass" parameter for States ad Objects
                                      • (Apollon77) Prevent hangs on "iobroker upgrade self" from 1.5 to 2.0
                                      • (bluefox) Update IPs information periodically
                                      • (bluefox) Remove safe-replace, bluebird, pyconf packages
                                      • (bluefox) Fix alias logic in some places
                                      • (paul53/AlCalzone/Apollon77) Fix datatype of system.host.cpu and system.adapter.XY.Z.cpu
                                      • (Apollon77) Make sure alias.0 and other controller objects are also checked and created if needed on setup first when updating
                                      • (bluefox) Allow one state to multiple aliases connections

                                      Einziges noch offenes Thema, was wir aber noch nicht nachstellen konnten ist das, das bisher bei 2 Usern nach dem Update Vis mit einem PermissionError nicht mehr lädt :-(

                                      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
                                      arteckA sigi234S 2 Antworten Letzte Antwort
                                      0
                                      • apollon77A apollon77

                                        Hi All,

                                        Auf Github gibt es die 2.0.35 die heute Abend vorauss. ins Latest kommt.

                                        Fixes:

                                        • (Apollon77) Allow to use Redis password as "pass" parameter for States ad Objects
                                        • (Apollon77) Prevent hangs on "iobroker upgrade self" from 1.5 to 2.0
                                        • (bluefox) Update IPs information periodically
                                        • (bluefox) Remove safe-replace, bluebird, pyconf packages
                                        • (bluefox) Fix alias logic in some places
                                        • (paul53/AlCalzone/Apollon77) Fix datatype of system.host.cpu and system.adapter.XY.Z.cpu
                                        • (Apollon77) Make sure alias.0 and other controller objects are also checked and created if needed on setup first when updating
                                        • (bluefox) Allow one state to multiple aliases connections

                                        Einziges noch offenes Thema, was wir aber noch nicht nachstellen konnten ist das, das bisher bei 2 Usern nach dem Update Vis mit einem PermissionError nicht mehr lädt :-(

                                        arteckA Offline
                                        arteckA Offline
                                        arteck
                                        Developer Most Active
                                        schrieb am zuletzt editiert von
                                        #849

                                        @apollon77 hängts mit dem auth zusammen ??? vielleicht ?? also mein altes problem

                                        zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                        apollon77A 1 Antwort Letzte Antwort
                                        0
                                        • arteckA arteck

                                          @apollon77 hängts mit dem auth zusammen ??? vielleicht ?? also mein altes problem

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

                                          @arteck Das Web bei Ihm läuft als Admin und so ... Also kein Auth im Spiel

                                          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
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          638

                                          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