Ram läuft voll
-
@homoran said in Ram läuft voll:
Bitte dann ein Issue bei dem Adapter aufmachen
Bei dem Calendar Adapter ? Naja denke eher schlechte Karten, wenn der seit 2020 nichts mehr passiert ist.
Auf jeden Fall hoffe ich das es das war. Mein Kopf raucht, daheim ging nichts mehr. Jetzt kehr langsam Ruhe ein Gott sei Dank.
-
@d3ltoroxp sagte in Ram läuft voll:
Bei dem Calendar Adapter ?
Ja, auf GitHub
@d3ltoroxp sagte in Ram läuft voll:
eher schlechte Karten, wenn der seit 2020 nichts mehr passiert ist.
dann erst recht
-
Last Online 4 Nov 2020, 13:15 ich denke nicht das da noch Interesse besteht weiter zu entwickeln. Aber ich werd dort dann mal ein issue aufmachen.
-
@d3ltoroxp Hat das eigentlich einen besonderen Grund das du den Calender Adapter nutzt?
Ich nutze seit Anfang an den Ical Adapter und hatt bisher noch keine Probleme.
Da gibt es dann ganz komfortabel noch den TrashSchedule Adapter dazu und du sparst dir auch das Blockly. -
@chaot Uff, ich weiß gar nicht wie ich auf den gekommen bin. Es gab dort halt den Text in den DP's, damit konnte ich dann eben meine Müll VIS mit betreiben. Dann muss ich mir auch mal den Trash Adapter anschauen. Danke für den Tipp.
Des weiteren klang das ja recht ambitioniert, was er da vor hatte.
-
@d3ltoroxp sagte in Ram läuft voll:
Dann muss ich mir auch mal den Trash Adapter anschauen
Der arbeitet hervorragend mit ical zusammen.
Alles mit ganz paar einfachen Einstellungen
-
Hm ich dachte schon es wäre alles gut, grad meiner Frau noch gesagt, läuft jetzt wieder TOP. Jetzt wollt ich noch mal in ioB rein schauen, zag geht nichts mehr...
Kann man denn irgendwo in einer Log ersehen, wer oder was den Ram dann so zu ballert ?
host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[12]: 20: 0x1446459 [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[12]: 19: 0xc25506 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[11]: 18: 0xc24e86 [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[11]: 17: 0xc238db [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[11]: 16: 0xb11ed0 void node::StreamBase::JSMethod<&node::StreamBase::Writev>(v8::FunctionCallbackInfo<v8::Value> const&) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[10]: 15: 0xb0fcec node::StreamBase::Writev(v8::FunctionCallbackInfo<v8::Value> const&) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[10]: 14: 0xb1d4a3 node::StringBytes::Write(v8::Isolate*, char*, unsigned long, v8::Local<v8::Value>, node::encoding, int*) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[10]: 13: 0xbcab28 v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[9]: 12: 0xfaa04a v8::internal::String::SlowFlatten(v8::internal::Isolate*, v8::internal::Handle<v8::internal::ConsString>, v8::internal::AllocationType) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[8]: 11: 0xd47bc0 v8::internal::FactoryBase<v8::internal::Factory>::NewRawOneByteString(int, v8::internal::AllocationType) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[8]: 10: 0xd45bb4 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[7]: 9: 0xd4bd2d v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[6]: 8: 0xd8655c v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.709 error Caught by controller[5]: 7: 0xd8299b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[4]: 6: 0xd74b5f [io.javascript.0] host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[3]: 5: 0xd73fd5 [io.javascript.0] host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[3]: 4: 0xbb7dc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[3]: 3: 0xbb7a4e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[2]: 2: 0x96e0af node::FatalError(char const*, char const*) [io.javascript.0] host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[1]: 1: 0xa389b0 node::Abort() [io.javascript.0] host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[0]: <--- JS stacktrace ---> host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[0]: [9379:0x6134740] 35017744 ms: Mark-sweep (reduce) 1993.0 (2051.5) -> 1993.0 (2052.5) MB, 1251.3 / 0.0 ms (average mu = 0.215, current mu = 0.175) allocation failure GC in old space requested host.iobroker 2022-01-03 20:24:09.708 error Caught by controller[0]: [9379:0x6134740] 35016227 ms: Mark-sweep (reduce) 1993.1 (2051.5) -> 1993.0 (2052.5) MB, 1239.4 / 0.0 ms (average mu = 0.250, current mu = 0.201) allocation failure GC in old space requested host.iobroker 2022-01-03 20:24:09.705 error Caught by controller[0]: <--- Last few GCs ---> Habs rein geschafft, das steht aktuell in der Log.Hm ob er hier stresst ?
weatherunderground.0 2022-01-03 20:21:09.941 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.941 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.941 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.35h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.940 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.940 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.939 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.34h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.939 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.938 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.938 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.33h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.938 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.937 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.937 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.32h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.936 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.930 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.930 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.31h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.929 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.929 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.929 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.30h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.928 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.928 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.927 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.29h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.927 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.926 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.926 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.28h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.926 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.925 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.925 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.27h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.924 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.924 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.924 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.26h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.923 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.923 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.922 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.25h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.921 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.921 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.921 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.24h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.920 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.920 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.920 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.23h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.919 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.919 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.918 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.22h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.918 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.917 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.917 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.21h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.917 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.916 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.916 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.20h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.915 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.915 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.915 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.19h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.914 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.914 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.913 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.18h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.913 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.912 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.912 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.17h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.912 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.911 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.911 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.16h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.910 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.910 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.910 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.15h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.909 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.909 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.908 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.14h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.908 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.907 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.907 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.13h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.907 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.906 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.906 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.12h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.905 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.905 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.905 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.11h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.904 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.904 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.903 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.10h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.902 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.902 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.902 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.9h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.901 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.900 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.900 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.8h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.899 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.899 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.899 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.7h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.898 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.898 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.898 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.6h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.897 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.897 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.897 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.5h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.896 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.896 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.896 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.4h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.895 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.895 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.894 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.3h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.894 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.894 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.893 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.2h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.893 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:09.892 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:09.892 warn Could not perform strict object check of state weatherunderground.0.forecastHourly.1h.time: Connection is closed. weatherunderground.0 2022-01-03 20:21:08.860 error Could not parse hourly Forecast-Data: Error: DB closed weatherunderground.0 2022-01-03 20:21:08.859 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:06.836 error exception in daily forecast data Error: DB closed weatherunderground.0 2022-01-03 20:21:06.835 warn get state error: Connection is closed. weatherunderground.0 2022-01-03 20:21:05.203 error exception in daily forecast data Error: DB closed weatherunderground.0 2022-01-03 20:21:02.962 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason weatherunderground.0 2022-01-03 20:21:02.961 warn force terminate weatherunderground.0 2022-01-03 20:20:04.456 info State value to set for "weatherunderground.0.forecast.2d.icon" has to be type "string" but received type "number" weatherunderground.0 2022-01-03 20:20:04.371 info State value to set for "weatherunderground.0.forecast.1d.windDirectionMax" has to be type "string" but received type "number" weatherunderground.0 2022-01-03 20:20:04.260 info State value to set for "weatherunderground.0.forecast.1d.icon" has to be type "string" but received type "number" weatherunderground.0 2022-01-03 20:20:04.148 info State value to set for "weatherunderground.0.forecast.0d.windDirectionMax" has to be type "string" but received type "number" -
@d3ltoroxp sagte in Ram läuft voll:
Kann man denn irgendwo in einer Log ersehen, wer oder was den Ram dann so zu ballert ?
Seit wann steigt der denn wieder?
Möglichkeit:
Den RAM-Verbrauch loggen
Dann beim nächsten mal nachsehen welches Skript gestartet ist, als das Malhuer begann -
@homoran gefühlt vor ein paar Min. Hatte es den ganzen Tag im Blick, hab auch meine VIS für den Müll angepasst. Ich habe immer auf den Ram geschaut, alles gut, lief auch immer flüssig. Jetzt eben wars so. Komischweise nichts gemacht und er hat sich wieder beruhigt, lieg jetzt wieder bei 3 GB und er läuft wieder stabil.
Könnte das hier das ausgelöst haben ?
Ich hab Motion Detection am Tablet an, wenn der vllt immer on / off triggert ? Das ist neu, da jetzt grad viel Bewegung im Esszimmer ist, als heute Mittag, viel es da vllt nicht auf ?
-
@d3ltoroxp falls wert, ist doch schon wahr, warum dann noch doppelt gemoppelt auf wahr prüfen
-
@crunchip soll eine Schleife wein, war so gedacht das bei Screen On der rechte Teil gestartet wird, wenn er am Ende angelangt ist prüft er ob das Display noch an ist, wenn ja geht es ja wieder von vorne los, wenn nicht dann wars das.
Könnte der fast Absturz hierdurch passiert sein ? Weil es kein sauberes Script ist ? -
@d3ltoroxp
Alles Vermutungen.
Monitore mal eine Zeit lang kontinuierlich dein RAM.
Wenn man dann sieht welcher Prozess es ist, dann kann man weiterschauen.Falls es der javascript adapter ist dann muss man eigentlich alle skripte abschalten und stück für stück wieder einschalten um zu sehen, ob es an einem bestimmte skript liegt.
Du kannst hier ja mal nach dem Stichwort Speicherlecks suchen, da findest diverse Hinweise wie das abläuft -
@oliverio sagte in Ram läuft voll:
Monitore mal eine Zeit lang kontinuierlich dein RAM.
wie macht man das in proxmox.
Würde mich auch interessieren. -
ich würde atop empfehlen um das system nicht durch eine umfangreichere monitoringlösung noch mehr zu belasten. ist auch nicht proxmox spezifisch
ich habe das selbst vor längerer zeit mal verwendet.das tool kann normal installiert werden und über shell aufgerufen werden.
apt install atopüber dem standardbefehl top hinaus kann es seine daten auch in eine datei schreiben, welche man zu einem späteren Zeitpunkt öffnen kann und dann über alle zeitsamples durchblättern kann
-
@bahnuhr
z.B mit dem proxmox Adapter. Das sind Datenpunkte einer VM, die lassen sich mit History usw. loggen
-
@fredf
für diesen fehlerfall geht es eher um ein prozessbasiertes RAM monitoring.
Ansonsten findet man den Übeltäter nicht. -
@oliverio said in Ram läuft voll:
ich würde atop empfehlen um das system nicht durch eine umfangreichere monitoringlösung noch mehr zu belasten. ist auch nicht proxmox spezifisch
ich habe das selbst vor längerer zeit mal verwendet.das tool kann normal installiert werden und über shell aufgerufen werden.
apt install atopüber dem standardbefehl top hinaus kann es seine daten auch in eine datei schreiben, welche man zu einem späteren Zeitpunkt öffnen kann und dann über alle zeitsamples durchblättern kann
Seh ich denn dann in der Datei, wer was ausgelöst hat ? Oder muss ich grad zufällig an der Maschine sein und sehen das der Ram ausgelastet ist, um dann mit Zeitstempel zu suchen ?
-
@oliverio said in Ram läuft voll:
kann es seine daten auch in eine datei schreiben, welche man zu einem späteren Zeitpunkt öffnen kann und dann über alle zeitsamples durchblättern kann
mehr ist natürlich in der man page (link oben gepostet) im abschnitt Raw Data Storage beschrieben
-
Ich habe das Tool noch nicht am laufen, aber merke gerade das der Ram steigt und ioB träge wird. In der Log taucht wieder "dasWetter Adapter" auf.
host.iobroker 2022-01-04 12:32:10.495 error instance system.adapter.daswetter.0 terminated with code 15 (UNKNOWN_ERROR) daswetter.0 2022-01-04 12:32:10.415 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_3": Connection is closed. daswetter.0 2022-01-04 12:32:10.414 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.windchill_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.windchill_value": Connection is closed.] daswetter.0 2022-01-04 12:32:10.412 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.windchill_value": Connection is closed. daswetter.0 2022-01-04 12:32:10.412 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.snowline_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.snowline_value": Connection is closed.] daswetter.0 2022-01-04 12:32:10.411 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.snowline_value": Connection is closed. daswetter.0 2022-01-04 12:32:10.411 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.clouds_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.clouds_value": Connection is closed.] daswetter.0 2022-01-04 12:32:10.410 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.clouds_value": Connection is closed. daswetter.0 2022-01-04 12:32:10.410 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.pressure_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.pressure_value": Connection is closed.] daswetter.0 2022-01-04 12:32:10.410 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.pressure_value": Connection is closed. daswetter.0 2022-01-04 12:32:10.409 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.humidity_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.humidity_value": Connection is closed.] daswetter.0 2022-01-04 12:32:10.401 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.humidity_value": Connection is closed. daswetter.0 2022-01-04 12:32:10.400 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.rain_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.rain_value": Connection is closed.] daswetter.0 2022-01-04 12:32:10.400 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.windgusts_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.windgusts_value": Connection is closed.] daswetter.0 2022-01-04 12:32:10.399 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.windgusts_value": Connection is closed. daswetter.0 2022-01-04 12:32:10.400 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.rain_value": Connection is closed. daswetter.0 2022-01-04 12:32:10.399 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.windIconURL: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.windIconURL": Connection is closed.] daswetter.0 2022-01-04 12:32:10.398 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.windIconURL": Connection is closed. daswetter.0 2022-01-04 12:32:10.398 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_value": Connection is closed.] daswetter.0 2022-01-04 12:32:10.397 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_value": Connection is closed. daswetter.0 2022-01-04 12:32:10.396 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_dir: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_dir": Connection is closed.] daswetter.0 2022-01-04 12:32:10.394 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_dir": Connection is closed. daswetter.0 2022-01-04 12:32:10.393 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_symbol": Connection is closed. daswetter.0 2022-01-04 12:32:10.393 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_symbolB: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_symbolB": Connection is closed.] daswetter.0 2022-01-04 12:32:10.392 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.iconURL: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.iconURL": Connection is closed.] daswetter.0 2022-01-04 12:32:10.393 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_symbol: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_symbol": Connection is closed.] daswetter.0 2022-01-04 12:32:10.392 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.iconURL": Connection is closed. daswetter.0 2022-01-04 12:32:10.392 error Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.wind_symbolB": Connection is closed. daswetter.0 2022-01-04 12:32:10.391 error exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.symbol_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_2.Hour_8.symbol_value": Connection is closed.] -
@d3ltoroxp
Das kann auch nur eine Begleiterscheinung des geringen RAM sein.
Wenn es mit diesem Adapter ein Problem gäbe dann wärst du nicht der einzige der hier schreibtWenn du mit Top dir mal die Prozesse anschaust, welche Prozesse benötigen den gerade viel RAM?
Zeig hier mal die Ausgabe des folgenden Befehls
ps -eo pmem,pcpu,vsize,pid,cmd | sort -k 1 -nr | head -20
