NEWS
[gelöst] pivccu3 3.71.12 und nodejs 18.x
ioBroker Allgemein
148
Beiträge
7
Kommentatoren
22.9k
Aufrufe
3
Watching
-
Die Abstürze bleiben leider ein Thema und sind seit den Update auf nodejs18 auch sehr stark geworden. Ich habe jetzt jeden Morgen das Tinker Board neu starten müssen. Ich habe auch beide Boards S und ohne S laufen lassen, beide stürzen ab.
Zum Zeitpunkt des Absturzes war aber genügend freier Speicher vorhanden.
Um 7:36 hab es den letzten Eintrag mit dem freien Speicher, um 8:59 habe ich neu gestartet. Hier ist das Log mit etwas Vorlauf. Vorher gibt es aber ausschließlich gelbe warnungen vom alexa2 Adapter.
Bitte schaut mal auf 2 Sachen:
- Die Zeitstempel Es fängt mit 7:17 an lauft bis 7:34 und dann kommt wieder 7:17 Dann kommt ein Neustart wie es aussieht, dann Einträge aus der Zukunft.
- Die ERROR Meldungen - Ich habe um 8:59 neu gestartet und da laufen die Adapter alle und verursachen eine Fehlermeldung. Aber das kann ja ein gespeicherter Status auf der SD sein weil das System ja nicht weiß das es weg war ...
Aber woher kommt der Neustart um 7:17 der zum Stillstand führt ?
2023-10-02 07:17:58.448 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.online" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.496 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.capabilities" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.540 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.softwareVersion" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.586 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.isMultiroomDevice" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.632 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.multiroomMembers" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.676 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.isMultiroomMember" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.720 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceType" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.768 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceTypeString" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.816 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.serialNumber" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.860 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.name" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.904 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceFamily" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:58.961 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Preferences.connectedSpeaker" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:20.782 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.online" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:20.794 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.capabilities" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:20.840 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.softwareVersion" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:20.914 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.isMultiroomDevice" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:20.964 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.multiroomMembers" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:21.008 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.isMultiroomMember" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:21.052 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceType" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:21.096 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceTypeString" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:21.140 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.serialNumber" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:21.184 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.name" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:21.228 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceFamily" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:21.273 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Preferences.connectedSpeaker" has no existing object, this might lead to an error in future versions 2023-10-02 07:23:36.913 - warn: controme.0 (3271) State "controme.0.10.sensors.VSensor*2.actualTemperature" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.204 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.online" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.381 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.capabilities" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.430 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.softwareVersion" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.476 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.isMultiroomDevice" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.520 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.multiroomMembers" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.540 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.isMultiroomMember" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.546 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceType" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.556 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceTypeString" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.592 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.serialNumber" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.601 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.name" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.608 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceFamily" has no existing object, this might lead to an error in future versions 2023-10-02 07:28:42.614 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Preferences.connectedSpeaker" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.308 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.online" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.357 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.capabilities" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.423 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.softwareVersion" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.469 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.isMultiroomDevice" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.543 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.multiroomMembers" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.598 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.isMultiroomMember" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.648 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceType" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.699 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceTypeString" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.748 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.serialNumber" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.803 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.name" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.840 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Info.deviceFamily" has no existing object, this might lead to an error in future versions 2023-10-02 07:34:03.852 - warn: alexa2.0 (3035) State "alexa2.0.Echo-Devices.746cf09ab16f4f78aadb5d83807d50ac.Preferences.connectedSpeaker" has no existing object, this might lead to an error in future versions 2023-10-02 07:17:16.655 - info: host.ioBroker iobroker.js-controller version 5.0.12 js-controller starting 2023-10-02 07:17:16.662 - info: host.ioBroker Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2023-10-02 07:17:16.663 - info: host.ioBroker hostname: ioBroker, node: v18.18.0 2023-10-02 07:17:16.663 - info: host.ioBroker ip addresses: 2023-10-02 07:17:22.948 - info: host.ioBroker connected to Objects and States 2023-10-02 07:17:23.069 - info: host.ioBroker added notifications configuration of host 2023-10-02 07:17:25.115 - info: host.ioBroker Delete state "system.host.ioBroker.versions.nodeCurrent" 2023-10-02 07:17:25.117 - info: host.ioBroker 40 instances found 2023-10-02 07:17:25.223 - info: host.ioBroker starting 28 instances 2023-10-02 07:17:25.827 - info: host.ioBroker Delete state "system.host.ioBroker.versions.nodeNewest" 2023-10-02 07:17:25.843 - info: host.ioBroker Delete state "system.host.ioBroker.versions.nodeNewestNext" 2023-10-02 07:17:25.921 - info: host.ioBroker instance system.adapter.admin.0 started with pid 1966 2023-10-02 07:17:25.930 - info: host.ioBroker Delete state "system.host.ioBroker.versions.npmCurrent" 2023-10-02 07:17:25.981 - info: host.ioBroker Delete state "system.host.ioBroker.versions.npmNewest" 2023-10-02 07:17:26.033 - info: host.ioBroker Delete state "system.host.ioBroker.versions.npmNewestNext" 2023-10-02 07:17:26.084 - info: host.ioBroker Some obsolete host states deleted. 2023-10-02 07:17:30.025 - info: host.ioBroker instance system.adapter.javascript.0 started with pid 1981 2023-10-02 07:17:34.204 - error: admin.0 (1966) admin.0 already running 2023-10-02 07:17:34.209 - warn: admin.0 (1966) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 07:17:34.288 - info: host.ioBroker instance system.adapter.sql.0 started with pid 1996 2023-10-02 07:17:35.617 - error: host.ioBroker instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 07:17:35.618 - info: host.ioBroker Restart adapter system.adapter.admin.0 because enabled 2023-10-02 07:17:38.653 - info: host.ioBroker instance system.adapter.telegram.0 started with pid 2081 2023-10-02 07:17:43.647 - info: host.ioBroker instance system.adapter.alexa2.0 started with pid 2191 2023-10-02 07:17:44.679 - error: javascript.0 (1981) javascript.0 already running 2023-10-02 07:17:44.694 - warn: javascript.0 (1981) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 07:17:47.201 - error: sql.0 (1996) sql.0 already running 2023-10-02 07:17:47.214 - warn: sql.0 (1996) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 07:17:47.274 - info: host.ioBroker instance system.adapter.geofency.0 started with pid 2288 2023-10-02 07:17:48.561 - error: host.ioBroker instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 07:17:48.562 - info: host.ioBroker Restart adapter system.adapter.javascript.0 because enabled 2023-10-02 10:32:48.547 - error: host.ioBroker instance system.adapter.sql.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 10:32:48.552 - info: host.ioBroker Restart adapter system.adapter.sql.0 because enabled 2023-10-02 10:32:52.469 - info: host.ioBroker instance system.adapter.hm-rega.0 started with pid 2465 2023-10-02 08:55:29.672 - warn: telegram.0 (2081) slow connection to states DB. Still waiting ... 2023-10-02 08:55:33.267 - info: host.ioBroker instance system.adapter.hm-rpc.0 started with pid 2537 2023-10-02 08:55:33.571 - warn: alexa2.0 (2191) slow connection to states DB. Still waiting ... 2023-10-02 08:55:36.735 - error: telegram.0 (2081) telegram.0 already running 2023-10-02 08:55:36.743 - warn: telegram.0 (2081) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:55:37.475 - warn: geofency.0 (2288) slow connection to states DB. Still waiting ... 2023-10-02 08:55:37.653 - info: host.ioBroker instance system.adapter.melcloud.0 started with pid 2557 2023-10-02 08:55:40.475 - error: alexa2.0 (2191) alexa2.0 already running 2023-10-02 08:55:40.477 - warn: alexa2.0 (2191) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:55:42.662 - warn: hm-rega.0 (2465) slow connection to objects DB. Still waiting ... 2023-10-02 08:55:42.693 - info: host.ioBroker instance system.adapter.nuki-extended.0 started with pid 2604 2023-10-02 08:55:45.348 - error: geofency.0 (2288) geofency.0 already running 2023-10-02 08:55:45.351 - warn: geofency.0 (2288) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:55:49.271 - info: host.ioBroker instance system.adapter.admin.0 started with pid 2665 2023-10-02 08:55:49.594 - info: host.ioBroker instance system.adapter.tr-064.0 started with pid 2670 2023-10-02 08:55:50.612 - warn: hm-rpc.0 (2537) slow connection to objects DB. Still waiting ... 2023-10-02 08:55:50.515 - error: host.ioBroker instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:55:50.516 - info: host.ioBroker Restart adapter system.adapter.telegram.0 because enabled 2023-10-02 08:55:57.861 - warn: melcloud.0 (2557) slow connection to objects DB. Still waiting ... 2023-10-02 08:56:00.342 - warn: hm-rega.0 (2465) slow connection to states DB. Still waiting ... 2023-10-02 08:56:00.887 - error: host.ioBroker instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:56:00.910 - info: host.ioBroker Restart adapter system.adapter.alexa2.0 because enabled 2023-10-02 08:56:06.095 - info: host.ioBroker instance system.adapter.backitup.0 started with pid 2809 2023-10-02 08:56:10.930 - warn: nuki-extended.0 (2604) slow connection to objects DB. Still waiting ... 2023-10-02 08:56:15.534 - warn: admin.0 (2665) slow connection to objects DB. Still waiting ... 2023-10-02 08:56:15.855 - info: host.ioBroker instance system.adapter.controme.0 started with pid 2823 2023-10-02 08:56:16.194 - warn: tr-064.0 (2670) slow connection to objects DB. Still waiting ... 2023-10-02 08:56:16.799 - error: host.ioBroker instance system.adapter.geofency.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:56:16.800 - info: host.ioBroker Restart adapter system.adapter.geofency.0 because enabled 2023-10-02 08:56:18.154 - warn: hm-rpc.0 (2537) slow connection to states DB. Still waiting ... 2023-10-02 08:56:25.290 - info: host.ioBroker instance system.adapter.hue-extended.0 started with pid 2836 2023-10-02 08:56:26.097 - warn: backitup.0 (2809) slow connection to objects DB. Still waiting ... 2023-10-02 08:56:25.507 - info: host.ioBroker instance system.adapter.discovery.0 started with pid 2837 2023-10-02 08:56:37.514 - warn: controme.0 (2823) slow connection to objects DB. Still waiting ... 2023-10-02 08:56:39.186 - info: host.ioBroker instance system.adapter.javascript.0 started with pid 2862 2023-10-02 08:56:39.513 - error: hm-rega.0 (2465) hm-rega.0 already running 2023-10-02 08:56:39.517 - warn: hm-rega.0 (2465) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:56:39.897 - info: host.ioBroker instance system.adapter.homepilot20.0 started with pid 2871 2023-10-02 08:56:42.091 - info: host.ioBroker instance system.adapter.sql.0 started with pid 2883 2023-10-02 08:56:42.955 - warn: melcloud.0 (2557) slow connection to states DB. Still waiting ... 2023-10-02 08:56:49.486 - warn: discovery.0 (2837) slow connection to objects DB. Still waiting ... 2023-10-02 08:56:52.254 - warn: hue-extended.0 (2836) slow connection to objects DB. Still waiting ... 2023-10-02 08:56:52.549 - info: host.ioBroker instance system.adapter.info.0 started with pid 2898 2023-10-02 08:57:01.779 - info: host.ioBroker instance system.adapter.iot.0 started with pid 2911 2023-10-02 08:57:06.964 - warn: nuki-extended.0 (2604) slow connection to states DB. Still waiting ... 2023-10-02 08:57:11.090 - warn: homepilot20.0 (2871) slow connection to objects DB. Still waiting ... 2023-10-02 08:57:12.458 - warn: sql.0 (2883) slow connection to objects DB. Still waiting ... 2023-10-02 08:57:20.727 - error: hm-rpc.0 (2537) hm-rpc.0 already running 2023-10-02 08:57:20.730 - warn: hm-rpc.0 (2537) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:57:23.686 - warn: javascript.0 (2862) slow connection to objects DB. Still waiting ... 2023-10-02 08:57:23.787 - info: host.ioBroker instance system.adapter.jarvis.0 started with pid 2941 2023-10-02 08:57:25.856 - warn: tr-064.0 (2670) slow connection to states DB. Still waiting ... 2023-10-02 08:57:25.897 - warn: admin.0 (2665) slow connection to states DB. Still waiting ... 2023-10-02 08:57:32.827 - info: host.ioBroker instance system.adapter.statistics.0 started with pid 2957 2023-10-02 08:57:33.108 - info: host.ioBroker instance system.adapter.mercedesme.0 started with pid 2958 2023-10-02 08:57:35.947 - info: host.ioBroker instance system.adapter.tinker.0 started with pid 2977 2023-10-02 08:57:40.505 - warn: iot.0 (2911) slow connection to objects DB. Still waiting ... 2023-10-02 08:57:42.948 - warn: info.0 (2898) slow connection to objects DB. Still waiting ... 2023-10-02 08:57:51.226 - warn: backitup.0 (2809) slow connection to states DB. Still waiting ... 2023-10-02 08:57:52.444 - info: host.ioBroker instance system.adapter.telegram.0 started with pid 2994 2023-10-02 08:57:52.910 - info: host.ioBroker instance system.adapter.yahka.0 started with pid 2996 2023-10-02 08:57:53.446 - info: host.ioBroker instance system.adapter.terminal.0 started with pid 3005 2023-10-02 08:57:58.391 - error: melcloud.0 (2557) melcloud.0 already running 2023-10-02 08:57:58.403 - warn: melcloud.0 (2557) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:57:58.385 - info: host.ioBroker instance system.adapter.text2command.0 started with pid 3028 2023-10-02 08:58:11.940 - warn: statistics.0 (2957) slow connection to objects DB. Still waiting ... 2023-10-02 08:58:14.313 - warn: mercedesme.0 (2958) slow connection to objects DB. Still waiting ... 2023-10-02 08:58:15.877 - warn: jarvis.0 (2941) slow connection to objects DB. Still waiting ... 2023-10-02 08:58:16.534 - warn: controme.0 (2823) slow connection to states DB. Still waiting ... 2023-10-02 08:58:16.643 - warn: tinker.0 (2977) slow connection to objects DB. Still waiting ... 2023-10-02 08:58:18.464 - error: host.ioBroker instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:58:18.482 - info: host.ioBroker Restart adapter system.adapter.hm-rega.0 because enabled 2023-10-02 08:58:28.376 - info: host.ioBroker instance system.adapter.alexa2.0 started with pid 3050 2023-10-02 08:58:28.861 - info: host.ioBroker instance system.adapter.upnp.0 started with pid 3051 2023-10-02 08:58:38.322 - warn: text2command.0 (3028) slow connection to objects DB. Still waiting ... 2023-10-02 08:58:37.833 - info: host.ioBroker instance system.adapter.web.0 started with pid 3075 2023-10-02 08:58:43.163 - warn: discovery.0 (2837) slow connection to states DB. Still waiting ... 2023-10-02 08:58:43.240 - error: nuki-extended.0 (2604) nuki-extended.0 already running 2023-10-02 08:58:43.244 - warn: nuki-extended.0 (2604) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:58:44.155 - warn: terminal.0 (3005) slow connection to objects DB. Still waiting ... 2023-10-02 08:58:45.193 - warn: yahka.0 (2996) slow connection to objects DB. Still waiting ... 2023-10-02 08:58:47.647 - warn: telegram.0 (2994) slow connection to objects DB. Still waiting ... 2023-10-02 08:58:59.697 - info: host.ioBroker instance system.adapter.withings.0 started with pid 3095 2023-10-02 08:59:05.814 - warn: hue-extended.0 (2836) slow connection to states DB. Still waiting ... 2023-10-02 08:59:12.167 - warn: alexa2.0 (3050) slow connection to objects DB. Still waiting ... 2023-10-02 08:59:00.334 - info: host.ioBroker instance system.adapter.geofency.0 started with pid 3096 2023-10-02 08:59:16.458 - error: tr-064.0 (2670) tr-064.0 already running 2023-10-02 08:59:16.461 - warn: tr-064.0 (2670) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:16.581 - error: host.ioBroker instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:16.582 - info: host.ioBroker Restart adapter system.adapter.hm-rpc.0 because enabled 2023-10-02 08:59:19.219 - warn: upnp.0 (3051) slow connection to objects DB. Still waiting ... 2023-10-02 08:59:22.856 - error: host.ioBroker instance system.adapter.melcloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:22.850 - error: backitup.0 (2809) backitup.0 already running 2023-10-02 08:59:22.853 - warn: backitup.0 (2809) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:22.863 - info: host.ioBroker Restart adapter system.adapter.melcloud.0 because enabled 2023-10-02 08:59:23.470 - warn: homepilot20.0 (2871) slow connection to states DB. Still waiting ... 2023-10-02 08:59:23.807 - error: controme.0 (2823) controme.0 already running 2023-10-02 08:59:23.810 - warn: controme.0 (2823) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:24.176 - warn: sql.0 (2883) slow connection to states DB. Still waiting ... 2023-10-02 08:59:24.463 - warn: web.0 (3075) slow connection to objects DB. Still waiting ... 2023-10-02 08:59:25.444 - error: host.ioBroker instance system.adapter.nuki-extended.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:25.446 - info: host.ioBroker Restart adapter system.adapter.nuki-extended.0 because enabled 2023-10-02 08:59:25.832 - error: discovery.0 (2837) discovery.0 already running 2023-10-02 08:59:25.836 - warn: discovery.0 (2837) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:26.394 - warn: javascript.0 (2862) slow connection to states DB. Still waiting ... 2023-10-02 08:59:26.584 - error: host.ioBroker instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:26.584 - info: host.ioBroker Restart adapter system.adapter.tr-064.0 because enabled 2023-10-02 08:59:27.551 - error: hue-extended.0 (2836) hue-extended.0 already running 2023-10-02 08:59:27.553 - warn: hue-extended.0 (2836) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:27.884 - warn: iot.0 (2911) slow connection to states DB. Still waiting ... 2023-10-02 08:59:28.361 - warn: info.0 (2898) slow connection to states DB. Still waiting ... 2023-10-02 08:59:28.458 - info: host.ioBroker instance system.adapter.hm-rega.0 started with pid 3128 2023-10-02 08:59:28.481 - error: homepilot20.0 (2871) homepilot20.0 already running 2023-10-02 08:59:28.483 - warn: homepilot20.0 (2871) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:29.471 - warn: geofency.0 (3096) slow connection to objects DB. Still waiting ... 2023-10-02 08:59:29.700 - warn: withings.0 (3095) slow connection to objects DB. Still waiting ... 2023-10-02 08:59:30.507 - warn: statistics.0 (2957) slow connection to states DB. Still waiting ... 2023-10-02 08:59:30.661 - error: host.ioBroker instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:30.662 - info: host.ioBroker Restart adapter system.adapter.backitup.0 because enabled 2023-10-02 08:59:32.149 - error: host.ioBroker instance system.adapter.controme.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:32.209 - warn: mercedesme.0 (2958) slow connection to states DB. Still waiting ... 2023-10-02 08:59:32.166 - info: host.ioBroker Restart adapter system.adapter.controme.0 because enabled 2023-10-02 08:59:33.227 - warn: jarvis.0 (2941) slow connection to states DB. Still waiting ... 2023-10-02 08:59:33.311 - error: iot.0 (2911) iot.0 already running 2023-10-02 08:59:33.314 - warn: iot.0 (2911) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:34.004 - warn: tinker.0 (2977) slow connection to states DB. Still waiting ... 2023-10-02 08:59:34.642 - error: info.0 (2898) info.0 already running 2023-10-02 08:59:34.646 - warn: info.0 (2898) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:34.932 - error: host.ioBroker instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:34.933 - info: host.ioBroker Restart adapter system.adapter.discovery.0 because enabled 2023-10-02 08:59:35.728 - warn: text2command.0 (3028) slow connection to states DB. Still waiting ... 2023-10-02 08:59:36.292 - error: statistics.0 (2957) statistics.0 already running 2023-10-02 08:59:36.304 - warn: statistics.0 (2957) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:36.601 - error: host.ioBroker instance system.adapter.hue-extended.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:36.602 - info: host.ioBroker Restart adapter system.adapter.hue-extended.0 because enabled 2023-10-02 08:59:37.197 - warn: terminal.0 (3005) slow connection to states DB. Still waiting ... 2023-10-02 08:59:37.295 - error: mercedesme.0 (2958) mercedesme.0 already running 2023-10-02 08:59:37.307 - warn: mercedesme.0 (2958) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:37.982 - error: host.ioBroker instance system.adapter.homepilot20.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:37.982 - info: host.ioBroker Restart adapter system.adapter.homepilot20.0 because enabled 2023-10-02 08:59:38.314 - error: jarvis.0 (2941) jarvis.0 already running 2023-10-02 08:59:38.317 - warn: jarvis.0 (2941) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:38.390 - warn: yahka.0 (2996) slow connection to states DB. Still waiting ... 2023-10-02 08:59:38.879 - error: tinker.0 (2977) tinker.0 already running 2023-10-02 08:59:38.891 - warn: tinker.0 (2977) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:39.585 - error: host.ioBroker instance system.adapter.iot.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:39.682 - warn: telegram.0 (2994) slow connection to states DB. Still waiting ... 2023-10-02 08:59:39.598 - info: host.ioBroker Restart adapter system.adapter.iot.0 because enabled 2023-10-02 08:59:39.703 - error: text2command.0 (3028) text2command.0 already running 2023-10-02 08:59:39.706 - warn: text2command.0 (3028) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:40.201 - error: host.ioBroker instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:40.426 - warn: alexa2.0 (3050) slow connection to states DB. Still waiting ... 2023-10-02 08:59:40.203 - info: host.ioBroker Restart adapter system.adapter.info.0 because enabled 2023-10-02 08:59:40.755 - error: host.ioBroker instance system.adapter.statistics.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:40.755 - error: terminal.0 (3005) terminal.0 already running 2023-10-02 08:59:40.767 - warn: terminal.0 (3005) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:40.756 - info: host.ioBroker Restart adapter system.adapter.statistics.0 because enabled 2023-10-02 08:59:41.321 - warn: upnp.0 (3051) slow connection to states DB. Still waiting ... 2023-10-02 08:59:41.343 - error: host.ioBroker instance system.adapter.mercedesme.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:41.342 - error: yahka.0 (2996) yahka.0 already running 2023-10-02 08:59:41.351 - warn: yahka.0 (2996) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:41.343 - info: host.ioBroker Restart adapter system.adapter.mercedesme.0 because enabled 2023-10-02 08:59:42.078 - warn: web.0 (3075) slow connection to states DB. Still waiting ... 2023-10-02 08:59:42.530 - error: host.ioBroker instance system.adapter.jarvis.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:42.861 - warn: geofency.0 (3096) slow connection to states DB. Still waiting ... 2023-10-02 08:59:42.538 - info: host.ioBroker Restart adapter system.adapter.jarvis.0 because enabled 2023-10-02 08:59:43.261 - error: upnp.0 (3051) upnp.0 already running 2023-10-02 08:59:43.263 - warn: upnp.0 (3051) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:43.268 - error: host.ioBroker instance system.adapter.tinker.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:43.335 - warn: withings.0 (3095) slow connection to states DB. Still waiting ... 2023-10-02 08:59:43.268 - info: host.ioBroker Restart adapter system.adapter.tinker.0 because enabled 2023-10-02 08:59:44.007 - error: web.0 (3075) web.0 already running 2023-10-02 08:59:44.010 - warn: web.0 (3075) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:44.015 - error: host.ioBroker instance system.adapter.text2command.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:44.016 - info: host.ioBroker Restart adapter system.adapter.text2command.0 because enabled 2023-10-02 08:59:44.517 - error: withings.0 (3095) withings.0 already running 2023-10-02 08:59:44.521 - warn: withings.0 (3095) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-10-02 08:59:44.573 - error: host.ioBroker instance system.adapter.terminal.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:44.574 - info: host.ioBroker Restart adapter system.adapter.terminal.0 because enabled 2023-10-02 08:59:45.282 - error: host.ioBroker instance system.adapter.yahka.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:45.283 - info: host.ioBroker Restart adapter system.adapter.yahka.0 because enabled 2023-10-02 08:59:45.684 - error: host.ioBroker instance system.adapter.upnp.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:45.685 - info: host.ioBroker Restart adapter system.adapter.upnp.0 because enabled 2023-10-02 08:59:46.765 - error: host.ioBroker instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:46.769 - info: host.ioBroker Restart adapter system.adapter.web.0 because enabled 2023-10-02 08:59:46.769 - error: host.ioBroker instance system.adapter.withings.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-10-02 08:59:46.770 - info: host.ioBroker Restart adapter system.adapter.withings.0 because enabled 2023-10-02 08:59:47.451 - info: host.ioBroker instance system.adapter.hm-rpc.0 started with pid 3143 2023-10-02 08:59:48.348 - info: geofency.0 (3096) starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.geofency, node: v18.18.0, js-controller: 5.0.12 2023-10-02 08:59:48.466 - info: geofency.0 (3096) http server listening on port 7999 2023-10-02 08:59:56.269 - error: sql.0 (2883) Counter must have type "number"! 2023-10-02 08:59:56.314 - error: sql.0 (2883) Counter must have type "number"! 2023-10-02 08:59:57.232 - info: host.ioBroker stopInstance system.adapter.alexa2.0 (force=false, process=true) 2023-10-02 08:59:59.992 - info: host.ioBroker stopInstance system.adapter.alexa2.0 send kill signalViele Grüße,
Marc@meicker dann hast du noch ein unentdecktes Problem.
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
woher kommt der Neustart um 7:17 der zum Stillstand führt ?
ist nämlich zumindest in diesem log nichts von zu sehen.
Die Fehler danach entstehen dadurch, dass anscheinend kein vollständiger Absturz stattgefunden hat, und die alten Prozesse noch laufen
-
@meicker dann hast du noch ein unentdecktes Problem.
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
woher kommt der Neustart um 7:17 der zum Stillstand führt ?
ist nämlich zumindest in diesem log nichts von zu sehen.
Die Fehler danach entstehen dadurch, dass anscheinend kein vollständiger Absturz stattgefunden hat, und die alten Prozesse noch laufen
wenn der Absturz stattgefunden hat blinken die LED nicht mehr. Ich nehme dann die SD raus, ziehe den Strom ab, Karte rein und gebe wieder Strom.
Dann wird ja alles neu gestartet und er findet dann die noch laufenden Dienste maximal in einem Status. Aber nachdem der Strom weg war sollte ja kein Duenst mehr laufen ☺️
Eine Idee - Was ist wenn die SD Karte langsam um ist. Wollte gleich mal ne kopie ziehen und auf eine andere flaschen. Das ist ja ein Teil was mit dem Fehler umgezogen ist …
-
wenn der Absturz stattgefunden hat blinken die LED nicht mehr. Ich nehme dann die SD raus, ziehe den Strom ab, Karte rein und gebe wieder Strom.
Dann wird ja alles neu gestartet und er findet dann die noch laufenden Dienste maximal in einem Status. Aber nachdem der Strom weg war sollte ja kein Duenst mehr laufen ☺️
Eine Idee - Was ist wenn die SD Karte langsam um ist. Wollte gleich mal ne kopie ziehen und auf eine andere flaschen. Das ist ja ein Teil was mit dem Fehler umgezogen ist …
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
Ich nehme dann die SD raus, ziehe den Strom ab, Karte rein und gebe wieder Strom.
Systemkiller...
-
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
Ich nehme dann die SD raus, ziehe den Strom ab, Karte rein und gebe wieder Strom.
Systemkiller...
ja - aber irgendwie muss ich ja neu starten, oder ? 😅
Oder meinst Du es gibt eine bessere Reihenfolge ? Wenn ich die Karte nach dem Strom stecke läuft es schon mal nicht weil die Karte dann wohl zum booten nicht mehr erkannt wird … -
ja - aber irgendwie muss ich ja neu starten, oder ? 😅
Oder meinst Du es gibt eine bessere Reihenfolge ? Wenn ich die Karte nach dem Strom stecke läuft es schon mal nicht weil die Karte dann wohl zum booten nicht mehr erkannt wird …@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
ja - aber irgendwie muss ich ja neu starten, oder ?
Mit dem 'Klammergriff'.
Ich vermute aber, das dein Ding an gleich mehreren Stellen einfach defekt ist. -
wenn der Absturz stattgefunden hat blinken die LED nicht mehr. Ich nehme dann die SD raus, ziehe den Strom ab, Karte rein und gebe wieder Strom.
Dann wird ja alles neu gestartet und er findet dann die noch laufenden Dienste maximal in einem Status. Aber nachdem der Strom weg war sollte ja kein Duenst mehr laufen ☺️
Eine Idee - Was ist wenn die SD Karte langsam um ist. Wollte gleich mal ne kopie ziehen und auf eine andere flaschen. Das ist ja ein Teil was mit dem Fehler umgezogen ist …
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
Ich nehme dann die SD raus, ziehe den Strom ab, Karte rein und gebe wieder Strom.
und das ist die gsnze Zeit immer noch dieselbe Karte?
-
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
ja - aber irgendwie muss ich ja neu starten, oder ?
Mit dem 'Klammergriff'.
Ich vermute aber, das dein Ding an gleich mehreren Stellen einfach defekt ist.@thomas-braun
Klammergriff ? Bitte mal näher erläutern bitte ... -
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
Ich nehme dann die SD raus, ziehe den Strom ab, Karte rein und gebe wieder Strom.
und das ist die gsnze Zeit immer noch dieselbe Karte?
-
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
ja - aber irgendwie muss ich ja neu starten, oder ?
Mit dem 'Klammergriff'.
Ich vermute aber, das dein Ding an gleich mehreren Stellen einfach defekt ist.hab ich glaube ich gefunden - geht aber nicht wenn es das mit den zwei Pinnen brücken ist weil das Homematic Modul drauf steckt.
Das Ding sind aber zwei Boards die das gleiche machen ... denke ich eigentlich dann eher nicht ...
-
@thomas-braun
Klammergriff ? Bitte mal näher erläutern bitte ...@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
@thomas-braun
Klammergriff ? Bitte mal näher erläutern bitte ...siehe Wikipedia
tastatur dran und dann Tastenkombination -
hab ich glaube ich gefunden - geht aber nicht wenn es das mit den zwei Pinnen brücken ist weil das Homematic Modul drauf steckt.
Das Ding sind aber zwei Boards die das gleiche machen ... denke ich eigentlich dann eher nicht ...
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
Das Ding sind aber zwei Boards die das gleiche machen ... denke ich eigentlich dann eher nich
Deswegen eird wahrscheinlich die Karte gewaltig morsch sein
-
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
@thomas-braun
Klammergriff ? Bitte mal näher erläutern bitte ...siehe Wikipedia
tastatur dran und dann Tastenkombination -
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
Das Ding sind aber zwei Boards die das gleiche machen ... denke ich eigentlich dann eher nich
Deswegen eird wahrscheinlich die Karte gewaltig morsch sein
-
ok - hab keine Tastatur dran - aber mal interessant zu wissen ob ein eingefrorenes System was nicht mehr erreichbar ist auf eine Tastatur hört ...
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
aber mal interessant zu wissen ob ein eingefrorenes System was nicht mehr erreichbar ist auf eine Tastatur hört ...
Tut es.
-
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
aber mal interessant zu wissen ob ein eingefrorenes System was nicht mehr erreichbar ist auf eine Tastatur hört ...
Tut es.
@thomas-braun
muss aber wahrscheinlich per USB dran sein, oder ? -
@thomas-braun
muss aber wahrscheinlich per USB dran sein, oder ?Besser ja. Mit Funktastatur funktioniert es ggfs nicht.
-
@thomas-braun
muss aber wahrscheinlich per USB dran sein, oder ?@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
@thomas-braun
muss aber wahrscheinlich per USB dran sein, oder ?jepp, PS/2 hat der pi ja nicht.
:duckundwech:
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 -
-
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
@thomas-braun
muss aber wahrscheinlich per USB dran sein, oder ?jepp, PS/2 hat der pi ja nicht.
:duckundwech:
Wer hat denn auch noch eine Playstation 2 am Start?
(Sie sind alt, wenn Sie diese Schnittstelle kennen!)
-
@meicker sagte in pivccu3 3.71.12 und nodejs 18.x:
@thomas-braun
muss aber wahrscheinlich per USB dran sein, oder ?jepp, PS/2 hat der pi ja nicht.
:duckundwech:
-
Wer hat denn auch noch eine Playstation 2 am Start?
(Sie sind alt, wenn Sie diese Schnittstelle kennen!)
@thomas-braun sagte in pivccu3 3.71.12 und nodejs 18.x:
Wer hat denn auch noch eine Playstation 2 am Start?
(Sie sind alt, wenn Sie diese Schnittstelle kennen!)
ich hab noch eine Tastatur mit DIN Stecker rumliegen.
wie alt.....
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 -
411
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge