Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Installation auf NUC mit Proxmox

NEWS

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

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

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

Installation auf NUC mit Proxmox

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
128 Beiträge 29 Kommentatoren 26.7k Aufrufe 9 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • M Offline
    M Offline
    Mr. Moose
    schrieb am zuletzt editiert von
    #115

    Hallo,

    da der Raspberry mit seinem 1 GB RAM langsam am Ende ist, bin ich gerade dabei einen Intel NUC (NUC6CAYH) mit 4GB RAM und 320 GB HDD (RAM und HDD hatte ich noch rumliegen) einzurichten.

    Soweit hat auch alles super funktioniert nur ein einziges Problem habe ich. Der zwave Adapter lässt sich nicht installieren. Da ich aber 12 Fibaro Rolladenaktoren habe, ist das leider ein OK Kriterium. Vielleicht hat ja noch einer eine Idee.

    EDIT: Ich habe es geschafft. Damit das hier nicht so viel Platz weg nimmt habe ich den Rest mal in den Spoiler gepackt.

    Da es letztlich nur indirekt an Proxmox lag, kann ein Mod das ja vielleicht komplett löschen.

    Erstens fehlte noch unzip. Das seht nur in der Beschreibung des Adapters, dass man das braucht. Könnte man doch bestimmt bei der Installations automatisch installieren lassen.

    Und dann war noch ein Problem, dass der USB Z-Wave stick nicht richtig an den Container weitergereicht wurde. Das habe ich mit der folgenden Anleitung behoben: http://coldcorner.de/2018/07/12/proxmox … wave-uzb1/

    ! Bei der Installation aus admin kommt:

    $ ./iobroker add zwave  --host iobroker-ct-deb
    NPM version: 6.4.1
    npm install iobroker.zwave --unsafe-perm --production --save --prefix "/opt/iobroker" (System call)
    We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
    >!     #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.
    >! sudo: no tty present and no askpass program specified
    /opt/iobroker/node_modules/iobroker.zwave/lib/preinstall.js:16
        if (!suppressException) throw e;
                                ^
    >! Error: Command failed: sudo apt-get install libudev-dev -y
    >! We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
    >!     #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.
    >! sudo: no tty present and no askpass program specified
    >!     at checkExecSyncError (child_process.js:607:13)
        at Object.execSync (child_process.js:647:13)
        at doScript (/opt/iobroker/node_modules/iobroker.zwave/lib/preinstall.js:13:15)
        at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.zwave/lib/preinstall.js:26:7)
        at Module._compile (module.js:653:30)
        at Object.Module._extensions..js (module.js:664:10)
        at Module.load (module.js:566:32)
        at tryModuleLoad (module.js:506:12)
        at Function.Module._load (module.js:498:3)
        at Function.Module.runMain (module.js:694:10)
    >! npm
    
    ERR!
    
    code
     ELIFECYCLE
    npm
    
    ERR!
    
    errno
     1npm
    
    ERR!
     iobroker.zwave@1.3.1 preinstall: `node lib/preinstall.js`npm ERR! Exit status 1
    >! npm ERR! npm ERR! Failed at the iobroker.zwave@1.3.1 preinstall script.
    npm ERR!
     This is probably not a problem with npm. There is likely additional logging output above.
    >! npm
    
    ERR!
     A complete log of this run can be found in:
    npm
    
    ERR!
         /home/iobroker/.npm/_logs/2019-01-17T21_46_12_471Z-debug.log
    host.iobroker-ct-deb install adapter zwave
    NPM version: 6.4.1npm install iobroker.zwave --unsafe-perm --production --save --prefix "/opt/iobroker" (System call)
    >! We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
    >!     #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.
    >! sudo: no tty present and no askpass program specified
    /opt/iobroker/node_modules/iobroker.zwave/lib/preinstall.js:16
        if (!suppressException) throw e;
                                ^
    >! Error: Command failed: sudo apt-get install libudev-dev -y
    >! We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
    >!     #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.
    >! sudo: no tty present and no askpass program specified
    >!     at checkExecSyncError (child_process.js:607:13)
        at Object.execSync (child_process.js:647:13)
        at doScript (/opt/iobroker/node_modules/iobroker.zwave/lib/preinstall.js:13:15)
        at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.zwave/lib/preinstall.js:26:7)
        at Module._compile (module.js:653:30)
        at Object.Module._extensions..js (module.js:664:10)
        at Module.load (module.js:566:32)
        at tryModuleLoad (module.js:506:12)
        at Function.Module._load (module.js:498:3)
        at Function.Module.runMain (module.js:694:10)
    >! npm
    
    ERR!
    
    code
     ELIFECYCLE
    npm
    
    ERR!
    
    errno 1npm
    
    ERR!
     iobroker.zwave@1.3.1 preinstall: `node lib/preinstall.js`npm ERR! Exit status 1
    npm
     ERR! npm ERR! Failed at the iobroker.zwave@1.3.1 preinstall script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    >! npm
    
    ERR!
     A complete log of this run can be found in:
    npm
    
    ERR!
         /home/iobroker/.npm/_logs/2019-01-17T21_46_28_337Z-debug.log
    host.iobroker-ct-deb install adapter zwave
    NPM version: 6.4.1npm install iobroker.zwave --unsafe-perm --production --save --prefix "/opt/iobroker" (System call)
    >! We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
    >!     #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.
    >! sudo: no tty present and no askpass program specified
    /opt/iobroker/node_modules/iobroker.zwave/lib/preinstall.js:16
        if (!suppressException) throw e;
                                ^
    >! Error: Command failed: sudo apt-get install libudev-dev -y
    >! We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
    >!     #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.
    >! sudo: no tty present and no askpass program specified
    >!     at checkExecSyncError (child_process.js:607:13)
        at Object.execSync (child_process.js:647:13)
        at doScript (/opt/iobroker/node_modules/iobroker.zwave/lib/preinstall.js:13:15)
        at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.zwave/lib/preinstall.js:26:7)
        at Module._compile (module.js:653:30)
        at Object.Module._extensions..js (module.js:664:10)
        at Module.load (module.js:566:32)
        at tryModuleLoad (module.js:506:12)
        at Function.Module._load (module.js:498:3)
        at Function.Module.runMain (module.js:694:10)
    >! npm
    
    ERR!
    
    code
     ELIFECYCLE
    npm
    
    ERR!
    
    errno
     1npm
    
    ERR! iobroker.zwave@1.3.1 preinstall: `node lib/preinstall.js`
    npm ERR! Exit status 1npm ERR! 
    npm ERR! Failed at the iobroker.zwave@1.3.1 preinstall script.
    npm 
    ERR! This is probably not a problem with npm. There is likely additional logging output above.
    >! npm
    
    ERR!
     A complete log of this run can be found in:
    npm
    
    ERR!
         /home/iobroker/.npm/_logs/2019-01-17T21_46_43_961Z-debug.log
    host.iobroker-ct-deb install adapter zwave
    ERROR: host.iobroker-ct-deb Cannot install zwave
    ERROR: process exited with code 13</anonymous></anonymous></anonymous>
    

    Bei der Installation mit "sudo -H npm i iobroker.zwave –unsafe-perm" aus der Konsole kommt:

    > iobroker.zwave@1.3.1 preinstall /home/iobroker/.npm/_logs/node_modules/iobroker.zwave
    > node lib/preinstall.js
    >! ---> find /tmp -name 'CentralScene.h'
    ---> find /usr/include/ -name 'CentralScene.h'
    ---> find /usr/local/include/ -name 'CentralScene.h'
    CentralScene.h found in /usr/local/include/openzwave/command_classes/CentralScene.h
    >! ---> find /usr/local/include/ -name 'CentralScene.h'|grep 'createSupportedKeyAttributesValues'
    ---> Error: Command failed: find /usr/local/include/ -name 'CentralScene.h'|grep 'createSupportedKeyAttributesValues'
    ---> apt-get install libudev-dev -y
    ---> curl -L -O https://github.com/OpenZWave/open-zwave/archive/master.zip
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
    100   125    0   125    0     0    228      0 --:--:-- --:--:-- --:--:--   228
    100 1880k    0 1880k    0     0   840k      0 --:--:--  0:00:02 --:--:-- 1940k
    ---> rm -rf open-zwave-master
    ---> unzip master.zip && rm master.zip
    ---> cd open-zwave-master && curl -O -L https://github.com/OpenZWave/open-zwave/pull/1125.patch && patch -p1 < 1125.patch
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
    100   147    0   147    0     0    250      0 --:--:-- --:--:-- --:--:--   250
    100 16081    0 16081    0     0  12336      0 --:--:--  0:00:01 --:--:-- 30001
    ---> cd open-zwave-master && make && make install
    Makefile:224: Documentation not being built
    npm WARN saveError ENOENT: no such file or directory, open '/home/iobroker/.npm/_logs/package.json'
    npm WARN enoent ENOENT: no such file or directory, open '/home/iobroker/.npm/_logs/package.json'
    npm WARN _logs No description
    npm WARN _logs No repository field.
    npm WARN _logs No README data
    npm WARN _logs No license field.
    >! + iobroker.zwave@1.3.1
    updated 1 package and audited 6 packages in 176.514s
    found 0 vulnerabilities
    

    Versucht habe ich es mit einem Container mit Debian 9.5.1 und mit einem Container mit Ubuntu 18.10 jeweils priviligiert und unpriviligiert (was auch immer sich dadurch ändert). ioBroker habe ich jeweils einmal nach der neuen und einmal nach der alten Methode installiert und die avahi-daemon Änderung hat auch nichts gebracht.

    ! Mit einer virtuellen Maschine mit Debian 9.6.0 habe ich es auch noch versucht - leider auch erfolglos.
    ! Mir gehen langsam die Ideen aus, und aus Verzweiflung spiele ich schon mit dem Gedanken, den Raspberry als Multihost nur für Z-Wave weiterzubetrieben.

    1 Antwort Letzte Antwort
    0
    • Schuko80S Offline
      Schuko80S Offline
      Schuko80
      schrieb am zuletzt editiert von
      #116

      Wenn du mehr wie einen Stick verwendest, wäre es ratsam, diese per Udev eindeutig zu benennen und dann erst durchzureichen

      Nuc6cayh + Proxmox / Zigbee (Deconz / Conbee I ) / ZWave / Homematic (CCU2)

      1 Antwort Letzte Antwort
      0
      • X Offline
        X Offline
        Xanon
        schrieb am zuletzt editiert von
        #117

        Hallo,
        ich habe auch einen NUC mit Proxmox am laufen.
        Ich lasse iobroker jede Nacht um 4:00 Uhr Neustarten.
        Läuft seit dem 1 A.
        Heute habe ich es nach langer Zeit mal wieder gehabt, dass mein System nicht mehr Reagiert hat (Kein Zugriff mehr auf iobroker / Vis ).
        Weder über Webbrowser noch über Terminal.
        Ich habe die VM neugestartet und alles lief wieder sauber.

        Habe mir vor dem Neustart das LOG angesehen, kann dort aber nichts auffälliges erkennen. (Allerdings habe ich da auch nicht wirklich die Ahnung von)
        Sieht von euch jemand, wo das Problem sein könnte?
        Das Problem Problem ist irgendwann zwischen 23:00 Uhr und 00:45 Uhr aufgetreten.
        Braucht Ihr noch weitere Daten?

        Ich will nächste Woche in den Urlaub und da wäre es ärgerlich, wenn mir dies in dem Zeitraum passiert.

        Jun  8 22:58:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 22:59:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 22:59:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 22:59:32 pve rrdcached[1204]: flushing old values
        Jun  8 22:59:32 pve rrdcached[1204]: rotating journals
        Jun  8 22:59:32 pve rrdcached[1204]: started new journal /var/lib/rrdcached/journal/rrd.journal.1560027572.272352
        Jun  8 22:59:32 pve rrdcached[1204]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1560020372.272331
        Jun  8 23:00:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:00:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:01:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:01:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:01:28 pve pveproxy[10583]: worker exit
        Jun  8 23:01:28 pve pveproxy[1475]: worker 10583 finished
        Jun  8 23:01:28 pve pveproxy[1475]: starting 1 worker(s)
        Jun  8 23:01:28 pve pveproxy[1475]: worker 25349 started
        Jun  8 23:02:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:02:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:03:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:03:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:04:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:04:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:05:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:05:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:06:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:06:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:07:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:07:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:07:58 pve pveproxy[10421]: worker exit
        Jun  8 23:07:58 pve pveproxy[1475]: worker 10421 finished
        Jun  8 23:07:58 pve pveproxy[1475]: starting 1 worker(s)
        Jun  8 23:07:58 pve pveproxy[1475]: worker 26805 started
        Jun  8 23:08:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:08:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:08:28 pve pveproxy[9156]: worker exit
        Jun  8 23:08:28 pve pveproxy[1475]: worker 9156 finished
        Jun  8 23:08:28 pve pveproxy[1475]: starting 1 worker(s)
        Jun  8 23:08:28 pve pveproxy[1475]: worker 26933 started
        Jun  8 23:09:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:09:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:10:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:10:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:11:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:11:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:12:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:12:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:13:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:13:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:14:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:14:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:15:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:15:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:16:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:16:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:17:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:17:01 pve CRON[28866]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
        Jun  8 23:17:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:18:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:18:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:18:38 pve pvedaemon[980]: worker exit
        Jun  8 23:18:38 pve pvedaemon[1421]: worker 980 finished
        Jun  8 23:18:38 pve pvedaemon[1421]: starting 1 worker(s)
        Jun  8 23:18:38 pve pvedaemon[1421]: worker 29228 started
        Jun  8 23:19:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:19:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:20:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:20:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:20:08 pve pvedaemon[308]: worker exit
        Jun  8 23:20:08 pve pvedaemon[1421]: worker 308 finished
        Jun  8 23:20:08 pve pvedaemon[1421]: starting 1 worker(s)
        Jun  8 23:20:08 pve pvedaemon[1421]: worker 29579 started
        Jun  8 23:21:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:21:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:22:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:22:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:23:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:23:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:24:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:24:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:25:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:25:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:26:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:26:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:27:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:27:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:28:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:28:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:29:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:29:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:30:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:30:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:31:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:31:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:32:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:32:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:33:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:33:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:34:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:34:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:35:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:35:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:36:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:36:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:37:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:37:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:38:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:38:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:39:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:39:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:40:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:40:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:41:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:41:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:42:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:42:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:43:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:43:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:44:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:44:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:45:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:45:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:46:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:46:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:47:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:47:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:48:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:48:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:49:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:49:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:50:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:50:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:51:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:51:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:52:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:52:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:53:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:53:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:54:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:54:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:55:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:55:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:56:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:56:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:57:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:57:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:58:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:58:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:59:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  8 23:59:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  8 23:59:32 pve rrdcached[1204]: flushing old values
        Jun  8 23:59:32 pve rrdcached[1204]: rotating journals
        Jun  8 23:59:32 pve rrdcached[1204]: started new journal /var/lib/rrdcached/journal/rrd.journal.1560031172.272349
        Jun  8 23:59:32 pve rrdcached[1204]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1560023972.272342
        Jun  9 00:00:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:00:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:01:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:01:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:02:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:02:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:02:52 pve pvedaemon[29579]: <root@pam> successful auth for user 'root@pam'
        Jun  9 00:03:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:03:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:04:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:04:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:05:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:05:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:06:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:06:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:07:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:07:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:08:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:08:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:09:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:09:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:10:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:10:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:11:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:11:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:11:09 pve pveproxy[25349]: worker exit
        Jun  9 00:11:09 pve pveproxy[1475]: worker 25349 finished
        Jun  9 00:11:09 pve pveproxy[1475]: starting 1 worker(s)
        Jun  9 00:11:09 pve pveproxy[1475]: worker 8713 started
        Jun  9 00:12:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:12:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:13:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:13:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:14:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:14:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:15:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:15:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:16:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:16:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:16:19 pve pveproxy[26933]: worker exit
        Jun  9 00:16:19 pve pveproxy[1475]: worker 26933 finished
        Jun  9 00:16:19 pve pveproxy[1475]: starting 1 worker(s)
        Jun  9 00:16:19 pve pveproxy[1475]: worker 9882 started
        Jun  9 00:17:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:17:01 pve CRON[10048]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
        Jun  9 00:17:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:18:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:18:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:18:29 pve pvedaemon[15212]: worker exit
        Jun  9 00:18:29 pve pvedaemon[1421]: worker 15212 finished
        Jun  9 00:18:29 pve pvedaemon[1421]: starting 1 worker(s)
        Jun  9 00:18:29 pve pvedaemon[1421]: worker 10374 started
        Jun  9 00:19:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:19:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:20:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:20:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:21:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:21:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:22:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:22:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:23:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:23:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:23:29 pve pveproxy[26805]: worker exit
        Jun  9 00:23:29 pve pveproxy[1475]: worker 26805 finished
        Jun  9 00:23:29 pve pveproxy[1475]: starting 1 worker(s)
        Jun  9 00:23:29 pve pveproxy[1475]: worker 11502 started
        Jun  9 00:24:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:24:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:24:01 pve CRON[11640]: (root) CMD ([ $(date +%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-linux/scrub)
        Jun  9 00:25:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:25:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:26:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:26:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:27:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:27:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:28:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:28:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:29:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:29:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:30:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:30:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:31:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:31:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:32:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:32:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:33:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:33:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:34:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:34:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:35:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:35:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:36:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:36:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:37:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:37:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:38:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:38:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:39:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:39:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:40:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:40:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:41:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:41:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:42:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:42:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:43:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:43:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:43:59 pve systemd[1]: Created slice User Slice of root.
        Jun  9 00:43:59 pve systemd[1]: Starting User Manager for UID 0...
        Jun  9 00:43:59 pve systemd[1]: Started Session 277 of user root.
        Jun  9 00:43:59 pve systemd[13704]: Reached target Timers.
        Jun  9 00:43:59 pve systemd[13704]: Reached target Paths.
        Jun  9 00:43:59 pve systemd[13704]: Listening on GnuPG cryptographic agent (access for web browsers).
        Jun  9 00:43:59 pve systemd[13704]: Listening on GnuPG cryptographic agent and passphrase cache.
        Jun  9 00:43:59 pve systemd[13704]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
        Jun  9 00:43:59 pve systemd[13704]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
        Jun  9 00:43:59 pve systemd[13704]: Reached target Sockets.
        Jun  9 00:43:59 pve systemd[13704]: Reached target Basic System.
        Jun  9 00:43:59 pve systemd[13704]: Reached target Default.
        Jun  9 00:43:59 pve systemd[13704]: Startup finished in 38ms.
        Jun  9 00:43:59 pve systemd[1]: Started User Manager for UID 0.
        Jun  9 00:44:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:44:01 pve systemd[1]: Started Proxmox VE replication runner.
        Jun  9 00:45:00 pve systemd[1]: Starting Proxmox VE replication runner...
        Jun  9 00:45:01 pve systemd[1]: Started Proxmox VE replication runner.
        
        1 Antwort Letzte Antwort
        0
        • X Offline
          X Offline
          Xanon
          schrieb am zuletzt editiert von
          #118

          Hallo ,
          irgendetwas schein bei meinem NUC noch immer nicht sauber zu laufen.

          Heute mittag ist mein System mit iobroker mal wieder abgeschmiert (in meiner Abwesenheit)
          Kein Zugriff auf iobroker mehr.

          Als ich zuhause war, habe ich mir das Log vom Nun angesehen und festgestellt das mein Log überschwemmt wurde von:

          Nov 28 06:25:05 pve liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="817" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
          Nov 28 06:25:05 pve spiceproxy[1509]: restarting server
          Nov 28 06:25:05 pve spiceproxy[1509]: starting 1 worker(s)
          Nov 28 06:25:05 pve spiceproxy[1509]: worker 10104 started
          Nov 28 06:25:05 pve pveproxy[1476]: restarting server
          Nov 28 06:25:05 pve pveproxy[1476]: starting 3 worker(s)
          Nov 28 06:25:05 pve pveproxy[1476]: worker 10105 started
          Nov 28 06:25:05 pve pveproxy[1476]: worker 10106 started
          Nov 28 06:25:05 pve pveproxy[1476]: worker 10107 started
          Nov 28 06:25:10 pve spiceproxy[9074]: worker exit
          Nov 28 06:25:10 pve pveproxy[28262]: worker exit
          Nov 28 06:25:10 pve pveproxy[27911]: worker exit
          Nov 28 06:25:10 pve pveproxy[29688]: worker exit
          Nov 28 06:25:10 pve pveproxy[1476]: worker 28262 finished
          Nov 28 06:25:10 pve pveproxy[1476]: worker 29688 finished
          Nov 28 06:25:10 pve pveproxy[1476]: worker 27911 finished
          Nov 28 06:25:11 pve spiceproxy[1509]: worker 9074 finished
          Nov 28 06:26:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:26:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:27:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:27:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:28:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:28:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:29:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:29:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:30:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:30:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:31:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:31:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:32:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:32:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:33:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:33:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:34:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:34:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:35:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:35:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:36:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:36:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:37:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:37:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:37:50 pve pvedaemon[16345]: worker exit
          Nov 28 06:37:50 pve pvedaemon[1422]: worker 16345 finished
          Nov 28 06:37:50 pve pvedaemon[1422]: starting 1 worker(s)
          Nov 28 06:37:50 pve pvedaemon[1422]: worker 12977 started
          Nov 28 06:38:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:38:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:39:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:39:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:39:20 pve systemd[1]: Starting Daily apt upgrade and clean activities...
          Nov 28 06:39:21 pve systemd[1]: Started Daily apt upgrade and clean activities.
          Nov 28 06:39:21 pve systemd[1]: apt-daily-upgrade.timer: Adding 38min 3.159092s random time.
          Nov 28 06:39:21 pve systemd[1]: apt-daily-upgrade.timer: Adding 58min 57.998026s random time.
          Nov 28 06:40:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:40:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:41:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:41:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:42:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:42:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:43:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:43:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:44:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:44:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:45:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:45:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:46:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:46:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:47:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:47:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:48:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:48:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:49:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:49:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:50:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:50:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:51:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:51:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:51:50 pve pvedaemon[19539]: worker exit
          Nov 28 06:51:50 pve pvedaemon[1422]: worker 19539 finished
          Nov 28 06:51:50 pve pvedaemon[1422]: starting 1 worker(s)
          Nov 28 06:51:50 pve pvedaemon[1422]: worker 16206 started
          Nov 28 06:52:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:52:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:52:23 pve rrdcached[1211]: flushing old values
          Nov 28 06:52:23 pve rrdcached[1211]: rotating journals
          Nov 28 06:52:23 pve rrdcached[1211]: started new journal /var/lib/rrdcached/journal/rrd.journal.1574920343.354189
          Nov 28 06:52:23 pve rrdcached[1211]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1574913143.354113
          Nov 28 06:53:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:53:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:54:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:54:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:55:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:55:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:56:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:56:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:56:20 pve pvedaemon[20881]: worker exit
          Nov 28 06:56:21 pve pvedaemon[1422]: worker 20881 finished
          Nov 28 06:56:21 pve pvedaemon[1422]: starting 1 worker(s)
          Nov 28 06:56:21 pve pvedaemon[1422]: worker 17225 started
          Nov 28 06:57:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:57:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:58:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:58:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 06:59:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 06:59:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:00:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:00:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:01:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:01:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:02:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:02:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:03:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:03:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:04:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:04:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:05:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:05:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:06:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:06:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:07:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:07:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:08:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:08:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:09:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:09:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:10:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:10:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:11:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:11:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:12:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:12:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:13:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:13:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:14:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:14:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:15:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:15:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:16:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:16:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:17:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:17:01 pve CRON[21917]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
          Nov 28 07:17:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:18:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:18:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:19:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:19:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:20:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:20:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:21:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:21:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:22:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:22:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:23:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:23:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:24:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:24:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:25:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:25:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:26:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:26:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:27:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:27:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:28:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:28:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:29:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:29:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:30:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:30:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:31:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:31:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:32:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:32:01 pve systemd[1]: Started Proxmox VE replication runner.
          Nov 28 07:33:00 pve systemd[1]: Starting Proxmox VE replication runner...
          Nov 28 07:33:01 pve systemd[1]: Started Proxmox VE replication runner.
          

          Das ganze Log ist voll mit diesem pve systemd[1]: Starting Proxmox VE replication runner...
          Kann das der Grund für einen Absturz sein?
          Jemand ne Ahnung, was da passiert, bzw. wie so etwas unterbinden kann?

          Wie kann ich sonst dem Übeltäter auf die schliche kommen?
          Mal läuft das System 3 Wochen ohne Probleme durch und mal hält es gerade mal einen Tag.
          Update und Upgrade durchgeführt.
          Macht Ihr ein regelmäßigen Neustart ?

          Gruß
          Marcus

          ChaotC 1 Antwort Letzte Antwort
          0
          • X Xanon

            Hallo ,
            irgendetwas schein bei meinem NUC noch immer nicht sauber zu laufen.

            Heute mittag ist mein System mit iobroker mal wieder abgeschmiert (in meiner Abwesenheit)
            Kein Zugriff auf iobroker mehr.

            Als ich zuhause war, habe ich mir das Log vom Nun angesehen und festgestellt das mein Log überschwemmt wurde von:

            Nov 28 06:25:05 pve liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="817" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
            Nov 28 06:25:05 pve spiceproxy[1509]: restarting server
            Nov 28 06:25:05 pve spiceproxy[1509]: starting 1 worker(s)
            Nov 28 06:25:05 pve spiceproxy[1509]: worker 10104 started
            Nov 28 06:25:05 pve pveproxy[1476]: restarting server
            Nov 28 06:25:05 pve pveproxy[1476]: starting 3 worker(s)
            Nov 28 06:25:05 pve pveproxy[1476]: worker 10105 started
            Nov 28 06:25:05 pve pveproxy[1476]: worker 10106 started
            Nov 28 06:25:05 pve pveproxy[1476]: worker 10107 started
            Nov 28 06:25:10 pve spiceproxy[9074]: worker exit
            Nov 28 06:25:10 pve pveproxy[28262]: worker exit
            Nov 28 06:25:10 pve pveproxy[27911]: worker exit
            Nov 28 06:25:10 pve pveproxy[29688]: worker exit
            Nov 28 06:25:10 pve pveproxy[1476]: worker 28262 finished
            Nov 28 06:25:10 pve pveproxy[1476]: worker 29688 finished
            Nov 28 06:25:10 pve pveproxy[1476]: worker 27911 finished
            Nov 28 06:25:11 pve spiceproxy[1509]: worker 9074 finished
            Nov 28 06:26:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:26:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:27:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:27:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:28:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:28:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:29:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:29:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:30:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:30:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:31:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:31:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:32:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:32:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:33:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:33:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:34:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:34:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:35:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:35:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:36:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:36:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:37:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:37:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:37:50 pve pvedaemon[16345]: worker exit
            Nov 28 06:37:50 pve pvedaemon[1422]: worker 16345 finished
            Nov 28 06:37:50 pve pvedaemon[1422]: starting 1 worker(s)
            Nov 28 06:37:50 pve pvedaemon[1422]: worker 12977 started
            Nov 28 06:38:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:38:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:39:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:39:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:39:20 pve systemd[1]: Starting Daily apt upgrade and clean activities...
            Nov 28 06:39:21 pve systemd[1]: Started Daily apt upgrade and clean activities.
            Nov 28 06:39:21 pve systemd[1]: apt-daily-upgrade.timer: Adding 38min 3.159092s random time.
            Nov 28 06:39:21 pve systemd[1]: apt-daily-upgrade.timer: Adding 58min 57.998026s random time.
            Nov 28 06:40:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:40:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:41:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:41:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:42:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:42:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:43:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:43:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:44:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:44:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:45:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:45:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:46:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:46:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:47:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:47:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:48:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:48:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:49:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:49:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:50:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:50:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:51:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:51:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:51:50 pve pvedaemon[19539]: worker exit
            Nov 28 06:51:50 pve pvedaemon[1422]: worker 19539 finished
            Nov 28 06:51:50 pve pvedaemon[1422]: starting 1 worker(s)
            Nov 28 06:51:50 pve pvedaemon[1422]: worker 16206 started
            Nov 28 06:52:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:52:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:52:23 pve rrdcached[1211]: flushing old values
            Nov 28 06:52:23 pve rrdcached[1211]: rotating journals
            Nov 28 06:52:23 pve rrdcached[1211]: started new journal /var/lib/rrdcached/journal/rrd.journal.1574920343.354189
            Nov 28 06:52:23 pve rrdcached[1211]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1574913143.354113
            Nov 28 06:53:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:53:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:54:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:54:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:55:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:55:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:56:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:56:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:56:20 pve pvedaemon[20881]: worker exit
            Nov 28 06:56:21 pve pvedaemon[1422]: worker 20881 finished
            Nov 28 06:56:21 pve pvedaemon[1422]: starting 1 worker(s)
            Nov 28 06:56:21 pve pvedaemon[1422]: worker 17225 started
            Nov 28 06:57:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:57:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:58:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:58:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 06:59:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 06:59:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:00:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:00:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:01:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:01:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:02:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:02:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:03:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:03:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:04:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:04:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:05:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:05:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:06:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:06:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:07:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:07:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:08:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:08:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:09:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:09:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:10:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:10:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:11:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:11:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:12:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:12:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:13:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:13:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:14:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:14:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:15:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:15:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:16:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:16:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:17:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:17:01 pve CRON[21917]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
            Nov 28 07:17:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:18:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:18:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:19:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:19:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:20:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:20:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:21:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:21:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:22:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:22:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:23:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:23:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:24:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:24:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:25:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:25:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:26:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:26:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:27:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:27:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:28:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:28:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:29:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:29:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:30:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:30:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:31:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:31:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:32:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:32:01 pve systemd[1]: Started Proxmox VE replication runner.
            Nov 28 07:33:00 pve systemd[1]: Starting Proxmox VE replication runner...
            Nov 28 07:33:01 pve systemd[1]: Started Proxmox VE replication runner.
            

            Das ganze Log ist voll mit diesem pve systemd[1]: Starting Proxmox VE replication runner...
            Kann das der Grund für einen Absturz sein?
            Jemand ne Ahnung, was da passiert, bzw. wie so etwas unterbinden kann?

            Wie kann ich sonst dem Übeltäter auf die schliche kommen?
            Mal läuft das System 3 Wochen ohne Probleme durch und mal hält es gerade mal einen Tag.
            Update und Upgrade durchgeführt.
            Macht Ihr ein regelmäßigen Neustart ?

            Gruß
            Marcus

            ChaotC Offline
            ChaotC Offline
            Chaot
            schrieb am zuletzt editiert von
            #119

            @Xanon Warum soll eine Replikation durchgeführt werden?
            Hast du zwei Knoten/Server am laufen?

            ioBroker auf NUC unter Proxmox; VIS: 12" Touchscreen und 17" Touch; Lichtsteuerung, Thermometer und Sensoren: Tasmota (39); Ambiente Beleuchtung: WLED (9); Heizung: DECT Thermostate (9) an Fritz 6690; EMS-ESP; 1 Echo V2; 3 Echo DOT; 1 Echo Connect; 2 Echo Show 5; Unifi Ap-Ac Lite.

            X 1 Antwort Letzte Antwort
            0
            • ChaotC Chaot

              @Xanon Warum soll eine Replikation durchgeführt werden?
              Hast du zwei Knoten/Server am laufen?

              X Offline
              X Offline
              Xanon
              schrieb am zuletzt editiert von
              #120

              @Chaot

              Ich hoffe nicht 😬

              Bin was NUC und Proxmox angeht jetzt nicht ganz so bewandert.
              Kann ich das irgendwo sehen / nachvollziehen.

              1 Antwort Letzte Antwort
              0
              • X Offline
                X Offline
                Xanon
                schrieb am zuletzt editiert von
                #121

                So hab noch mal nachgesehen.
                keine zwei Knoten / Server am laufen.
                Unter dem Punkt Replizierung steht:
                "Replizierung benötigt mindestens zwei Knoten"

                Der Logeintrag scheint kein unbekanntes Problem zu sein
                Link Text

                Die Frage ist wie bekomme ich raus, was mein System immer mal wieder in die Knie zwingt?

                BBTownB 1 Antwort Letzte Antwort
                0
                • X Xanon

                  So hab noch mal nachgesehen.
                  keine zwei Knoten / Server am laufen.
                  Unter dem Punkt Replizierung steht:
                  "Replizierung benötigt mindestens zwei Knoten"

                  Der Logeintrag scheint kein unbekanntes Problem zu sein
                  Link Text

                  Die Frage ist wie bekomme ich raus, was mein System immer mal wieder in die Knie zwingt?

                  BBTownB Offline
                  BBTownB Offline
                  BBTown
                  schrieb am zuletzt editiert von
                  #122

                  @Xanon in dem Beitrag deines Links waren doch auch die Lösungsansätze für die Log-Einträge enthalten

                  ioBroker auf NUC (VM debian v13 (Trixie ), node v22.21.0 npm v10.9.4, js-controller v7.0.7 jsonl/jsonl / HomeMatic CCU-2 (Wired und Funk) / Philips HUE / echo.DOT / Broadlink RM pro / SONOS

                  1 Antwort Letzte Antwort
                  0
                  • BuZZyB Offline
                    BuZZyB Offline
                    BuZZy
                    schrieb am zuletzt editiert von BuZZy
                    #123

                    Diese Logeinträge hatte ich auch.. ioBroker (oder andere VMs) haben sich bei mir aber nie aufgehängt..
                    Habe die Logeinträge trotzdem auch vor kurzem abgestellt weil sie einfach nervig waren.. :laughing:

                    Dein Problem muss also ein anderes sein und ich würde mir die Logfiles auf der VM angucken (da wo ioBroker drauf läuft).. Und nicht die Logfiles vom Proxmox Host.

                    Gruß

                    1 Antwort Letzte Antwort
                    0
                    • X Offline
                      X Offline
                      Xanon
                      schrieb am zuletzt editiert von
                      #124

                      @BuZZy sagte in Installation auf NUC mit Proxmox:

                      Diese Logeinträge hatte ich auch.. ioBroker (oder andere VMs) haben sich bei mir aber nie aufgehängt..
                      Habe die Logeinträge trotzdem auch vor kurzem abgestellt weil sie einfach nervig waren.. :laughing:

                      Dein Problem muss also ein anderes sein und ich würde mir die Logfiles auf der VM angucken (da wo ioBroker drauf läuft).. Und nicht die Logfiles vom Proxmox Host.

                      Gruß

                      Hallo,
                      da das ganze System immer mal wieder zusammenbricht und ich im iObroker Log nichts erkennen konnte, ich aber diese Log-Einträge im NUC gesehen hatte, bin ich davon ausgegangen das es vielleicht mit dem NUC zusammenhängt.

                      Hätte ja sein können, das jemand anderes dieses Problem auch bereits hatte aber nichts geschrieben hat.

                      Falls das Problem mit dem Log noch jemand haben sollte mit dem ...

                      Das ganze Log ist voll mit diesem
                      
                       pve systemd[1]: Starting Proxmox VE replication runner...
                      

                      Ich habe das Problem nun gelöst indem ich folgendes im Terminal eingeben habe:

                      systemctl edit --full pvesr.timer
                      

                      Dort habe ich unter dem Punkt:

                      **[Timer]
                      OnCalendar=minutely**
                      

                      auf

                      **[Timer]
                      OnCalendar=monthly**
                      

                      geändert.

                      Bis jetzt keine Einträge mehr :-)

                      Ich beobachte weiter und danke Euch für die Unterstützung.

                      Gruß
                      Marcus

                      1 Antwort Letzte Antwort
                      0
                      • opossumO Offline
                        opossumO Offline
                        opossum
                        schrieb am zuletzt editiert von
                        #125

                        Hallo,

                        ich habe noch eine Frage zu Promox. Ich habe versucht, von einem Snapshot meiner Prod eine Testumgebung als VM über Klonen zu bauen. Das ging gründlich schief. Der Rechner, von dem aus ich auf Proxmox zugriff, hatte keine Netzwerkverbindung mehr. Alles tot. Alle Webinterfaces waren weg (iobrokerprod als auch pve). Es ging auch kein ssh-Zugriff mehr über putty, nix. Ich habe dann den NUC durch "hartes" Ausschalten abgewürgt mit dem Wissen, dass ich vielleicht alles neu bauen müsse. Aber die Kiste lief wieder hoch, auch der iobrokerprod startete, alles gut. Geklont habe ich dann von der laufenden Maschine. Dann nach Anleitung /etc/hostname und /etc/hosts sowie die ssh-keys erneuert. Dann lief die Testumgebung. Ist die Option Klonen Buggy unter proxmox?
                        Fehlermeldung von proxmox im log: Unable to read tail (got 0 Bytes).

                        https://schlepper-petersdorf.jimdofree.com/

                        BuZZyB 1 Antwort Letzte Antwort
                        0
                        • opossumO Offline
                          opossumO Offline
                          opossum
                          schrieb am zuletzt editiert von
                          #126

                          Hallo,

                          noch eine zweite Frage: Der Adapter proxmox verliert bei mir beim Neustart des iobroker immer das Zugriffspasswort zu proxmox, kann das jemand bestätigen?

                          https://schlepper-petersdorf.jimdofree.com/

                          1 Antwort Letzte Antwort
                          0
                          • opossumO opossum

                            Hallo,

                            ich habe noch eine Frage zu Promox. Ich habe versucht, von einem Snapshot meiner Prod eine Testumgebung als VM über Klonen zu bauen. Das ging gründlich schief. Der Rechner, von dem aus ich auf Proxmox zugriff, hatte keine Netzwerkverbindung mehr. Alles tot. Alle Webinterfaces waren weg (iobrokerprod als auch pve). Es ging auch kein ssh-Zugriff mehr über putty, nix. Ich habe dann den NUC durch "hartes" Ausschalten abgewürgt mit dem Wissen, dass ich vielleicht alles neu bauen müsse. Aber die Kiste lief wieder hoch, auch der iobrokerprod startete, alles gut. Geklont habe ich dann von der laufenden Maschine. Dann nach Anleitung /etc/hostname und /etc/hosts sowie die ssh-keys erneuert. Dann lief die Testumgebung. Ist die Option Klonen Buggy unter proxmox?
                            Fehlermeldung von proxmox im log: Unable to read tail (got 0 Bytes).

                            BuZZyB Offline
                            BuZZyB Offline
                            BuZZy
                            schrieb am zuletzt editiert von BuZZy
                            #127

                            @opossum sagte in Installation auf NUC mit Proxmox:

                            Hallo,

                            ich habe noch eine Frage zu Promox. Ich habe versucht, von einem Snapshot meiner Prod eine Testumgebung als VM über Klonen zu bauen. Das ging gründlich schief. [.......] Ist die Option Klonen Buggy unter proxmox?

                            Wie genau hast du denn geklont? Was heißt bei dir "bauen"? :laughing:

                            Wenn du auf der laufenden VM einen Rechtsklick machst dann hast du doch die Option "Klonen" und da kannst du dann auswählen auf welchen Snapshot-Zustand der Klon gesetzt werden soll.. 2 Klicks und der Klon ist fertig.
                            Damit habe ich noch nie Probleme gehabt.

                            @opossum sagte in Installation auf NUC mit Proxmox:

                            Hallo,

                            noch eine zweite Frage: Der Adapter proxmox verliert bei mir beim Neustart des iobroker immer das Zugriffspasswort zu proxmox, kann das jemand bestätigen?

                            Nein, läuft bei mir ohne Probleme - auch nach Neustart.

                            Gruß

                            1 Antwort Letzte Antwort
                            0
                            • opossumO Offline
                              opossumO Offline
                              opossum
                              schrieb am zuletzt editiert von
                              #128

                              Hallo, @BuZZy ,

                              danke für die schnelle Antwort. "Bauen" heisst, ich wollt ein VM anlegen als Testumgebung. Dazu habe ich genau das gemacht, was Du beschrieben hast. Beim ersten Mal habe ich einen vorhandene Snapshot ausgewählt, beim zweiten Mal habe ich als Einstellung "current" gelassen. Damit ging das dann auch fix. Das mit dem Passwort werde ich beobachten.

                              https://schlepper-petersdorf.jimdofree.com/

                              1 Antwort Letzte Antwort
                              0
                              Antworten
                              • In einem neuen Thema antworten
                              Anmelden zum Antworten
                              • Älteste zuerst
                              • Neuste zuerst
                              • Meiste Stimmen


                              Support us

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

                              654

                              Online

                              32.4k

                              Benutzer

                              81.4k

                              Themen

                              1.3m

                              Beiträge
                              Community
                              Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                              ioBroker Community 2014-2025
                              logo
                              • Anmelden

                              • Du hast noch kein Konto? Registrieren

                              • Anmelden oder registrieren, um zu suchen
                              • Erster Beitrag
                                Letzter Beitrag
                              0
                              • Home
                              • Aktuell
                              • Tags
                              • Ungelesen 0
                              • Kategorien
                              • Unreplied
                              • Beliebt
                              • GitHub
                              • Docu
                              • Hilfe