Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. [gelöst] iobroker "not running" über Nacht

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    17
    1
    608

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    5.6k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.5k

[gelöst] iobroker "not running" über Nacht

Scheduled Pinned Locked Moved Error/Bug
18 Posts 5 Posters 896 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • HomoranH Do not disturb
    HomoranH Do not disturb
    Homoran
    Global Moderator Administrators
    wrote on last edited by
    #2

    bitte auch mal hier:

    iobroker list instances
    

    Gruß

    Rainer

    kein Support per PN! - Fragen im Forum stellen -
    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
    Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
    der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

    1 Reply Last reply
    0
    • S Offline
      S Offline
      schneidy76
      wrote on last edited by
      #3

      Hi Rainer,

      gerne:
      2631_2018-12-29_14_37_25-.png
      VG Torsten

      Raspberry Matic (RP3), LIVE PV Monitoring mit Smartmeter, Poolsteuerung mit NodeRed, KNX Ausbau (ersetzt stückweise HM & klassische Installation), ioBroker Multihost (RP4 &RP2), Visu mit VIS

      1 Reply Last reply
      0
      • HomoranH Do not disturb
        HomoranH Do not disturb
        Homoran
        Global Moderator Administrators
        wrote on last edited by
        #4

        Du kommst also über <ip>:8081 auf den Admin?

        aber:
        @Schneidy76:

        hat gefühlt in letzter Zeit viel länger gedauert. `
        Mach mal sicherheitshalber ein Backup

        @schneidy76:

        Den Opi habe ich nun neu gebootet, zur Zeit läuft alles. `
        Also läuft es jetzt oder nicht?

        Gruß

        Rainer</ip>

        kein Support per PN! - Fragen im Forum stellen -
        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
        Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

        1 Reply Last reply
        0
        • S Offline
          S Offline
          schneidy76
          wrote on last edited by
          #5

          Hi Rainer,

          Backup läuft jede Nacht automatisch durch.

          Ja, nach den Reboot des Orange Pi läuft im Moment alles.

          Was mir aufgefallen ist, iobroker war auf dem Slave auch tot. Ob zuerst, oder als Folge muss ich mal schauen. :?

          Raspberry Matic (RP3), LIVE PV Monitoring mit Smartmeter, Poolsteuerung mit NodeRed, KNX Ausbau (ersetzt stückweise HM & klassische Installation), ioBroker Multihost (RP4 &RP2), Visu mit VIS

          1 Reply Last reply
          0
          • S Offline
            S Offline
            schneidy76
            wrote on last edited by
            #6

            2631_2018-12-29_15_31_52-c__users_schne_desktop_iobroker.2018-12-29.log_-notepad_.png
            da muss irgendwas passiert sein (blauer Punkt)

            Raspberry Matic (RP3), LIVE PV Monitoring mit Smartmeter, Poolsteuerung mit NodeRed, KNX Ausbau (ersetzt stückweise HM & klassische Installation), ioBroker Multihost (RP4 &RP2), Visu mit VIS

            1 Reply Last reply
            0
            • HomoranH Do not disturb
              HomoranH Do not disturb
              Homoran
              Global Moderator Administrators
              wrote on last edited by
              #7

              @schneidy76:

              Backup läuft jede Nacht automatisch durch. `
              incl. "iobroker stoppen"?

              Gruß

              Rainer

              kein Support per PN! - Fragen im Forum stellen -
              Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
              Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
              der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

              1 Reply Last reply
              0
              • S Offline
                S Offline
                schneidy76
                wrote on last edited by
                #8

                nein, minimal jeden Tag

                das komplette -inkl. Stop- alle 3 Tage

                das mache ich mit dem backitup Adapter…

                Raspberry Matic (RP3), LIVE PV Monitoring mit Smartmeter, Poolsteuerung mit NodeRed, KNX Ausbau (ersetzt stückweise HM & klassische Installation), ioBroker Multihost (RP4 &RP2), Visu mit VIS

                1 Reply Last reply
                0
                • HomoranH Do not disturb
                  HomoranH Do not disturb
                  Homoran
                  Global Moderator Administrators
                  wrote on last edited by
                  #9

                  @schneidy76:

                  das komplette -inkl. Stop- alle 3 Tage `
                  war letzte Nacht ein komplett dran?

                  Dann könnte das ja der Grund für "not running" sein, wenn iob danach nicht wieder hochgekommen ist.

                  Gruß

                  Rainer

                  kein Support per PN! - Fragen im Forum stellen -
                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                  Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                  der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                  1 Reply Last reply
                  0
                  • S Offline
                    S Offline
                    schneidy76
                    wrote on last edited by
                    #10

                    wäre möglich, aber laut log lief alles bis 5 Uhr

                    dann diese Meldung:

                    admin.0 Unsubscribe from all states, except system's, because over 3 seconds the number of events is over 200 (in last second 0
                    

                    das Backup läuft um 03:00Uhr durch, da sehe ich kein Stop

                    Raspberry Matic (RP3), LIVE PV Monitoring mit Smartmeter, Poolsteuerung mit NodeRed, KNX Ausbau (ersetzt stückweise HM & klassische Installation), ioBroker Multihost (RP4 &RP2), Visu mit VIS

                    1 Reply Last reply
                    0
                    • apollon77A Offline
                      apollon77A Offline
                      apollon77
                      wrote on last edited by
                      #11

                      Schau mal ins /var/log/syslog um die Zeit ob da was mit "oom" steht

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

                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                      1 Reply Last reply
                      0
                      • S Offline
                        S Offline
                        schneidy76
                        wrote on last edited by
                        #12

                        nein, habe nichts gefunden

                        Dec 28 06:30:02 localhost CRON[5905]: (CRON) info (No MTA installed, discarding output)
                        Dec 28 06:35:02 localhost CRON[6160]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 06:45:01 localhost CRON[6189]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 06:55:01 localhost CRON[6216]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 07:05:01 localhost CRON[6259]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 07:15:01 localhost CRON[6282]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 07:17:01 localhost CRON[6289]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 07:25:01 localhost CRON[6315]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 07:35:01 localhost CRON[6348]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 07:45:01 localhost CRON[6378]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 07:55:01 localhost CRON[6405]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 08:05:01 localhost CRON[6479]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 08:15:01 localhost CRON[6532]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 08:17:01 localhost CRON[6539]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 08:25:01 localhost CRON[6695]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 08:35:01 localhost CRON[6724]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 08:45:01 localhost CRON[6773]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 08:55:01 localhost CRON[6800]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 09:05:01 localhost CRON[6843]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 09:15:01 localhost CRON[6876]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 09:17:01 localhost CRON[6883]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 09:25:01 localhost CRON[6909]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 09:35:01 localhost CRON[6942]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 09:45:01 localhost CRON[6971]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 09:55:01 localhost CRON[6998]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 10:05:01 localhost CRON[7131]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 10:15:01 localhost CRON[7154]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 10:17:01 localhost CRON[7161]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 10:25:01 localhost CRON[7201]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 10:35:01 localhost CRON[7360]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 10:45:01 localhost CRON[7389]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 10:55:01 localhost CRON[7427]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 11:05:01 localhost CRON[7550]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 11:15:01 localhost CRON[7573]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 11:17:01 localhost CRON[7580]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 11:25:01 localhost CRON[7606]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 11:35:01 localhost CRON[7649]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 11:45:01 localhost CRON[7678]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 11:55:01 localhost CRON[7735]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 12:05:01 localhost CRON[7778]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 12:15:01 localhost CRON[7811]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 12:17:01 localhost CRON[7818]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 12:25:01 localhost CRON[7844]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 12:35:01 localhost CRON[7887]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 12:45:01 localhost CRON[8117]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 12:55:01 localhost CRON[8365]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 13:05:01 localhost CRON[8598]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 13:15:01 localhost CRON[8851]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 13:17:01 localhost CRON[8868]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 13:25:02 localhost CRON[9035]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 13:35:01 localhost CRON[9318]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 13:45:01 localhost CRON[9527]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 13:55:01 localhost CRON[9974]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 14:05:01 localhost CRON[10363]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 14:15:01 localhost CRON[10541]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 14:17:01 localhost CRON[10578]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 14:25:01 localhost CRON[10724]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 14:35:01 localhost CRON[10831]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 14:45:01 localhost CRON[11178]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 14:55:01 localhost CRON[11370]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 15:05:01 localhost CRON[11568]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 15:15:01 localhost CRON[11663]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 15:17:01 localhost CRON[11670]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 15:25:02 localhost CRON[11858]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 15:35:01 localhost CRON[11902]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 15:45:01 localhost CRON[11991]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 15:55:01 localhost CRON[12159]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 16:05:01 localhost CRON[12423]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 16:15:01 localhost CRON[12506]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 16:17:02 localhost CRON[12573]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 16:25:01 localhost CRON[12609]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 16:35:01 localhost CRON[12842]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 16:45:01 localhost CRON[13111]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 16:55:01 localhost CRON[13481]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 17:05:01 localhost CRON[13927]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 17:15:01 localhost CRON[14223]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 17:17:01 localhost CRON[14380]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 17:25:01 localhost CRON[14601]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 17:35:01 localhost CRON[14961]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 17:45:01 localhost CRON[15100]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 17:55:01 localhost CRON[15357]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 18:05:01 localhost CRON[15690]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 18:15:01 localhost CRON[16014]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 18:17:01 localhost CRON[16059]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 18:25:01 localhost CRON[16099]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 18:35:01 localhost CRON[16230]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 18:45:01 localhost CRON[16273]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 18:55:01 localhost CRON[16300]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 19:05:01 localhost CRON[16343]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 19:15:01 localhost CRON[16366]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 19:17:01 localhost CRON[16373]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 19:25:01 localhost CRON[16409]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 19:35:01 localhost CRON[16442]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 19:45:01 localhost CRON[16491]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 19:55:02 localhost CRON[16518]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 20:05:01 localhost CRON[16561]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 20:15:01 localhost CRON[16584]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 20:17:01 localhost CRON[16591]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 20:25:01 localhost CRON[16617]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 20:35:01 localhost CRON[16650]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 20:45:01 localhost CRON[16679]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 20:55:01 localhost CRON[16706]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 21:05:01 localhost CRON[16749]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 21:15:01 localhost CRON[16772]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 21:17:01 localhost CRON[16779]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 21:24:24 localhost systemd[1]: Starting Cleanup of Temporary Directories...
                        Dec 28 21:24:25 localhost systemd[1]: Started Cleanup of Temporary Directories.
                        Dec 28 21:25:01 localhost CRON[16806]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 21:35:01 localhost CRON[16839]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 21:45:01 localhost CRON[16868]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 21:55:01 localhost CRON[16895]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 22:05:01 localhost CRON[16938]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 22:15:01 localhost CRON[16961]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 22:17:01 localhost CRON[16968]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 22:25:01 localhost CRON[16994]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 22:35:01 localhost CRON[17027]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 22:45:01 localhost CRON[17056]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 22:55:01 localhost CRON[17083]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 23:05:01 localhost CRON[17126]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 23:15:01 localhost CRON[17149]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 23:17:01 localhost CRON[17156]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 28 23:25:01 localhost CRON[17182]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 23:35:01 localhost CRON[17215]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 23:45:01 localhost CRON[17244]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 23:55:01 localhost CRON[17271]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 28 23:59:01 localhost CRON[17278]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 60 2)
                        Dec 29 00:00:01 localhost CRON[17299]: (root) CMD (/usr/lib/armbian/apt-updates)
                        Dec 29 00:05:01 localhost CRON[17324]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 00:15:01 localhost CRON[17347]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 00:17:01 localhost CRON[17354]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 29 00:25:01 localhost CRON[17380]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 00:35:02 localhost CRON[17413]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 00:45:01 localhost CRON[17442]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 00:55:01 localhost CRON[17469]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 01:05:01 localhost CRON[17512]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 01:15:01 localhost CRON[17535]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 01:17:01 localhost CRON[17542]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 29 01:25:02 localhost CRON[17568]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 01:35:01 localhost CRON[17601]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 01:45:01 localhost CRON[17630]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 01:55:01 localhost CRON[17657]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 02:05:01 localhost CRON[17710]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 02:15:01 localhost CRON[17733]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 02:17:02 localhost CRON[17740]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 29 02:25:01 localhost CRON[17766]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 02:35:01 localhost CRON[17799]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 02:45:01 localhost CRON[17828]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 02:55:01 localhost CRON[17855]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 03:05:01 localhost CRON[17898]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 03:15:01 localhost CRON[17921]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 03:17:01 localhost CRON[17928]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 29 03:25:01 localhost CRON[17954]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 03:35:01 localhost CRON[17987]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 03:45:01 localhost CRON[18016]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 03:55:01 localhost CRON[18043]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 04:05:01 localhost CRON[18086]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 04:15:01 localhost CRON[18109]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 04:17:01 localhost CRON[18116]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 29 04:25:01 localhost CRON[18142]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 04:35:01 localhost CRON[18175]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 04:45:01 localhost CRON[18204]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 04:55:01 localhost CRON[18231]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 05:05:01 localhost CRON[18274]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 05:15:02 localhost CRON[18297]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 05:17:01 localhost CRON[18304]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 29 05:25:01 localhost CRON[18330]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 05:35:01 localhost CRON[18357]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 05:45:01 localhost CRON[18360]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 05:55:01 localhost CRON[18363]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 06:05:01 localhost CRON[18367]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 06:15:01 localhost CRON[18370]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 06:17:01 localhost CRON[18373]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                        Dec 29 06:25:01 localhost CRON[18384]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 06:25:01 localhost CRON[18385]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
                        Dec 29 06:35:01 localhost CRON[18483]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
                        Dec 29 06:35:11 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="517" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
                        
                        

                        Raspberry Matic (RP3), LIVE PV Monitoring mit Smartmeter, Poolsteuerung mit NodeRed, KNX Ausbau (ersetzt stückweise HM & klassische Installation), ioBroker Multihost (RP4 &RP2), Visu mit VIS

                        1 Reply Last reply
                        0
                        • apollon77A Offline
                          apollon77A Offline
                          apollon77
                          wrote on last edited by
                          #13

                          Also war es mal kein RAM Problem.

                          Was nützt du für ein Netzteil? >2.1A?

                          Gesendet vom Handy …

                          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 Reply Last reply
                          0
                          • S Offline
                            S Offline
                            schneidy76
                            wrote on last edited by
                            #14

                            2,4 bzw. auch 3A je nachdem wo das Teil gerade liegt. Weniger als 2,4A habe ich gar nicht. LAN passt auch.

                            :?

                            Vg Torsten

                            Raspberry Matic (RP3), LIVE PV Monitoring mit Smartmeter, Poolsteuerung mit NodeRed, KNX Ausbau (ersetzt stückweise HM & klassische Installation), ioBroker Multihost (RP4 &RP2), Visu mit VIS

                            1 Reply Last reply
                            0
                            • D Offline
                              D Offline
                              dondaik
                              wrote on last edited by
                              #15

                              na dann bin ich ja nicht alleine … auch wenn es ein tinkerboard ist :-)

                              wer Schreibfehler findet darf sie behalten … :-(

                              Ps: Anfänger im Bereich Tinkerboard + IOBROKER !

                              1 Reply Last reply
                              0
                              • MatzebhvM Offline
                                MatzebhvM Offline
                                Matzebhv
                                wrote on last edited by
                                #16

                                admin.0 Unsubscribe from all states, except system's, because over 3 seconds the number of events is over 200 (in last second 0)

                                Die Meldung kommt bei mir sobald ich den Tab Ereignisse aufrufe. Da ist aber auch tatsächlich die Hölle los.

                                Kurz danach kommt dann: admin.0 2018-12-31 14:01:05.626 info Subscribe on all states again

                                Ich verstehe das aber eher als Hinweis und nicht als Fehler.

                                Gruß

                                Matze

                                1 Reply Last reply
                                0
                                • apollon77A Offline
                                  apollon77A Offline
                                  apollon77
                                  wrote on last edited by
                                  #17

                                  Das ist sich kein Fehler und nur relevant wenn man aktiv Admin offen hat.

                                  Gesendet vom Handy …

                                  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 Reply Last reply
                                  0
                                  • S Offline
                                    S Offline
                                    schneidy76
                                    wrote on last edited by
                                    #18

                                    Update: es läuft seit gut 3 Tagen jetzt stabil.

                                    Ich konnte die Abstürze vom Slave beheben - war wohl ein Wärmeproblem, oder das Netzteil (es gab ein Neues).

                                    Den DWD Adapter habe ich neu konfiguriert und die Abfrageintervalle verlängert.

                                    Alle Adapter die gestoppt waren, habe ich nun konfiguriert und sauber jetzt am laufen.

                                    Was es genau war weiß ich nicht, aber in der Summe läuft der Master jetzt ohne Hänger und der Slave auch…

                                    Vielen Dank für die Denkanstöße!!!!

                                    VG Torsten

                                    Raspberry Matic (RP3), LIVE PV Monitoring mit Smartmeter, Poolsteuerung mit NodeRed, KNX Ausbau (ersetzt stückweise HM & klassische Installation), ioBroker Multihost (RP4 &RP2), Visu mit VIS

                                    1 Reply Last reply
                                    0
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes


                                    Support us

                                    ioBroker
                                    Community Adapters
                                    Donate

                                    708

                                    Online

                                    32.7k

                                    Users

                                    82.6k

                                    Topics

                                    1.3m

                                    Posts
                                    Community
                                    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                    ioBroker Community 2014-2025
                                    logo
                                    • Login

                                    • Don't have an account? Register

                                    • Login or register to search.
                                    • First post
                                      Last post
                                    0
                                    • Home
                                    • Recent
                                    • Tags
                                    • Unread 0
                                    • Categories
                                    • Unreplied
                                    • Popular
                                    • GitHub
                                    • Docu
                                    • Hilfe