Proxmox VM friert ein
-
@trooper sagte in Proxmox VM friert ein:
alles nicht im Root installiert
@trooper sagte in Proxmox VM friert ein:
*** User and Groups *** root /root root
@trooper sagte in Proxmox VM friert ein:
läuft nicht mal einen Nacht durch
mal ne andere Speicherkarte testen
-
diese anzeige richtet sich nur danach wie man die diag abfragt:
selbe abfrage mit dem user:
Skript v.2023-04-02 *** BASE SYSTEM *** Architecture : aarch64 Docker : false Virtualization : none Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy PRETTY_NAME="Armbian 23.02.2 Jammy" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy Systemuptime and Load: 10:48:36 up 20 min, 2 users, load average: 0.11, 0.15, 0.16 CPU threads: 6 *** Time and Time Zones *** Local time: Thu 2023-04-13 10:48:36 CEST Universal time: Thu 2023-04-13 08:48:36 UTC RTC time: Thu 2023-04-13 08:48:36 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** iobroker /home/iobroker iobroker tty disk dialout sudo audio video plugdev games users systemd-journal input netdev i2c *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 3.9G 398M 2.9G 5.0M 544M 3.4G Swap: 1.9G 0B 1.9G Total: 5.8G 398M 4.9G 3863 M total memory 398 M used memory 302 M active memory 474 M inactive memory 2920 M free memory 30 M buffer memory 514 M swap cache 1931 M total swap 0 M used swap 1931 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on tmpfs tmpfs 387M 5.8M 381M 2% /run /dev/mmcblk1p1 ext4 29G 2.0G 27G 8% / tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 1.9G 0 1.9G 0% /tmp /dev/zram1 ext4 47M 2.3M 42M 6% /var/log tmpfs tmpfs 387M 0 387M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [sudo] password for iobroker: [Thu Apr 13 10:27:50 2023] Kernel command line: root=UUID=d2ca5998-a4b5-4be3-a461-968167bef317 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=b7307320-01 usb-storage.quirks= cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [Thu Apr 13 10:27:56 2023] EXT4-fs (mmcblk1p1): mounted filesystem with writeback data mode. Opts: (null). Quota mode: none. [Thu Apr 13 10:27:57 2023] EXT4-fs (mmcblk1p1): re-mounted. Opts: commit=600,errors=remount-ro. Quota mode: none. [Thu Apr 13 10:27:59 2023] EXT4-fs (zram1): mounted filesystem without journal. Opts: discard. Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk1p1 ext4 rw,noatime,errors=remount-ro,commit=600 |-/var/log.hdd /dev/mmcblk1p1[/var/log] ext4 rw,noatime,errors=remount-ro,commit=600 `-/var/log /dev/zram1 ext4 rw,relatime,discard Files in neuralgic directories: /var: 413M /var/ 212M /var/cache 208M /var/cache/apt 197M /var/lib 174M /var/lib/apt/lists /opt/iobroker/backups: 8.8M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 45M /opt/iobroker/iobroker-data/ 35M /opt/iobroker/iobroker-data/files 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static 13M /opt/iobroker/iobroker-data/files/admin.admin/custom The five largest files in iobroker-data are: 6.8M /opt/iobroker/iobroker-data/objects.jsonl 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map 4.5M /opt/iobroker/iobroker-data/files/web.admin/static/js/2.b1d56998.chunk.js.map 2.8M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js 2.0M /opt/iobroker/iobroker-data/states.jsonl *** NodeJS-Installation *** /usr/bin/nodejs v16.19.1 /usr/bin/node v16.19.1 /usr/bin/npm 8.19.3 /usr/bin/npx 8.19.3 nodejs: Installed: 16.19.1-deb-1nodesource1 Candidate: 16.19.1-deb-1nodesource1 Version table: *** 16.19.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x jammy/main arm64 Packages 100 /var/lib/dpkg/status 12.22.9~dfsg-1ubuntu3 500 500 http://ports.ubuntu.com jammy/universe arm64 Packages Temp directories causing npm8 problem: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 4.0.24 admin: 6.3.5 javascript: "javascript" not found Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : rockpi-4c - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : rockpi-4c - enabled + system.adapter.discovery.0 : discovery : rockpi-4c - enabled system.adapter.vis.0 : vis : rockpi-4c - enabled + system.adapter.web.0 : web : rockpi-4c - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : rockpi-4c - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : rockpi-4c - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "backitup" : 2.6.16 , installed 2.6.16 Adapter "discovery" : 3.1.0 , installed 3.1.0 Controller "js-controller": 4.0.24 , installed 4.0.24 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "vis" : 1.4.16 , installed 1.4.16 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0 Objects and States Please stand by - This may take a while Objects: 179 States: 143 *** OS-Repositories and Updates *** Hit:1 http://ports.ubuntu.com jammy InRelease Hit:2 http://ports.ubuntu.com jammy-security InRelease Hit:3 http://ports.ubuntu.com jammy-updates InRelease Hit:4 http://ports.ubuntu.com jammy-backports InRelease Hit:5 https://deb.nodesource.com/node_16.x jammy InRelease Hit:6 http://mirrors.dotsrc.org/armbian-apt jammy InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 101 19818 688/systemd-resolve tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 11337 1/init tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 19894 915/sshd: /usr/sbin tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 23327 849/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 23320 849/iobroker.js-con tcp6 0 0 :::8081 :::* LISTEN 1000 11247 1504/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1000 23429 1561/io.web.0 tcp6 0 0 :::111 :::* LISTEN 0 11339 1/init tcp6 0 0 :::22 :::* LISTEN 0 19896 915/sshd: /usr/sbin udp 0 0 127.0.0.53:53 0.0.0.0:* 101 19817 688/systemd-resolve udp 0 0 0.0.0.0:111 0.0.0.0:* 0 11338 1/init udp 0 0 127.0.0.1:323 0.0.0.0:* 0 23277 938/chronyd udp6 0 0 :::111 :::* 0 11340 1/init udp6 0 0 ::1:323 :::* 0 23278 938/chronyd *** Log File - Last 25 Lines *** 2023-04-13 10:44:22.053 - info: host.rockpi-4c stopInstance system.adapter.backitup.0 send kill signal 2023-04-13 10:44:22.068 - info: admin.0 (1504) <== Disconnect system.user.admin from ::ffff:192.168.1.61 2023-04-13 10:44:22.634 - info: host.rockpi-4c instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-04-13 10:44:25.113 - info: host.rockpi-4c instance system.adapter.backitup.0 started with pid 3751 2023-04-13 10:44:25.394 - info: admin.0 (1504) ==> Connected system.user.admin from ::ffff:192.168.1.61 2023-04-13 10:44:27.219 - info: backitup.0 (3751) starting. Version 2.6.16 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.19.1, js-controller: 4.0.24 2023-04-13 10:44:27.381 - info: backitup.0 (3751) [iobroker] backup was activated at 11:00 every 1 day(s) 2023-04-13 10:44:46.624 - info: admin.0 (1504) <== Disconnect system.user.admin from ::ffff:192.168.1.61 2023-04-13 10:45:01.463 - info: admin.0 (1504) ==> Connected system.user.admin from ::ffff:192.168.1.61 2023-04-13 10:45:24.514 - info: host.rockpi-4c stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-04-13 10:45:24.528 - info: backitup.0 (3751) Got terminate signal TERMINATE_YOURSELF 2023-04-13 10:45:24.532 - info: backitup.0 (3751) cleaned everything up... 2023-04-13 10:45:24.535 - info: backitup.0 (3751) terminating 2023-04-13 10:45:24.539 - info: backitup.0 (3751) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-04-13 10:45:24.569 - info: admin.0 (1504) <== Disconnect system.user.admin from ::ffff:192.168.1.61 2023-04-13 10:45:24.573 - info: host.rockpi-4c stopInstance system.adapter.backitup.0 send kill signal 2023-04-13 10:45:25.156 - info: host.rockpi-4c instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-04-13 10:45:27.651 - info: host.rockpi-4c instance system.adapter.backitup.0 started with pid 3793 2023-04-13 10:45:29.799 - info: backitup.0 (3793) starting. Version 2.6.16 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.19.1, js-controller: 4.0.24 2023-04-13 10:45:29.965 - info: backitup.0 (3793) [iobroker] backup was activated at 11:00 every 1 day(s) 2023-04-13 10:45:36.282 - info: admin.0 (1504) ==> Connected system.user.admin from ::ffff:192.168.1.61 2023-04-13 10:45:45.562 - info: admin.0 (1504) <== Disconnect system.user.admin from ::ffff:192.168.1.61 2023-04-13 10:45:47.050 - info: admin.0 (1504) ==> Connected system.user.admin from ::ffff:192.168.1.61 2023-04-13 10:46:07.543 - info: admin.0 (1504) <== Disconnect system.user.admin from ::ffff:192.168.1.61 web 2023-04-13 10:46:09.595 - info: admin.0 (1504) <== Disconnect system.user.admin from ::ffff:192.168.1.61 adminEine Speicherkarte nutze ich nicht Sondern einen EPROM
Ich teste dann nochmal mit eine SD mal sehen
-
@trooper sagte in Proxmox VM friert ein:
diese anzeige richtet sich nur danach wie man die diag abfragt:
Natürlich. Aber da man auch nie als root direkt eingeloggt ist passt das schon.
-
@thomas-braun sagte in Proxmox VM friert ein:
nie als root direkt eingeloggt ist
und bei einem ubuntu dann wohl eher auch noch bewusst freigeschaltet
-
@crunchip sagte in Proxmox VM friert ein:
und bei einem ubuntu dann wohl eher auch noch bewusst freigeschaltet
Bei so etwas exotischeren Varianten wie hier weiß ich es nicht.
Aber bei den gängigen ubuntus müsste man den aktiv ausbuddeln, der root ist im Standard nicht direkt zugänglich. -
@crunchip
bei armbian ist es schon freigeschaltet war auch überraschthab den root auch gerade nur genutzt um die abfrage zu machen.
Ich frage mich was der iobroker in der Nacht macht das er sich da immer aufhängt mir ist es am tag noch nicht aufgefallen.
-
@trooper sagte in Proxmox VM friert ein:
Ich frage mich was der iobroker in der Nacht macht
Backups sind da ein Kandidat.
hab den root auch gerade nur genutzt um die abfrage zu machen.
"Nie als root" bedeutet eigentlich gar nicht. Also im Sinne von: Überhaupt nicht.
-
an Backups hab ich auch gedacht zeit hab ich schon geändert.
hatte ein versuch gemacht mit 11:00 Uhr heute
keine probleme -
@trooper sagte in Proxmox VM friert ein:
in der Nacht
Netzwerktrennung, wobei das eigentlich kein Auslöser sein dürfte
-
Schau mal in das journal zu den Zeiten rein, wenn das Ding wegknickt.
Und zu den verwendeten Usern: Leg dir einen User an, der nicht 'iobroker' heißt.
trooper@hostsähe ja auch fein aus. -
@crunchip
eine Netzwerktrennung habe ich nicht, nur einmal die Woche die Internet Verbindungdas Problem dabei ist das die logs dann teilweise leer sind da ja der ganze rockpi sich komplett aufhängt und ohne neustart per strom an/aus geht nix mehr.
wenn ich nur armbian drauf habe läuft alles super
welches Journal meinst du genau wo soll ich nach schauen
-
-
@thomas-braun
das passt hier nicht rein zu viele Zeichenggf. https://docs.google.com/document/d/1Ww7WcLnSYOweuwp9gjRcaXpXRS95Tv9eJP0GLmuiGas/edit?usp=sharing
-
@trooper
Den Betrachtungs-Zeitraum kann man einschränken. Siehe Wiki. -
@thomas-braun
steht eh nix drin nur die Sachen nach dem Neustart davor ist alles weg. -
Dann schau in die Datei davor rein.
-
@thomas-braun
genau da ist das Problem
es gibt davor keine dateidas syslog gibt etwas aus
einmal
Apr 12 22:42:04 rockpi-4c chronyd[919]: System clock TAI offset set to 37 seconds Apr 12 22:42:08 rockpi-4c systemd[1]: Starting system activity accounting tool... Apr 12 22:42:08 rockpi-4c systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Apr 12 22:42:08 rockpi-4c systemd[1]: sysstat-collect.service: Deactivated successfully. Apr 12 22:42:08 rockpi-4c systemd[1]: Finished system activity accounting tool. Apr 12 22:42:23 rockpi-4c systemd[1]: systemd-hostnamed.service: Deactivated successfully. Apr 12 22:42:44 rockpi-4c bash[824]: ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging] Apr 12 22:42:44 rockpi-4c bash[824]: Send diag info: {"uuid":"c1b40163-c876-817d-fb52-0ed724c840f1","language":"de","country":"","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.19.1","arch":"arm64","docker":false,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.6.16","platform":"Javascript/Node.js"},"web":{"version":"4.3.0","platform":"Javascript/Node.js"},"vis":{"version":"1.4.16","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":5,"compactMode":false,"noCompactInstances":0,"model":"Cortex-A53","cpus":6,"mem":4051189760,"ostype":"Linux","city":"Schwerin","vis":6} Apr 12 22:45:01 rockpi-4c CRON[1587]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Apr 12 22:45:01 rockpi-4c CRON[1586]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Apr 12 22:47:29 rockpi-4c chronyd[919]: Selected source 54.38.156.22 (1.ubuntu.pool.ntp.org) Apr 12 22:47:58 rockpi-4c bash[824]: ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] Apr 12 22:47:58 rockpi-4c bash[824]: ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging] Apr 12 22:48:06 rockpi-4c bash[824]: ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging] Apr 12 22:48:27 rockpi-4c bash[824]: Send diag info: {"uuid":"c1b40163-c876-817d-fb52-0ed724c840f1","language":"de","country":"","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.19.1","arch":"arm64","docker":false,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.6.16","platform":"Javascript/Node.js"},"web":{"version":"4.3.0","platform":"Javascript/Node.js"},"vis":{"version":"1.4.16","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":5,"compactMode":false,"noCompactInstances":0,"model":"Cortex-A53","cpus":6,"mem":4051189760,"ostype":"Linux","city":"Schwerin","vis":6} Apr 12 22:50:00 rockpi-4c systemd[1]: Starting system activity accounting tool... Apr 12 22:50:00 rockpi-4c systemd[1]: sysstat-collect.service: Deactivated successfully. Apr 12 22:50:00 rockpi-4c systemd[1]: Finished system activity accounting tool. Apr 12 22:55:01 rockpi-4c CRON[1710]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Apr 12 22:57:20 rockpi-4c systemd[1]: Starting Cleanup of Temporary Directories... Apr 12 22:57:20 rockpi-4c systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Apr 12 22:57:20 rockpi-4c systemd[1]: Finished Cleanup of Temporary Directories. Apr 12 23:00:00 rockpi-4c systemd[1]: Starting system activity accounting tool... Apr 12 23:00:00 rockpi-4c systemd[1]: sysstat-collect.service: Deactivated successfully. Apr 12 23:00:00 rockpi-4c systemd[1]: Finished system activity accounting tool. Apr 12 23:00:01 rockpi-4c CRON[1721]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Apr 12 23:05:01 rockpi-4c CRON[1735]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Apr 12 23:10:20 rockpi-4c systemd[1]: Starting system activity accounting tool... Apr 12 23:10:20 rockpi-4c systemd[1]: sysstat-collect.service: Deactivated successfully. Apr 12 23:10:20 rockpi-4c systemd[1]: Finished system activity accounting tool. Apr 12 23:15:01 rockpi-4c CRON[1751]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Apr 12 23:15:01 rockpi-4c CRON[1750]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Apr 12 23:17:01 rockpi-4c CRON[1763]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 12 23:20:00 rockpi-4c systemd[1]: Starting system activity accounting tool... Apr 12 23:20:00 rockpi-4c systemd[1]: sysstat-collect.service: Deactivated successfully. Apr 12 23:20:00 rockpi-4c systemd[1]: Finished system activity accounting tool. Apr 12 23:25:01 rockpi-4c CRON[1783]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Apr 12 23:30:00 rockpi-4c systemd[1]: Starting system activity accounting tool... Apr 12 23:30:00 rockpi-4c systemd[1]: sysstat-collect.service: Deactivated successfully. Apr 12 23:30:00 rockpi-4c systemd[1]: Finished system activity accounting tool. Apr 12 23:30:01 rockpi-4c CRON[1790]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Apr 12 23:35:01 rockpi-4c CRON[1805]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Apr 12 23:40:20 rockpi-4c systemd[1]: Starting system activity accounting tool... Apr 12 23:40:20 rockpi-4c systemd[1]: sysstat-collect.service: Deactivated successfully. Apr 12 23:40:20 rockpi-4c systemd[1]: Finished system activity accounting tool. Apr 12 23:45:01 rockpi-4c CRON[1823]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Apr 12 23:45:01 rockpi-4c CRON[1824]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Apr 12 23:50:00 rockpi-4c systemd[1]: Starting system activity accounting tool... Apr 12 23:50:00 rockpi-4c systemd[1]: sysstat-collect.service: Deactivated successfully. Apr 12 23:50:00 rockpi-4c systemd[1]: Finished system activity accounting tool. Apr 12 23:55:01 rockpi-4c CRON[1845]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Apr 12 23:59:01 rockpi-4c CRON[1852]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 60 2) Apr 13 00:00:00 rockpi-4c systemd[1]: Starting Daily dpkg database backup service... Apr 13 00:00:00 rockpi-4c systemd[1]: Starting system activity accounting tool... Apr 13 00:00:00 rockpi-4c systemd[1]: Starting Rotate log files... Apr 13 00:00:00 rockpi-4c systemd[1]: sysstat-collect.service: Deactivated successfully. Apr 13 00:00:00 rockpi-4c systemd[1]: Finished system activity accounting tool. Apr 13 00:00:00 rockpi-4c armbian-ramlog[1876]: Thu Apr 13 12:00:00 AM CEST 2023: Syncing logs to storage Apr 13 00:00:00 rockpi-4c armbian-ramlog[1881]: sending incremental file list Apr 13 00:00:00 rockpi-4c armbian-ramlog[1881]: ./ Apr 13 00:00:00 rockpi-4c armbian-ramlog[1881]: armbian-hardware-monitor.log Apr 13 00:00:00 rockpi-4c armbian-ramlog[1881]: auth.log Apr 13 00:00:00 rockpi-4c armbian-ramlog[1881]: boot.log Apr 13 00:00:00 rockpi-4c armbian-ramlog[1881]: dmesg Apr 13 00:00:00 rockpi-4c armbian-ramlog[1881]: dmesg.0 Apr 13 00:00:00 rockpi-4c armbian-ramlog[1881]: kern.log Apr 13 01:17:05 rockpi-4c systemd-random-seed[438]: Kernel entropy pool is not initialized yet, waiting until it is. Apr 13 01:17:05 rockpi-4c systemd-udevd[470]: Using default interface naming scheme 'v249'. Apr 13 01:17:05 rockpi-4c systemd-udevd[470]: eth0: Failed to query device driver: Device or resource busy Apr 13 01:17:05 rockpi-4c systemd-udevd[470]: eth0: Could not set offload features, ignoring: Device or resource busy Apr 13 01:17:05 rockpi-4c systemd-udevd[487]: Using default interface naming scheme 'v249'. Apr 13 01:17:05 rockpi-4c systemd-udevd[487]: wlan0: Process '/sbin/iw dev wlan0 set power_save off' failed with exit code 1. Apr 13 01:17:05 rockpi-4c fake-hwclock[413]: Wed Apr 12 11:17:01 PM UTC 2023 Apr 13 01:17:05 rockpi-4c systemd[1]: Starting Flush Journal to Persistent Storage... Apr 13 01:17:05 rockpi-4c armbian-zram-config[500]: Setting up swapspace version 1, size = 1.9 GiB (2025590784 bytes) Apr 13 01:17:05 rockpi-4c armbian-zram-config[500]: no label, UUID=3f834bf3-a042-4a4e-adb1-2826356f3da2 Apr 13 01:17:05 rockpi-4c armbian-zram-config[637]: mke2fs 1.46.5 (30-Dec-2021) Apr 13 01:17:05 rockpi-4c armbian-zram-config[637]: Discarding device blocks: 0/12800#010#010#010#010#010#010#010#010#010#010#010 #010#010#010#010#010#010#010#010#010#010#010done Apr 13 01:17:05 rockpi-4c armbian-zram-config[637]: Creating filesystem with 12800 4k blocks and 12800 inodes Apr 13 01:17:05 rockpi-4c armbian-zram-config[637]: Allocating group tables: 0/1#010#010#010 #010#010#010done Apr 13 01:17:05 rockpi-4c armbian-zram-config[637]: Writing inode tables: 0/1#010#010#010 #010#010#010done Apr 13 01:17:05 rockpi-4c armbian-zram-config[637]: Writing superblocks and filesystem accounting information: 0/1#010#010#010 #010#010#010done Apr 13 01:17:05 rockpi-4c ifup[555]: /etc/network/if-up.d/resolved: 12: mystatedir: not found Apr 13 01:17:05 rockpi-4c armbian-ramlog[644]: e2label: Bad magic number in super-block while trying to open /dev/zram0 Apr 13 01:17:05 rockpi-4c armbian-ramlog[647]: Mounting /dev/zram1 as /var/log Apr 13 01:17:05 rockpi-4c armbian-ramlog[653]: Thu Apr 13 01:17:03 AM CEST 2023: Loading logs from storage Apr 13 01:17:05 rockpi-4c armbian-ramlog[656]: sending incremental file list Apr 13 01:17:05 rockpi-4c armbian-ramlog[656]: ./ Apr 13 01:17:05 rockpi-4c armbian-ramlog[656]: alternatives.log Apr 13 01:17:05 rockpi-4c armbian-ramlog[656]: armbian-hardware-monitor.log Apr 13 01:17:05 rockpi-4c kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] Apr 13 01:17:05 rockpi-4c armbian-ramlog[656]: auth.log Apr 13 01:17:05 rockpi-4c kernel: [ 0.000000] Linux version 5.15.80-rockchip64 (root@746a5325a2a9) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #22.11.1 SMP PREEMPT Wed Nov 30 11:12:47 UTC 2022 Apr 13 01:17:05 rockpi-4c kernel: [ 0.000000] Machine model: Radxa ROCK Pi 4C Apr 13 01:17:05 rockpi-4c kernel: [ 0.000000] efi: UEFI not found. Apr 13 01:17:05 rockpi-4c kernel: [ 0.000000] NUMA: No NUMA configuration found Apr 13 01:17:05 rockpi-4c armbian-ramlog[656]: boot.log Apr 13 01:17:05 rockpi-4c kernel: [ 0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000000f7ffffff] Apr 13 01:17:05 rockpi-4c kernel: [ 0.000000] NUMA: NODE_DATA [mem 0xf77d6100-0xf77d7fff] -
@trooper sagte in Proxmox VM friert ein:
e2label: Bad magic number in super-block while trying to open /dev/zram0
Das würde ich mir anschauen, das riecht nach Ärger mit/im Dateisystem.
-
Gut wenn das die Ursache ist wars das für mich ich installiere nicht nochmal alles neu auf dem rockpi
es ist die Standard Installation und die macht schon Fehler so ein ...
Danke mit dem Rockpi mach ich nicht weiter mit iobroker den nur die Software hat Probleme nach der Installation alles andere läuft Fehler frei genau wie die VMs auf meiner anderen Kiste fehlerfrei.ich denke der Fehler ist der iobroker der mit bestimmten Systemen einfach nicht läuft.
Danke trotzdem -
@trooper sagte in Proxmox VM friert ein:
genau da ist das Problem
es gibt davor keine datei
das syslog gibt etwas ausMoin,
ich bin kein Experte, was all die RasPIs und anderen Kleinstplatinen Rechner angeht und auch die dazugehörigen Betriebssysteme habe ich nicht am Laufen, nur so wie ich das interpretiere, macht Dein System alle fünf Minuten folgendes
Damit sammelt das OS Metriken, die per SAR ausgewertet werden können, ich denke, die dazugehörigen Files findest Du unter
/var/log/sysstatApr 12 23:25:01 rockpi-4c CRON[1783]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)Dann werden die in der
RAM-Disk = zram.0 oder wenn Fehler zram.1abgelegten Logfiles komprimiert und auf der Platte abgelegt, glaube ich, musst Du mal schauen, was das Skript genau macht, Skript läuft auch alle fünf Minuten. Und wenn Files aus derRAM-Disknicht auf Platte geschrieben werden, dann ist es logisch, dass die nach einem Reboot, Stromlos etc. weg sind ist haltRAM-DiskCRON[1790]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)Ich habe nur gegoogelt und kurz überflogen, aber da gibt es wohl mehrere, die Probleme damit haben / hatten, einiges aus 2022 und auch 2023.
VG
Bernd
