Re: RevPiPyLoad prevents loading PIN Dropdown at RevPi Nodes
Posted: 10 Apr 2021, 18:57
Hi Jonas,
After having posted my previous reaction (see above) the same error returned almost instantly. Most of the input signals from DIO's come in (as well as external Modbus-input) but with about 10 sec delay. Outputs aren't sent at all. I had to replace all revpi-output-nodes with exec-nodes (piTest) to keep the system kind of operating. The revpi is also very busy; Nodered is using about ca. 60% CPU and 35% memory (before update noderedrevpinodes it used to be max 15%/20%). There's obviously something wrong.
Here's a part of revpi-server.log. Many websocket-warnings.
Greetings,
Bert
After having posted my previous reaction (see above) the same error returned almost instantly. Most of the input signals from DIO's come in (as well as external Modbus-input) but with about 10 sec delay. Outputs aren't sent at all. I had to replace all revpi-output-nodes with exec-nodes (piTest) to keep the system kind of operating. The revpi is also very busy; Nodered is using about ca. 60% CPU and 35% memory (before update noderedrevpinodes it used to be max 15%/20%). There's obviously something wrong.
Here's a part of revpi-server.log. Many websocket-warnings.
Any idea what might be the problem?2021-04-10 18:05:49,485 root : WARNING Connection to websocket client b6c5bcd0-767c-4936-8022-0f7e3dd1d323 closed unexpected.
2021-04-10 18:05:49,486 root : INFO Client( b6c5bcd0-767c-4936-8022-0f7e3dd1d323 ) disconnected
2021-04-10 18:05:49,495 root : WARNING Connection to websocket client eeed3149-ecd0-4b3c-af99-d6324fba530c closed unexpected.
2021-04-10 18:05:49,496 root : INFO Client( eeed3149-ecd0-4b3c-af99-d6324fba530c ) disconnected
2021-04-10 18:05:49,498 root : WARNING Connection to websocket client cdcb3d01-8c7a-4501-9c84-4a6b2371006d closed unexpected.
2021-04-10 18:05:49,499 root : INFO Client( cdcb3d01-8c7a-4501-9c84-4a6b2371006d ) disconnected
2021-04-10 18:05:51,360 root : INFO New client connected and was given id <websockets.server.WebSocketServerProtocol object at 0x72ca9cf0>
2021-04-10 18:05:51,365 root : INFO New client connected and was given id <websockets.server.WebSocketServerProtocol object at 0x7521d030>
2021-04-10 18:05:51,990 root : INFO User is authorized
2021-04-10 18:05:51,995 root : INFO New client connected and was given id <websockets.server.WebSocketServerProtocol object at 0x7521d6d0>
2021-04-10 18:05:52,085 root : INFO User is authorized
2021-04-10 18:05:52,194 root : INFO User is authorized
2021-04-10 18:05:52,402 root : WARNING Connection to websocket client 03ae3b32-f1bf-453c-a0c1-ef9c5e816069 closed unexpected.
2021-04-10 18:05:52,406 root : INFO Client( 03ae3b32-f1bf-453c-a0c1-ef9c5e816069 ) disconnected
2021-04-10 18:05:52,620 asyncio : ERROR Task exception was never retrieved
future: <Task finished coro=<RevPiServer.publish_messages_to_client() done, defined at revpi-server.py:237> exception=ConnectionClosed('WebSocket connection is closed: code = 1005, no reason.',)>
Traceback (most recent call last):
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "revpi-server.py", line 242, in publish_messages_to_client
yield from client.websocket.send(message)
File "/usr/lib/python3/dist-packages/websockets/protocol.py", line 309, in send
yield from self.ensure_open()
File "/usr/lib/python3/dist-packages/websockets/protocol.py", line 401, in ensure_open
raise ConnectionClosed(self.close_code, self.close_reason)
websockets.exceptions.ConnectionClosed: WebSocket connection is closed: code = 1005, no reason.
2021-04-10 18:05:53,113 root : WARNING Connection to websocket client 3db7a883-ef8b-49e7-a458-ee42d548c6a8 closed unexpected.
2021-04-10 18:05:53,114 root : INFO Client( 3db7a883-ef8b-49e7-a458-ee42d548c6a8 ) disconnected
2021-04-10 18:05:53,382 root : WARNING Connection to websocket client 33f1d4d9-168e-417c-b3c1-e01358bd92d7 closed unexpected.
2021-04-10 18:05:53,384 root : INFO Client( 33f1d4d9-168e-417c-b3c1-e01358bd92d7 ) disconnected
Greetings,
Bert