openWB Forum

Die modulare Wallbox
https://forum.openwb.de/

openWB braucht sehr lange zum Laden der Seiten

https://forum.openwb.de/viewtopic.php?t=6697

Seite 1 von 1

openWB braucht sehr lange zum Laden der Seiten

Verfasst: So Mär 19, 2023 12:53 pm
von Mafaldo
openWB Standard 2.0
sw. version 294

vielleicht noch wichtig:
IP KSEM: 192.168.178.112
IP Plenticore: 192.168.178.21
IP Piko: 192.168.178.111

vor ein paar Tagen bemerkte ich dass die Hauptseite nur langsam geladen wurde.
Seit heute dauert es über eine Minute. Mal werden die Seiten zügig aufgerufen
und beim nächsten Klick ist wieder warten angesagt oder es kam die Meldung
dass der Server nicht antwortete.

Ein Blick ins Log ergab folgendes:

Code: Alles auswählen

During handling of the above exception, another exception occurred:

pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.21:1502)]
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/sync.py", line 107, in execute
return self.execute(request)
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/common.py", line 114, in read_holding_registers
data = self._client.read_holding_registers(addr, 2, unit=71)
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 89, in ReadFloat32
self.attr_KSEM.I_P1_A = round(self.ReadFloat32(222), 2)
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 302, in ReadKSEM300
Traceback (most recent call last):
2023-03-19 02:23:45: PID: 3400: legacy run server: Unhandled exception
2023-03-19 02:23:45: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.21, 1502) failed: timed out
2023-03-19 02:21:50: PID: 25925: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-19 02:20:03: PID: 13048: ##### cron5min.sh finished ##### (LV0)
2023-03-19 02:20:02: PID: 13291: Starting OpenWB services (LV0)
2023-03-19 02:20:01: PID: 13048: ##### cron5min.sh started ##### (LV0)
2023-03-19 02:15:03: PID: 6906: ##### cron5min.sh finished ##### (LV0)
2023-03-19 02:15:02: PID: 7152: Starting OpenWB services (LV0)
2023-03-19 02:15:02: PID: 6906: ##### cron5min.sh started ##### (LV0)
2023-03-19 02:10:03: PID: 700: ##### cron5min.sh finished ##### (LV0)
2023-03-19 02:10:02: PID: 945: Starting OpenWB services (LV0)
2023-03-19 02:10:01: PID: 700: ##### cron5min.sh started ##### (LV0)
2023-03-19 02:05:03: PID: 26949: ##### cron5min.sh finished ##### (LV0)
2023-03-19 02:05:01: PID: 27192: Starting OpenWB services (LV0)
2023-03-19 02:05:01: PID: 26949: ##### cron5min.sh started ##### (LV0)
2023-03-19 02:02:30: PID: 6583: **** WARNING **** Regulation loop needs 8 seconds (LV0)
AttributeError: 'plenticore' object has no attribute 'IP'
+ "(falsche WR-IP?)" + str(sys.exc_info()[0]))
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 345, in ReadKSEM300
WR1.ReadKSEM300()
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 406, in update
parser.set_defaults(RUN=lambda args: function(*[getattr(args, argument_name) for argument_name in arg_spec.args]))
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 19, in <lambda>
args.RUN(args)
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 34, in run_using_positional_cli_args
run_using_positional_cli_args(update, argv)
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 630, in main
importlib.import_module(parsed[0]).main(parsed[1:])
File "/var/www/html/openWB/packages/legacy_run_server.py", line 109, in handle_message
self.__callback(read_all_bytes(connection))
File "/var/www/html/openWB/packages/legacy_run_server.py", line 87, in handle_connection
yield
File "/var/www/html/openWB/packages/legacy_run_server.py", line 48, in redirect_stdout_stderr_exceptions_to_log
Traceback (most recent call last):

During handling of the above exception, another exception occurred:

pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.21:1502)]
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/sync.py", line 107, in execute
return self.execute(request)
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/common.py", line 114, in read_holding_registers
data = self._client.read_holding_registers(addr, 2, unit=71)
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 89, in ReadFloat32
self.attr_KSEM.I_P1_A = round(self.ReadFloat32(222), 2)
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 302, in ReadKSEM300
Traceback (most recent call last):
2023-03-19 02:02:26: PID: 3400: legacy run server: Unhandled exception
2023-03-19 02:02:26: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.21, 1502) failed: timed out
2023-03-19 02:00:03: PID: 20846: ##### cron5min.sh finished ##### (LV0)
2023-03-19 02:00:01: PID: 21080: Starting OpenWB services (LV0)
2023-03-19 02:00:01: PID: 20846: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:55:02: PID: 14723: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:55:01: PID: 14965: Starting OpenWB services (LV0)
2023-03-19 01:55:01: PID: 14723: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:51:33: PID: 20211: **** FATAL ********************************* (LV0)
2023-03-19 01:51:33: PID: 20211: **** FATAL Regulation loop needs 11 seconds (LV0)
2023-03-19 01:51:33: PID: 20211: **** FATAL ********************************* (LV0)
2023-03-19 01:51:31: PID: 20479: Previous regulation loop still running. Skipping. (LV0) at 35 main /var/www/html/openWB/regel.sh
20211
2023-03-19 01:50:02: PID: 9792: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:50:01: PID: 10028: Starting OpenWB services (LV0)
2023-03-19 01:50:01: PID: 9792: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:48:49: PID: 31923: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-19 01:48:19: PID: 28130: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-19 01:45:03: PID: 3666: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:45:02: PID: 3898: Starting OpenWB services (LV0)
2023-03-19 01:45:01: PID: 3666: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:41:39: PID: 9267: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-19 01:40:03: PID: 29886: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:40:02: PID: 30124: Starting OpenWB services (LV0)
2023-03-19 01:40:02: PID: 29886: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:38:00: PID: 13267: **** WARNING **** Regulation loop needs 8 seconds (LV0)
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.112:502)]
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/sync.py", line 119, in __enter__
with self.client:
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 38, in run
runner.run()
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 99, in update
parser.set_defaults(RUN=lambda args: function(*[getattr(args, argument_name) for argument_name in arg_spec.args]))
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 19, in <lambda>
args.RUN(args)
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 34, in run_using_positional_cli_args
run_using_positional_cli_args(update, argv)
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 103, in main
importlib.import_module(parsed[0]).main(parsed[1:])
File "/var/www/html/openWB/packages/legacy_run_server.py", line 109, in handle_message
self.__callback(read_all_bytes(connection))
File "/var/www/html/openWB/packages/legacy_run_server.py", line 87, in handle_connection
yield
File "/var/www/html/openWB/packages/legacy_run_server.py", line 48, in redirect_stdout_stderr_exceptions_to_log
Traceback (most recent call last):
2023-03-19 01:37:59: PID: 3400: legacy run server: Unhandled exception
2023-03-19 01:37:59: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.112, 502) failed: timed out
2023-03-19 01:35:03: PID: 23691: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:35:02: PID: 23940: Starting OpenWB services (LV0)
2023-03-19 01:35:02: PID: 23691: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:30:03: PID: 17585: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:30:01: PID: 17818: Starting OpenWB services (LV0)
2023-03-19 01:30:01: PID: 17585: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:25:03: PID: 11461: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:25:02: PID: 11695: Starting OpenWB services (LV0)
2023-03-19 01:25:01: PID: 11461: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:21:15: PID: 14438: **** FATAL ********************************* (LV0)
2023-03-19 01:21:15: PID: 14438: **** FATAL Regulation loop needs 13 seconds (LV0)
2023-03-19 01:21:15: PID: 14438: **** FATAL ********************************* (LV0)
2023-03-19 01:21:12: PID: 14689: Previous regulation loop still running. Skipping. (LV0) at 35 main /var/www/html/openWB/regel.sh
14438
2023-03-19 01:20:03: PID: 6525: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:20:02: PID: 6758: Starting OpenWB services (LV0)
2023-03-19 01:20:01: PID: 6525: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:15:02: PID: 32716: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:15:01: PID: 502: Starting OpenWB services (LV0)
2023-03-19 01:15:01: PID: 32716: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:11:59: PID: 8525: **** WARNING **** Regulation loop needs 8 seconds (LV0)
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.112:502)]
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/sync.py", line 119, in __enter__
with self.client:
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 38, in run
runner.run()
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 99, in update
parser.set_defaults(RUN=lambda args: function(*[getattr(args, argument_name) for argument_name in arg_spec.args]))
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 19, in <lambda>
args.RUN(args)
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 34, in run_using_positional_cli_args
run_using_positional_cli_args(update, argv)
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 103, in main
importlib.import_module(parsed[0]).main(parsed[1:])
File "/var/www/html/openWB/packages/legacy_run_server.py", line 109, in handle_message
self.__callback(read_all_bytes(connection))
File "/var/www/html/openWB/packages/legacy_run_server.py", line 87, in handle_connection
yield
File "/var/www/html/openWB/packages/legacy_run_server.py", line 48, in redirect_stdout_stderr_exceptions_to_log
Traceback (most recent call last):
2023-03-19 01:11:57: PID: 3400: legacy run server: Unhandled exception
2023-03-19 01:11:57: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.112, 502) failed: timed out
2023-03-19 01:10:03: PID: 26609: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:10:02: PID: 26848: Starting OpenWB services (LV0)
2023-03-19 01:10:01: PID: 26609: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:05:03: PID: 20430: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:05:02: PID: 20657: Starting OpenWB services (LV0)
2023-03-19 01:05:01: PID: 20430: ##### cron5min.sh started ##### (LV0)
2023-03-19 01:02:29: PID: 32391: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-19 01:01:39: PID: 26034: **** WARNING **** Regulation loop needs 8 seconds (LV0)
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.112:502)]
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/sync.py", line 119, in __enter__
with self.client:
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 38, in run
runner.run()
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 99, in update
parser.set_defaults(RUN=lambda args: function(*[getattr(args, argument_name) for argument_name in arg_spec.args]))
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 19, in <lambda>
args.RUN(args)
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 34, in run_using_positional_cli_args
run_using_positional_cli_args(update, argv)
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 103, in main
importlib.import_module(parsed[0]).main(parsed[1:])
File "/var/www/html/openWB/packages/legacy_run_server.py", line 109, in handle_message
self.__callback(read_all_bytes(connection))
File "/var/www/html/openWB/packages/legacy_run_server.py", line 87, in handle_connection
yield
File "/var/www/html/openWB/packages/legacy_run_server.py", line 48, in redirect_stdout_stderr_exceptions_to_log
Traceback (most recent call last):
2023-03-19 01:01:37: PID: 3400: legacy run server: Unhandled exception
2023-03-19 01:01:37: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.112, 502) failed: timed out
2023-03-19 01:00:02: PID: 14308: ##### cron5min.sh finished ##### (LV0)
2023-03-19 01:00:01: PID: 14547: Starting OpenWB services (LV0)
2023-03-19 01:00:01: PID: 14308: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:55:50: PID: 13566: **** WARNING **** Regulation loop needs 8 seconds (LV0)
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.112:502)]
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/sync.py", line 119, in __enter__
with self.client:
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 38, in run
runner.run()
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 99, in update
parser.set_defaults(RUN=lambda args: function(*[getattr(args, argument_name) for argument_name in arg_spec.args]))
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 19, in <lambda>
args.RUN(args)
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 34, in run_using_positional_cli_args
run_using_positional_cli_args(update, argv)
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 103, in main
importlib.import_module(parsed[0]).main(parsed[1:])
File "/var/www/html/openWB/packages/legacy_run_server.py", line 109, in handle_message
self.__callback(read_all_bytes(connection))
File "/var/www/html/openWB/packages/legacy_run_server.py", line 87, in handle_connection
yield
File "/var/www/html/openWB/packages/legacy_run_server.py", line 48, in redirect_stdout_stderr_exceptions_to_log
Traceback (most recent call last):
2023-03-19 00:55:48: PID: 3400: legacy run server: Unhandled exception
2023-03-19 00:55:48: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.112, 502) failed: timed out
2023-03-19 00:55:03: PID: 8191: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:55:02: PID: 8438: Starting OpenWB services (LV0)
2023-03-19 00:55:02: PID: 8191: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:51:49: PID: 15070: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-19 00:50:03: PID: 2007: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:50:02: PID: 2279: Starting OpenWB services (LV0)
2023-03-19 00:50:01: PID: 2007: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:45:03: PID: 28290: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:45:02: PID: 28530: Starting OpenWB services (LV0)
2023-03-19 00:45:01: PID: 28290: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:40:03: PID: 22193: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:40:02: PID: 22424: Starting OpenWB services (LV0)
2023-03-19 00:40:01: PID: 22193: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:39:29: PID: 17090: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-19 00:35:03: PID: 16002: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:35:02: PID: 16243: Starting OpenWB services (LV0)
2023-03-19 00:35:02: PID: 16002: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:30:03: PID: 9890: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:30:02: PID: 10132: Starting OpenWB services (LV0)
2023-03-19 00:30:01: PID: 9890: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:29:10: PID: 2171: **** FATAL ********************************* (LV0)
2023-03-19 00:29:10: PID: 2171: **** FATAL Regulation loop needs 9 seconds (LV0)
2023-03-19 00:29:10: PID: 2171: **** FATAL ********************************* (LV0)
2023-03-19 00:26:43: PID: 16761: Modbus EVSE read CP1 issue - using previous state '1' (LV0)
2023-03-19 00:25:03: PID: 3751: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:25:02: PID: 4009: Starting OpenWB services (LV0)
2023-03-19 00:25:02: PID: 3751: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:20:34: PID: 1563: **** FATAL ********************************* (LV0)
2023-03-19 00:20:34: PID: 1563: **** FATAL Regulation loop needs 13 seconds (LV0)
2023-03-19 00:20:34: PID: 1563: **** FATAL ********************************* (LV0)
2023-03-19 00:20:31: PID: 1879: Previous regulation loop still running. Skipping. (LV0) at 35 main /var/www/html/openWB/regel.sh
1563
2023-03-19 00:20:03: PID: 31157: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:20:01: PID: 31398: Starting OpenWB services (LV0)
2023-03-19 00:20:01: PID: 31157: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:15:03: PID: 25037: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:15:02: PID: 25275: Starting OpenWB services (LV0)
2023-03-19 00:15:02: PID: 25037: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:13:19: PID: 11019: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-19 00:13:15: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.111, 1502) failed: timed out
2023-03-19 00:10:03: PID: 18925: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:10:02: PID: 19160: Starting OpenWB services (LV0)
2023-03-19 00:10:01: PID: 18925: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:05:03: PID: 12746: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:05:02: PID: 12979: Starting OpenWB services (LV0)
2023-03-19 00:05:01: PID: 12746: ##### cron5min.sh started ##### (LV0)
2023-03-19 00:01:49: PID: 19596: **** WARNING **** Regulation loop needs 8 seconds (LV0)
Trigger update of logfiles...
Not deleting randomSleepValue of "0"
Start cron nightly @ So 19. Mär 00:01:01 CET 2023
2023-03-19 00:00:03: PID: 6517: ##### cron5min.sh finished ##### (LV0)
2023-03-19 00:00:02: PID: 6762: Starting OpenWB services (LV0)
2023-03-19 00:00:01: PID: 6517: ##### cron5min.sh started ##### (LV0)
2023-03-18 23:55:03: PID: 32744: ##### cron5min.sh finished ##### (LV0)
2023-03-18 23:55:02: PID: 546: Starting OpenWB services (LV0)
2023-03-18 23:55:01: PID: 32744: ##### cron5min.sh started ##### (LV0)
2023-03-18 23:50:03: PID: 26625: ##### cron5min.sh finished ##### (LV0)
2023-03-18 23:50:02: PID: 26868: Starting OpenWB services (LV0)
2023-03-18 23:50:01: PID: 26625: ##### cron5min.sh started ##### (LV0)
2023-03-18 23:45:02: PID: 20532: ##### cron5min.sh finished ##### (LV0)
2023-03-18 23:45:01: PID: 20757: Starting OpenWB services (LV0)
2023-03-18 23:45:01: PID: 20532: ##### cron5min.sh started ##### (LV0)
2023-03-18 23:40:19: PID: 15965: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-18 23:40:03: PID: 14406: ##### cron5min.sh finished ##### (LV0)
2023-03-18 23:40:02: PID: 14654: Starting OpenWB services (LV0)
2023-03-18 23:40:01: PID: 14406: ##### cron5min.sh started ##### (LV0)
2023-03-18 23:35:03: PID: 8235: ##### cron5min.sh finished ##### (LV0)
2023-03-18 23:35:02: PID: 8465: Starting OpenWB services (LV0)
2023-03-18 23:35:01: PID: 8235: ##### cron5min.sh started ##### (LV0)
2023-03-18 23:33:59: PID: 31615: **** WARNING **** Regulation loop needs 8 seconds (LV0)
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.112:502)]
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/sync.py", line 119, in __enter__
with self.client:
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 38, in run
runner.run()
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 99, in update
parser.set_defaults(RUN=lambda args: function(*[getattr(args, argument_name) for argument_name in arg_spec.args]))
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 19, in <lambda>
args.RUN(args)
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 34, in run_using_positional_cli_args
run_using_positional_cli_args(update, argv)
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 103, in main
importlib.import_module(parsed[0]).main(parsed[1:])
File "/var/www/html/openWB/packages/legacy_run_server.py", line 109, in handle_message
self.__callback(read_all_bytes(connection))
File "/var/www/html/openWB/packages/legacy_run_server.py", line 87, in handle_connection
yield
File "/var/www/html/openWB/packages/legacy_run_server.py", line 48, in redirect_stdout_stderr_exceptions_to_log
Traceback (most recent call last):
2023-03-18 23:33:58: PID: 3400: legacy run server: Unhandled exception
2023-03-18 23:33:57: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.112, 502) failed: timed out
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.112:502)]
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/sync.py", line 119, in __enter__
with self.client:
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 38, in run
runner.run()
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 99, in update
parser.set_defaults(RUN=lambda args: function(*[getattr(args, argument_name) for argument_name in arg_spec.args]))
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 19, in <lambda>
args.RUN(args)
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 34, in run_using_positional_cli_args
run_using_positional_cli_args(update, argv)
File "/var/www/html/openWB/modules/bezug_ksem/readksem.py", line 103, in main
importlib.import_module(parsed[0]).main(parsed[1:])
File "/var/www/html/openWB/packages/legacy_run_server.py", line 109, in handle_message
self.__callback(read_all_bytes(connection))
File "/var/www/html/openWB/packages/legacy_run_server.py", line 87, in handle_connection
yield
File "/var/www/html/openWB/packages/legacy_run_server.py", line 48, in redirect_stdout_stderr_exceptions_to_log
Traceback (most recent call last):
2023-03-18 23:32:17: PID: 3400: legacy run server: Unhandled exception
2023-03-18 23:32:17: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.112, 502) failed: timed out
2023-03-18 23:30:02: PID: 2028: ##### cron5min.sh finished ##### (LV0)
2023-03-18 23:30:01: PID: 2290: Starting OpenWB services (LV0)
2023-03-18 23:30:01: PID: 2028: ##### cron5min.sh started ##### (LV0)
2023-03-18 23:27:00: PID: 10232: **** FATAL ********************************* (LV0)
2023-03-18 23:27:00: PID: 10232: **** FATAL Regulation loop needs 9 seconds (LV0)
2023-03-18 23:27:00: PID: 10232: **** FATAL ********************************* (LV0)
2023-03-18 23:25:02: PID: 28331: ##### cron5min.sh finished ##### (LV0)
2023-03-18 23:25:01: PID: 28556: Starting OpenWB services (LV0)
2023-03-18 23:25:01: PID: 28331: ##### cron5min.sh started ##### (LV0)
2023-03-18 23:24:13: PID: 21967: Modbus EVSE read CP1 issue - using previous state '1' (LV0)
AttributeError: 'plenticore' object has no attribute 'IP'
+ "(falsche WR-IP?)" + str(sys.exc_info()[0]))
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 345, in ReadKSEM300
WR1.ReadKSEM300()
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 406, in update
parser.set_defaults(RUN=lambda args: function(*[getattr(args, argument_name) for argument_name in arg_spec.args]))
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 19, in <lambda>
args.RUN(args)
File "/var/www/html/openWB/packages/helpermodules/cli/_run_using_positional_cli_args.py", line 34, in run_using_positional_cli_args
run_using_positional_cli_args(update, argv)
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 630, in main
importlib.import_module(parsed[0]).main(parsed[1:])
File "/var/www/html/openWB/packages/legacy_run_server.py", line 109, in handle_message
self.__callback(read_all_bytes(connection))
File "/var/www/html/openWB/packages/legacy_run_server.py", line 87, in handle_connection
yield
File "/var/www/html/openWB/packages/legacy_run_server.py", line 48, in redirect_stdout_stderr_exceptions_to_log
Traceback (most recent call last):

During handling of the above exception, another exception occurred:

pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.21:1502)]
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/sync.py", line 107, in execute
return self.execute(request)
File "/usr/local/lib/python3.5/dist-packages/pymodbus/client/common.py", line 114, in read_holding_registers
data = self._client.read_holding_registers(addr, 2, unit=71)
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 89, in ReadFloat32
self.attr_KSEM.I_P1_A = round(self.ReadFloat32(222), 2)
File "/var/www/html/openWB/modules/wr_plenticore/read_kostalplenticore.py", line 302, in ReadKSEM300
Traceback (most recent call last):
2023-03-18 23:20:36: PID: 3400: legacy run server: Unhandled exception
2023-03-18 23:20:36: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.21, 1502) failed: timed out
2023-03-18 23:20:05: PID: 22098: ##### cron5min.sh finished ##### (LV0)
2023-03-18 23:20:03: PID: 22455: Starting OpenWB services (LV0)
2023-03-18 23:20:02: PID: 22098: ##### cron5min.sh started ##### (LV0)
2023-03-18 23:19:34: PID: 18379: Modbus EVSE read CP1 issue - using previous state '1' (LV0)
2023-03-18 23:18:49: PID: 12008: **** WARNING **** Regulation loop needs 8 seconds (LV0)
2023-03-18 23:17:57: PID: 3400: pymodbus.client.sync: Connection to (192.168.178.111, 1502) failed: timed out
2023-03-18 23:15:03: PID: 16082: ##### cron5min.sh finished ##### (LV0)
--------------------------------------------
ab hier nach unten schaut es normal aus.

Da ich den KSEM im Verdacht hatte schaute ich da mal über den Browser rein.
War aber alles normal.
Auszug aus dem SystemState Log dort:
-----------------------

Firmware version: 2.1.0
Product: KOSTAL Smart Energy Meter
Device type: hw0100
Uptime:  09:40:44  up 38 days 11:46,  0 users,  load average: 1.31, 0.89, 0.78

Network status: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:d0:93:51:f4:5f brd ff:ff:ff:ff:ff:ff
    inet6 fe80::2d0:93ff:fe51:f45f/64 scope link 
       valid_lft forever preferred_lft forever
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
4: lan0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000
    link/ether 00:d0:93:51:f4:5f brd ff:ff:ff:ff:ff:ff
5: lan1@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 state LOWERLAYERDOWN group default qlen 1000
    link/ether 00:d0:93:51:f4:5f brd ff:ff:ff:ff:ff:ff
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:d0:93:51:f4:5f brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.112/24 metric 1024 brd 192.168.178.255 scope global dynamic br0
       valid_lft 562442sec preferred_lft 562442sec
    inet6 fe80::2d0:93ff:fe51:f45f/64 scope link 
       valid_lft forever preferred_lft forever
ab hier nach unten schaut es normal aus.

Da ich erst den KSEM im Verdacht hatte schaute ich da mal über den Browser rein.
War aber alles normal.
Auszug aus dem SystemState Log dort:

Code: Alles auswählen

Firmware version: 2.1.0
Product: KOSTAL Smart Energy Meter
Device type: hw0100
Uptime:  09:40:44  up 38 days 11:46,  0 users,  load average: 1.31, 0.89, 0.78

Network status: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:d0:93:51:f4:5f brd ff:ff:ff:ff:ff:ff
    inet6 fe80::2d0:93ff:fe51:f45f/64 scope link 
       valid_lft forever preferred_lft forever
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
4: lan0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000
    link/ether 00:d0:93:51:f4:5f brd ff:ff:ff:ff:ff:ff
5: lan1@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 state LOWERLAYERDOWN group default qlen 1000
    link/ether 00:d0:93:51:f4:5f brd ff:ff:ff:ff:ff:ff
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:d0:93:51:f4:5f brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.112/24 metric 1024 brd 192.168.178.255 scope global dynamic br0
       valid_lft 562442sec preferred_lft 562442sec
    inet6 fe80::2d0:93ff:fe51:f45f/64 scope link 
       valid_lft forever preferred_lft forever
Nachdem ich nun das neueste nightly aufgespielt habe hängt die oWB wieder beim Start
und geht überhaupt nicht mehr weiter.
Sonst hatte sie, wenn sie einmal am Laufen war auf der Hauptseite alles richtig angezeigt.
Ob die Speicherkarte die Grätsche gemacht hat?

