Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. iob diag - Skript

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    iob diag - Skript

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

      @homoran

      Inkl. Timezone:

      *** BASISSYSTEM ***
      CPU-Architektur: aarch64
      Docker: Nein
      No LSB modules are available.
      Distributor ID: Debian
      Description:    Debian GNU/Linux 11 (bullseye)
      Release:        11
      Codename:       bullseye
      
      *** Zeit und Zeitzonen ***
                     Local time: Tue 2022-11-01 16:10:31 CET
                 Universal time: Tue 2022-11-01 15:10:31 UTC
                       RTC time: n/a
                      Time zone: Europe/Berlin (CET, +0100)
      System clock synchronized: yes
                    NTP service: active
                RTC in local TZ: no
      
      *** ARBEITSSPEICHER ***
                     total        used        free      shared  buff/cache   available
      Mem:           7.7Gi       2.3Gi       3.2Gi       0.0Ki       2.2Gi       5.3Gi
      Swap:           99Mi          0B        99Mi
      Total:         7.8Gi       2.3Gi       3.3Gi
      
      *** Nodejs-Installation ***
      /usr/bin/nodejs         v18.12.0
      /usr/bin/node           v18.12.0
      /usr/bin/npm            8.19.2
      
      *** ioBroker-Installation ***
      js-controller:  4.0.23
      Updates + Repos:
      Used repository: beta
      
      *** User und Gruppen ***
      echad
      /home/echad
      echad adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
      
      *** Server-Setup ***
      Konsole: tty
      Desktop:
      
      *** Repositories und OS-Updates ***
      Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
      Hit:2 http://deb.debian.org/debian bullseye InRelease
      Hit:3 http://phoscon.de/apt/deconz bullseye InRelease
      Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
      Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease
      Hit:6 http://packages.azlux.fr/debian bullseye InRelease
      Hit:7 http://deb.debian.org/debian bullseye-backports InRelease
      Hit:8 https://repos.influxdata.com/debian bullseye InRelease
      Hit:9 https://packages.grafana.com/oss/deb stable InRelease
      Hit:10 https://deb.nodesource.com/node_10.x bullseye InRelease
      Hit:11 https://deb.nodesource.com/node_12.x bullseye InRelease
      Hit:12 https://deb.nodesource.com/node_14.x bullseye InRelease
      Hit:13 https://deb.nodesource.com/node_16.x bullseye InRelease
      Hit:14 https://packages.redis.io/deb bullseye InRelease
      Hit:15 https://deb.volian.org/volian scar InRelease
      Hit:16 https://deb.nodesource.com/node_18.x bullseye InRelease
      Hit:17 https://deb.nodesource.com/node_19.x bullseye InRelease
      Get:19 https://pkgs.tailscale.com/stable/debian bullseye InRelease
      Hit:18 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease
      Fetched 5,545 B in 3s (1,679 B/s)
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      All packages are up to date.
      nodejs:
        Installed: 18.12.0-deb-1nodesource1
        Candidate: 18.12.0-deb-1nodesource1
        Version table:
           19.0.0-deb-1nodesource1 500
              500 https://deb.nodesource.com/node_19.x bullseye/main arm64 Packages
       *** 18.12.0-deb-1nodesource1 501
              500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages
              100 /var/lib/dpkg/status
           16.18.0-deb-1nodesource1 500
              500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages
           14.20.1-deb-1nodesource1 500
              500 https://deb.nodesource.com/node_14.x bullseye/main arm64 Packages
           12.22.12-deb-1nodesource1 500
              500 https://deb.nodesource.com/node_12.x bullseye/main arm64 Packages
           12.22.12~dfsg-1~deb11u1 500
              500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages
           12.22.5~dfsg-2~11u1 500
              500 http://deb.debian.org/debian bullseye/main arm64 Packages
           10.24.1-deb-1nodesource1 500
              500 https://deb.nodesource.com/node_10.x bullseye/main arm64 Packages
      
      R 1 Reply Last reply Reply Quote 3
      • R
        reutli @Thomas Braun last edited by

        @thomas-braun

        great stuff 👍

        1 Reply Last reply Reply Quote 0
        • F
          fastfoot @Thomas Braun last edited by

          @thomas-braun sagte in iob diag - Skript:

          Vielleicht mag ja jemand mit Docker oder LXC das mal ausführen und den Output zeigen?

          timedatectl kennt das image nicht

          *** BASISSYSTEM ***
          CPU-Architektur: x86_64
          Docker: Ja
          Distributor ID: Debian
          Description:    Debian GNU/Linux 11 (bullseye)
          Release:        11
          Codename:       bullseye
          
          Systemuptime und Load:
           22:56:04 up 16 min,  0 users,  load average: 0,67, 1,35, 1,27
          CPU threads: 4
          
          *** Zeit und Zeitzonen ***
          ./iob_diag: line 42: timedatectl: command not found
          
          *** ARBEITSSPEICHER ***
                         total        used        free      shared  buff/cache   available
          Mem:           7,7Gi       2,9Gi       841Mi       330Mi       3,9Gi       3,9Gi
          Swap:           31Gi          0B        31Gi
          Total:          38Gi       2,9Gi        32Gi
          
          *** Nodejs-Installation ***
          /usr/bin/nodejs         v16.18.0
          /usr/bin/node           v16.18.0
          /usr/bin/npm            8.19.2
          
          nodejs:
            Installed: 16.18.0-deb-1nodesource1
            Candidate: 16.18.0-deb-1nodesource1
            Version table:
           *** 16.18.0-deb-1nodesource1 500
                  500 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages
                  100 /var/lib/dpkg/status
               12.22.12~dfsg-1~deb11u1 500
                  500 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages
               12.22.5~dfsg-2~11u1 500
                  500 http://deb.debian.org/debian bullseye/main amd64 Packages
          
          *** ioBroker-Installation ***
          js-controller:  4.0.23
          
          Updates + Repos:
          Used repository: beta
          
          *** User und Gruppen ***
          root
          /opt/iobroker
          root
          
          *** X-Server-Setup ***
          X-Server: Nein
          Desktop: 
          Konsole: 
          
          *** Repositories und OS-Updates ***
          Hit:1 http://deb.debian.org/debian bullseye InRelease
          Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease
          Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
          Hit:4 https://deb.nodesource.com/node_16.x bullseye InRelease
          Reading package lists... Done                       
          Building dependency tree... Done
          Reading state information... Done
          All packages are up to date.
          
          Thomas Braun 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @fastfoot last edited by Thomas Braun

            @fastfoot

            Danke schön!
            Hast du auch vielleicht eine Alternative?
            Funktioniert das:

            date -u && date && date +"%Z %z" && cat /etc/timezone
            
            F 1 Reply Last reply Reply Quote 0
            • F
              fastfoot @Thomas Braun last edited by

              @thomas-braun sagte in iob diag - Skript:

              Funktioniert das:

              Di 1. Nov 22:10:28 UTC 2022
              Di 1. Nov 23:10:28 CET 2022
              CET +0100
              Europe/Berlin```
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @fastfoot last edited by Thomas Braun

                @fastfoot

                Prima, dann fummel ich das so rein.

                [Edit:] Ist drin.

                F 1 Reply Last reply Reply Quote 1
                • F
                  fastfoot @Thomas Braun last edited by

                  @thomas-braun sagte in iob diag - Skript:

                  [Edit:] Ist drin.

                  Läuft!

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

                    @fastfoot

                    Prima. Und die Ergebnisse treffen vermutlich zu?
                    Also Docker und kein X-Server usw?

                    F Quarkmax 2 Replies Last reply Reply Quote 0
                    • F
                      fastfoot @Thomas Braun last edited by

                      @thomas-braun sagte in iob diag - Skript:

                      @fastfoot

                      Prima. Und die Ergebnisse treffen vermutlich zu?
                      Also Docker und kein X-Server usw?

                      genau, sieht für mich korrekt aus

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

                        @thomas-braun
                        Auf Proxmox im LXC -super.

                        *** BASISSYSTEM ***
                        CPU-Architektur: x86_64
                        Docker: Nein
                        Distributor ID: Ubuntu
                        Description:    Ubuntu 22.04.1 LTS
                        Release:        22.04
                        Codename:       jammy
                        
                        Systemuptime und Load:
                         23:25:18 up 1 day,  9:15,  1 user,  load average: 0,63, 0,98, 0,82
                        CPU threads: 4
                        
                        *** Zeit und Zeitzonen ***
                        Di 1. Nov 22:25:18 UTC 2022
                        Di 1. Nov 23:25:18 CET 2022
                        CET +0100
                        Europe/Berlin
                        
                        *** ARBEITSSPEICHER ***
                                       total        used        free      shared  buff/cache   available
                        Mem:           6,0Gi       3,3Gi       2,1Gi       0,0Ki       575Mi       2,7Gi
                        Swap:          512Mi       0,0Ki       511Mi
                        Total:         6,5Gi       3,3Gi       2,6Gi
                        
                        *** Nodejs-Installation ***
                        /usr/bin/nodejs         v16.18.0
                        /usr/bin/node           v16.18.0
                        /usr/bin/npm            8.19.2
                        
                        nodejs:
                          Installiert:           16.18.0-deb-1nodesource1
                          Installationskandidat: 16.18.0-deb-1nodesource1
                          Versionstabelle:
                         *** 16.18.0-deb-1nodesource1 500
                                500 https://deb.nodesource.com/node_16.x jammy/main amd64 Packages
                                100 /var/lib/dpkg/status
                             12.22.9~dfsg-1ubuntu3 500
                                500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
                        
                        *** ioBroker-Installation ***
                        js-controller:  4.0.23
                        
                        Updates + Repos:
                        Used repository: Beta (latest)
                        Adapter    "eventlist"    : 1.1.1    , installed 0.5.5  [Updatable]
                        
                        *** User und Gruppen ***
                        pi
                        /home/pi
                        pi sudo iobroker
                        
                        *** X-Server-Setup ***
                        X-Server: Nein
                        Desktop:
                        Konsole: tty
                        
                        *** Repositories und OS-Updates ***
                        OK:1 http://archive.ubuntu.com/ubuntu jammy InRelease
                        OK:2 https://repos.influxdata.com/ubuntu stable InRelease
                        Holen:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
                        OK:4 https://deb.nodesource.com/node_16.x jammy InRelease
                        Holen:5 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
                        Es wurden 224 kB in 1 s geholt (229 kB/s).
                        Paketlisten werden gelesen… Fertig
                        Abhängigkeitsbaum wird aufgebaut… Fertig
                        Statusinformationen werden eingelesen… Fertig
                        Alle Pakete sind aktuell.
                        

                        Vielen Dank für die Diagnose...

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

                          @fastfoot

                          Okay. Dann muss ich nur noch für wayland was finden...
                          Werd ich wohl auf dem Bastel-Pi mal ein GUI inkl. wayland hochzimmern müssen.

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

                            @quarkmax

                            Kannst du mal schauen was dabei in deinem LXC herum kommt?

                            echo `[ ! -f /.dockerenv ]` $?
                            
                            Quarkmax 1 Reply Last reply Reply Quote 0
                            • Quarkmax
                              Quarkmax @Thomas Braun last edited by

                              @thomas-braun

                              
                              pi@ioBroker:~$ echo `[ ! -f /.dockerenv ]` $?
                              0
                              pi@ioBroker:~$
                              
                              
                              
                              Thomas Braun 2 Replies Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Quarkmax last edited by

                                @quarkmax

                                Schade. Ich such noch einen Weg einen (Proxmox) LXC zu identifizieren.

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

                                  @quarkmax

                                  Kannst du mal

                                  cat /proc/1/sched | head -n 1
                                  

                                  im Container ausführen?

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

                                    @thomas-braun
                                    Da kommt dann diese Ausgabe

                                    pi@ioBroker:~$ cat /proc/1/sched | head -n 1
                                    systemd (1, #threads: 1)
                                    pi@ioBroker:~$
                                    
                                    
                                    Thomas Braun 2 Replies Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @Quarkmax last edited by

                                      @quarkmax
                                      Schade. Hatte gehofft das sei evtl. 'bash' statt 'systemd'.

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

                                        @quarkmax

                                        Bitte mal

                                        systemd-detect-virt
                                        

                                        versuchen.

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

                                          @thomas-braun
                                          Perfekt

                                          pi@ioBroker:~$ systemd-detect-virt
                                          lxc
                                          pi@ioBroker:~$
                                          
                                          
                                          Thomas Braun 1 Reply Last reply Reply Quote 1
                                          • Thomas Braun
                                            Thomas Braun Most Active @Quarkmax last edited by Thomas Braun

                                            @quarkmax

                                            BINGO! 😄

                                            [Edit:] skript ist aktualisiert.

                                            Quarkmax 1 Reply Last reply Reply Quote 2
                                            • First post
                                              Last post

                                            Support us

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

                                            824
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            49
                                            715
                                            133084
                                            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