[vz-users] vzlogger produziert Fehlermeldungen
applicationMGR
applicationMGR at ecoCuyo.de
Fr Apr 21 11:35:01 CEST 2023
Hallo,
die Speicherauslastung des RAM ist hoch steigt langsam aber stetig an, bis er (rand-)voll läuft:
Gestern Abend:
top - 20:20:01 up 27 min, 1 user, load average: 0,00, 0,04, 0,04
Tasks: 144 total, 1 running, 143 sleeping, 0 stopped, 0 zombie
%CPU(s): 0,6 us, 1,3 sy, 0,0 ni, 97,9 id, 0,0 wa, 0,0 hi, 0,2 si, 0,0 st
MiB Spch: 965,6 total, 541,0 free, 224,2 used, 200,4 buff/cache
MiB Swap: 0,0 total, 0,0 free, 0,0 used. 687,1 avail Spch
PID USER PR NI VIRT RES SHR S %CPU %MEM ZEIT+ BEFEHL
442 avahi 20 0 6916 2644 2384 S 1,3 0,3 0:00.81 avahi-daemon
821 vzlogger 20 0 120276 10904 9780 S 1,3 1,1 0:14.76 vzlogger
474 root 20 0 92200 35064 15788 S 1,0 3,5 0:09.51 php
Soeben:
top - 10:05:40 up 14:12, 1 user, load average: 0,05, 0,06, 0,06
Tasks: 142 total, 1 running, 141 sleeping, 0 stopped, 0 zombie
%CPU(s): 0,6 us, 0,4 sy, 0,0 ni, 99,0 id, 0,0 wa, 0,0 hi, 0,0 si, 0,0 st
MiB Spch: 965,6 total, 118,5 free, 532,6 used, 314,5 buff/cache
MiB Swap: 0,0 total, 0,0 free, 0,0 used. 375,1 avail Spch
PID USER PR NI VIRT RES SHR S %CPU %MEM ZEIT+ BEFEHL
18289 vzlogger 20 0 120276 11844 10716 S 1,3 1,2 0:05.05 vzlogger
474 root 20 0 354860 295708 15788 S 1,0 29,9 7:36.80 php
Mit kam der Gedanke, dass das ggf. an der Aggregation liegen könnte (in vzlogger.conf aggtime 60 Sekunden):
*/10 * * * * flock -n /tmp/flock-vz_aggregate.lock php /var/www/volkszaehler.org/misc/tools/aggregate.php run -m delta -l minute >/dev/null
1 * * * * flock -n /tmp/flock-vz_aggregate.lock php /var/www/volkszaehler.org/misc/tools/aggregate.php run -m delta -l hour >/dev/null
0 1 * * * flock -n /tmp/flock-vz_aggregate.lock php /var/www/volkszaehler.org/misc/tools/aggregate.php run -m delta -l day >/dev/null
Durch den Wrapper sollten sich die php-cron-Jobs bei Performance eigentlich nicht stapeln oder doch?
Im Moment läuft der Logger störungsfrei und die CPU dreht größtenteils Däumchen…
$ vmstat 5
procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
r b swpd frei buff Cache si so bi bo in cs us sy id wa st
1 0 0 124836 42384 280104 0 0 1 1 191 112 0 0 99 0 0
0 0 0 124584 42384 280104 0 0 0 5 4874 1458 0 0 99 0 0
0 0 0 124584 42384 280104 0 0 0 0 4540 1185 0 0 100 0 0
0 0 0 124360 42384 280108 0 0 0 1 5120 1553 1 1 99 0 0
0 0 0 124360 42388 280108 0 0 0 8 4964 1968 0 0 100 0 0
0 0 0 124360 42388 280104 0 0 0 0 5052 1552 1 1 98 0 0
1 0 0 124136 42396 280104 0 0 0 19 5202 1584 0 0 99 0 0
0 0 0 124136 42396 280104 0 0 0 2 4804 1657 0 1 99 0 0
0 0 0 124136 42396 280104 0 0 0 5 5036 1929 0 1 99 0 0
0 0 0 124136 42396 280104 0 0 0 0 5088 1745 0 0 99 0 0
0 0 0 124136 42396 280104 0 0 0 45 5064 1872 1 0 99 0 0
0 0 0 124136 42404 280104 0 0 0 6 4880 1631 0 1 99 0 0
0 0 0 124136 42404 280104 0 0 0 5 5487 2082 1 2 98 0 0
0 0 0 124136 42408 280104 0 0 0 17 4880 1601 0 0 100 0 0
0 0 0 124136 42408 280104 0 0 0 0 5251 1271 0 1 99 0 0
Kann das am push-server liegen?
Bei einer anderen Installation auf einem Raspi 4 mit 8GB sieht das ähnlich aus: Da frisst php >2GB Memory - das hätte dem kleinen Raspi 3 bereits den Garaus gemacht.
top - 19:44:49 up 88 days, 6:13, 3 users, load average: 0.32, 0.53, 0.57
Tasks: 190 total, 1 running, 188 sleeping, 0 stopped, 1 zombie
%CPU(s): 7.4 us, 1.9 sy, 0.8 ni, 89.6 id, 0.3 wa, 0.0 hi, 0.1 si, 0.0 st
MiB Spch: 7899.4 total, 263.7 free, 3618.9 used, 4016.8 buff/cache
MiB Swap: 100.0 total, 97.2 free, 2.8 used. 3991.1 avail Spch
PID USER PR NI VIRT RES SHR S %CPU %MEM ZEIT+ BEFEHL
1208 pi 20 0 1667904 366952 47704 S 20.1 4.5 5810:57 lxpanel
20400 vzlogger 20 0 103884 11892 10748 S 4.9 0.1 93:57.30 vzlogger
14555 pi 30 10 10152 6544 3744 S 4.6 0.1 0:20.08 shadebobs
539 root 20 0 2992672 2.8g 15860 S 3.3 36.2 4048:36 php
1202 pi 20 0 354884 85812 60576 S 2.6 1.1 1629:17 mutter
12485 root 20 0 0 0 0 I 2.6 0.0 0:36.09 kworker/u8:1-events_unbound
1037 root 20 0 301976 54052 32336 S 2.0 0.7 20173:10 Xorg
668 root 20 0 81516 25808 15528 S 1.0 0.3 1185:13 php
13541 root 20 0 86032 29608 15928 S 1.0 0.4 0:00.75 php
627 mysql 20 0 602432 203564 18972 S 0.7 2.5 1353:17 mariadbd
14307 root 20 0 0 0 0 I 0.7 0.0 0:10.32 kworker/u8:0-events_unbound
14790 pi 20 0 11628 3364 2608 R 0.7 0.0 0:00.36 top
16102 www-data 20 0 240104 7704 3128 S 0.7 0.1 1:11.35 apache2
14388 root 20 0 0 0 0 I 0.3 0.0 0:00.03 kworker/1:2-events
1 root 20 0 33984 9052 7028 S 0.0 0.1 23:48.76 systemd
Auch bei diesem Raspi4-System ist der Arbeitsspeicher nach vzlogger Neusart wieder frei:
top - 11:28:39 up 15:05, 4 users, load average: 0.26, 0.31, 0.52
Tasks: 193 total, 1 running, 192 sleeping, 0 stopped, 0 zombie
%CPU(s): 6.4 us, 3.2 sy, 0.8 ni, 88.8 id, 0.4 wa, 0.0 hi, 0.3 si, 0.0 st
MiB Spch: 7899.4 total, 6683.4 free, 428.5 used, 787.5 buff/cache
MiB Swap: 100.0 total, 100.0 free, 0.0 used. 7211.0 avail Spch
Wo muss ich da weiter bohren, um der Ursache auf den Grund zu gehen?
Beste Grüße & schönes WE
Armin
> Am 20.04.2023 um 23:13 schrieb Maik Weidemann <m+vz at weidemann.online>:
>
> Hi,
>
> die Fehlermeldung deutet auf ein Problem mit der Datenbank hin. Dort soll etwas geschrieben werden, was schon existiert.
>
> Gruß
> Maik
>
>
> Am 20.04.23 um 15:23 schrieb applicationMGR:
>> Hallo,
>>
>> habe eben wieder ins Log des vzloggers geschaut, weil das Frontend nicht so recht funktioniert und es scheint Probleme mit der Middleware bei chn0 und chn4 zu geben (siehe vzlogger.conf weiter unten).
>>
>> Hat jemand damit Erfahrung und weiß möglicherweise, woher das kommen kann?
>>
>> [Apr 20 11:36:41][chn0] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
>> [Apr 20 11:36:41][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>> [Apr 20 11:37:40][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>> [Apr 20 11:37:41][chn0] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
>> [Apr 20 11:38:41][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>> [Apr 20 11:38:41][chn0] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
>> [Apr 20 11:39:52][chn0] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
>> [Apr 20 11:39:55][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>> [Apr 20 11:41:06][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>> [Apr 20 11:41:08][chn0] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
>> [Apr 20 11:41:40][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>> [Apr 20 11:41:41][chn0] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
>> [Apr 20 11:42:40][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>> [Apr 20 11:42:41][chn0] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
>> [Apr 20 11:43:40][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>> [Apr 20 11:44:41][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>> [Apr 20 11:45:41][chn4] CURL Error from middleware: 'UniqueConstraintViolationException': 'An exception occurred while executing 'INSERT INTO data (channel_id, timestamp, value) VALUES (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>>
>> Freue mich über Eure Hilfe!
>>
>> Viele Grüße
>> Armin
>>
>>
>>> Anfang der weitergeleiteten Nachricht:
>>>
>>> Von: applicationMGR <applicationMGR at ecoCuyo.de <mailto:applicationMGR at ecoCuyo.de>>
>>> Betreff: Aw: Push-Server sendet keine Null-Werte
>>> Datum: 17. April 2023 um 19:59:04 MESZ
>>> An: volkszaehler-users <volkszaehler-users at demo.volkszaehler.org <mailto:volkszaehler-users at demo.volkszaehler.org>>
>>>
>>> Hallo,
>>>
>>> kann es ein Performance-Problem mit der MariaDB sein? Die Installation läuft auf einem Raspberry Pi 3 Model B Rev 1.2 mit SanDisk Ultra 16 GB microSDHC Memory Card.
>>>
>>> Die Datenbank selbst scheint beim Neustart heute Morgen i.O:
>>>
>>> Apr 17 10:19:32 ecoRaspi01 systemd[1]: Starting MariaDB 10.5.15 database server...
>>> Apr 17 10:19:34 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:34 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.15-MariaDB-0+deb11u1) starting as process 560 ...
>>> Apr 17 10:19:34 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:34 0 [Note] InnoDB: Uses event mutexes
>>> Apr 17 10:19:34 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:34 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: Number of pools: 1
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: Using generic crc32 instructions
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: Using Linux native AIO
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: Completed initialization of buffer pool
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: 128 rollback segments are active.
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: Creating shared tablespace for temporary tables
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: 10.5.15 started; log sequence number 988900435; transaction id 1390134
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] Plugin 'FEEDBACK' is disabled.
>>> Apr 17 10:19:35 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:35 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
>>> Apr 17 10:19:36 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:36 0 [Note] Server socket created on IP: '127.0.0.1'.
>>> Apr 17 10:19:36 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:36 0 [Note] Reading of all Master_info entries succeeded
>>> Apr 17 10:19:36 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:36 0 [Note] Added new Master_info '' to hash table
>>> Apr 17 10:19:36 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:36 0 [Note] /usr/sbin/mariadbd: ready for connections.
>>> Apr 17 10:19:36 ecoRaspi01 mariadbd[560]: Version: '10.5.15-MariaDB-0+deb11u1' socket: '/run/mysqld/mysqld.sock' port: 3306 Raspbian 11
>>> Apr 17 10:19:37 ecoRaspi01 mariadbd[560]: 2023-04-17 10:19:37 0 [Note] InnoDB: Buffer pool(s) load completed at 230417 10:19:37
>>> Apr 17 10:19:38 ecoRaspi01 systemd[1]: Started MariaDB 10.5.15 database server.
>>> Apr 17 10:19:38 ecoRaspi01 /etc/mysql/debian-start[652]: This installation of MariaDB is already upgraded to 10.5.15-MariaDB.
>>> Apr 17 10:19:38 ecoRaspi01 /etc/mysql/debian-start[652]: There is no need to run mysql_upgrade again for 10.5.15-MariaDB.
>>>
>>>
>>> Im syslog standen davor unzählige Errors:
>>>
>>> Apr 17 08:44:23 MeinHost mariadbd[559]: 2023-04-17 8:43:29 2046 [Warning] Aborted connection 2046 to db: 'volkszaehler' user: 'vz' host: 'localhost' (Got an error reading communication packets)
>>> Apr 17 08:44:26 MeinHost mariadbd[559]: 2023-04-17 8:43:38 2047 [Warning] Aborted connection 2047 to db: 'volkszaehler' user: 'vz' host: 'localhost' (Got an error reading communication packets)
>>> Apr 17 08:44:31 MeinHost mariadbd[559]: 2023-04-17 8:44:04 2048 [Warning] Aborted connection 2048 to db: 'volkszaehler' user: 'vz' host: 'localhost' (Got an error reading communication packets)
>>> Apr 17 08:44:36 MeinHost mariadbd[559]: 2023-04-17 8:44:05 2049 [Warning] Aborted connection 2049 to db: 'volkszaehler' user: 'vz' host: 'localhost' (Got an error reading communication packets)
>>> Apr 17 08:44:40 MeinHost mariadbd[559]: 2023-04-17 8:44:16 2050 [Warning] Aborted connection 2050 to db: 'volkszaehler' user: 'vz' host: 'localhost' (Got an error reading communication packets)
>>> Apr 17 08:44:42 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info] User Deprecated: Method "Psr\Http\Message\RequestInterface::getMethod()" might add "string" as a native return type declaration in the future. Do the same in implementation "RingCentral\Psr7\Request" now to avoid errors or add an explicit @return annotation to suppress this message.
>>> Apr 17 08:44:44 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info] User Deprecated: Method "Psr\Http\Message\RequestInterface::withMethod()" might add "static" as a native return type declaration in the future. Do the same in implementation "RingCentral\Psr7\Request" now to avoid errors or add an explicit @return annotation to suppress this message.
>>> Apr 17 08:44:47 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info] User Deprecated: Method "Psr\Http\Message\RequestInterface::getUri()" might add "UriInterface" as a native return type declaration in the future. Do the same in implementation "RingCentral\Psr7\Request" now to avoid errors or add an explicit @return annotation to suppress this message.
>>> Apr 17 08:44:52 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info] User Deprecated: Method "Psr\Http\Message\RequestInterface::withUri()" might add "static" as a native return type declaration in the future. Do the same in implementation "RingCentral\Psr7\Request" now to avoid errors or add an explicit @return annotation to suppress this message.
>>> Apr 17 08:44:58 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info] User Deprecated: Method "Psr\Http\Message\MessageInterface::withHeader()" might add "static" as a native return type declaration in the future. Do the same in implementation "RingCentral\Psr7\Request" now to avoid errors or add an explicit @return annotation to suppress this message.
>>> Apr 17 08:45:04 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info] User Deprecated: Method "Psr\Http\Message\ServerRequestInterface::getServerParams()" might add "array" as a native return type declaration in the future. Do the same in implementation "React\Http\Message\ServerRequest" now to avoid errors or add an explicit @return annotation to suppress this message.
>>>
>>> Sagt das jemanden etwas hinsichtlich wo ich den/die Fehler suchen muss?
>>>
>>> Viele Grüße
>>> Armin
>>>
>>>
>>>
>>>> Am 17.04.2023 um 11:20 schrieb applicationMGR <applicationMGR at ecoCuyo.de <mailto:applicationMGR at ecoCuyo.de>>:
>>>>
>>>> Hallo,
>>>>
>>>> seit der Umsrtellung auf vzlogger v0.8.1 based on heads/direction_from_status-0-g408df91556 from Sun, 15 Jan 2023 02:00:27 +0100 laufen in der vzlogger.log massenhaft Fehler auf und der Server stürzt regelmäßig ab.
>>>>
>>>>
>>>> $ tail -f /var/log/vzlogger/vzlogger.log
>>>> [Apr 17 10:16:15][chn1] CURL: Timeout was reached
>>>> [Apr 17 10:16:45][chn2] CURL: Timeout was reached
>>>> [Apr 17 10:17:16][chn3] CURL: Timeout was reached
>>>> [Apr 17 10:17:31][chn0] CURL Error from middleware: unexpected character
>>>> [Apr 17 10:18:02][chn2] CURL: Timeout was reached
>>>> [Apr 17 10:18:04][push] CURL: http://127.0.0.1:5582 <http://127.0.0.1:5582/> Timeout was reached
>>>> [Apr 17 10:18:33][chn3] CURL: Timeout was reached
>>>> [Apr 17 10:18:57][push] CURL: http://127.0.0.1:5582 <http://127.0.0.1:5582/> Timeout was reached
>>>> [Apr 17 10:19:03][chn0] CURL: Timeout was reached
>>>> [Apr 17 10:19:18][push] CURL: http://127.0.0.1:5582 <http://127.0.0.1:5582/> Failure when receiving data from the peer
>>>>
>>>> Die Konfiguration sieht so aus:
>>>>
>>>> {
>>>> "verbosity": 1,
>>>> "log": "/var/log/vzlogger/vzlogger.log",
>>>> "retry": 30,
>>>>
>>>> "local": {
>>>> "enabled": true,
>>>> "port": 8081,
>>>> "index": true,
>>>> "timeout": 30,
>>>> "buffer": -2
>>>> },
>>>>
>>>> "push": [
>>>> {
>>>> "url": "http://127.0.0.1:5582 <http://127.0.0.1:5582/>"
>>>> }
>>>> ],
>>>>
>>>> "mqtt": {
>>>> "enabled": false, // enable mqtt client. needs host and port as well
>>>> "host": "test.mosquitto.org <http://test.mosquitto.org/>", // mqtt server addr
>>>> "port": 1883, // 1883 for unencrypted, 8883 enc, 8884 enc cert needed,
>>>> "cafile": "", // optional file with server CA
>>>> "capath": "", // optional path for server CAs. see mosquitto.conf. Specify only cafile or capath
>>>> "certfile": "", // optional file for your client certificate (e.g. client.crt)
>>>> "keyfile": "", // optional path for your client certficate private key (e.g. client.key)
>>>> "keypass": "", // optional password for your private key
>>>> "keepalive": 30, // optional keepalive in seconds.
>>>> "topic": "vzlogger/data", // optional topic dont use $ at start and no / at end
>>>> "id": "", // optional static id, if not set "vzlogger_<pid>" will be used
>>>> "user": "", // optional user name for the mqtt server
>>>> "pass": "", // optional password for the mqtt server
>>>> "retain": false, // optional use retain message flag
>>>> "rawAndAgg": false, // optional publish raw values even if agg mode is used
>>>> "qos": 0, // optional quality of service, default is 0
>>>> "timestamp": false // optional whether to include a timestamp in the payload
>>>> },
>>>>
>>>> "meters": [
>>>> {
>>>> "enabled" : true,
>>>> "protocol" : "sml",
>>>> "device" : "/dev/usb-ir-lesekopf0",
>>>> "aggtime" : 60,
>>>> "aggfixedinterval" : true,
>>>> "channels": [{
>>>> "uuid" : „8c4d02b0-xxxx-xxxx-xxxxxxxxxxxx",
>>>> "middleware" : "http://localhost/middleware.php <http://localhost/middleware.php>",
>>>> "identifier" : "1-0:2.8.0", /* PV-2.8.0-Erzeugung */
>>>> "duplicates": 3600,
>>>> "aggmode" : "AVG"
>>>> }, {
>>>> "uuid" : "6c9c10a0--xxxx-xxxx-xxxxxxxxxxxx",
>>>> "middleware" : "http://localhost/middleware.php <http://localhost/middleware.php>",
>>>> "identifier" : "1-0:15.7.0", /* PV-15.7.0-Wirkleistung */
>>>> "aggmode" : "AVG"
>>>> }]
>>>> }, {
>>>> "enabled" : true,
>>>> "protocol" : "sml",
>>>> "device" : "/dev/usb-ir-lesekopf1",
>>>> "direction_from_status": true,
>>>> "aggtime" : 60,
>>>> "aggfixedinterval" : true,
>>>> "channels" :[{
>>>> "uuid" : "b9693e00-xxxx-xxxx-xxxxxxxxxxxx",
>>>> "middleware" : "http://localhost/middleware.php <http://localhost/middleware.php>",
>>>> "identifier" : "1-0:1.8.0", /* Haus-1.8.0-Bezug */
>>>> "duplicates": 3600,
>>>> "aggmode" : "AVG"
>>>> }, {
>>>> "uuid" : "ec7c7360-xxxx-xxxx-xxxxxxxxxxxx",
>>>> "middleware" : "http://localhost/middleware.php <http://localhost/middleware.php>",
>>>> "identifier" : "1-0:2.8.0", /* Haus-2.8.0-Lieferung */
>>>> "duplicates": 3600,
>>>> "aggmode" : "AVG"
>>>> }, {
>>>> "uuid" : "61d5d350-xxxx-xxxx-xxxxxxxxxxxx",
>>>> "middleware" : "http://localhost/middleware.php <http://localhost/middleware.php>",
>>>> "identifier" : "1-0:15.7.0", /* Haus-15.7.0-Wirkleistung */
>>>> "duplicates": 3600,
>>>> "aggmode" : "AVG"
>>>> }]
>>>> }
>>>> ]
>>>> }
>>>>
>>>> Hat jemand eine Ahnung, was ich da ändern könnte, um wieder Stabilität ins System zu bringen?
>>>>
>>>> Viele Grüße
>>>> Armin
>>>>
>>>>
>>>>
>>>>
>>>>> Am 02.04.2023 um 17:43 schrieb Emilio ecoCuyo <Emilio at ecoCuyo.de <mailto:Emilio at ecoCuyo.de>>:
>>>>>
>>>>> Hallo zusammen,
>>>>>
>>>>> versuche aktuell per vzlogger push eine Installation von evcc zu versorgen, um eine Wallbox PV-geführt zu betreiben.
>>>>> Dabei entsteht ein Problem mit dem verwendeten EMH Zweirichtungszähler, der den Wert der aktuellen Wirkleistung nur vorzeichenlos ausgibt, wodurch anhand dieses Werts nicht klar wird, ob Bezug oder Lieferung stattfindet.
>>>>>
>>>>> Beim Debuggen mit verbosity 15 konnte ich nachvollziehen, dass zwar die Energiewerte aller angelegten Kanäle ge-pushed werden(mtr1 ist der Zeirichtungszähler). Im Log sieht man an den OBIS Codes, dass sämtliche Zählerwerte als Energiewerte in Wh sowie die aktuelle Leistung in W ausgegeben werden, auf wenn kein Verbrauch auf der UUID für "Bezug" stattfand.
>>>>>
>>>>> [Mar 27 16:20:10][mtr1] Reading: id=1-0:1.8.0*255/ObisIdentifier:1-0:1.8.0*255 value=17886641.20 ts=1679926810623
>>>>> [Mar 27 16:20:10][mtr1] Reading: id=1-0:2.8.0*255/ObisIdentifier:1-0:2.8.0*255 value=62185513.20 ts=1679926810623
>>>>> [Mar 27 16:20:10][mtr1] Reading: id=1-0:1.8.1*255/ObisIdentifier:1-0:1.8.1*255 value=17886641.20 ts=1679926810623
>>>>> [Mar 27 16:20:10][mtr1] Reading: id=1-0:2.8.1*255/ObisIdentifier:1-0:2.8.1*255 value=62185513.30 ts=1679926810623
>>>>> [Mar 27 16:20:10][mtr1] Reading: id=1-0:1.8.2*255/ObisIdentifier:1-0:1.8.2*255 value=0.00 ts=1679926810623
>>>>> [Mar 27 16:20:10][mtr1] Reading: id=1-0:15.7.0*255/ObisIdentifier:1-0:15.7.0*255 value=3448.40 ts=1679926810623
>>>>> [Mar 27 16:20:10][chn1] Adding reading to queue (value=17886641.20 ts=1679926810623)
>>>>> [Mar 27 16:20:10][push] added to uuid xxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>> [Mar 27 16:20:10][chn2] Adding reading to queue (value=62185513.20 ts=1679926810623)
>>>>> [Mar 27 16:20:10][push] added to uuid yyyyyyyyyyyyyyyyyyyyyyy
>>>>> [Mar 27 16:20:10][chn3] Adding reading to queue (value=3448.40 ts=1679926810623)
>>>>> [Mar 27 16:20:10][push] added to uuid zzzzzzzzzzzzzzzzzzzzzzzzzzz
>>>>> [Mar 27 16:20:10][push] push: { "data": [ { "uuid": "zzzzzzzzzzzzzzzzzzzzzzzzzzz", "tuples": [ [ 1679926810623, 3448.4000000000001 ] ] }, { "uuid": "yyyyyyyyyyyyyyyyyyyyyyy", "tuples": [ [ 1679926810623, 62185513.200000003 ] ] }, { "uuid": "xxxxxxxxxxxxxxxxxxxxxxxxxxx", "tuples": [ [ 1679926810623, 17886641.199999999 ] ] } ] }
>>>>>
>>>>> Leider wird wie mir scheint dann beim push für einen unveränderten Energiezähler kein Wert Null für die Leistung ausgegeben, die aus dem Differential der letzten beiden tuples berechnet wird. Ist ja eigentlich auch nicht nötig… doch manchmal eben doch.
>>>>>
>>>>> Das Thema habe ich auch in https://github.com/evcc-io/evcc/discussions/6021 <https://github.com/evcc-io/evcc/discussions/6021> adressiert, weil das Problem eigentlich das Plugin "calc" von evcc ist. Doch bislang hatte da noch niemand eine zündende Idee.
>>>>>
>>>>> Vielleicht weiß jemand weiter? So etwas wie send_zero wie beim S0-Protokoll gibt’s wohl nicht?
>>>>>
>>>>> Viele Grüße
>>>>> Armin
>>>>
>>>
>>
>
-------------- nächster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://demo.volkszaehler.org/pipermail/volkszaehler-users/attachments/20230421/da5992f9/attachment-0001.html>
Mehr Informationen über die Mailingliste volkszaehler-users