NEWS
Grafana Update Probleme
-
@thomas-braun
Das ist die Ausgabe:pi@homebridge:~ $ sudo apt-mark hold grafana grafana set on hold. pi@homebridge:~ $ sudo apt update Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 https://packages.grafana.com/oss/deb stable InRelease Hit:4 https://deb.nodesource.com/node_14.x bullseye InRelease Hit:5 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease Hit:6 https://repos.influxdata.com/debian bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 3 packages can be upgraded. Run 'apt list --upgradable' to see them. pi@homebridge:~ $ apt list --upgradable Listing... Done grafana/stable 8.5.0 armhf [upgradable from: 8.4.7] libcamera0/stable 0~git20220426+18e68a9b-1 armhf [upgradable from: 0~git20220303+e68e0f1e-1] raspi-config/stable 20220425 all [upgradable from: 20220419] pi@homebridge:~ $ sudo apt-get clean --dry-run Del /var/cache/apt/archives/* /var/cache/apt/archives/partial/* Del /var/lib/apt/lists/partial/* Del /var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin pi@homebridge:~ $ sudo apt-get clean pi@homebridge:~ $Mit besten Grüßen
Andy -
@thomas-braun
Das ist die Ausgabe:pi@homebridge:~ $ sudo apt-mark hold grafana grafana set on hold. pi@homebridge:~ $ sudo apt update Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 https://packages.grafana.com/oss/deb stable InRelease Hit:4 https://deb.nodesource.com/node_14.x bullseye InRelease Hit:5 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease Hit:6 https://repos.influxdata.com/debian bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 3 packages can be upgraded. Run 'apt list --upgradable' to see them. pi@homebridge:~ $ apt list --upgradable Listing... Done grafana/stable 8.5.0 armhf [upgradable from: 8.4.7] libcamera0/stable 0~git20220426+18e68a9b-1 armhf [upgradable from: 0~git20220303+e68e0f1e-1] raspi-config/stable 20220425 all [upgradable from: 20220419] pi@homebridge:~ $ sudo apt-get clean --dry-run Del /var/cache/apt/archives/* /var/cache/apt/archives/partial/* Del /var/lib/apt/lists/partial/* Del /var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin pi@homebridge:~ $ sudo apt-get clean pi@homebridge:~ $@damrak2022 Auf die Oberfläche komme ich noch nicht. Muss ich nochmal
systemctl restart grafana-servermachen?
Mit besten Grüßen
Andy -
@damrak2022 Auf die Oberfläche komme ich noch nicht. Muss ich nochmal
systemctl restart grafana-servermachen?
@damrak2022 sagte in Grafana Update Probleme:
systemctl restart grafana-server
sudo systemctl restart grafana-serverapt policy grafana*sagt?
-
@damrak2022 sagte in Grafana Update Probleme:
systemctl restart grafana-server
sudo systemctl restart grafana-serverapt policy grafana*sagt?
@thomas-braun sagte in Grafana Update Probleme:
apt policy grafana*
Leider immer noch das:
pi@homebridge:~ $ sudo systemctl restart grafana-server pi@homebridge:~ $ apt policy grafana* N: Unable to locate package grafana-rpi_7.4.3_armhf.deb pi@homebridge:~ $Mit besten Grüßen
Andy -
@thomas-braun sagte in Grafana Update Probleme:
apt policy grafana*
Leider immer noch das:
pi@homebridge:~ $ sudo systemctl restart grafana-server pi@homebridge:~ $ apt policy grafana* N: Unable to locate package grafana-rpi_7.4.3_armhf.deb pi@homebridge:~ $@damrak2022 sagte in Grafana Update Probleme:
Unable to locate package grafana-rpi_7.4.3_armhf.deb
und täglich grüsst das Murmeltier
umgestiegen von Proxmox auf Unraid
-
@thomas-braun sagte in Grafana Update Probleme:
apt policy grafana*
Leider immer noch das:
pi@homebridge:~ $ sudo systemctl restart grafana-server pi@homebridge:~ $ apt policy grafana* N: Unable to locate package grafana-rpi_7.4.3_armhf.deb pi@homebridge:~ $Dann weiß ich auch nicht wo das noch hängt.
Muss man vielleicht mal mit find über das System schrubben.
Da weiß ich aber so aus dem Kopf nicht die Parameter.Schau mal mit
sudo grep -rnw / -e 'grafana-rpi_7.4.3_armhf.deb'danach.
-
@damrak2022 sagte in Grafana Update Probleme:
Unable to locate package grafana-rpi_7.4.3_armhf.deb
und täglich grüsst das Murmeltier
@crunchip Ich google auch schon die ganze Zeit finde aber nichts zu diesem Problem.
Muss jetzt aufhören, da ich weg muss.
Danke an Euch, ich hoffe wir bekommen das hinpi@homebridge:~ $ sudo grep -rnw / -e 'grafana-rpi_7.4.3_armhf.deb' grep: /sys/kernel/tracing/per_cpu/cpu3/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu3/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu3/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu2/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu2/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu2/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu1/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu1/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu1/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu0/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu0/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu0/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/trace_marker_raw: Invalid argument grep: /sys/kernel/tracing/trace_marker: Invalid argument grep: /sys/kernel/tracing/free_buffer: Invalid argument grep: /sys/kernel/tracing/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/dri/1/Writeback-1/vrr_range: No such device grep: /sys/kernel/debug/dri/1/HDMI-A-2/vrr_range: No such device grep: /sys/kernel/debug/dri/1/HDMI-A-1/vrr_range: No such device grep: /sys/kernel/debug/clear_warn_once: Permission denied grep: /sys/kernel/debug/tracing/per_cpu/cpu3/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu3/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu3/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu2/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu2/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu2/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu1/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu1/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu1/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu0/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu0/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu0/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/trace_marker_raw: Invalid argument grep: /sys/kernel/debug/tracing/trace_marker: Invalid argument grep: /sys/kernel/debug/tracing/free_buffer: Invalid argument grep: /sys/kernel/debug/tracing/trace_pipe: Resource temporarily unavailable Segmentation fault pi@homebridge:~ $ Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798031] Internal error: : 1211 [#1] SMP ARM Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798600] Process grep (pid: 6264, stack limit = 0x4f745707) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798611] Stack: (0xc59c9d80 to 0xc59ca000) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798622] 9d80: c59c9dac c59c9d90 c0895498 c08953a4 c59c9dbc c59c9da0 c2308200 00000014 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798635] 9da0: c59c9dbc c59c9db0 c088c124 c089546c c59c9dec c59c9dc0 c088f8f4 c088c10c Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798648] 9dc0: 0000002e c2308200 00000014 c59c9e3c c7b80000 00018000 c59c9f58 00000efc Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798660] 9de0: c59c9e0c c59c9df0 c088fa0c c088f890 0000004b c2308200 00000014 c7b80000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798673] 9e00: c59c9e7c c59c9e10 c0894804 c088f9cc 00000014 3391a86e c3a42010 c1205048 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798685] 9e20: 01a39000 c0e8e918 c0e8e910 00000000 00000046 00000000 c59c9e54 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798698] 9e40: 00000046 00000000 c59c9ee4 3391a86e c045c164 c3880540 c0894a5c c1c77c38 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798710] 9e60: 01a39000 00018000 c59c9f58 c06545ec c59c9e94 c59c9e80 c0894a94 c08946bc Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798723] 9e80: 00018000 c59c9f58 c59c9ebc c59c9e98 c0654650 c0894a68 c3880540 00018000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798735] 9ea0: c1205048 00000000 01a39000 c59c9f58 c59c9f54 c59c9ec0 c0455ae0 c06545f8 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798748] 9ec0: c045c4a0 3391a86e c1205048 becee1e0 00000000 00000001 c59c9f94 c59c9ee8 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798760] 9ee0: c045c584 c045bff4 000007ff 00008100 00000001 00001000 00000000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798773] 9f00: 00201000 00000000 00001eb5 c047ab64 3391a86e c1205048 b6fba500 7ff00000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798785] 9f20: 00000003 3391a86e 01a39000 c1205048 c3880540 00000000 00000000 c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798798] 9f40: 01a39000 00018000 c59c9f94 c59c9f58 c0456240 c0455a38 00000000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798810] 9f60: 00000000 3391a86e 00000000 00000003 b6fba500 7ff00000 00000003 c0200244 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798823] 9f80: c59c8000 00000003 c59c9fa4 c59c9f98 c04562d0 c04561e4 00000000 c59c9fa8 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798835] 9fa0: c0200040 c04562c4 00000003 b6fba500 00000003 01a39000 00018000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798848] 9fc0: 00000003 b6fba500 7ff00000 00000003 00000003 01a39000 00000003 00018000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798860] 9fe0: 00046e38 becee138 b6e56134 b6e56150 60000010 00000003 00000000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798871] Backtrace: Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798880] [<c0895398>] (regmap_mmio_read32le) from [<c0895498>] (regmap_mmio_read+0x38/0x74) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798900] [<c0895460>] (regmap_mmio_read) from [<c088c124>] (_regmap_bus_reg_read+0x24/0x28) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798920] r5:00000014 r4:c2308200 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798927] [<c088c100>] (_regmap_bus_reg_read) from [<c088f8f4>] (_regmap_read+0x70/0x13c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798944] [<c088f884>] (_regmap_read) from [<c088fa0c>] (regmap_read+0x4c/0x6c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798962] r10:00000efc r9:c59c9f58 r8:00018000 r7:c7b80000 r6:c59c9e3c r5:00000014 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798973] r4:c2308200 r3:0000002e Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798981] [<c088f9c0>] (regmap_read) from [<c0894804>] (regmap_read_debugfs+0x154/0x364) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799000] r7:c7b80000 r6:00000014 r5:c2308200 r4:0000004b Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799008] [<c08946b0>] (regmap_read_debugfs) from [<c0894a94>] (regmap_map_read_file+0x38/0x40) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799029] r10:c06545ec r9:c59c9f58 r8:00018000 r7:01a39000 r6:c1c77c38 r5:c0894a5c Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799040] r4:c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799047] [<c0894a5c>] (regmap_map_read_file) from [<c0654650>] (full_proxy_read+0x64/0x80) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799065] [<c06545ec>] (full_proxy_read) from [<c0455ae0>] (vfs_read+0xb4/0x344) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799085] r9:c59c9f58 r8:01a39000 r7:00000000 r6:c1205048 r5:00018000 r4:c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799095] [<c0455a2c>] (vfs_read) from [<c0456240>] (ksys_read+0x68/0xe0) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799111] r10:00018000 r9:01a39000 r8:c3880540 r7:00000000 r6:00000000 r5:c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799122] r4:c1205048 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799129] [<c04561d8>] (ksys_read) from [<c04562d0>] (sys_read+0x18/0x1c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799145] r10:00000003 r9:c59c8000 r8:c0200244 r7:00000003 r6:7ff00000 r5:b6fba500 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799156] r4:00000003 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799162] [<c04562b8>] (sys_read) from [<c0200040>] (ret_fast_syscall+0x0/0x1c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799179] Exception stack(0xc59c9fa8 to 0xc59c9ff0) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799190] 9fa0: 00000003 b6fba500 00000003 01a39000 00018000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799202] 9fc0: 00000003 b6fba500 7ff00000 00000003 00000003 01a39000 00000003 00018000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799214] 9fe0: 00046e38 becee138 b6e56134 b6e56150 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799225] Code: e5903000 e0831001 e5910000 f57ff04f (e89da800)Mit besten Grüßen
Andy -
@crunchip Ich google auch schon die ganze Zeit finde aber nichts zu diesem Problem.
Muss jetzt aufhören, da ich weg muss.
Danke an Euch, ich hoffe wir bekommen das hinpi@homebridge:~ $ sudo grep -rnw / -e 'grafana-rpi_7.4.3_armhf.deb' grep: /sys/kernel/tracing/per_cpu/cpu3/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu3/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu3/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu2/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu2/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu2/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu1/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu1/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu1/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu0/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu0/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu0/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/trace_marker_raw: Invalid argument grep: /sys/kernel/tracing/trace_marker: Invalid argument grep: /sys/kernel/tracing/free_buffer: Invalid argument grep: /sys/kernel/tracing/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/dri/1/Writeback-1/vrr_range: No such device grep: /sys/kernel/debug/dri/1/HDMI-A-2/vrr_range: No such device grep: /sys/kernel/debug/dri/1/HDMI-A-1/vrr_range: No such device grep: /sys/kernel/debug/clear_warn_once: Permission denied grep: /sys/kernel/debug/tracing/per_cpu/cpu3/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu3/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu3/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu2/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu2/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu2/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu1/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu1/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu1/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu0/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu0/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu0/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/trace_marker_raw: Invalid argument grep: /sys/kernel/debug/tracing/trace_marker: Invalid argument grep: /sys/kernel/debug/tracing/free_buffer: Invalid argument grep: /sys/kernel/debug/tracing/trace_pipe: Resource temporarily unavailable Segmentation fault pi@homebridge:~ $ Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798031] Internal error: : 1211 [#1] SMP ARM Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798600] Process grep (pid: 6264, stack limit = 0x4f745707) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798611] Stack: (0xc59c9d80 to 0xc59ca000) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798622] 9d80: c59c9dac c59c9d90 c0895498 c08953a4 c59c9dbc c59c9da0 c2308200 00000014 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798635] 9da0: c59c9dbc c59c9db0 c088c124 c089546c c59c9dec c59c9dc0 c088f8f4 c088c10c Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798648] 9dc0: 0000002e c2308200 00000014 c59c9e3c c7b80000 00018000 c59c9f58 00000efc Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798660] 9de0: c59c9e0c c59c9df0 c088fa0c c088f890 0000004b c2308200 00000014 c7b80000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798673] 9e00: c59c9e7c c59c9e10 c0894804 c088f9cc 00000014 3391a86e c3a42010 c1205048 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798685] 9e20: 01a39000 c0e8e918 c0e8e910 00000000 00000046 00000000 c59c9e54 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798698] 9e40: 00000046 00000000 c59c9ee4 3391a86e c045c164 c3880540 c0894a5c c1c77c38 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798710] 9e60: 01a39000 00018000 c59c9f58 c06545ec c59c9e94 c59c9e80 c0894a94 c08946bc Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798723] 9e80: 00018000 c59c9f58 c59c9ebc c59c9e98 c0654650 c0894a68 c3880540 00018000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798735] 9ea0: c1205048 00000000 01a39000 c59c9f58 c59c9f54 c59c9ec0 c0455ae0 c06545f8 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798748] 9ec0: c045c4a0 3391a86e c1205048 becee1e0 00000000 00000001 c59c9f94 c59c9ee8 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798760] 9ee0: c045c584 c045bff4 000007ff 00008100 00000001 00001000 00000000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798773] 9f00: 00201000 00000000 00001eb5 c047ab64 3391a86e c1205048 b6fba500 7ff00000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798785] 9f20: 00000003 3391a86e 01a39000 c1205048 c3880540 00000000 00000000 c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798798] 9f40: 01a39000 00018000 c59c9f94 c59c9f58 c0456240 c0455a38 00000000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798810] 9f60: 00000000 3391a86e 00000000 00000003 b6fba500 7ff00000 00000003 c0200244 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798823] 9f80: c59c8000 00000003 c59c9fa4 c59c9f98 c04562d0 c04561e4 00000000 c59c9fa8 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798835] 9fa0: c0200040 c04562c4 00000003 b6fba500 00000003 01a39000 00018000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798848] 9fc0: 00000003 b6fba500 7ff00000 00000003 00000003 01a39000 00000003 00018000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798860] 9fe0: 00046e38 becee138 b6e56134 b6e56150 60000010 00000003 00000000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798871] Backtrace: Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798880] [<c0895398>] (regmap_mmio_read32le) from [<c0895498>] (regmap_mmio_read+0x38/0x74) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798900] [<c0895460>] (regmap_mmio_read) from [<c088c124>] (_regmap_bus_reg_read+0x24/0x28) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798920] r5:00000014 r4:c2308200 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798927] [<c088c100>] (_regmap_bus_reg_read) from [<c088f8f4>] (_regmap_read+0x70/0x13c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798944] [<c088f884>] (_regmap_read) from [<c088fa0c>] (regmap_read+0x4c/0x6c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798962] r10:00000efc r9:c59c9f58 r8:00018000 r7:c7b80000 r6:c59c9e3c r5:00000014 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798973] r4:c2308200 r3:0000002e Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798981] [<c088f9c0>] (regmap_read) from [<c0894804>] (regmap_read_debugfs+0x154/0x364) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799000] r7:c7b80000 r6:00000014 r5:c2308200 r4:0000004b Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799008] [<c08946b0>] (regmap_read_debugfs) from [<c0894a94>] (regmap_map_read_file+0x38/0x40) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799029] r10:c06545ec r9:c59c9f58 r8:00018000 r7:01a39000 r6:c1c77c38 r5:c0894a5c Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799040] r4:c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799047] [<c0894a5c>] (regmap_map_read_file) from [<c0654650>] (full_proxy_read+0x64/0x80) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799065] [<c06545ec>] (full_proxy_read) from [<c0455ae0>] (vfs_read+0xb4/0x344) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799085] r9:c59c9f58 r8:01a39000 r7:00000000 r6:c1205048 r5:00018000 r4:c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799095] [<c0455a2c>] (vfs_read) from [<c0456240>] (ksys_read+0x68/0xe0) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799111] r10:00018000 r9:01a39000 r8:c3880540 r7:00000000 r6:00000000 r5:c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799122] r4:c1205048 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799129] [<c04561d8>] (ksys_read) from [<c04562d0>] (sys_read+0x18/0x1c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799145] r10:00000003 r9:c59c8000 r8:c0200244 r7:00000003 r6:7ff00000 r5:b6fba500 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799156] r4:00000003 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799162] [<c04562b8>] (sys_read) from [<c0200040>] (ret_fast_syscall+0x0/0x1c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799179] Exception stack(0xc59c9fa8 to 0xc59c9ff0) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799190] 9fa0: 00000003 b6fba500 00000003 01a39000 00018000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799202] 9fc0: 00000003 b6fba500 7ff00000 00000003 00000003 01a39000 00000003 00018000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799214] 9fe0: 00046e38 becee138 b6e56134 b6e56150 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799225] Code: e5903000 e0831001 e5910000 f57ff04f (e89da800)Gut, die Idee war jetzt zugegeben nicht meine beste... :-D
-
@crunchip Ich google auch schon die ganze Zeit finde aber nichts zu diesem Problem.
Muss jetzt aufhören, da ich weg muss.
Danke an Euch, ich hoffe wir bekommen das hinpi@homebridge:~ $ sudo grep -rnw / -e 'grafana-rpi_7.4.3_armhf.deb' grep: /sys/kernel/tracing/per_cpu/cpu3/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu3/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu3/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu2/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu2/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu2/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu1/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu1/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu1/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu0/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu0/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/tracing/per_cpu/cpu0/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/tracing/trace_marker_raw: Invalid argument grep: /sys/kernel/tracing/trace_marker: Invalid argument grep: /sys/kernel/tracing/free_buffer: Invalid argument grep: /sys/kernel/tracing/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/dri/1/Writeback-1/vrr_range: No such device grep: /sys/kernel/debug/dri/1/HDMI-A-2/vrr_range: No such device grep: /sys/kernel/debug/dri/1/HDMI-A-1/vrr_range: No such device grep: /sys/kernel/debug/clear_warn_once: Permission denied grep: /sys/kernel/debug/tracing/per_cpu/cpu3/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu3/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu3/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu2/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu2/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu2/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu1/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu1/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu1/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu0/snapshot_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu0/trace_pipe_raw: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/per_cpu/cpu0/trace_pipe: Resource temporarily unavailable grep: /sys/kernel/debug/tracing/trace_marker_raw: Invalid argument grep: /sys/kernel/debug/tracing/trace_marker: Invalid argument grep: /sys/kernel/debug/tracing/free_buffer: Invalid argument grep: /sys/kernel/debug/tracing/trace_pipe: Resource temporarily unavailable Segmentation fault pi@homebridge:~ $ Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798031] Internal error: : 1211 [#1] SMP ARM Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798600] Process grep (pid: 6264, stack limit = 0x4f745707) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798611] Stack: (0xc59c9d80 to 0xc59ca000) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798622] 9d80: c59c9dac c59c9d90 c0895498 c08953a4 c59c9dbc c59c9da0 c2308200 00000014 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798635] 9da0: c59c9dbc c59c9db0 c088c124 c089546c c59c9dec c59c9dc0 c088f8f4 c088c10c Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798648] 9dc0: 0000002e c2308200 00000014 c59c9e3c c7b80000 00018000 c59c9f58 00000efc Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798660] 9de0: c59c9e0c c59c9df0 c088fa0c c088f890 0000004b c2308200 00000014 c7b80000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798673] 9e00: c59c9e7c c59c9e10 c0894804 c088f9cc 00000014 3391a86e c3a42010 c1205048 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798685] 9e20: 01a39000 c0e8e918 c0e8e910 00000000 00000046 00000000 c59c9e54 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798698] 9e40: 00000046 00000000 c59c9ee4 3391a86e c045c164 c3880540 c0894a5c c1c77c38 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798710] 9e60: 01a39000 00018000 c59c9f58 c06545ec c59c9e94 c59c9e80 c0894a94 c08946bc Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798723] 9e80: 00018000 c59c9f58 c59c9ebc c59c9e98 c0654650 c0894a68 c3880540 00018000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798735] 9ea0: c1205048 00000000 01a39000 c59c9f58 c59c9f54 c59c9ec0 c0455ae0 c06545f8 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798748] 9ec0: c045c4a0 3391a86e c1205048 becee1e0 00000000 00000001 c59c9f94 c59c9ee8 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798760] 9ee0: c045c584 c045bff4 000007ff 00008100 00000001 00001000 00000000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798773] 9f00: 00201000 00000000 00001eb5 c047ab64 3391a86e c1205048 b6fba500 7ff00000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798785] 9f20: 00000003 3391a86e 01a39000 c1205048 c3880540 00000000 00000000 c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798798] 9f40: 01a39000 00018000 c59c9f94 c59c9f58 c0456240 c0455a38 00000000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798810] 9f60: 00000000 3391a86e 00000000 00000003 b6fba500 7ff00000 00000003 c0200244 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798823] 9f80: c59c8000 00000003 c59c9fa4 c59c9f98 c04562d0 c04561e4 00000000 c59c9fa8 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798835] 9fa0: c0200040 c04562c4 00000003 b6fba500 00000003 01a39000 00018000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798848] 9fc0: 00000003 b6fba500 7ff00000 00000003 00000003 01a39000 00000003 00018000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798860] 9fe0: 00046e38 becee138 b6e56134 b6e56150 60000010 00000003 00000000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798871] Backtrace: Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798880] [<c0895398>] (regmap_mmio_read32le) from [<c0895498>] (regmap_mmio_read+0x38/0x74) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798900] [<c0895460>] (regmap_mmio_read) from [<c088c124>] (_regmap_bus_reg_read+0x24/0x28) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798920] r5:00000014 r4:c2308200 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798927] [<c088c100>] (_regmap_bus_reg_read) from [<c088f8f4>] (_regmap_read+0x70/0x13c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798944] [<c088f884>] (_regmap_read) from [<c088fa0c>] (regmap_read+0x4c/0x6c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798962] r10:00000efc r9:c59c9f58 r8:00018000 r7:c7b80000 r6:c59c9e3c r5:00000014 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798973] r4:c2308200 r3:0000002e Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.798981] [<c088f9c0>] (regmap_read) from [<c0894804>] (regmap_read_debugfs+0x154/0x364) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799000] r7:c7b80000 r6:00000014 r5:c2308200 r4:0000004b Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799008] [<c08946b0>] (regmap_read_debugfs) from [<c0894a94>] (regmap_map_read_file+0x38/0x40) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799029] r10:c06545ec r9:c59c9f58 r8:00018000 r7:01a39000 r6:c1c77c38 r5:c0894a5c Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799040] r4:c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799047] [<c0894a5c>] (regmap_map_read_file) from [<c0654650>] (full_proxy_read+0x64/0x80) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799065] [<c06545ec>] (full_proxy_read) from [<c0455ae0>] (vfs_read+0xb4/0x344) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799085] r9:c59c9f58 r8:01a39000 r7:00000000 r6:c1205048 r5:00018000 r4:c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799095] [<c0455a2c>] (vfs_read) from [<c0456240>] (ksys_read+0x68/0xe0) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799111] r10:00018000 r9:01a39000 r8:c3880540 r7:00000000 r6:00000000 r5:c3880540 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799122] r4:c1205048 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799129] [<c04561d8>] (ksys_read) from [<c04562d0>] (sys_read+0x18/0x1c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799145] r10:00000003 r9:c59c8000 r8:c0200244 r7:00000003 r6:7ff00000 r5:b6fba500 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799156] r4:00000003 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799162] [<c04562b8>] (sys_read) from [<c0200040>] (ret_fast_syscall+0x0/0x1c) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799179] Exception stack(0xc59c9fa8 to 0xc59c9ff0) Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799190] 9fa0: 00000003 b6fba500 00000003 01a39000 00018000 00000000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799202] 9fc0: 00000003 b6fba500 7ff00000 00000003 00000003 01a39000 00000003 00018000 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799214] 9fe0: 00046e38 becee138 b6e56134 b6e56150 Message from syslogd@homebridge at Apr 26 17:43:42 ... kernel:[ 2407.799225] Code: e5903000 e0831001 e5910000 f57ff04f (e89da800)@damrak2022 vllt ist es doch eine Möglichkeit diese
grafana-rpi_7.4.3_armhf.debnochmal von Hand zu installieren und anschliessend deinstallieren.Zuvor würde ich allerdings , den aktuellen Grafana Ordner wegsichern und die aktuelle Version runterwerfen.
Wenn das klappt, normal per apt wieder instalieren und die Config/Dashboard zurückspielen
Was anderes fällt mit da jetzt auch nicht mehr ein
umgestiegen von Proxmox auf Unraid
-
@damrak2022 vllt ist es doch eine Möglichkeit diese
grafana-rpi_7.4.3_armhf.debnochmal von Hand zu installieren und anschliessend deinstallieren.Zuvor würde ich allerdings , den aktuellen Grafana Ordner wegsichern und die aktuelle Version runterwerfen.
Wenn das klappt, normal per apt wieder instalieren und die Config/Dashboard zurückspielen
Was anderes fällt mit da jetzt auch nicht mehr ein
-
@crunchip ja, das könnte ich probieren. Wie sichere ich den Ordner weg?
@damrak2022
edit:das zeug liegt ja wo anders, muss ich mal suchen wo das liegt und ob man das überhaupt dann so wiederverwenden kann
z.b. so,
das ist der PATHS_DATA da liegt die grafana.db, die brauchst, denn da sind deine dashboards enthaltencp -r /var/lib/grafana/ /tmp/die anderen Ordner wären
PATHS_CONFIG /etc/grafana/grafana.ini PATHS_DATA /var/lib/grafana PATHS_HOME /usr/share/grafana PATHS_LOGS /var/log/grafana PATHS_PLUGINS /var/lib/grafana/plugins PATHS_PROVISIONING /etc/grafana/provisioningeventuell wäre das eine Möglichkeit
deinstallieren
sudo apt-get remove --auto-remove grafanaInstallation dann
sudo apt-get install -y adduser libfontconfig1 wget https://dl.grafana.com/oss/release/grafana-rpi_7.4.3_armhf.deb sudo dpkg -i grafana-rpi_7.4.3_armhf.debanschliessend dies wieder deinstallieren
sudo apt-get purge grafana-rpiumgestiegen von Proxmox auf Unraid
-
@damrak2022
edit:das zeug liegt ja wo anders, muss ich mal suchen wo das liegt und ob man das überhaupt dann so wiederverwenden kann
z.b. so,
das ist der PATHS_DATA da liegt die grafana.db, die brauchst, denn da sind deine dashboards enthaltencp -r /var/lib/grafana/ /tmp/die anderen Ordner wären
PATHS_CONFIG /etc/grafana/grafana.ini PATHS_DATA /var/lib/grafana PATHS_HOME /usr/share/grafana PATHS_LOGS /var/log/grafana PATHS_PLUGINS /var/lib/grafana/plugins PATHS_PROVISIONING /etc/grafana/provisioningeventuell wäre das eine Möglichkeit
deinstallieren
sudo apt-get remove --auto-remove grafanaInstallation dann
sudo apt-get install -y adduser libfontconfig1 wget https://dl.grafana.com/oss/release/grafana-rpi_7.4.3_armhf.deb sudo dpkg -i grafana-rpi_7.4.3_armhf.debanschliessend dies wieder deinstallieren
sudo apt-get purge grafana-rpiWürde mich wundern, wenn das so funktionieren würde.
dpkg hat soweit ich mich erinnere eine von apt unabhängige Datenbank über die installierten Pakete.Was gescheiteres fällt mir aber zugegeben im Moment auch nicht ein.
-
Würde mich wundern, wenn das so funktionieren würde.
dpkg hat soweit ich mich erinnere eine von apt unabhängige Datenbank über die installierten Pakete.Was gescheiteres fällt mir aber zugegeben im Moment auch nicht ein.
@thomas-braun sagte in Grafana Update Probleme:
Was gescheiteres fällt mir aber zugegeben im Moment auch nicht ein
na wen dir nichts weiter einfällt, was soll ich da sagen :joy:
ich hoffe halt, das dadurch der Rest verschwindetumgestiegen von Proxmox auf Unraid
-
@crunchip Das hat leider nicht geholfen.
Mittlerweile habe ich wieder die 8.4.7 drauf. Was mich wundert ist folgendes:
Nach Eingabe des Befehlssystemctl enable grafana-servermuss ich 4 mal mein Passwort eingeben - siehe hier:
systemctl enable grafana-server Synchronizing state of grafana-server.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable grafana-server ==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon === Authentication is required to reload the systemd state. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === ==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon === Authentication is required to reload the systemd state. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files === Authentication is required to manage system service or unit files. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === ==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon === Authentication is required to reload the systemd state. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === pi@homebridge:~ $Ist ja auch nicht normal, zumal der "reload-daemon" 3 mal auftaucht.
Ich glaube das lag daran, das ich den Befehl zuerst ohne "sudo" ausgeführt habeMit besten Grüßen
Andy -
@thomas-braun sagte in Grafana Update Probleme:
Was gescheiteres fällt mir aber zugegeben im Moment auch nicht ein
na wen dir nichts weiter einfällt, was soll ich da sagen :joy:
ich hoffe halt, das dadurch der Rest verschwindet@crunchip Da ich Euch nicht ewig mit diesem Mist nerven möchte, habe ich eine Frage zum Restore.
Bei Google Drive liegen bei mir Backups von JavaScripts, Influxdb, HisoryDB und ioBroker
Das älteste Backup ist vom 17.04.2022
Da habe ich allerdings schon mit Grafana gearbeitet.Gibt es eine Möglichkeit mein ältestes Backup einzuspielen und dabei Grafana wegzulassen. Die OneClick Option wird da ja nicht gehen da ich dann wieder die Daten von Grafana mit drin habe.
Falls ja, wie muss ich das dann genau machen?Mit besten Grüßen
Andy -
@crunchip Da ich Euch nicht ewig mit diesem Mist nerven möchte, habe ich eine Frage zum Restore.
Bei Google Drive liegen bei mir Backups von JavaScripts, Influxdb, HisoryDB und ioBroker
Das älteste Backup ist vom 17.04.2022
Da habe ich allerdings schon mit Grafana gearbeitet.Gibt es eine Möglichkeit mein ältestes Backup einzuspielen und dabei Grafana wegzulassen. Die OneClick Option wird da ja nicht gehen da ich dann wieder die Daten von Grafana mit drin habe.
Falls ja, wie muss ich das dann genau machen?@damrak2022 sagte in Grafana Update Probleme:
Bei Google Drive liegen bei mir Backups von JavaScripts, Influxdb, HisoryDB und ioBroker
Die Updates haben nichts mit der gekippten Installation auf dem System zu tun. Solange das auf Seiten des Paketmanager schief bleibt bringen dir die Backups des ioBrokers nichts.
-
@damrak2022 sagte in Grafana Update Probleme:
Bei Google Drive liegen bei mir Backups von JavaScripts, Influxdb, HisoryDB und ioBroker
Die Updates haben nichts mit der gekippten Installation auf dem System zu tun. Solange das auf Seiten des Paketmanager schief bleibt bringen dir die Backups des ioBrokers nichts.
@thomas-braun Das ist nicht gut. Ich google schon wieder seit Stunden. Das einzige was mir aufgefallen ist das es im Netz einige Beiträge zu
E: Unable to locate package grafana gibtaber nicht zu
N: Unable to locate package grafana
was bei mir erscheint
-
@crunchip Das hat leider nicht geholfen.
Mittlerweile habe ich wieder die 8.4.7 drauf. Was mich wundert ist folgendes:
Nach Eingabe des Befehlssystemctl enable grafana-servermuss ich 4 mal mein Passwort eingeben - siehe hier:
systemctl enable grafana-server Synchronizing state of grafana-server.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable grafana-server ==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon === Authentication is required to reload the systemd state. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === ==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon === Authentication is required to reload the systemd state. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files === Authentication is required to manage system service or unit files. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === ==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon === Authentication is required to reload the systemd state. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === pi@homebridge:~ $Ist ja auch nicht normal, zumal der "reload-daemon" 3 mal auftaucht.
Ich glaube das lag daran, das ich den Befehl zuerst ohne "sudo" ausgeführt habe@damrak2022 dann hast du hövhstwahrscheinlich den service Eintrag noch von den anderen drin stehen.
Schau mal das an
https://forum.iobroker.net/post/379964umgestiegen von Proxmox auf Unraid
-
@damrak2022 dann hast du hövhstwahrscheinlich den service Eintrag noch von den anderen drin stehen.
Schau mal das an
https://forum.iobroker.net/post/379964@crunchip Das hate ich schon mal gelesen und bin es eben nochmal erneut durchgegangen. Nur hat mir da leider nichts weitergeholfen.
Da er mir bei mir ja immer wieder auf die "N unable to locate Grafana 7.4.3" verweist, bzw rummeckert, frage ich mich mit welchem Befehl man diese Reste aufspüren könnte, um sie dann zu löschen
Ich selbst habe schon versucht mit dem "find" etwas zu finden, bin mir aber nicht sicher ob meine Befehle korrekt waren. -
@damrak2022 dann hast du hövhstwahrscheinlich den service Eintrag noch von den anderen drin stehen.
Schau mal das an
https://forum.iobroker.net/post/379964@crunchip So Gott sei Dank, das Problem ist beseitigt und alles läuft wieder rund. Mit Hilfe wurde entdeckt, das in der config wohl ein paar #Zeichen nicht vorhanden waren.
Nochmal vielen Dank an @crunchip und @thomas-braun die bestimmt schon an mir verzweifelt sind und trotzdem nicht aufgegeben haben mir zu helfen.Mit besten Grüßen
Andy
Support us
672
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge