NEWS
Absturz jede Woche beheben
ioBroker Allgemein
58
Beiträge
8
Kommentatoren
5.6k
Aufrufe
6
Watching
-
685 iobroker 20 0 5538316 524848 43196 S 10,6 13,5 28:12.16 iobroker.js-con 930 iobroker 20 0 1113292 254616 41504 S 4,3 6,6 7:25.09 io.javascript.0 1922 iobroker 20 0 992800 134144 37468 S 4,0 3,5 4:32.80 io.web.0 1270 iobroker 20 0 698396 105620 41816 S 3,3 2,7 1:58.72 io.tr-064.0 430 influxdb 20 0 1162896 170956 61164 S 2,7 4,4 1:13.06 influxd 1343 iobroker 20 0 991888 140904 42544 S 2,7 3,6 1:09.23 io.tuya.0 979 iobroker 20 0 990256 113036 36288 S 2,3 2,9 3:43.55 io.influxdb.0 1647 iobroker 20 0 695388 94176 41664 S 1,3 2,4 0:53.42 io.opendtu.0 2067 iobroker 20 0 689704 86468 36956 S 1,0 2,2 0:39.57 io.reolink.2 394 avahi 20 0 7144 3272 2764 S 0,7 0,1 0:04.66 avahi-daemon 15 root 20 0 0 0 0 I 0,3 0,0 0:09.28 rcu_preempt 1568 iobroker 20 0 681412 74640 36316 S 0,3 1,9 0:13.01 io.harmony.0 69037 root 20 0 0 0 0 I 0,3 0,0 0:00.02 kworker/u8:0-events_unbound 71584 pi 20 0 10256 3416 2836 R 0,3 0,1 0:00.18 top 1 root 20 0 164996 10036 7328 S 0,0 0,3 0:02.89 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.03 kthreadd 3 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rcu_gp 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rcu_par_gp 5 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 slub_flushwq 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 netns 10 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 mm_percpu_wq 11 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_tasks_kthread 12 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_tasks_rude_kthread 13 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_tasks_trace_kthread 14 root 20 0 0 0 0 S 0,0 0,0 0:01.61 ksoftirqd/0 16 root rt 0 0 0 0 S 0,0 0,0 0:00.01 migration/0 17 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/0 18 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/1 19 root rt 0 0 0 0 S 0,0 0,0 0:00.02 migration/1 20 root 20 0 0 0 0 S 0,0 0,0 0:00.56 ksoftirqd/1 23 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/2 24 root rt 0 0 0 0 S 0,0 0,0 0:00.01 migration/2 25 root 20 0 0 0 0 S 0,0 0,0 0:00.56 ksoftirqd/2 28 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/3 29 root rt 0 0 0 0 S 0,0 0,0 0:00.02 migration/3 30 root 20 0 0 0 0 S 0,0 0,0 0:00.49 ksoftirqd/3 33 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kdevtmpfs 34 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 inet_frag_wq 36 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kauditd 38 root 20 0 0 0 0 S 0,0 0,0 0:00.00 khungtaskd 40 root 20 0 0 0 0 S 0,0 0,0 0:00.00 oom_reaper 41 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 writeback 42 root 20 0 0 0 0 S 0,0 0,0 0:01.39 kcompactd0 43 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kintegrityd 44 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kblockd 45 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 blkcg_punt_bio 46 root -51 0 0 0 0 S 0,0 0,0 0:00.00 watchdogd 50 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rpciod 51 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 xprtiod 55 root 20 0 0 0 0 S 0,0 0,0 0:00.55 kswapd0 56 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 nfsiod 57 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kthrotld 65 root 20 0 0 0 0 S 0,0 0,0 0:00.00 hwrng 66 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 iscsi_conn_clea -
685 iobroker 20 0 5538316 524848 43196 S 10,6 13,5 28:12.16 iobroker.js-con 930 iobroker 20 0 1113292 254616 41504 S 4,3 6,6 7:25.09 io.javascript.0 1922 iobroker 20 0 992800 134144 37468 S 4,0 3,5 4:32.80 io.web.0 1270 iobroker 20 0 698396 105620 41816 S 3,3 2,7 1:58.72 io.tr-064.0 430 influxdb 20 0 1162896 170956 61164 S 2,7 4,4 1:13.06 influxd 1343 iobroker 20 0 991888 140904 42544 S 2,7 3,6 1:09.23 io.tuya.0 979 iobroker 20 0 990256 113036 36288 S 2,3 2,9 3:43.55 io.influxdb.0 1647 iobroker 20 0 695388 94176 41664 S 1,3 2,4 0:53.42 io.opendtu.0 2067 iobroker 20 0 689704 86468 36956 S 1,0 2,2 0:39.57 io.reolink.2 394 avahi 20 0 7144 3272 2764 S 0,7 0,1 0:04.66 avahi-daemon 15 root 20 0 0 0 0 I 0,3 0,0 0:09.28 rcu_preempt 1568 iobroker 20 0 681412 74640 36316 S 0,3 1,9 0:13.01 io.harmony.0 69037 root 20 0 0 0 0 I 0,3 0,0 0:00.02 kworker/u8:0-events_unbound 71584 pi 20 0 10256 3416 2836 R 0,3 0,1 0:00.18 top 1 root 20 0 164996 10036 7328 S 0,0 0,3 0:02.89 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.03 kthreadd 3 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rcu_gp 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rcu_par_gp 5 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 slub_flushwq 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 netns 10 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 mm_percpu_wq 11 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_tasks_kthread 12 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_tasks_rude_kthread 13 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_tasks_trace_kthread 14 root 20 0 0 0 0 S 0,0 0,0 0:01.61 ksoftirqd/0 16 root rt 0 0 0 0 S 0,0 0,0 0:00.01 migration/0 17 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/0 18 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/1 19 root rt 0 0 0 0 S 0,0 0,0 0:00.02 migration/1 20 root 20 0 0 0 0 S 0,0 0,0 0:00.56 ksoftirqd/1 23 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/2 24 root rt 0 0 0 0 S 0,0 0,0 0:00.01 migration/2 25 root 20 0 0 0 0 S 0,0 0,0 0:00.56 ksoftirqd/2 28 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/3 29 root rt 0 0 0 0 S 0,0 0,0 0:00.02 migration/3 30 root 20 0 0 0 0 S 0,0 0,0 0:00.49 ksoftirqd/3 33 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kdevtmpfs 34 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 inet_frag_wq 36 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kauditd 38 root 20 0 0 0 0 S 0,0 0,0 0:00.00 khungtaskd 40 root 20 0 0 0 0 S 0,0 0,0 0:00.00 oom_reaper 41 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 writeback 42 root 20 0 0 0 0 S 0,0 0,0 0:01.39 kcompactd0 43 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kintegrityd 44 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kblockd 45 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 blkcg_punt_bio 46 root -51 0 0 0 0 S 0,0 0,0 0:00.00 watchdogd 50 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rpciod 51 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 xprtiod 55 root 20 0 0 0 0 S 0,0 0,0 0:00.55 kswapd0 56 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 nfsiod 57 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kthrotld 65 root 20 0 0 0 0 S 0,0 0,0 0:00.00 hwrng 66 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 iscsi_conn_clea@g-hawk das ist eine scheduled Instanz.
Die startet kurz, macht ihre Arbeit und legt sich wieder schlafen.klar, dass das Leistung kostet. Ich habe den Adapter nicht, aber 70% CPU ist imho nicht normal
-
@g-hawk das ist eine scheduled Instanz.
Die startet kurz, macht ihre Arbeit und legt sich wieder schlafen.klar, dass das Leistung kostet. Ich habe den Adapter nicht, aber 70% CPU ist imho nicht normal
-
Hallo
Eben war ich am Skripte schreiben als er wieder abgestürzt ist.
Folgendes steht im Log, das steht da immer wenn er abstürzt.
Interessant sind die Zeiten...
Was sagt ihr dazu kann man da irgendwas dran erkennen?2024-03-04 14:50:52.843 - info: smartmeter.0 (1271) Received 19 values, 8 updated 2024-03-04 14:50:59.633 - info: smartmeter.1 (1281) Received 19 values, 10 updated 2024-03-04 14:31:15.741 - info: host.Raspberrypi iobroker.js-controller version 5.0.19 js-controller starting 2024-03-04 14:31:15.748 - info: host.Raspberrypi Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-03-04 14:31:15.749 - info: host.Raspberrypi hostname: Raspberrypi, node: v18.19.1 2024-03-04 14:31:15.750 - info: host.Raspberrypi ip addresses: fd00::c7f0:7c62:3e69:b975 fe80::6213:58b0:7758:34f6 2024-03-04 14:31:20.834 - info: host.Raspberrypi connected to Objects and States 2024-03-04 14:31:20.955 - info: host.Raspberrypi added notifications configuration of host 2024-03-04 14:31:22.401 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeCurrent" 2024-03-04 14:31:22.404 - info: host.Raspberrypi 61 instances found 2024-03-04 14:31:22.527 - info: host.Raspberrypi starting 42 instances 2024-03-04 14:31:22.789 - info: host.Raspberrypi instance system.adapter.admin.0 started with pid 930 2024-03-04 14:31:22.815 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeNewest" 2024-03-04 14:31:22.868 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeNewestNext" 2024-03-04 14:31:22.922 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmCurrent" 2024-03-04 14:31:22.977 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmNewest" 2024-03-04 14:31:23.029 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmNewestNext" 2024-03-04 14:31:23.080 - info: host.Raspberrypi Some obsolete host states deleted. 2024-03-04 14:31:26.368 - error: admin.0 (930) admin.0 already running 2024-03-04 14:31:26.372 - warn: admin.0 (930) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:26.720 - info: host.Raspberrypi instance system.adapter.javascript.0 started with pid 941 2024-03-04 14:31:27.169 - error: host.Raspberrypi instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:27.170 - info: host.Raspberrypi Restart adapter system.adapter.admin.0 because enabled 2024-03-04 14:31:30.725 - info: host.Raspberrypi instance system.adapter.pushover.0 started with pid 963 2024-03-04 14:31:31.150 - error: javascript.0 (941) javascript.0 already running 2024-03-04 14:31:31.154 - warn: javascript.0 (941) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:31.897 - error: host.Raspberrypi instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:31.898 - info: host.Raspberrypi Restart adapter system.adapter.javascript.0 because enabled 2024-03-04 14:31:33.149 - error: pushover.0 (963) pushover.0 already running 2024-03-04 14:31:33.155 - warn: pushover.0 (963) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:33.922 - error: host.Raspberrypi instance system.adapter.pushover.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:33.923 - info: host.Raspberrypi Restart adapter system.adapter.pushover.0 because enabled 2024-03-04 14:31:34.723 - info: host.Raspberrypi instance system.adapter.influxdb.0 started with pid 974 2024-03-04 14:58:15.470 - error: influxdb.0 (974) influxdb.0 already running 2024-03-04 14:58:15.474 - warn: influxdb.0 (974) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:16.168 - error: host.Raspberrypi instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:16.169 - info: host.Raspberrypi Restart adapter system.adapter.influxdb.0 because enabled 2024-03-04 14:58:16.770 - info: host.Raspberrypi instance system.adapter.backitup.0 started with pid 990 2024-03-04 14:58:19.145 - error: backitup.0 (990) backitup.0 already running 2024-03-04 14:58:19.149 - warn: backitup.0 (990) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:19.845 - error: host.Raspberrypi instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:19.846 - info: host.Raspberrypi Restart adapter system.adapter.backitup.0 because enabled 2024-03-04 14:58:20.766 - info: host.Raspberrypi instance system.adapter.alexa2.0 started with pid 1001 2024-03-04 14:58:23.177 - error: alexa2.0 (1001) alexa2.0 already running 2024-03-04 14:58:23.182 - warn: alexa2.0 (1001) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:23.873 - error: host.Raspberrypi instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:23.874 - info: host.Raspberrypi Restart adapter system.adapter.alexa2.0 because enabled 2024-03-04 14:58:24.770 - info: host.Raspberrypi instance system.adapter.hm-rega.0 started with pid 1014 2024-03-04 14:58:27.245 - error: hm-rega.0 (1014) hm-rega.0 already running 2024-03-04 14:58:27.250 - warn: hm-rega.0 (1014) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:27.946 - error: host.Raspberrypi instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:27.948 - info: host.Raspberrypi Restart adapter system.adapter.hm-rega.0 because enabled 2024-03-04 14:58:28.777 - info: host.Raspberrypi instance system.adapter.hm-rpc.0 started with pid 1025 2024-03-04 14:58:29.135 - info: host.Raspberrypi instance system.adapter.hm-rega.0 started with pid 1034 2024-03-04 14:58:31.626 - error: hm-rpc.0 (1025) hm-rpc.0 already running 2024-03-04 14:58:31.632 - warn: hm-rpc.0 (1025) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:32.368 - error: host.Raspberrypi instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:32.369 - info: host.Raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled 2024-03-04 14:58:32.769 - info: host.Raspberrypi instance system.adapter.hm-rpc.1 started with pid 1049 2024-03-04 14:58:32.859 - info: hm-rega.0 (1034) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.1, js-controller: 5.0.19 2024-03-04 14:58:33.674 - info: host.Raspberrypi instance system.adapter.hm-rpc.0 started with pid 1060 2024-03-04 14:58:33.736 - info: hm-rega.0 (1034) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT 2024-03-04 14:58:33.852 - info: hm-rega.0 (1034) ReGaHSS 192.168.10.19 up 2024-03-04 14:58:33.959 - info: hm-rega.0 (1034) time difference local-ccu 1s 2024-03-04 14:58:35.724 - info: host.Raspberrypi instance system.adapter.admin.0 started with pid 1075 2024-03-04 14:58:35.842 - error: hm-rpc.1 (1049) hm-rpc.1 already running 2024-03-04 14:58:35.849 - warn: hm-rpc.1 (1049) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:36.937 - error: host.Raspberrypi instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:36.938 - info: host.Raspberrypi Restart adapter system.adapter.hm-rpc.1 because enabled 2024-03-04 14:58:37.037 - info: host.Raspberrypi instance scheduled system.adapter.ical.0 0,30 * * * * 2024-03-04 14:58:37.044 - info: host.Raspberrypi instance system.adapter.ical.0 started with pid 1082 2024-03-04 14:58:38.222 - info: host.Raspberrypi instance system.adapter.hm-rpc.1 started with pid 1089 2024-03-04 14:58:38.440 - info: hm-rpc.0 (1060) starting. Version 1.16.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.1, js-controller: 5.0.19 2024-03-04 14:58:39.360 - info: hm-rpc.0 (1060) xmlrpc server is trying to listen on 192.168.10.13:2001 2024-03-04 14:58:39.362 - info: hm-rpc.0 (1060) xmlrpc client is trying to connect to 192.168.10.19:2001/ with ["http://192.168.10.13:2001","Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:39.523 - info: hm-rpc.0 (1060) xmlrpc <- system.listMethods ["Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:39.556 - info: hm-rpc.0 (1060) xmlrpc <- listDevices ["Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:40.021 - info: hm-rpc.0 (1060) xmlrpc -> 252 devices 2024-03-04 14:58:40.130 - info: hm-rpc.0 (1060) Connected 2024-03-04 14:58:40.486 - info: host.Raspberrypi instance system.adapter.javascript.0 started with pid 1108 2024-03-04 14:58:41.252 - info: host.Raspberrypi instance scheduled system.adapter.ical.1 0,30 * * * *Gruß
-
Hallo
Eben war ich am Skripte schreiben als er wieder abgestürzt ist.
Folgendes steht im Log, das steht da immer wenn er abstürzt.
Interessant sind die Zeiten...
Was sagt ihr dazu kann man da irgendwas dran erkennen?2024-03-04 14:50:52.843 - info: smartmeter.0 (1271) Received 19 values, 8 updated 2024-03-04 14:50:59.633 - info: smartmeter.1 (1281) Received 19 values, 10 updated 2024-03-04 14:31:15.741 - info: host.Raspberrypi iobroker.js-controller version 5.0.19 js-controller starting 2024-03-04 14:31:15.748 - info: host.Raspberrypi Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-03-04 14:31:15.749 - info: host.Raspberrypi hostname: Raspberrypi, node: v18.19.1 2024-03-04 14:31:15.750 - info: host.Raspberrypi ip addresses: fd00::c7f0:7c62:3e69:b975 fe80::6213:58b0:7758:34f6 2024-03-04 14:31:20.834 - info: host.Raspberrypi connected to Objects and States 2024-03-04 14:31:20.955 - info: host.Raspberrypi added notifications configuration of host 2024-03-04 14:31:22.401 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeCurrent" 2024-03-04 14:31:22.404 - info: host.Raspberrypi 61 instances found 2024-03-04 14:31:22.527 - info: host.Raspberrypi starting 42 instances 2024-03-04 14:31:22.789 - info: host.Raspberrypi instance system.adapter.admin.0 started with pid 930 2024-03-04 14:31:22.815 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeNewest" 2024-03-04 14:31:22.868 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeNewestNext" 2024-03-04 14:31:22.922 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmCurrent" 2024-03-04 14:31:22.977 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmNewest" 2024-03-04 14:31:23.029 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmNewestNext" 2024-03-04 14:31:23.080 - info: host.Raspberrypi Some obsolete host states deleted. 2024-03-04 14:31:26.368 - error: admin.0 (930) admin.0 already running 2024-03-04 14:31:26.372 - warn: admin.0 (930) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:26.720 - info: host.Raspberrypi instance system.adapter.javascript.0 started with pid 941 2024-03-04 14:31:27.169 - error: host.Raspberrypi instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:27.170 - info: host.Raspberrypi Restart adapter system.adapter.admin.0 because enabled 2024-03-04 14:31:30.725 - info: host.Raspberrypi instance system.adapter.pushover.0 started with pid 963 2024-03-04 14:31:31.150 - error: javascript.0 (941) javascript.0 already running 2024-03-04 14:31:31.154 - warn: javascript.0 (941) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:31.897 - error: host.Raspberrypi instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:31.898 - info: host.Raspberrypi Restart adapter system.adapter.javascript.0 because enabled 2024-03-04 14:31:33.149 - error: pushover.0 (963) pushover.0 already running 2024-03-04 14:31:33.155 - warn: pushover.0 (963) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:33.922 - error: host.Raspberrypi instance system.adapter.pushover.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:33.923 - info: host.Raspberrypi Restart adapter system.adapter.pushover.0 because enabled 2024-03-04 14:31:34.723 - info: host.Raspberrypi instance system.adapter.influxdb.0 started with pid 974 2024-03-04 14:58:15.470 - error: influxdb.0 (974) influxdb.0 already running 2024-03-04 14:58:15.474 - warn: influxdb.0 (974) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:16.168 - error: host.Raspberrypi instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:16.169 - info: host.Raspberrypi Restart adapter system.adapter.influxdb.0 because enabled 2024-03-04 14:58:16.770 - info: host.Raspberrypi instance system.adapter.backitup.0 started with pid 990 2024-03-04 14:58:19.145 - error: backitup.0 (990) backitup.0 already running 2024-03-04 14:58:19.149 - warn: backitup.0 (990) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:19.845 - error: host.Raspberrypi instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:19.846 - info: host.Raspberrypi Restart adapter system.adapter.backitup.0 because enabled 2024-03-04 14:58:20.766 - info: host.Raspberrypi instance system.adapter.alexa2.0 started with pid 1001 2024-03-04 14:58:23.177 - error: alexa2.0 (1001) alexa2.0 already running 2024-03-04 14:58:23.182 - warn: alexa2.0 (1001) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:23.873 - error: host.Raspberrypi instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:23.874 - info: host.Raspberrypi Restart adapter system.adapter.alexa2.0 because enabled 2024-03-04 14:58:24.770 - info: host.Raspberrypi instance system.adapter.hm-rega.0 started with pid 1014 2024-03-04 14:58:27.245 - error: hm-rega.0 (1014) hm-rega.0 already running 2024-03-04 14:58:27.250 - warn: hm-rega.0 (1014) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:27.946 - error: host.Raspberrypi instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:27.948 - info: host.Raspberrypi Restart adapter system.adapter.hm-rega.0 because enabled 2024-03-04 14:58:28.777 - info: host.Raspberrypi instance system.adapter.hm-rpc.0 started with pid 1025 2024-03-04 14:58:29.135 - info: host.Raspberrypi instance system.adapter.hm-rega.0 started with pid 1034 2024-03-04 14:58:31.626 - error: hm-rpc.0 (1025) hm-rpc.0 already running 2024-03-04 14:58:31.632 - warn: hm-rpc.0 (1025) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:32.368 - error: host.Raspberrypi instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:32.369 - info: host.Raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled 2024-03-04 14:58:32.769 - info: host.Raspberrypi instance system.adapter.hm-rpc.1 started with pid 1049 2024-03-04 14:58:32.859 - info: hm-rega.0 (1034) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.1, js-controller: 5.0.19 2024-03-04 14:58:33.674 - info: host.Raspberrypi instance system.adapter.hm-rpc.0 started with pid 1060 2024-03-04 14:58:33.736 - info: hm-rega.0 (1034) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT 2024-03-04 14:58:33.852 - info: hm-rega.0 (1034) ReGaHSS 192.168.10.19 up 2024-03-04 14:58:33.959 - info: hm-rega.0 (1034) time difference local-ccu 1s 2024-03-04 14:58:35.724 - info: host.Raspberrypi instance system.adapter.admin.0 started with pid 1075 2024-03-04 14:58:35.842 - error: hm-rpc.1 (1049) hm-rpc.1 already running 2024-03-04 14:58:35.849 - warn: hm-rpc.1 (1049) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:36.937 - error: host.Raspberrypi instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:36.938 - info: host.Raspberrypi Restart adapter system.adapter.hm-rpc.1 because enabled 2024-03-04 14:58:37.037 - info: host.Raspberrypi instance scheduled system.adapter.ical.0 0,30 * * * * 2024-03-04 14:58:37.044 - info: host.Raspberrypi instance system.adapter.ical.0 started with pid 1082 2024-03-04 14:58:38.222 - info: host.Raspberrypi instance system.adapter.hm-rpc.1 started with pid 1089 2024-03-04 14:58:38.440 - info: hm-rpc.0 (1060) starting. Version 1.16.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.1, js-controller: 5.0.19 2024-03-04 14:58:39.360 - info: hm-rpc.0 (1060) xmlrpc server is trying to listen on 192.168.10.13:2001 2024-03-04 14:58:39.362 - info: hm-rpc.0 (1060) xmlrpc client is trying to connect to 192.168.10.19:2001/ with ["http://192.168.10.13:2001","Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:39.523 - info: hm-rpc.0 (1060) xmlrpc <- system.listMethods ["Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:39.556 - info: hm-rpc.0 (1060) xmlrpc <- listDevices ["Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:40.021 - info: hm-rpc.0 (1060) xmlrpc -> 252 devices 2024-03-04 14:58:40.130 - info: hm-rpc.0 (1060) Connected 2024-03-04 14:58:40.486 - info: host.Raspberrypi instance system.adapter.javascript.0 started with pid 1108 2024-03-04 14:58:41.252 - info: host.Raspberrypi instance scheduled system.adapter.ical.1 0,30 * * * *Gruß
@g-hawk sagte in Absturz jede Woche beheben:
Interessant sind die Zeiten...
das ist das log beim Neustart, leider nicht von davor. Das müsste aber als Datei vorliegen.
Die Zeiten scheinen daher zu rühren, dass es etwas dauert, bis der Raspi sich wieder mit dem ntp-Server synchronisiert.
-
Hallo
Eben war ich am Skripte schreiben als er wieder abgestürzt ist.
Folgendes steht im Log, das steht da immer wenn er abstürzt.
Interessant sind die Zeiten...
Was sagt ihr dazu kann man da irgendwas dran erkennen?2024-03-04 14:50:52.843 - info: smartmeter.0 (1271) Received 19 values, 8 updated 2024-03-04 14:50:59.633 - info: smartmeter.1 (1281) Received 19 values, 10 updated 2024-03-04 14:31:15.741 - info: host.Raspberrypi iobroker.js-controller version 5.0.19 js-controller starting 2024-03-04 14:31:15.748 - info: host.Raspberrypi Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-03-04 14:31:15.749 - info: host.Raspberrypi hostname: Raspberrypi, node: v18.19.1 2024-03-04 14:31:15.750 - info: host.Raspberrypi ip addresses: fd00::c7f0:7c62:3e69:b975 fe80::6213:58b0:7758:34f6 2024-03-04 14:31:20.834 - info: host.Raspberrypi connected to Objects and States 2024-03-04 14:31:20.955 - info: host.Raspberrypi added notifications configuration of host 2024-03-04 14:31:22.401 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeCurrent" 2024-03-04 14:31:22.404 - info: host.Raspberrypi 61 instances found 2024-03-04 14:31:22.527 - info: host.Raspberrypi starting 42 instances 2024-03-04 14:31:22.789 - info: host.Raspberrypi instance system.adapter.admin.0 started with pid 930 2024-03-04 14:31:22.815 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeNewest" 2024-03-04 14:31:22.868 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeNewestNext" 2024-03-04 14:31:22.922 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmCurrent" 2024-03-04 14:31:22.977 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmNewest" 2024-03-04 14:31:23.029 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmNewestNext" 2024-03-04 14:31:23.080 - info: host.Raspberrypi Some obsolete host states deleted. 2024-03-04 14:31:26.368 - error: admin.0 (930) admin.0 already running 2024-03-04 14:31:26.372 - warn: admin.0 (930) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:26.720 - info: host.Raspberrypi instance system.adapter.javascript.0 started with pid 941 2024-03-04 14:31:27.169 - error: host.Raspberrypi instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:27.170 - info: host.Raspberrypi Restart adapter system.adapter.admin.0 because enabled 2024-03-04 14:31:30.725 - info: host.Raspberrypi instance system.adapter.pushover.0 started with pid 963 2024-03-04 14:31:31.150 - error: javascript.0 (941) javascript.0 already running 2024-03-04 14:31:31.154 - warn: javascript.0 (941) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:31.897 - error: host.Raspberrypi instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:31.898 - info: host.Raspberrypi Restart adapter system.adapter.javascript.0 because enabled 2024-03-04 14:31:33.149 - error: pushover.0 (963) pushover.0 already running 2024-03-04 14:31:33.155 - warn: pushover.0 (963) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:33.922 - error: host.Raspberrypi instance system.adapter.pushover.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:33.923 - info: host.Raspberrypi Restart adapter system.adapter.pushover.0 because enabled 2024-03-04 14:31:34.723 - info: host.Raspberrypi instance system.adapter.influxdb.0 started with pid 974 2024-03-04 14:58:15.470 - error: influxdb.0 (974) influxdb.0 already running 2024-03-04 14:58:15.474 - warn: influxdb.0 (974) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:16.168 - error: host.Raspberrypi instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:16.169 - info: host.Raspberrypi Restart adapter system.adapter.influxdb.0 because enabled 2024-03-04 14:58:16.770 - info: host.Raspberrypi instance system.adapter.backitup.0 started with pid 990 2024-03-04 14:58:19.145 - error: backitup.0 (990) backitup.0 already running 2024-03-04 14:58:19.149 - warn: backitup.0 (990) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:19.845 - error: host.Raspberrypi instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:19.846 - info: host.Raspberrypi Restart adapter system.adapter.backitup.0 because enabled 2024-03-04 14:58:20.766 - info: host.Raspberrypi instance system.adapter.alexa2.0 started with pid 1001 2024-03-04 14:58:23.177 - error: alexa2.0 (1001) alexa2.0 already running 2024-03-04 14:58:23.182 - warn: alexa2.0 (1001) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:23.873 - error: host.Raspberrypi instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:23.874 - info: host.Raspberrypi Restart adapter system.adapter.alexa2.0 because enabled 2024-03-04 14:58:24.770 - info: host.Raspberrypi instance system.adapter.hm-rega.0 started with pid 1014 2024-03-04 14:58:27.245 - error: hm-rega.0 (1014) hm-rega.0 already running 2024-03-04 14:58:27.250 - warn: hm-rega.0 (1014) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:27.946 - error: host.Raspberrypi instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:27.948 - info: host.Raspberrypi Restart adapter system.adapter.hm-rega.0 because enabled 2024-03-04 14:58:28.777 - info: host.Raspberrypi instance system.adapter.hm-rpc.0 started with pid 1025 2024-03-04 14:58:29.135 - info: host.Raspberrypi instance system.adapter.hm-rega.0 started with pid 1034 2024-03-04 14:58:31.626 - error: hm-rpc.0 (1025) hm-rpc.0 already running 2024-03-04 14:58:31.632 - warn: hm-rpc.0 (1025) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:32.368 - error: host.Raspberrypi instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:32.369 - info: host.Raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled 2024-03-04 14:58:32.769 - info: host.Raspberrypi instance system.adapter.hm-rpc.1 started with pid 1049 2024-03-04 14:58:32.859 - info: hm-rega.0 (1034) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.1, js-controller: 5.0.19 2024-03-04 14:58:33.674 - info: host.Raspberrypi instance system.adapter.hm-rpc.0 started with pid 1060 2024-03-04 14:58:33.736 - info: hm-rega.0 (1034) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT 2024-03-04 14:58:33.852 - info: hm-rega.0 (1034) ReGaHSS 192.168.10.19 up 2024-03-04 14:58:33.959 - info: hm-rega.0 (1034) time difference local-ccu 1s 2024-03-04 14:58:35.724 - info: host.Raspberrypi instance system.adapter.admin.0 started with pid 1075 2024-03-04 14:58:35.842 - error: hm-rpc.1 (1049) hm-rpc.1 already running 2024-03-04 14:58:35.849 - warn: hm-rpc.1 (1049) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:36.937 - error: host.Raspberrypi instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:36.938 - info: host.Raspberrypi Restart adapter system.adapter.hm-rpc.1 because enabled 2024-03-04 14:58:37.037 - info: host.Raspberrypi instance scheduled system.adapter.ical.0 0,30 * * * * 2024-03-04 14:58:37.044 - info: host.Raspberrypi instance system.adapter.ical.0 started with pid 1082 2024-03-04 14:58:38.222 - info: host.Raspberrypi instance system.adapter.hm-rpc.1 started with pid 1089 2024-03-04 14:58:38.440 - info: hm-rpc.0 (1060) starting. Version 1.16.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.1, js-controller: 5.0.19 2024-03-04 14:58:39.360 - info: hm-rpc.0 (1060) xmlrpc server is trying to listen on 192.168.10.13:2001 2024-03-04 14:58:39.362 - info: hm-rpc.0 (1060) xmlrpc client is trying to connect to 192.168.10.19:2001/ with ["http://192.168.10.13:2001","Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:39.523 - info: hm-rpc.0 (1060) xmlrpc <- system.listMethods ["Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:39.556 - info: hm-rpc.0 (1060) xmlrpc <- listDevices ["Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:40.021 - info: hm-rpc.0 (1060) xmlrpc -> 252 devices 2024-03-04 14:58:40.130 - info: hm-rpc.0 (1060) Connected 2024-03-04 14:58:40.486 - info: host.Raspberrypi instance system.adapter.javascript.0 started with pid 1108 2024-03-04 14:58:41.252 - info: host.Raspberrypi instance scheduled system.adapter.ical.1 0,30 * * * *Gruß
@g-hawk
starting 42 instancesKönnte auch etwas zu viel sein.
-
Hallo
Eben war ich am Skripte schreiben als er wieder abgestürzt ist.
Folgendes steht im Log, das steht da immer wenn er abstürzt.
Interessant sind die Zeiten...
Was sagt ihr dazu kann man da irgendwas dran erkennen?2024-03-04 14:50:52.843 - info: smartmeter.0 (1271) Received 19 values, 8 updated 2024-03-04 14:50:59.633 - info: smartmeter.1 (1281) Received 19 values, 10 updated 2024-03-04 14:31:15.741 - info: host.Raspberrypi iobroker.js-controller version 5.0.19 js-controller starting 2024-03-04 14:31:15.748 - info: host.Raspberrypi Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-03-04 14:31:15.749 - info: host.Raspberrypi hostname: Raspberrypi, node: v18.19.1 2024-03-04 14:31:15.750 - info: host.Raspberrypi ip addresses: fd00::c7f0:7c62:3e69:b975 fe80::6213:58b0:7758:34f6 2024-03-04 14:31:20.834 - info: host.Raspberrypi connected to Objects and States 2024-03-04 14:31:20.955 - info: host.Raspberrypi added notifications configuration of host 2024-03-04 14:31:22.401 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeCurrent" 2024-03-04 14:31:22.404 - info: host.Raspberrypi 61 instances found 2024-03-04 14:31:22.527 - info: host.Raspberrypi starting 42 instances 2024-03-04 14:31:22.789 - info: host.Raspberrypi instance system.adapter.admin.0 started with pid 930 2024-03-04 14:31:22.815 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeNewest" 2024-03-04 14:31:22.868 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.nodeNewestNext" 2024-03-04 14:31:22.922 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmCurrent" 2024-03-04 14:31:22.977 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmNewest" 2024-03-04 14:31:23.029 - info: host.Raspberrypi Delete state "system.host.Raspberrypi.versions.npmNewestNext" 2024-03-04 14:31:23.080 - info: host.Raspberrypi Some obsolete host states deleted. 2024-03-04 14:31:26.368 - error: admin.0 (930) admin.0 already running 2024-03-04 14:31:26.372 - warn: admin.0 (930) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:26.720 - info: host.Raspberrypi instance system.adapter.javascript.0 started with pid 941 2024-03-04 14:31:27.169 - error: host.Raspberrypi instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:27.170 - info: host.Raspberrypi Restart adapter system.adapter.admin.0 because enabled 2024-03-04 14:31:30.725 - info: host.Raspberrypi instance system.adapter.pushover.0 started with pid 963 2024-03-04 14:31:31.150 - error: javascript.0 (941) javascript.0 already running 2024-03-04 14:31:31.154 - warn: javascript.0 (941) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:31.897 - error: host.Raspberrypi instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:31.898 - info: host.Raspberrypi Restart adapter system.adapter.javascript.0 because enabled 2024-03-04 14:31:33.149 - error: pushover.0 (963) pushover.0 already running 2024-03-04 14:31:33.155 - warn: pushover.0 (963) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:31:33.922 - error: host.Raspberrypi instance system.adapter.pushover.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:31:33.923 - info: host.Raspberrypi Restart adapter system.adapter.pushover.0 because enabled 2024-03-04 14:31:34.723 - info: host.Raspberrypi instance system.adapter.influxdb.0 started with pid 974 2024-03-04 14:58:15.470 - error: influxdb.0 (974) influxdb.0 already running 2024-03-04 14:58:15.474 - warn: influxdb.0 (974) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:16.168 - error: host.Raspberrypi instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:16.169 - info: host.Raspberrypi Restart adapter system.adapter.influxdb.0 because enabled 2024-03-04 14:58:16.770 - info: host.Raspberrypi instance system.adapter.backitup.0 started with pid 990 2024-03-04 14:58:19.145 - error: backitup.0 (990) backitup.0 already running 2024-03-04 14:58:19.149 - warn: backitup.0 (990) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:19.845 - error: host.Raspberrypi instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:19.846 - info: host.Raspberrypi Restart adapter system.adapter.backitup.0 because enabled 2024-03-04 14:58:20.766 - info: host.Raspberrypi instance system.adapter.alexa2.0 started with pid 1001 2024-03-04 14:58:23.177 - error: alexa2.0 (1001) alexa2.0 already running 2024-03-04 14:58:23.182 - warn: alexa2.0 (1001) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:23.873 - error: host.Raspberrypi instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:23.874 - info: host.Raspberrypi Restart adapter system.adapter.alexa2.0 because enabled 2024-03-04 14:58:24.770 - info: host.Raspberrypi instance system.adapter.hm-rega.0 started with pid 1014 2024-03-04 14:58:27.245 - error: hm-rega.0 (1014) hm-rega.0 already running 2024-03-04 14:58:27.250 - warn: hm-rega.0 (1014) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:27.946 - error: host.Raspberrypi instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:27.948 - info: host.Raspberrypi Restart adapter system.adapter.hm-rega.0 because enabled 2024-03-04 14:58:28.777 - info: host.Raspberrypi instance system.adapter.hm-rpc.0 started with pid 1025 2024-03-04 14:58:29.135 - info: host.Raspberrypi instance system.adapter.hm-rega.0 started with pid 1034 2024-03-04 14:58:31.626 - error: hm-rpc.0 (1025) hm-rpc.0 already running 2024-03-04 14:58:31.632 - warn: hm-rpc.0 (1025) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:32.368 - error: host.Raspberrypi instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:32.369 - info: host.Raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled 2024-03-04 14:58:32.769 - info: host.Raspberrypi instance system.adapter.hm-rpc.1 started with pid 1049 2024-03-04 14:58:32.859 - info: hm-rega.0 (1034) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.1, js-controller: 5.0.19 2024-03-04 14:58:33.674 - info: host.Raspberrypi instance system.adapter.hm-rpc.0 started with pid 1060 2024-03-04 14:58:33.736 - info: hm-rega.0 (1034) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT 2024-03-04 14:58:33.852 - info: hm-rega.0 (1034) ReGaHSS 192.168.10.19 up 2024-03-04 14:58:33.959 - info: hm-rega.0 (1034) time difference local-ccu 1s 2024-03-04 14:58:35.724 - info: host.Raspberrypi instance system.adapter.admin.0 started with pid 1075 2024-03-04 14:58:35.842 - error: hm-rpc.1 (1049) hm-rpc.1 already running 2024-03-04 14:58:35.849 - warn: hm-rpc.1 (1049) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2024-03-04 14:58:36.937 - error: host.Raspberrypi instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2024-03-04 14:58:36.938 - info: host.Raspberrypi Restart adapter system.adapter.hm-rpc.1 because enabled 2024-03-04 14:58:37.037 - info: host.Raspberrypi instance scheduled system.adapter.ical.0 0,30 * * * * 2024-03-04 14:58:37.044 - info: host.Raspberrypi instance system.adapter.ical.0 started with pid 1082 2024-03-04 14:58:38.222 - info: host.Raspberrypi instance system.adapter.hm-rpc.1 started with pid 1089 2024-03-04 14:58:38.440 - info: hm-rpc.0 (1060) starting. Version 1.16.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.1, js-controller: 5.0.19 2024-03-04 14:58:39.360 - info: hm-rpc.0 (1060) xmlrpc server is trying to listen on 192.168.10.13:2001 2024-03-04 14:58:39.362 - info: hm-rpc.0 (1060) xmlrpc client is trying to connect to 192.168.10.19:2001/ with ["http://192.168.10.13:2001","Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:39.523 - info: hm-rpc.0 (1060) xmlrpc <- system.listMethods ["Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:39.556 - info: hm-rpc.0 (1060) xmlrpc <- listDevices ["Raspberrypi:hm-rpc.0:5328f3ff804d13e23c227f6c4373fef7"] 2024-03-04 14:58:40.021 - info: hm-rpc.0 (1060) xmlrpc -> 252 devices 2024-03-04 14:58:40.130 - info: hm-rpc.0 (1060) Connected 2024-03-04 14:58:40.486 - info: host.Raspberrypi instance system.adapter.javascript.0 started with pid 1108 2024-03-04 14:58:41.252 - info: host.Raspberrypi instance scheduled system.adapter.ical.1 0,30 * * * *Gruß
-
@g-hawk hab jetzt beim durscrollen erst mitbekommen.
RP4 mit proxmox auf einer 32er Karte?
Sorry... Da wundert mich nichts.@da_woody sagte in Absturz jede Woche beheben:
mit proxmox
das hab ich nicht gelesen.
Warum hackt ihr auf der 32GB Karte rum?
Solange die nicht voll ist, ist das ok
kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@da_woody sagte in Absturz jede Woche beheben:
mit proxmox
das hab ich nicht gelesen.
Warum hackt ihr auf der 32GB Karte rum?
Solange die nicht voll ist, ist das ok
-
@da_woody sagte in Absturz jede Woche beheben:
mit proxmox
das hab ich nicht gelesen.
Warum hackt ihr auf der 32GB Karte rum?
Solange die nicht voll ist, ist das ok
@homoran sagte in Absturz jede Woche beheben:
das hab ich nicht gelesen.
Kannste auch nicht gelesen haben, ist nämlich kein virtuelles System.
Solange die nicht voll ist, ist das ok
Aber auf dem Weg dorthin. 80% ist gut gefüllt.
-
@g-hawk
starting 42 instancesKönnte auch etwas zu viel sein.
@thomas-braun
Wieviel Instanzen kann der denn vertragen?
Wäre vielleicht ein PI5 8 GB mit m2 eine Alternative?
Ich dachte eigentlich immer ich habe es gar nicht so übertrieben.
Ich habe ca 40 Instanzen, 25000 Objekte und ca. 200 Skripte und eine recht umfangreiche VIS.
Ist das zuviel für den PI 4 mit 4GB?Gruß
-
@thomas-braun
Wieviel Instanzen kann der denn vertragen?
Wäre vielleicht ein PI5 8 GB mit m2 eine Alternative?
Ich dachte eigentlich immer ich habe es gar nicht so übertrieben.
Ich habe ca 40 Instanzen, 25000 Objekte und ca. 200 Skripte und eine recht umfangreiche VIS.
Ist das zuviel für den PI 4 mit 4GB?Gruß
@g-hawk sagte in Absturz jede Woche beheben:
Ich habe ca 40 Instanzen
@g-hawk sagte in Absturz jede Woche beheben:
Ist das zuviel für den PI 4 mit 4GB
Ja - grenzwertig ;)
-
@thomas-braun
Wieviel Instanzen kann der denn vertragen?
Wäre vielleicht ein PI5 8 GB mit m2 eine Alternative?
Ich dachte eigentlich immer ich habe es gar nicht so übertrieben.
Ich habe ca 40 Instanzen, 25000 Objekte und ca. 200 Skripte und eine recht umfangreiche VIS.
Ist das zuviel für den PI 4 mit 4GB?Gruß
@g-hawk sagte in Absturz jede Woche beheben:
Ist das zuviel für den PI 4 mit 4GB?
Joh.
Alleine die 40 Adapter kannst du mit je 80 - 100 MB veranschlagen. Damit biste also damit schon an der Grenze.
Dann braucht das OS noch ein wenig usw.
Wenn dann was läuft, was nochmal richtig RAM frisst (Backup z. B.) ist dann Schicht im Schacht. -
@g-hawk sagte in Absturz jede Woche beheben:
Ist das zuviel für den PI 4 mit 4GB?
Joh.
Alleine die 40 Adapter kannst du mit je 80 - 100 MB veranschlagen. Damit biste also damit schon an der Grenze.
Dann braucht das OS noch ein wenig usw.
Wenn dann was läuft, was nochmal richtig RAM frisst (Backup z. B.) ist dann Schicht im Schacht.@thomas-braun
Das komische ist nur dass es eine Woche lang gut geht und dann auf einmal nicht mehr.
Was wäre denn eine Alternative mit mehr Leistung? -
@thomas-braun
Das komische ist nur dass es eine Woche lang gut geht und dann auf einmal nicht mehr.
Was wäre denn eine Alternative mit mehr Leistung?@g-hawk sagte in Absturz jede Woche beheben:
@thomas-braun
Das komische ist nur dass es eine Woche lang gut geht und dann auf einmal nicht mehr.
Was wäre denn eine Alternative mit mehr Leistung?Na ja, ein Raspberrypi 4B mit 8G oder ein 5er mit 8G oder ein MiniPC mit Proxmox. Such dir was aus :man-shrugging: .
-
@thomas-braun
Das komische ist nur dass es eine Woche lang gut geht und dann auf einmal nicht mehr.
Was wäre denn eine Alternative mit mehr Leistung?@g-hawk sagte in Absturz jede Woche beheben:
Das komische ist nur dass es eine Woche lang gut geht und dann auf einmal nicht mehr.
Dann kippt dir das halt nach einer Woche um.
-
@g-hawk sagte in Absturz jede Woche beheben:
Das komische ist nur dass es eine Woche lang gut geht und dann auf einmal nicht mehr.
Dann kippt dir das halt nach einer Woche um.
Ich habe jetzt mal einen Test gemacht und alles neu gemacht.
Alles läuft so weit und die SD Karte ist nur noch zu 18% gefüllt.Ich habe nur ein Problem die Influxdb Datenbank wiederherzustellen.
Ich habe ein Backup von Influx über den Backitup Adapter beim Restore vom folgendes:
Started restore ... [DEBUG] [influxDB] - Created tmp directory [DEBUG] [influxDB] - Start infuxDB Restore ... [DEBUG] [influxDB] - influxdb.0 is stopped [ERROR] [influxDB] - Error: failed to check existence of organization "G.Hawk": 401 Unauthorized: unauthorized access [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory [DEBUG] [influxDB] - InfluxDB tmp directory was successfully deleted [DEBUG] [influxDB] - infuxDB Restore completed successfully [EXIT] influxDB restore done [DEBUG] [influxDB] - influxdb.0 startedKann mir jemand sagen, wie ich das Backup wieder einspiele?
Gruß G.Hawk
-
Ich habe jetzt mal einen Test gemacht und alles neu gemacht.
Alles läuft so weit und die SD Karte ist nur noch zu 18% gefüllt.Ich habe nur ein Problem die Influxdb Datenbank wiederherzustellen.
Ich habe ein Backup von Influx über den Backitup Adapter beim Restore vom folgendes:
Started restore ... [DEBUG] [influxDB] - Created tmp directory [DEBUG] [influxDB] - Start infuxDB Restore ... [DEBUG] [influxDB] - influxdb.0 is stopped [ERROR] [influxDB] - Error: failed to check existence of organization "G.Hawk": 401 Unauthorized: unauthorized access [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory [DEBUG] [influxDB] - InfluxDB tmp directory was successfully deleted [DEBUG] [influxDB] - infuxDB Restore completed successfully [EXIT] influxDB restore done [DEBUG] [influxDB] - influxdb.0 startedKann mir jemand sagen, wie ich das Backup wieder einspiele?
Gruß G.Hawk
816
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge