Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst]Proxmox crashed

    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

    [gelöst]Proxmox crashed

    This topic has been deleted. Only users with topic management privileges can see it.
    • Segway
      Segway @liv-in-sky last edited by

      @liv-in-sky

      ALLE Logs bereits angeschaut ? Kann ich mir nicht vorstellen, dass da nix drin steht !

      Output von:

      free -m
      df -h
      
      1 Reply Last reply Reply Quote 0
      • crunchip
        crunchip Forum Testing Most Active @liv-in-sky last edited by crunchip

        @liv-in-sky du hast unter anderem in
        var/log

        • daemon.log
        • dpkg.log
        • kern.log
        • user.log
        • syslog
          ...

        bzw mal die alten syslog.x.gz durchsehen ob da was auffälliges zu finden ist

        1 Reply Last reply Reply Quote 0
        • liv-in-sky
          liv-in-sky last edited by liv-in-sky

          oh - kein proxmox - kein pihole -kein forum 😞

          Image 4.png

          Image 5.png

          ist kein proxmox thema - wenn ich mit ubuntu statt debin-proxmox starte - passiert das selbe - einfach aus

          hab mal die usv abgesteckt - nicht das die noch probleme macht
          muss die log weiter checken - finde aber nix

          muss jetzt zum weihnachtsessen - melde mich später wieder

          1 Reply Last reply Reply Quote 0
          • liv-in-sky
            liv-in-sky last edited by

            und wieder passiert - um 18:00 war der server weg. danach neustart und alle mögl. logs kontrolliert zwischen 17:00 und 18:00 habe ich nichts mit dem server gemacht - um 18:00 haben dann alle sonoffs zu blinken begonnen und die vis drehte den kreisel

            iobroker log: startet um 18:08 mit eintragungen - davor ist nichts mehr
            proxmox server:

            was völlig unklar ist, sind die einträge in message und syslog. zeile 15658: um 17:58 geht es mit 17:18 weiter am selben datum - ich check das nicht in zeile 17192 kommt dann plötzlich ein sprung

            Dec 26 17:58:01 beelink systemd[1]: pvesr.service: Succeeded.
            Dec 26 17:58:01 beelink systemd[1]: Started Proxmox VE replication runner.
            Dec 26 17:58:01 beelink CRON[15364]: (root) CMD (/usr/local/bin/cpualarm)
            Dec 26 17:58:01 beelink CRON[15365]: (root) CMD (/usr/local/bin/tempcpu)
            Dec 26 17:58:21 beelink NetworkManager[734]: <info>  [1609001901.7687] device (wlp58s0): set-hw-addr: set MAC address to 8E:94:F8:10:8E:66 (scanning)
            Dec 26 17:58:21 beelink NetworkManager[734]: <info>  [1609001901.7744] device (wlp58s0): supplicant interface state: inactive -> disabled
            Dec 26 17:58:21 beelink NetworkManager[734]: <info>  [1609001901.8233] device (wlp58s0): supplicant interface state: disabled -> inactive
            Dec 26 17:58:21 beelink wpa_supplicant[721]: wlp58s0: Reject scan trigger since one is already pending
            Dec 26 17:59:00 beelink systemd[1]: Starting Proxmox VE replication runner...
            Dec 26 17:59:00 beelink systemd[1]: pvesr.service: Succeeded.
            Dec 26 17:59:00 beelink systemd[1]: Started Proxmox VE replication runner.
            Dec 26 17:59:01 beelink CRON[16119]: (root) CMD (/usr/local/bin/cpualarm)
            Dec 26 17:59:01 beelink CRON[16120]: (root) CMD (/usr/local/bin/tempcpu)
            Dec 26 17:18:34 beelink systemd-modules-load[343]: Inserted module 'vfio_pci'
            Dec 26 17:18:34 beelink systemd-modules-load[343]: Inserted module 'coretemp'
            Dec 26 17:18:34 beelink systemd-modules-load[343]: Inserted module 'iscsi_tcp'
            Dec 26 17:18:34 beelink systemd-tmpfiles[365]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
            Dec 26 17:18:34 beelink systemd-tmpfiles[365]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly.
            Dec 26 17:18:34 beelink systemd-tmpfiles[365]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
            Dec 26 17:18:34 beelink systemd-tmpfiles[365]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
            Dec 26 17:18:34 beelink systemd-tmpfiles[365]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly.
            Dec 26 17:18:34 beelink systemd-modules-load[343]: Inserted module 'ib_iser'
            Dec 26 17:18:34 beelink systemd[1]: Starting Flush Journal to Persistent Storage...
            Dec 26 17:18:34 beelink systemd-modules-load[343]: Inserted module 'vhost_net'
            Dec 26 17:18:34 beelink systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
            Dec
            

            syslog

            in messages ist das genauso:

            messages

            1 Reply Last reply Reply Quote 0
            • liv-in-sky
              liv-in-sky last edited by liv-in-sky

              und noch syslog vom iobroker container:

              dort ist bis 17:58 alle soweit normal - dann nix - und um 18:10 hatte ich wieder gestartet

              ec 26 17:45:01 iobroker59 CRON[32534]: (root) CMD (/usr/local/bin/mountstatus)
              Dec 26 17:46:01 iobroker59 CRON[32606]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:47:01 iobroker59 CRON[32659]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:47:03 iobroker59 bash[282]: Error: Encoding not recognized: 'ISO-8859-1 CONTENT-TRANSFER-ENCODING: QUOTED-PRINTABLE' (searched as: 'iso88591contenttransferencodingquotedprintable')
              Dec 26 17:47:03 iobroker59 bash[282]:     at Object.getCodec (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/node_modules/iconv-lite/lib/index.js:104:23)
              Dec 26 17:47:03 iobroker59 bash[282]:     at Object.getDecoder (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/node_modules/iconv-lite/lib/index.js:125:23)
              Dec 26 17:47:03 iobroker59 bash[282]:     at Object.decode (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/node_modules/iconv-lite/lib/index.js:38:25)
              Dec 26 17:47:03 iobroker59 bash[282]:     at convertIconvLite (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/lib/encoding.js:59:26)
              Dec 26 17:47:03 iobroker59 bash[282]:     at Object.convert (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/lib/encoding.js:35:22)
              Dec 26 17:47:03 iobroker59 bash[282]:     at MailParser._convertString (/opt/iobroker/node_modules/iobroker.javascript/node_modules/mailparser/lib/mailparser.js:1358:25)
              Dec 26 17:47:03 iobroker59 bash[282]:     at MailParser._convertStringToUTF8 (/opt/iobroker/node_modules/iobroker.javascript/node_modules/mailparser/lib/mailparser.js:1370:18)
              Dec 26 17:47:03 iobroker59 bash[282]:     at MailParser._finalizeContents (/opt/iobroker/node_modules/iobroker.javascript/node_modules/mailparser/lib/mailparser.js:975:50)
              Dec 26 17:47:03 iobroker59 bash[282]:     at MailParser._process (/opt/iobroker/node_modules/iobroker.javascript/node_modules/mailparser/lib/mailparser.js:247:18)
              Dec 26 17:47:03 iobroker59 bash[282]:     at processImmediate (internal/timers.js:461:21)
              Dec 26 17:47:04 iobroker59 bash[282]: Error: Encoding not recognized: 'ISO-8859-1 CONTENT-TRANSFER-ENCODING: QUOTED-PRINTABLE' (searched as: 'iso88591contenttransferencodingquotedprintable')
              Dec 26 17:47:04 iobroker59 bash[282]:     at Object.getCodec (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/node_modules/iconv-lite/lib/index.js:104:23)
              Dec 26 17:47:04 iobroker59 bash[282]:     at Object.getDecoder (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/node_modules/iconv-lite/lib/index.js:125:23)
              Dec 26 17:47:04 iobroker59 bash[282]:     at Object.decode (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/node_modules/iconv-lite/lib/index.js:38:25)
              Dec 26 17:47:04 iobroker59 bash[282]:     at convertIconvLite (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/lib/encoding.js:59:26)
              Dec 26 17:47:04 iobroker59 bash[282]:     at Object.convert (/opt/iobroker/node_modules/iobroker.javascript/node_modules/encoding/lib/encoding.js:35:22)
              Dec 26 17:47:04 iobroker59 bash[282]:     at MailParser._convertString (/opt/iobroker/node_modules/iobroker.javascript/node_modules/mailparser/lib/mailparser.js:1358:25)
              Dec 26 17:47:04 iobroker59 bash[282]:     at MailParser._convertStringToUTF8 (/opt/iobroker/node_modules/iobroker.javascript/node_modules/mailparser/lib/mailparser.js:1370:18)
              Dec 26 17:47:04 iobroker59 bash[282]:     at MailParser._finalizeContents (/opt/iobroker/node_modules/iobroker.javascript/node_modules/mailparser/lib/mailparser.js:975:50)
              Dec 26 17:47:04 iobroker59 bash[282]:     at MailParser._process (/opt/iobroker/node_modules/iobroker.javascript/node_modules/mailparser/lib/mailparser.js:247:18)
              Dec 26 17:47:04 iobroker59 bash[282]:     at processImmediate (internal/timers.js:461:21)
              Dec 26 17:47:06 iobroker59 dhclient[157]: PRC: Renewing lease on eth0.
              Dec 26 17:47:06 iobroker59 dhclient[157]: XMT: Renew on eth0, interval 9410ms.
              Dec 26 17:47:06 iobroker59 dhclient[157]: RCV: Reply message on eth0 from fe80::9ec7:a6ff:feff:a078.
              Dec 26 17:48:01 iobroker59 CRON[601]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:48:15 iobroker59 nmbd[194]: [2020/12/26 17:48:15.072240,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
              Dec 26 17:48:15 iobroker59 nmbd[194]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.59 for name HOME<1d>.
              Dec 26 17:48:15 iobroker59 nmbd[194]:   This response was from IP 192.168.178.10, reporting an IP address of 192.168.178.10.
              Dec 26 17:49:01 iobroker59 CRON[907]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:50:01 iobroker59 CRON[982]: (root) CMD (/usr/local/bin/mountstatus)
              Dec 26 17:50:01 iobroker59 CRON[983]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:51:01 iobroker59 CRON[1131]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:52:01 iobroker59 CRON[1833]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:53:01 iobroker59 CRON[1965]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:53:15 iobroker59 nmbd[194]: [2020/12/26 17:53:15.532571,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
              Dec 26 17:53:15 iobroker59 nmbd[194]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.59 for name HOME<1d>.
              Dec 26 17:53:15 iobroker59 nmbd[194]:   This response was from IP 192.168.178.10, reporting an IP address of 192.168.178.10.
              Dec 26 17:54:01 iobroker59 CRON[2060]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:55:01 iobroker59 CRON[2119]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
              Dec 26 17:55:01 iobroker59 CRON[2120]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:55:01 iobroker59 CRON[2121]: (root) CMD (/usr/local/bin/mountstatus)
              Dec 26 17:56:01 iobroker59 CRON[2461]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:57:01 iobroker59 CRON[2892]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:58:01 iobroker59 CRON[2956]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 17:58:16 iobroker59 nmbd[194]: [2020/12/26 17:58:16.031931,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
              Dec 26 17:58:16 iobroker59 nmbd[194]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.59 for name HOME<1d>.
              Dec 26 17:58:16 iobroker59 nmbd[194]:   This response was from IP 192.168.178.10, reporting an IP address of 192.168.178.10.
              Dec 26 17:59:01 iobroker59 CRON[3013]: (root) CMD (/usr/local/bin/cpualarm)
              Dec 26 18:10:04 iobroker59 systemd-sysctl[52]: Couldn't write '1' to 'fs/protected_hardlinks', ignoring: Read-only file system
              Dec 26 18:10:04 iobroker59 systemd-sysctl[52]: Couldn't write '1' to 'fs/protected_symlinks', ignoring: Read-only file system
              Dec 26 18:10:04 iobroker59 keyboard-setup.sh[51]: Dateideskriptor, der auf die Konsole verweist, konnte nicht gefunden werden.
              Dec 26 18:10:04 iobroker59 keyboard-setup.sh[51]: Dateideskriptor, der auf die Konsole verweist, konnte nicht gefunden werden.
              Dec 26 18:10:04 iobroker59 systemd[1]: Starting Flush Journal to Persistent Storage...
              Dec 26 18:10:04 iobroker59 keyboard-setup.sh[51]: Dateideskriptor, der auf die Konsole verweist, konnte nicht gefunden werden.
              Dec 26 18:10:04 iobroker59 systemd[1]: Started Create System Users.
              Dec 26 18:10:04 iobroker59 systemd[1]: Starting Create Static Device Nodes in /dev...
              Dec 26 18:10:04 iobroker59 systemd[1]: Started Create Static Device Nodes in /dev.
              
              

              1 Reply Last reply Reply Quote 0
              • liv-in-sky
                liv-in-sky last edited by

                ach ja - ich hatte noch die console offen: mit tail -f /var/log/syslog - ist dort stehen geblieben:

                Image 7.png

                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @liv-in-sky last edited by

                  @liv-in-sky Da hämmert ja auch stundenlang ein Prozess im Sekundentakt auf das System. Das mag das halt irgendwann nicht mehr.

                  liv-in-sky 1 Reply Last reply Reply Quote 0
                  • liv-in-sky
                    liv-in-sky @Thomas Braun last edited by

                    @Thomas-Braun was meinst du ?

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @liv-in-sky last edited by

                      @liv-in-sky Dieser Proxmox replication Kram. Was auch immer der tut. Aber das sieht für mich so aus, als wenn das nicht so sein sollte.

                      liv-in-sky 1 Reply Last reply Reply Quote 0
                      • liv-in-sky
                        liv-in-sky @Thomas Braun last edited by

                        @Thomas-Braun sagte in Proxmox crashed:

                        Proxmox replication

                        du meinst das:

                        Image 8.png

                        @Segway @crunchip @homecineplexx

                        habt ihr das auch? im proxmox forum steht, dass kann ignoriert werden

                        crunchip Thomas Braun 2 Replies Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @liv-in-sky last edited by

                          @liv-in-sky ja das ist so normal, hab ich bei all meinen drei Rechner
                          de7b5d45-3e6a-4b8e-8d52-52d6a3a796d8-image.png

                          1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @liv-in-sky last edited by

                            @liv-in-sky Ich hab ja keine Ahnung von Proxmox, aber ein Start von dem Dienst im Sekundentakt kann aus meiner Sicht nicht normal sein.

                            liv-in-sky 1 Reply Last reply Reply Quote 0
                            • liv-in-sky
                              liv-in-sky @Thomas Braun last edited by

                              @Thomas-Braun das ist doch minütlich oder meinst du was anderes

                              crunchip Thomas Braun 2 Replies Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active @liv-in-sky last edited by

                                @liv-in-sky ist in der Regel minütlich, immer ein block
                                started..
                                starting..
                                pvesr....

                                1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @liv-in-sky last edited by

                                  @liv-in-sky Ja, minütlich. Find ich immer noch ungewöhnlich, aber wenn das normal sein soll...

                                  liv-in-sky 2 Replies Last reply Reply Quote 0
                                  • liv-in-sky
                                    liv-in-sky @Thomas Braun last edited by

                                    @Thomas-Braun lt proxmox forum - ist normal - habe es aber auf monthly geändert - ich weiß nicht mal, was das genau ist

                                    https://forum.proxmox.com/threads/replication-runner-syslog.35600/

                                    1 Reply Last reply Reply Quote 0
                                    • liv-in-sky
                                      liv-in-sky @Thomas Braun last edited by liv-in-sky

                                      @Thomas-Braun

                                      kannst du dir den zeitsprung irgendwie erklären

                                      bis 17:58 alles ok - plötlich ist im log von 17:18 die rede - dann passiert da nichts- um 18:00 ist der server down und die zeit stimmt wieder

                                      Thomas Braun Homoran 2 Replies Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @liv-in-sky last edited by

                                        @liv-in-sky Nee, keine Ahnung, aber das ist auch mehr als merkwürdig.

                                        liv-in-sky 1 Reply Last reply Reply Quote 0
                                        • liv-in-sky
                                          liv-in-sky @Thomas Braun last edited by

                                          @Thomas-Braun hardware kaputt ?

                                          1 Reply Last reply Reply Quote 0
                                          • Homoran
                                            Homoran Global Moderator Administrators @liv-in-sky last edited by

                                            @liv-in-sky Das klingt für mich danach, dass da ggf. etwas neu startet und sich dann die Systemzeit holt und korrigiert

                                            liv-in-sky 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

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

                                            904
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            proxmox
                                            10
                                            98
                                            5519
                                            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