Edit: jetzt startet sie gar nicht mehr, nur schwarzer Bildschirm mit Fortschrittsbalken.
Ich hatte sie mal ganz vom Strom genommen und wieder eingeschalten.

Edit 2 am 20.03.: Nachdem ich mit einer alten SD-Karten Kopie vom letzten Jahr gestartet bin
konnte ich das Backup vom 19.03. mit der .294 wieder aufspielen. Scheint jetzt wieder zu laufen.
Die Zahlen für PV und Netzexport sind viel zu groß was sich vermutlich bis zum nächsten Tag
wieder ändern wird. Werde dann weiter berichten.

Re: openWB braucht sehr lange zum Laden der Seiten

Verfasst: Fr Apr 07, 2023 7:02 am
von simon.wosi
Hallo Mafaldo,

ich habe gerade ein ähnliches Problem in der SW Version 1.9.296 aber leider kein altes Backup, da es bei mir die Erstinstallation ist. Weißt du, wie ich auf eine alte SW Version downgrade?

Danke und Grüße,
Simon

Re: openWB braucht sehr lange zum Laden der Seiten

Verfasst: Fr Apr 07, 2023 10:29 am
von Mafaldo
Hallo @simon.wosi

wenn deine SD-Karte kaputt ist dann schreibe bitte an den Support.
Nach ein paar Tagen bekommst du eine neue Karte.
Bei mir hatte ich das Glück dass ich kurz bevor die Karte ihren Geist ganz
aufgegeben hatte noch ein Backup machen konnte.
Mit einer Kopie, zu der aber offiziell nicht geraten wird(?), konnte ich
die oWB wieder flottmachen.

Re: openWB braucht sehr lange zum Laden der Seiten

Verfasst: Fr Apr 07, 2023 10:36 am
von derNeueDet
Eigentlich sollte jedem klar sein, dass ein Hersteller niemandem raten wird, selbstständig die Finger in ein elektrisches Gerät zu stecken!
Und dass eine SD Karte zu imagen auch nicht durch jeden ohne Kenntnisse erfolgen kann, beweisen genügend Andere Stränge hier.

VG
Det

Re: openWB braucht sehr lange zum Laden der Seiten

Verfasst: Fr Apr 07, 2023 10:42 am
von Mafaldo
tja, dabei stecken eigentlich alle Infos in den Untiefen des Forums.
Ja, das mit den schiefgegangenen Versuchen habe ich auch gelesen.

Dabei ist es mit dem Win32Imager und einer Industrial SD-Karte nicht
wirklich schwer eine funktionsfähige Kopie zu erstellen.

Re: openWB braucht sehr lange zum Laden der Seiten

Verfasst: Fr Apr 07, 2023 12:12 pm
von simon.wosi
Ich habe keine fertig installierte openWB sondern wollte die Software auf einem Raspberry installieren. Hier lädt aber die Startseite nicht und ich suche aktuell den Fehler. Eigentlich möchte ich nur ausprobieren, die letzte Stable Version von openWB zu installieren und nicht die letzte Nightly.
Anscheinend haben mehrere das gleiche Problem bei der Nightly.

