Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Absturzursache Raspi und iO Broker finden

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Absturzursache Raspi und iO Broker finden

    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      Laser @Thomas Braun last edited by Laser

      @thomas-braun
      Ein Versuch:

      
      ======== Start marking the full check here =========
      
      Skript v.2023-01-02
      
      *** BASE SYSTEM ***
      Model           : Raspberry Pi 4 Model B Rev 1.4
      Architecture:   armv7l
      Docker:         false
      Virtualization: none
      Distributor ID: Raspbian
      Description:    Raspbian GNU/Linux 11 (bullseye)
      Release:        11
      Codename:       bullseye
      
      PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
      NAME="Raspbian GNU/Linux"
      VERSION_ID="11"
      VERSION="11 (bullseye)"
      VERSION_CODENAME=bullseye
      ID=raspbian
      ID_LIKE=debian
      HOME_URL="http://www.raspbian.org/"
      SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
      BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
      
      Systemuptime and Load:
       10:06:57 up 1 day,  1:32,  1 user,  load average: 0.41, 0.57, 0.50
      CPU threads: 4
      
      *** Time and Time Zones ***
      Wed Mar  1 09:06:57 UTC 2023
      Wed Mar  1 10:06:57 CET 2023
      CET +0100
      Europe/Berlin
      
      *** User and Groups ***
      pi
      /home/pi
      pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
      
      *** X-Server-Setup ***
      X-Server:       false
      Desktop:
      Terminal:       tty
      Boot Target:    multi-user.target
      
      *** MEMORY ***
                     total        used        free      shared  buff/cache   available
      Mem:            1.9G        1.1G        192M        1.0M        596M        861M
      Swap:            99M        1.0M         98M
      Total:          2.0G        1.1G        291M
      
               1871 M total memory
               1082 M used memory
                278 M active memory
               1280 M inactive memory
                192 M free memory
                 59 M buffer memory
                536 M swap cache
                 99 M total swap
                  1 M used swap
                 98 M free swap
      
      *** FILESYSTEM ***
      Filesystem     Type      Size  Used Avail Use% Mounted on
      /dev/root      ext4      110G  3.5G  102G   4% /
      devtmpfs       devtmpfs  775M     0  775M   0% /dev
      tmpfs          tmpfs     936M     0  936M   0% /dev/shm
      tmpfs          tmpfs     375M  1.1M  374M   1% /run
      tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
      /dev/sda1      vfat      255M   50M  206M  20% /boot
      tmpfs          tmpfs     188M     0  188M   0% /run/user/1000
      
      Messages in dmesg:
      [Tue Feb 28 08:34:47 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=E4:5F:01:1E:BF:CD vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000  console=ttyS0,115200 console=tty1 root=PARTUUID=a8b32cdb-02 rootfstype=ext4 fsck.repair=yes rootwait
      [Tue Feb 28 08:34:49 2023] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
      [Tue Feb 28 08:34:49 2023] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
      [Tue Feb 28 08:34:52 2023] EXT4-fs (sda2): re-mounted. Opts: commit=600. Quota mode: none.
      [Tue Feb 28 08:34:56 2023] systemd[1]: Started Periodic ext4 Online Metadata Check for All Filesystems.
      [Tue Feb 28 08:34:56 2023] systemd[1]: Starting Remove Stale Online ext4 Metadata Check Snapshots...
      [Tue Feb 28 08:34:56 2023] systemd[1]: Finished Remove Stale Online ext4 Metadata Check Snapshots.
      
      Show mounted filesystems (real ones only):
      TARGET      SOURCE    FSTYPE  OPTIONS
      /           /dev/sda2 ext4    rw,noatime,commit=600
      |-/run/owfs OWFS      fuse.OW rw,nosuid,nodev,relatime,user_id=0,group_id=0,allo
      `-/boot     /dev/sda1 vfat    rw,relatime,fmask=0022,dmask=0022,codepage=437,ioc
      
      Files in neuralgic directories:
      
      /var:
      498M    /var/
      279M    /var/cache
      274M    /var/cache/apt
      210M    /var/cache/apt/archives
      94M     /var/lib
      
      /opt/iobroker/backups:
      4.0K    /opt/iobroker/backups/
      
      /opt/iobroker/iobroker-data:
      530M    /opt/iobroker/iobroker-data/
      343M    /opt/iobroker/iobroker-data/history
      137M    /opt/iobroker/iobroker-data/files
      51M     /opt/iobroker/iobroker-data/files/javascript.admin
      34M     /opt/iobroker/iobroker-data/backup-objects
      
      The five largest files in iobroker-data are:
      9.1M    /opt/iobroker/iobroker-data/files/echarts.admin/static/js/2.bbf74d5f.chunk.js.map
      8.9M    /opt/iobroker/iobroker-data/files/echarts/static/js/2.3d2d025f.chunk.js.map
      8.9M    /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/2.3d2d025f.chunk.js.map
      8.4M    /opt/iobroker/iobroker-data/objects.jsonl
      8.3M    /opt/iobroker/iobroker-data/states.jsonl
      
      *** NodeJS-Installation ***
      
      /usr/bin/nodejs         v16.19.1
      /usr/bin/node           v16.19.1
      /usr/bin/npm            8.19.3
      /usr/bin/npx            8.19.3
      
      nodejs:
        Installed: 16.19.1-deb-1nodesource1
        Candidate: 16.19.1-deb-1nodesource1
        Version table:
       *** 16.19.1-deb-1nodesource1 500
              500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages
              100 /var/lib/dpkg/status
           12.22.12~dfsg-1~deb11u3 500
              500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
      
      Temp directories causing npm8 problem: 0
      
      *** ioBroker-Installation ***
      
      ioBroker Status
      iobroker is running on this host.
      
      
      Objects type: jsonl
      States  type: jsonl
      
      Core adapters versions
      js-controller:  4.0.24
      admin:          6.3.5
      javascript:     6.1.4
      
      Adapters from github:   0
      
      Adapter State
      + system.adapter.admin.1                  : admin                 : Heizung                                  -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.backitup.0               : backitup              : Heizung                                  -  enabled
      + system.adapter.discovery.0              : discovery             : Heizung                                  -  enabled
      + system.adapter.echarts.0                : echarts               : Heizung                                  -  enabled
        system.adapter.flot.0                   : flot                  : Heizung                                  - disabled
      + system.adapter.history.0                : history               : Heizung                                  -  enabled
      + system.adapter.hm-rega.0                : hm-rega               : Heizung                                  -  enabled
      + system.adapter.hm-rpc.0                 : hm-rpc                : Heizung                                  -  enabled, port: 0
      + system.adapter.hm-rpc.1                 : hm-rpc                : Heizung                                  -  enabled, port: 0
      + system.adapter.info.0                   : info                  : Heizung                                  -  enabled
      + system.adapter.javascript.0             : javascript            : Heizung                                  -  enabled
      + system.adapter.mqtt.0                   : mqtt                  : Heizung                                  -  enabled, port: 1883, bind: 0.0.0.0
      + system.adapter.net-tools.0              : net-tools             : Heizung                                  -  enabled
      + system.adapter.opendtu.0                : opendtu               : Heizung                                  -  enabled
      + system.adapter.owfs.0                   : owfs                  : Heizung                                  -  enabled, port: 4304
      + system.adapter.rpi2.0                   : rpi2                  : Heizung                                  -  enabled
      + system.adapter.shelly.1                 : shelly                : Heizung                                  -  enabled, port: 1882, bind: 0.0.0.0
      + system.adapter.simple-api.0             : simple-api            : Heizung                                  -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
        system.adapter.vis-bars.0               : vis-bars              : Heizung                                  - disabled
        system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : Heizung                                  - disabled
        system.adapter.vis.0                    : vis                   : Heizung                                  -  enabled
      + system.adapter.web.0                    : web                   : Heizung                                  -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      + system.adapter.zigbee.0                 : zigbee                : Heizung                                  -  enabled, port: /dev/ttyACM0
      
      + instance is alive
      
      Enabled adapters with bindings
      + system.adapter.admin.1                  : admin                 : Heizung                                  -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.hm-rpc.0                 : hm-rpc                : Heizung                                  -  enabled, port: 0
      + system.adapter.hm-rpc.1                 : hm-rpc                : Heizung                                  -  enabled, port: 0
      + system.adapter.mqtt.0                   : mqtt                  : Heizung                                  -  enabled, port: 1883, bind: 0.0.0.0
      + system.adapter.owfs.0                   : owfs                  : Heizung                                  -  enabled, port: 4304
      + system.adapter.shelly.1                 : shelly                : Heizung                                  -  enabled, port: 1882, bind: 0.0.0.0
      + system.adapter.simple-api.0             : simple-api            : Heizung                                  -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
      + system.adapter.web.0                    : web                   : Heizung                                  -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      + system.adapter.zigbee.0                 : zigbee                : Heizung                                  -  enabled, port: /dev/ttyACM0
      
      ioBroker-Repositories
      stable        : http://download.iobroker.net/sources-dist.json
      beta          : http://download.iobroker.net/sources-dist-latest.json
      
      Active repo(s): stable
      
      Installed ioBroker-Instances
      Used repository: stable
      Adapter    "admin"        : 6.3.5    , installed 6.3.5
      Adapter    "backitup"     : 2.5.12   , installed 2.5.12
      Adapter    "discovery"    : 3.1.0    , installed 3.1.0
      Adapter    "ds18b20"      : 1.6.1    , installed 1.6.1
      Adapter    "echarts"      : 1.0.12   , installed 1.0.12
      Adapter    "flot"         : 1.11.0   , installed 1.11.0
      Adapter    "history"      : 2.2.4    , installed 2.2.4
      Adapter    "hm-rega"      : 3.0.43   , installed 3.0.43
      Adapter    "hm-rpc"       : 1.15.16  , installed 1.15.16
      Adapter    "i2c"          : 1.2.1    , installed 1.2.1
      Adapter    "info"         : 1.9.19   , installed 1.9.19
      Adapter    "javascript"   : 6.1.4    , installed 6.1.4
      Controller "js-controller": 4.0.24   , installed 4.0.24
      Adapter    "mqtt"         : 4.0.7    , installed 4.0.7
      Adapter    "net-tools"    : 0.2.0    , installed 0.2.0
      Adapter    "owfs"         : 0.7.0    , installed 0.7.0
      Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
      Adapter    "shelly"       : 6.3.1    , installed 6.3.1
      Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
      Adapter    "socketio"     : 4.2.0    , installed 4.2.0
      Adapter    "vis"          : 1.4.15   , installed 1.4.15
      Adapter    "vis-bars"     : 0.1.4    , installed 0.1.4
      Adapter    "vis-hqwidgets": 1.3.0    , installed 1.3.0
      Adapter    "web"          : 4.3.0    , installed 4.3.0
      Adapter    "ws"           : 1.3.0    , installed 1.3.0
      Adapter    "zigbee"       : 1.8.10   , installed 1.8.10
      
      Objects and States
      Please stand by - This may take a while
      Objects:        3207
      States:         2406
      
      *** OS-Repositories and Updates ***
      ^C
      
      
      
      Thomas Braun 1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @Laser last edited by Thomas Braun

        @laser

        Das ist ja nur ein Bruchteil. Scroll an den Anfang...

        Oder hol das log aus /home/iobroker/iob_diag.log ab.

        L 1 Reply Last reply Reply Quote 0
        • L
          Laser @Thomas Braun last edited by

          @thomas-braun
          Habe Code Tags angepasst. Ein Log in iobroker finde ich nicht.

          Thomas Braun 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @Laser last edited by

            @laser

            Liegt hier:

            Oder hol das log aus /home/iobroker/iob_diag.log ab.

            L 1 Reply Last reply Reply Quote 0
            • L
              Laser @Thomas Braun last edited by

              @thomas-braun
              /home/iobroker ist leer...

              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Laser last edited by

                @laser

                ls -lah /home/iobroker
                
                L 1 Reply Last reply Reply Quote 0
                • L
                  Laser @Thomas Braun last edited by

                  @thomas-braun

                  
                  pi@Heizung:/home/iobroker $ ls -lah /home/iobroker
                  total 32K
                  drwxr-xr-x 4 iobroker iobroker 4.0K Dec 22 15:26 .
                  drwxr-xr-x 4 root     root     4.0K Dec 22 15:16 ..
                  -rw-r--r-- 1 iobroker iobroker  220 Mar 27  2022 .bash_logout
                  -rw-r--r-- 1 iobroker iobroker 3.5K Sep 22 02:05 .bashrc
                  drwxr-xr-x 3 iobroker iobroker 4.0K Dec 22 15:26 .cache
                  -rw-r--r-- 1 iobroker iobroker 1.7K Jul 10  2021 .mkshrc
                  drwxr-xr-x 5 iobroker iobroker 4.0K Dec 22 16:05 .npm
                  -rw-r--r-- 1 iobroker iobroker  807 Mar 27  2022 .profile
                  
                  
                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Laser last edited by

                    @laser

                    Keine Ahnung was da auf deinem System krumm ist.
                    Eigentlich wirft das skript ein log file da rein.

                    L 1 Reply Last reply Reply Quote 0
                    • L
                      Laser @Thomas Braun last edited by

                      @thomas-braun
                      Ich habe vor geraumer Zeit versucht, das Logging abzuschalten, da endlose Suchen in den Logs nichts gebracht haben. Diese Orgie haben wir ja schon mal durchgemacht. Offenbar steht der Prozessor, bevor etwas in irgendein Log geschrieben wird. Das Einzige, was die Logs mit Sicherheit machen, ist, die SSD im 5 Sekunden- Abstand kaputtzuschreiben.

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Laser last edited by

                        @laser sagte in Absturzursache Raspi und iO Broker finden:

                        Das Einzige, was die Logs mit Sicherheit machen, ist, die SSD im 5 Sekunden- Abstand kaputtzuschreiben.

                        Das log vom iob diag schreibt aber nur wenn es aufgerufen wird.

                        L 1 Reply Last reply Reply Quote 0
                        • L
                          Laser @Thomas Braun last edited by

                          @thomas-braun
                          OK, was soll ich jetzt tun?

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @Laser last edited by

                            @laser

                            Den Mittelteil posten.

                            L 1 Reply Last reply Reply Quote 0
                            • L
                              Laser @Thomas Braun last edited by

                              @thomas-braun
                              OK. Versuche ich. Wie kann ich den "Mittelteil" einfangen?

                              Thomas Braun 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Laser last edited by

                                @laser

                                In meinem Terminal scrolle ich bis zur Anfangsmarkierung nach oben, wenn der Tastendruck angefragt wird und kopiere das dann bis zur Endemarkierung.

                                L 1 Reply Last reply Reply Quote 0
                                • L
                                  Laser @Thomas Braun last edited by

                                  @thomas-braun
                                  Habe das Fenster schon vergrößert. Ab "Copy text starting here" verschwindet der bisher aufgelistete Text. Habe schon versucht, die Ausgabe in eine Textdatei umzuleiten. Hat bisher nicht funktioniert (Permission denied). "sudo iob diag >> Fehler.txt" ist offenbar falsch

                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @Laser last edited by Thomas Braun

                                    @laser

                                    Wer sagt denn was von sudo?

                                    Mir scheint, du hast dein System hinten und vorne verfummelt.

                                    iob diag > iob_diag.log
                                    
                                    L 1 Reply Last reply Reply Quote 0
                                    • L
                                      Laser @Thomas Braun last edited by

                                      @thomas-braun
                                      "Verfummelt" Das System habe ich schon x mal nach Beschreibung neu aufgesetzt. Was soll ich denn "verfummelt" haben?

                                      L Thomas Braun 2 Replies Last reply Reply Quote 0
                                      • L
                                        Laser @Laser last edited by

                                        
                                        pi@Heizung:/home/iobroker $ sudo iob diag >> Fehler.log
                                        -bash: Fehler.log: Permission denied
                                        pi@Heizung:/home/iobroker $ iob diag > iob_diag.log
                                        -bash: iob_diag.log: Permission denied
                                        pi@Heizung:/home/iobroker $ sudo iob diag > iob_diag.log
                                        -bash: iob_diag.log: Permission denied
                                        
                                        
                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @Laser last edited by

                                          @laser

                                          Das logging, die Rechte, was weiß ich...
                                          Jedenfalls landet in 'unverfummelten' Systemen z. B. ein log in /home/iobroker/iob_diag.log
                                          Bei dir offenbar nicht.

                                          L 1 Reply Last reply Reply Quote 0
                                          • L
                                            Laser @Thomas Braun last edited by Laser

                                            @thomas-braun
                                            Ich habe nichts vorsätzlich an Rechten geändert. Warum auch?
                                            Wenn das System funktioniert, fasse ich nichts an!

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            442
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            11
                                            148
                                            9156
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo