RevPi server

Post Reply
ivan.chonin@axbul.bg
Posts: 44
Joined: 28 Oct 2020, 09:36

RevPi server

Post by ivan.chonin@axbul.bg »

Hello,
We have the following problem when try to start the revpi server
see the pictures below.
What can be the problem ?
Attachments
Screenshot 2023-08-18 003507.png
Screenshot 2023-08-18 003507.png (50.31 KiB) Viewed 36371 times
jgerlach-erminas
Official 3rd Party Support Erminas
Posts: 38
Joined: 22 Jan 2020, 14:31

Re: RevPi server

Post by jgerlach-erminas »

Hello,

this can be caused by incombatible server and client versions. Could you please post the output from the following command:

Code: Select all

apt-cache policy noderedrevpinodes-server
Also tell us the version of the client, it can be found in the Node-RED palette manager:

Image

Greetings,
Jonas
ivan.chonin@axbul.bg
Posts: 44
Joined: 28 Oct 2020, 09:36

Re: RevPi server

Post by ivan.chonin@axbul.bg »

Hello,

See the verison below:
What is te best way to update?
Attachments
Screenshot 2023-08-18 222914.png
Screenshot 2023-08-18 222914.png (9.85 KiB) Viewed 36272 times
Screenshot 2023-08-18 222718.png
Screenshot 2023-08-18 222718.png (35.42 KiB) Viewed 36272 times
jgerlach-erminas
Official 3rd Party Support Erminas
Posts: 38
Joined: 22 Jan 2020, 14:31

Re: RevPi server

Post by jgerlach-erminas »

Hello,
sorry for the late reply.

I can't a see a problem here with the versions. Could you please attach a log of the server?

Code: Select all

cat /var/log/revpi-server.log
Regards,
Jonas
ivan.chonin@axbul.bg
Posts: 44
Joined: 28 Oct 2020, 09:36

Re: RevPi server

Post by ivan.chonin@axbul.bg »

Hello,
See attached the log
Attachments
Screenshot 2023-09-13 092823.jpg
Screenshot 2023-09-13 092823.jpg (108.32 KiB) Viewed 35234 times
jgerlach-erminas
Official 3rd Party Support Erminas
Posts: 38
Joined: 22 Jan 2020, 14:31

Re: RevPi server

Post by jgerlach-erminas »

Hello,

the new client version 1.1.0 is now available on https://flows.nodered.org/node/node-red ... evpi-nodes and can be updated soon via the palette manager.

There is also a debian package for the client, you can check if its installed with

Code: Select all

apt-cache policy node-red-contrib-revpi-nodes
Start Node-RED via systemd to use that:

Code: Select all

sudo systemctl start nodered
If you have the combination of server with verison1.0.5-1+ and client 1.1.0 your problem should be gone.

Regards,
Jonas
ivan.chonin@axbul.bg
Posts: 44
Joined: 28 Oct 2020, 09:36

Re: RevPi server

Post by ivan.chonin@axbul.bg »

I was able to update it from "Manage Pallete" Menu.
Now is working fine. Thank you!
Thomsn
Posts: 1
Joined: 22 Jun 2025, 20:33

Re: RevPi server

Post by Thomsn »

Hallo,
ich vermute ich habe ein ähnliches Problem.

Siehe mein log:

Code: Select all

pi@RevPi67364:~ $ cat /var/log/revpi-server.log
2025-06-22 17:22:15,929 root        : WARNING  No configuration file was found. Default options applied.
2025-06-22 17:22:15,969 root        : WARNING  Can't find valid certificate files, using self signed certificate instead!
2025-06-22 17:22:17,532 root        : INFO     Start revpi thread
2025-06-22 17:22:17,535 root        : INFO     Start websocket server thread
2025-06-22 17:42:29,086 root        : WARNING  No configuration file was found. Default options applied.
2025-06-22 17:42:29,125 root        : WARNING  Can't find valid certificate files, using self signed certificate instead!
2025-06-22 17:42:29,855 root        : INFO     Start revpi thread
2025-06-22 17:42:29,857 root        : INFO     Start websocket server thread
/usr/lib/python3/dist-packages/revpimodio2/modio.py:1060: RuntimeWarning: can not execute all event functions in one cycle - optimize your event functions or rise .cycletime
  RuntimeWarning
Exception ignored in: <module 'threading' from '/usr/lib/python3.7/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.7/threading.py", line 1281, in _shutdown
    t.join()
  File "/usr/lib/python3.7/threading.py", line 1032, in join
    self._wait_for_tstate_lock()
  File "/usr/lib/python3.7/threading.py", line 1048, in _wait_for_tstate_lock
    elif lock.acquire(block, timeout):
  File "revpi-server.py", line 398, in clean_on_exit
    return_message = {"name": io_name, "value": val, "error": "ERROR_PIN"}
SystemExit
2025-06-22 18:49:26,460 root        : WARNING  No configuration file was found. Default options applied.
2025-06-22 18:49:26,510 root        : WARNING  Can't find valid certificate files, using self signed certificate instead!
2025-06-22 18:49:31,684 root        : INFO     Start revpi thread
2025-06-22 18:49:31,687 root        : INFO     Start websocket server thread
Exception ignored in: <module 'threading' from '/usr/lib/python3.7/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.7/threading.py", line 1281, in _shutdown
    t.join()
  File "/usr/lib/python3.7/threading.py", line 1032, in join
    self._wait_for_tstate_lock()
  File "/usr/lib/python3.7/threading.py", line 1048, in _wait_for_tstate_lock
    elif lock.acquire(block, timeout):
  File "revpi-server.py", line 442, in clean_on_exit
    sys.exit()
SystemExit
2025-06-22 19:02:07,925 root        : WARNING  No configuration file was found. Default options applied.
2025-06-22 19:02:07,970 root        : WARNING  Can't find valid certificate files, using self signed certificate instead!
2025-06-22 19:02:11,463 root        : INFO     Start revpi thread
2025-06-22 19:02:11,466 root        : INFO     Start websocket server thread
2025-06-22 19:41:18,185 root        : INFO     New client connected and was given id 7fc71243-cb59-49e5-86f3-a788d102637f
2025-06-22 19:41:18,202 root        : INFO     Unsupported client version
2025-06-22 19:41:18,303 root        : ERROR    Connection to websocket client 7fc71243-cb59-49e5-86f3-a788d102637f closed unexpected: WebSocket connection is closed: code = 1005 (no status code [internal]), no reason
2025-06-22 19:41:18,389 root        : INFO     Client( 7fc71243-cb59-49e5-86f3-a788d102637f ) disconnected
2025-06-22 19:48:05,873 root        : INFO     New client connected and was given id 21a19d43-0563-4df7-b6ab-21e5cec74bc8
2025-06-22 19:48:05,878 root        : INFO     Unsupported client version
2025-06-22 19:48:05,985 root        : ERROR    Connection to websocket client 21a19d43-0563-4df7-b6ab-21e5cec74bc8 closed unexpected: WebSocket connection is closed: code = 1005 (no status code [internal]), no reason
2025-06-22 19:48:06,077 root        : INFO     Client( 21a19d43-0563-4df7-b6ab-21e5cec74bc8 ) disconnected
2025-06-22 19:50:50,524 root        : INFO     New client connected and was given id 77c52869-beb1-498a-bbfd-db998827ecae
2025-06-22 19:50:50,528 root        : INFO     Unsupported client version
2025-06-22 19:50:50,635 root        : ERROR    Connection to websocket client 77c52869-beb1-498a-bbfd-db998827ecae closed unexpected: WebSocket connection is closed: code = 1005 (no status code [internal]), no reason
2025-06-22 19:50:50,727 root        : INFO     Client( 77c52869-beb1-498a-bbfd-db998827ecae ) disconnected
2025-06-22 20:01:18,438 root        : INFO     New client connected and was given id c87ca30a-6152-4693-b482-6ed5822bb504
2025-06-22 20:01:18,443 root        : INFO     Unsupported client version
2025-06-22 20:01:18,551 root        : ERROR    Connection to websocket client c87ca30a-6152-4693-b482-6ed5822bb504 closed unexpected: WebSocket connection is closed: code = 1005 (no status code [internal]), no reason
2025-06-22 20:01:18,643 root        : INFO     Client( c87ca30a-6152-4693-b482-6ed5822bb504 ) disconnected
2025-06-22 20:01:41,594 root        : INFO     New client connected and was given id 50f0d6ab-0612-424a-8634-ab2e44dcf957
2025-06-22 20:01:41,598 root        : INFO     Unsupported client version
2025-06-22 20:01:41,706 root        : ERROR    Connection to websocket client 50f0d6ab-0612-424a-8634-ab2e44dcf957 closed unexpected: WebSocket connection is closed: code = 1005 (no status code [internal]), no reason
2025-06-22 20:01:41,797 root        : INFO     Client( 50f0d6ab-0612-424a-8634-ab2e44dcf957 ) disconnected
2025-06-22 20:02:58,125 root        : INFO     New client connected and was given id 4e89afc7-0173-4c44-9668-20bf8c3563fd
2025-06-22 20:02:58,129 root        : INFO     Unsupported client version
2025-06-22 20:02:58,237 root        : ERROR    Connection to websocket client 4e89afc7-0173-4c44-9668-20bf8c3563fd closed unexpected: WebSocket connection is closed: code = 1005 (no status code [internal]), no reason
2025-06-22 20:02:58,330 root        : INFO     Client( 4e89afc7-0173-4c44-9668-20bf8c3563fd ) disconnected
/usr/lib/python3/dist-packages/revpimodio2/modio.py:687: RuntimeWarning: got io error during 'autorefresh' and count 1 errors now | [Errno 11] Resource temporarily unavailable
  RuntimeWarning,
