Raspi SD-Speicher läuft voll... vermutlich durch Influxdb
-
Hallo zusammen,
nach einiger Zeit Betrieb läuft mein Raspi Speicher voll...
Ich vermute es liegt an Influxdb.Ich verwende aktuell alles auf einem System.
Iobroker, Influxdb und Grafana.
Aber das nur "so habe ich gedacht" mit wenigen Daten zwecks Grafanavisualisierung meiner Brauchwasserwärmepumpe... quasi aktueller Betrieb.Soweit so gut, oder auch nicht.
Nun stellt mich das System auf die Probe und ich komme schon wieder nicht weiter.
Filesystem Size Used Avail Use% Mounted on /dev/root 29G 28G 0 100% / devtmpfs 3.6G 0 3.6G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 1.6G 1.3M 1.6G 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 255M 32M 224M 13% /boot tmpfs 782M 24K 782M 1% /run/user/1000 /dev/sda1 299G 11M 299G 1% /media/iobroker/WD 320GBAngemacht ist es jetzt, ob gut oder nicht weiß ich nicht, über USB eine externe Festplatte anzuschließen (320GB) um dort nur die influxdb2 Daten zu speichern.
So der Plan- Die alten Daten sind mir egal.
- Datenbankwerte von mir aus können komplett gelöscht werden.
- neuer Speicherort auf /dev/sda1 festlegen
Die große Frage ist: Wie mach ich das ... Vielleicht könnte mir jemand unter die arme greifen und mir hilfreiche Tipps liefern.
Was ich aus dem Forum gesehen habe ist, das keine Scrapers aktiviert sein sollen in der Influxdb, ich hab nichts aktiviert aber da war natürlich was..., was mir das System sicherlich zugemüllt hat.
Unter Buckets habe ich 8 Tage Retention Time, das reicht für mich aus.
Aber dennoch ist die Karte voll. 
Hoffe hier kann mir jemand auf die Sprünge helfen
Beste Grüße
master_jo1 -
@master_jo1 sagte in Raspi SD-Speicher läuft voll... vermutlich durch Influxdb:
Ich vermute es liegt an Influxdb.
Dann schau mit
sudo ncdu /nach wo wirklich die dicken Datenhalden liegen.
-
@thomas-braun said in Raspi SD-Speicher läuft voll... vermutlich durch Influxdb:
sudo ncdu /
ausgeführt und folgendes erhalten:
ncdu 1.15.1 ~ Use the arrow keys to navigate, press ? for help --- / ---------------------------------------------------------------------------------------------------------------------------- 15.8 GiB [##########] /var 6.9 GiB [#### ] /opt 3.9 GiB [## ] /usr 1.1 GiB [ ] /home 39.6 MiB [ ] /root 32.0 MiB [ ] /boot 9.5 MiB [ ] /media 6.2 MiB [ ] /etc . 1.3 MiB [ ] /run 80.0 KiB [ ] /tmp e 16.0 KiB [ ] /lost+found e 4.0 KiB [ ] /srv e 4.0 KiB [ ] /mnt 0.0 B [ ] /sys . 0.0 B [ ] /proc 0.0 B [ ] /dev @ 0.0 B [ ] sbin @ 0.0 B [ ] lib @ 0.0 B [ ] binncdu 1.15.1 ~ Use the arrow keys to navigate, press ? for help --- /var/log --------------------------------------------------------------------------------------------------------------------- /.. 3.5 GiB [##########] syslog.1 3.0 GiB [######## ] syslog 3.0 GiB [######## ] daemon.log 2.9 GiB [######## ] daemon.log.1 1.0 GiB [## ] /journal 553.8 MiB [# ] messages.1 553.7 MiB [# ] user.log.1 29.8 MiB [ ] syslog.2.gz 27.0 MiB [ ] messages.2.gz 27.0 MiB [ ] user.log.2.gz 2.3 MiB [ ] daemon.log.2.gz 976.0 KiB [ ] messages 928.0 KiB [ ] wtmp 844.0 KiB [ ] user.log 520.0 KiB [ ] syslog.3.gz 484.0 KiB [ ] messages.3.gz 472.0 KiB [ ] user.log.3.gz 344.0 KiB [ ] /grafana 220.0 KiB [ ] syslog.4.gz 156.0 KiB [ ] /apt 148.0 KiB [ ] kern.log 116.0 KiB [ ] messages.4.gztiefer rein bei den ersten 5 komme ich nicht
unter opt:
ncdu 1.15.1 ~ Use the arrow keys to navigate, press ? for help --- /opt/iobroker ---------------------------------------------------------------------------------------------------------------- /.. 4.5 GiB [##########] /log 1.4 GiB [### ] /node_modules 922.4 MiB [## ] /iobroker-data 70.6 MiB [ ] /backups 1.1 MiB [ ] package-lock.json 4.0 KiB [ ] package.json 4.0 KiB [ ] iobroker 4.0 KiB [ ] INSTALLER_INFO.txt 4.0 KiB [ ] .npmrc @ 0.0 B [ ] iobncdu 1.15.1 ~ Use the arrow keys to navigate, press ? for help --- /opt/iobroker/log ------------------------------------------------------------------------------------------------------------ /.. 2.1 GiB [##########] iobroker.2024-09-29.log 1.9 GiB [######### ] iobroker.2024-10-02.log 116.9 MiB [ ] iobroker.2024-09-28.log.gz 88.3 MiB [ ] iobroker.2024-09-25.log.gz 81.6 MiB [ ] iobroker.2024-09-27.log.gz 78.6 MiB [ ] iobroker.2024-09-30.log.gz 57.8 MiB [ ] iobroker.2024-09-26.log.gz 9.4 MiB [ ] iobroker.2024-10-01.log.gz 632.0 KiB [ ] iobroker.2024-09-29.log.gz @ 0.0 B [ ] iobroker.current.log 0.0 B [ ] iobroker.2024-10-03.log 0.0 B [ ] iobroker-audit.jsonhier logged irgendwas meinen Speicher voll...
hat das was mit der influxdb zu tun? -
@master_jo1 sagte in Raspi SD-Speicher läuft voll... vermutlich durch Influxdb:
hier logged irgendwas meinen Speicher voll...
hat das was mit der influxdb zu tun?Dann musst du mal in die logs reinschauen. Da muss ja beständig irgendwas reingeschrieben werden, was zu den abnormen Größen führt.
Am besten per
tail -n 50 /opt/iobroker/log/iobroker.current.log -
dein Befehl führte zu keiner Ausgabe, habe mir dann mal den ersten log angeschaut
tail -n 50 /opt/iobroker/log/iobroker.2024-09-29.log 2024-09-29 06:39:35.119 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.120 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.121 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.122 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.123 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.123 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.125 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.125 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.126 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.127 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.128 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.128 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.129 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.129 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.130 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.130 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.131 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.131 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.131 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.132 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.132 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.133 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.133 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.134 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.134 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.135 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.135 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.136 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.136 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.137 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.137 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.137 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40207_M_AC_Power_A[modbus/0/holdingRegisters/40207_M_AC_Power_A] 2024-09-29 06:39:35.138 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.138 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.138 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.139 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40207_M_AC_Power_A[modbus/0/holdingRegisters/40207_M_AC_Power_A] 2024-09-29 06:39:35.139 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.140 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40209_M_AC_Power_C[modbus/0/holdingRegisters/40209_M_AC_Power_C] 2024-09-29 06:39:35.140 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.141 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.141 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:39:35.141 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40207_M_AC_Power_A[modbus/0/holdingRegisters/40207_M_AC_Power_A] 2024-09-29 06:39:35.142 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40208_M_AC_Power_B[modbus/0/holdingRegisters/40208_M_AC_Power_B] 2024-09-29 06:39:35.142 - info: mqtt.0 (447619) send2Server modbus.0.holdingRegisters.40206___M_AC_Power[modbus/0/holdingRegisters/40206___M_AC_Power] 2024-09-29 06:40:14.196 - warn: modbus.0 (447532) [1] Poll error count: 1 code: "App Timeout" 2024-09-29 06:40:14.196 - warn: modbus.1 (447365) [2] Poll error count: 1 code: "App Timeout" 2024-09-29 06:48:50.583 - info: modbus.0 (447532) Disconnected from slave 192.168.178.63 2024-09-29 06:48:52.027 - warn: modbus.1 (447365) [2] Poll error count: 2 code: "App Timeout" 2024-09-29 07:00:35.514 - info: modbus.0 (447532) Connected to slave 192.168.178.63 2024-09-29 06:54:04.918 - warn: modbus.1 (447365) Error: undefineddas hat alles mit meiner Brauchwasserwärmepumpe zu tun.
aber eigentlich nehme ich über Modus nur den State in den iobroker und der sollte es an influxdb2 geben, iobroker log soll da nicht erfolgen
da der Speicher aber nun voll ist, komme kann ich auf den iobroker über IP nicht mehr zugreifen.
Wie lösche ich z.B. die beiden folgenden Pfade um wieder "geschäftsfähig zu sein"
2.1 GiB [##########] iobroker.2024-09-29.log 1.9 GiB [######### ] iobroker.2024-10-02.log -
@master_jo1 sagte in Raspi SD-Speicher läuft voll... vermutlich durch Influxdb:
iobroker.2024-09-29.log
iob stop mqtt rm /opt/iobroker/log/iobroker/iobroker.2024-09-29.logUnd dann musst du dir anschauen, warum da alle Tausendstel Sekunde in das Log geschrieben wird.
Zu modbus kann ich dir aber nix sagen, hab ich noch nie verwendet. -
@thomas-braun said in Raspi SD-Speicher läuft voll... vermutlich durch Influxdb:
rm /opt/iobroker/log/iobroker/iobroker.2024-09-29.log
ok das mit dem rm hat schonmal geholfen, komme jetzt wenigstens wieder auf den iobroker
ich hab jetzt noch große Brocken in syslog und syslog.1 sowie daemon.log und daemon.log.1
exemplarisch einmal syslogs
kann man die auch einfach per rm löschen? Oder zerschieße ich mir da was
tail -n 50 /var/log/syslog Oct 3 14:05:45 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:05:45 pv power: 0W Oct 3 14:05:46 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:05:46 grid meter: tibberlink/0/Homes/9055a3d9-f5c1-492d-a5fa-9127ecc80dae/LiveMeasurement/power invalid: '{"val":922,"ack":true,"ts":1727901260496,"q":0,"from":"system.adapter.tibberlink.0","user":"system.user.admin","lc":1727901256828}' Oct 3 14:06:14 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:06:14 ---- Oct 3 14:06:15 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:06:15 charge power: 0W Oct 3 14:06:15 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:06:15 charge currents: [0 0 0]A Oct 3 14:06:15 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:06:15 pv 1 power: modbus/0/holdingRegisters/40083_I_AC_Power invalid: '{"val":0,"ack":true,"ts":1727882976534,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1727882976534}' Oct 3 14:06:15 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:06:15 pv power: 0W Oct 3 14:06:16 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:06:16 grid meter: tibberlink/0/Homes/9055a3d9-f5c1-492d-a5fa-9127ecc80dae/LiveMeasurement/power invalid: '{"val":922,"ack":true,"ts":1727901260496,"q":0,"from":"system.adapter.tibberlink.0","user":"system.user.admin","lc":1727901256828}' Oct 3 14:06:44 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:06:44 ---- Oct 3 14:06:45 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:06:45 charge power: 0W Oct 3 14:06:45 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:06:45 charge currents: [0 0 0]A Oct 3 14:06:45 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:06:45 pv 1 power: modbus/0/holdingRegisters/40083_I_AC_Power invalid: '{"val":0,"ack":true,"ts":1727882976534,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1727882976534}' Oct 3 14:06:45 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:06:45 pv power: 0W Oct 3 14:06:45 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:06:45 grid meter: tibberlink/0/Homes/9055a3d9-f5c1-492d-a5fa-9127ecc80dae/LiveMeasurement/power invalid: '{"val":922,"ack":true,"ts":1727901260496,"q":0,"from":"system.adapter.tibberlink.0","user":"system.user.admin","lc":1727901256828}' Oct 3 14:07:14 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:07:14 ---- Oct 3 14:07:14 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:07:14 charge power: 0W Oct 3 14:07:14 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:07:14 charge currents: [0 0 0]A Oct 3 14:07:15 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:07:15 pv 1 power: modbus/0/holdingRegisters/40083_I_AC_Power invalid: '{"val":0,"ack":true,"ts":1727882976534,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1727882976534}' Oct 3 14:07:15 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:07:15 pv power: 0W Oct 3 14:07:15 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:07:15 grid meter: tibberlink/0/Homes/9055a3d9-f5c1-492d-a5fa-9127ecc80dae/LiveMeasurement/power invalid: '{"val":922,"ack":true,"ts":1727901260496,"q":0,"from":"system.adapter.tibberlink.0","user":"system.user.admin","lc":1727901256828}' Oct 3 14:07:44 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:07:44 ---- Oct 3 14:07:44 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:07:44 charge power: 0W Oct 3 14:07:44 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:07:44 charge currents: [0 0 0]A Oct 3 14:07:45 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:07:45 pv 1 power: modbus/0/holdingRegisters/40083_I_AC_Power invalid: '{"val":0,"ack":true,"ts":1727882976534,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1727882976534}' Oct 3 14:07:45 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:07:45 pv power: 0W Oct 3 14:07:46 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:07:46 grid meter: tibberlink/0/Homes/9055a3d9-f5c1-492d-a5fa-9127ecc80dae/LiveMeasurement/power invalid: '{"val":922,"ack":true,"ts":1727901260496,"q":0,"from":"system.adapter.tibberlink.0","user":"system.user.admin","lc":1727901256828}' Oct 3 14:08:14 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:08:14 ---- Oct 3 14:08:15 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:08:15 charge power: 0W Oct 3 14:08:15 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:08:15 charge currents: [0 0 0]A Oct 3 14:08:15 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:08:15 pv 1 power: modbus/0/holdingRegisters/40083_I_AC_Power invalid: '{"val":0,"ack":true,"ts":1727882976534,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1727882976534}' Oct 3 14:08:15 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:08:15 pv power: 0W Oct 3 14:08:16 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:08:16 grid meter: tibberlink/0/Homes/9055a3d9-f5c1-492d-a5fa-9127ecc80dae/LiveMeasurement/power invalid: '{"val":922,"ack":true,"ts":1727901260496,"q":0,"from":"system.adapter.tibberlink.0","user":"system.user.admin","lc":1727901256828}' Oct 3 14:08:44 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:08:44 ---- Oct 3 14:08:44 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:08:44 charge power: 0W Oct 3 14:08:44 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:08:44 charge currents: [0 0 0]A Oct 3 14:08:45 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:08:45 pv 1 power: modbus/0/holdingRegisters/40083_I_AC_Power invalid: '{"val":0,"ack":true,"ts":1727882976534,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1727882976534}' Oct 3 14:08:45 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:08:45 pv power: 0W Oct 3 14:08:46 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:08:46 grid meter: tibberlink/0/Homes/9055a3d9-f5c1-492d-a5fa-9127ecc80dae/LiveMeasurement/power invalid: '{"val":922,"ack":true,"ts":1727901260496,"q":0,"from":"system.adapter.tibberlink.0","user":"system.user.admin","lc":1727901256828}' Oct 3 14:09:14 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:09:14 ---- Oct 3 14:09:15 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:09:15 charge power: 0W Oct 3 14:09:15 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:09:15 charge currents: [0 0 0]A Oct 3 14:09:15 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:09:15 pv 1 power: modbus/0/holdingRegisters/40083_I_AC_Power invalid: '{"val":0,"ack":true,"ts":1727882976534,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1727882976534}' Oct 3 14:09:15 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:09:15 pv power: 0W Oct 3 14:09:16 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:09:16 grid meter: tibberlink/0/Homes/9055a3d9-f5c1-492d-a5fa-9127ecc80dae/LiveMeasurement/power invalid: '{"val":922,"ack":true,"ts":1727901260496,"q":0,"from":"system.adapter.tibberlink.0","user":"system.user.admin","lc":1727901256828}' Oct 3 14:09:44 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:09:44 ---- Oct 3 14:09:45 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:09:45 charge power: 0W Oct 3 14:09:45 iobroker evcc[3352]: [lp-1 ] DEBUG 2024/10/03 14:09:45 charge currents: [0 0 0]A Oct 3 14:09:45 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:09:45 pv 1 power: modbus/0/holdingRegisters/40083_I_AC_Power invalid: '{"val":0,"ack":true,"ts":1727882976534,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1727882976534}' Oct 3 14:09:45 iobroker evcc[3352]: [site ] DEBUG 2024/10/03 14:09:45 pv power: 0W Oct 3 14:09:46 iobroker evcc[3352]: [site ] ERROR 2024/10/03 14:09:46 grid meter: tibberlink/0/Homes/9055a3d9-f5c1-492d-a5fa-9127ecc80dae/LiveMeasurement/power invalid: '{"val":922,"ack":true,"ts":1727901260496,"q":0,"from":"system.adapter.tibberlink.0","user":"system.user.admin","lc":1727901256828}'tail -n 50 /var/log/syslog.1 Sep 29 00:05:04 iobroker bash[444021]: }, Sep 29 00:05:04 iobroker bash[444021]: code: 'internal error', Sep 29 00:05:04 iobroker bash[444021]: _retryAfter: 0 Sep 29 00:05:04 iobroker bash[444021]: } Sep 29 00:05:04 iobroker bash[444021]: WARN: Write to InfluxDB failed (attempt: 1). m [HttpError]: unexpected error writing points to database: engine: error writing WAL entry: write /var/lib/influxdb/.influxdbv2/engine/wal/5466f945fd73caff/autogen/241/_00002.wal: no space left on device Sep 29 00:05:04 iobroker bash[444021]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/@influxdata/influxdb-client/src/impl/node/NodeHttpTransport.ts:354:11) Sep 29 00:05:04 iobroker bash[444021]: at IncomingMessage.emit (node:events:531:35) Sep 29 00:05:04 iobroker bash[444021]: at IncomingMessage.emit (node:domain:488:12) Sep 29 00:05:04 iobroker bash[444021]: at endReadableNT (node:internal/streams/readable:1696:12) Sep 29 00:05:04 iobroker bash[444021]: at processTicksAndRejections (node:internal/process/task_queues:82:21) { Sep 29 00:05:04 iobroker bash[444021]: statusCode: 500, Sep 29 00:05:04 iobroker bash[444021]: statusMessage: 'Internal Server Error', Sep 29 00:05:04 iobroker bash[444021]: body: '{"code":"internal error","message":"unexpected error writing points to database: engine: error writing WAL entry: write /var/lib/influxdb/.influxdbv2/engine/wal/5466f945fd73caff/autogen/241/_00002.wal: no space left on device"}', Sep 29 00:05:04 iobroker bash[444021]: contentType: 'application/json; charset=utf-8', Sep 29 00:05:04 iobroker bash[444021]: json: { Sep 29 00:05:04 iobroker bash[444021]: code: 'internal error', Sep 29 00:05:04 iobroker bash[444021]: message: 'unexpected error writing points to database: engine: error writing WAL entry: write /var/lib/influxdb/.influxdbv2/engine/wal/5466f945fd73caff/autogen/241/_00002.wal: no space left on device' Sep 29 00:05:04 iobroker bash[444021]: }, Sep 29 00:05:04 iobroker bash[444021]: code: 'internal error', Sep 29 00:05:04 iobroker bash[444021]: _retryAfter: 0 Sep 29 00:05:04 iobroker bash[444021]: } Sep 29 00:05:04 iobroker bash[444021]: ERROR: Write to InfluxDB failed (attempt: 6). Error: Max retry time exceeded. Sep 29 00:05:04 iobroker bash[444021]: at F.sendBatch (/opt/iobroker/node_modules/@influxdata/influxdb-client/src/impl/WriteApiImpl.ts:164:23) Sep 29 00:05:04 iobroker bash[444021]: at Timeout._onTimeout (/opt/iobroker/node_modules/@influxdata/influxdb-client/src/impl/RetryBuffer.ts:133:14) Sep 29 00:05:04 iobroker bash[444021]: at listOnTimeout (node:internal/timers:581:17) Sep 29 00:05:04 iobroker bash[444021]: at processTimers (node:internal/timers:519:7) Sep 29 00:05:04 iobroker bash[444021]: WARN: Write to InfluxDB failed (attempt: 1). m [HttpError]: unexpected error writing points to database: engine: error writing WAL entry: write /var/lib/influxdb/.influxdbv2/engine/wal/5466f945fd73caff/autogen/241/_00002.wal: no space left on device Sep 29 00:05:04 iobroker bash[444021]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/@influxdata/influxdb-client/src/impl/node/NodeHttpTransport.ts:354:11) Sep 29 00:05:04 iobroker bash[444021]: at IncomingMessage.emit (node:events:531:35) Sep 29 00:05:04 iobroker bash[444021]: at IncomingMessage.emit (node:domain:488:12) Sep 29 00:05:04 iobroker bash[444021]: at endReadableNT (node:internal/streams/readable:1696:12) Sep 29 00:05:04 iobroker bash[444021]: at processTicksAndRejections (node:internal/process/task_queues:82:21) { Sep 29 00:05:04 iobroker bash[444021]: statusCode: 500, Sep 29 00:05:04 iobroker bash[444021]: statusMessage: 'Internal Server Error', Sep 29 00:05:04 iobroker bash[444021]: body: '{"code":"internal error","message":"unexpected error writing points to database: engine: error writing WAL entry: write /var/lib/influxdb/.influxdbv2/engine/wal/5466f945fd73caff/autogen/241/_00002.wal: no space left on device"}', Sep 29 00:05:04 iobroker bash[444021]: contentType: 'application/json; charset=utf-8', Sep 29 00:05:04 iobroker bash[444021]: json: { Sep 29 00:05:04 iobroker bash[444021]: code: 'internal error', Sep 29 00:05:04 iobroker bash[444021]: message: 'unexpected error writing points to database: engine: error writing WAL entry: write /var/lib/influxdb/.influxdbv2/engine/wal/5466f945fd73caff/autogen/241/_00002.wal: no space left on device' Sep 29 00:05:04 iobroker bash[444021]: }, Sep 29 00:05:04 iobroker bash[444021]: code: 'internal error', Sep 29 00:05:04 iobroker bash[444021]: _retryAfter: 0 Sep 29 00:05:04 iobroker bash[444021]: } Sep 29 00:05:04 iobroker bash[444021]: ERROR: Write to InfluxDB failed (attempt: 6). Error: Max retry time exceeded. Sep 29 00:05:04 iobroker bash[444021]: at F.sendBatch (/opt/iobroker/node_modules/@influxdata/influxdb-client/src/impl/WriteApiImpl.ts:164:23) Sep 29 00:05:04 iobroker bash[444021]: at Timeout._onTimeout (/opt/iobroker/node_modules/@influxdata/influxdb-client/src/impl/RetryBuffer.ts:133:14) Sep 29 00:05:04 iobroker bash[444021]: at listOnTimeout (node:internal/timers:581:17) Sep 29 00:05:04 iobroker bash[444021]: at processTimers (node:internal/timers:519:7) Sep 29 00:05:04 iobroker bash[444021]: WARN: Write to InfluxDB failed (attempt: 1). m [HttpError]: unexpected error writing points to database: engine: error writing WAL entry: write /var/lib/influxdb/.influxdbv2/engine/wal/5466f945fd73caff/autogen/241/_00002.wal: no space left on device Sep 29 00:05:04 iobroker bash[444021]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/@influxdata/influxdb-client/src/impl/node/NodeHttpTransport.ts:354:11)so ein Mist das hat was mit evcc zu tun was ich versucht hab ans laufen zu bringen und bisher noch nicht geklappt...
denke den Titel des Topics passe ich an und schiebe es unter allgemein...
-
Wenn du loglevel auf debug gesetzt hast ist das klar, das die Logs so groß werden.
Lass von syslog und daemon.log die Finger. Reinschauen, aber nix löschen.