Re: openWB braucht sehr lange zum Laden der Seiten

Verfasst: Fr Apr 07, 2023 12:24 pm
von Mafaldo
da kann ich leider nicht weiter helfen, so tief stecke ich nicht in der Materie.

Re: openWB braucht sehr lange zum Laden der Seiten

Verfasst: Fr Apr 07, 2023 12:32 pm
von aiole
Eine "echte" industrial µSD-Card basiert auf SLC, 3D-SLC, 3D-pSLC, 3D-eTLC oder 3D-TLC. Die kosten jedoch teils >50 Eur für 16 GB µSD-Card.
Hier mal Infos zu den Speichertechniken: https://www.swissbit.com/de/technologie ... chnologie/

und hier 2 Beispiele sehr hochwertiger longlife-Karten:
S-58u - 3D-pSLC: https://www.mouser.de/ProductDetail/Swi ... cKzg%3D%3D
S-46u - pSLC: https://www.digikey.de/en/products/deta ... e=octopart

Das hier nutze ich in höher beanspruchten Testsystemen als günstigere Alternative ohne Probleme. Ist aber aktuell weder in 16 noch in 32GB lieferbar:
https://www.berrybase.de/raspikey-plug- ... ry-pi-16gb

Bedenkt vor allem - der Kardinalfehler der meisten ist => "hartes" Abschalten des Betriebssystems (WB ohne shutdown stromlos machen).
Dagegen schützt auch das noch so beste Speichermedium nicht und dürfte jeder/jedem vom Desktopbetriebsystem her bekannt sein.

Also Regel Nummer 1 - !!! immer ein "softer" Shutdown vor Stromlosmachen !!!
shutdown.jpg

Re: openWB braucht sehr lange zum Laden der Seiten

Verfasst: Fr Apr 07, 2023 12:43 pm
von Mafaldo
vielen Dank für die Tipps. :)

Meine SD ist auch von swissbit:
vorderseite.jpg
vorderseite.jpg (22.63 KiB) 663 mal betrachtet
rückseite.jpg
Gekauft bei xbay zum Preis von 10€ für 2 Stück.
Hoffentlich keine Fälschungen. :shock:

Nachtrag:
der RaspiKey ist hier noch erhältlich.
Dann werde ich wohl lieber den als Backup benutzen.
Alle Zeiten sind UTC
Seite 1 von 1

Powered by phpBB® Forum Software © phpBB Limited

Deutsche Übersetzung durch phpBB.de