/usr/lib/python3/dist-packages/revpimodio2/helper.py:600: RuntimeWarning: recover from io errors on process image - total count of 12154 errors now
  RuntimeWarning,
2025-06-22 20:16:30,139 root        : WARNING  Restarting revpimodio
2025-06-22 20:17:10,968 root        : INFO     New client connected and was given id 30e45e91-f2d4-4ff9-8559-904effc9f4cd
2025-06-22 20:17:10,975 root        : INFO     Unsupported client version
2025-06-22 20:17:11,079 root        : ERROR    Connection to websocket client 30e45e91-f2d4-4ff9-8559-904effc9f4cd closed unexpected: WebSocket connection is closed: code = 1005 (no status code [internal]), no reason
2025-06-22 20:17:11,171 root        : INFO     Client( 30e45e91-f2d4-4ff9-8559-904effc9f4cd ) disconnected
Exception ignored in: <module 'threading' from '/usr/lib/python3.7/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.7/threading.py", line 1281, in _shutdown
    t.join()
  File "/usr/lib/python3.7/threading.py", line 1032, in join
    self._wait_for_tstate_lock()
  File "/usr/lib/python3.7/threading.py", line 1048, in _wait_for_tstate_lock
    elif lock.acquire(block, timeout):
  File "revpi-server.py", line 442, in clean_on_exit
    sys.exit()
SystemExit
2025-06-22 20:18:36,081 root        : WARNING  No configuration file was found. Default options applied.
2025-06-22 20:18:36,134 root        : WARNING  Can't find valid certificate files, using self signed certificate instead!
2025-06-22 20:18:41,219 root        : INFO     Start revpi thread
2025-06-22 20:18:41,223 root        : INFO     Start websocket server thread
2025-06-22 20:19:28,420 root        : INFO     New client connected and was given id 7dbc016f-03d6-47ab-a7fb-abbc85ae77d2
2025-06-22 20:19:28,425 root        : INFO     Unsupported client version
2025-06-22 20:19:28,531 root        : ERROR    Connection to websocket client 7dbc016f-03d6-47ab-a7fb-abbc85ae77d2 closed unexpected: WebSocket connection is closed: code = 1005 (no status code [internal]), no reason
2025-06-22 20:19:28,622 root        : INFO     Client( 7dbc016f-03d6-47ab-a7fb-abbc85ae77d2 ) disconnected
2025-06-22 20:21:34,363 root        : INFO     New client connected and was given id 1078ea92-0cc1-4ed3-8fc6-26162aa6724d
2025-06-22 20:21:34,368 root        : INFO     Unsupported client version
2025-06-22 20:21:34,475 root        : ERROR    Connection to websocket client 1078ea92-0cc1-4ed3-8fc6-26162aa6724d closed unexpected: WebSocket connection is closed: code = 1005 (no status code [internal]), no reason
2025-06-22 20:21:34,567 root        : INFO     Client( 1078ea92-0cc1-4ed3-8fc6-26162aa6724d ) disconnected
Ich würde mich über einen Tipp sehr freuen

Grüße
Post Reply