Support thread for: PG3x v3.2.3 (August 29th, 2023)

sjpbailey · September 3, 2023

Dammit Jim! LOL!!!! WTH?

I should have looked before i took my whole system down.
I guess this is also my fault?
Why I cannot update Tuya.

OKAY!
I can surely see manually controlling my equipment for a few days.

I put in a ticket so now what, we just sit and look at it like a pet rock?
I see everyone else is:

2023-09-03 01:25:49,640 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30
2023-09-03 01:25:51,629 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30
2023-09-03 01:25:53,360 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30
2023-09-03 01:25:55,100 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30
2023-09-03 01:25:56,455 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True

level=30

DennisC · September 3, 2023

9 hours ago, bgrubb1 said:

just a note I upgraded 3.2.2 to 3.2.3 no issues (on a Polisy)

...Barry

I upgraded PG3x on a Polisy to 3.2.3 on Friday and my node servers are fine also.

SamM · September 3, 2023

It looks like I'm in the same situation with all node servers showing disconnected status after the most recent update. While it appears most of the other reports are 3.2.1/2 -> 3.2.3, I actually updated from 3.1.36 -> 3.2.3 (and IoX 5.6.3 -> 5.6.4). As instructed, I've re-installed all node servers. And have attempted a few reboots (both from the admin console UI and power cycling my eISY).

I've submitted a ticket with PG3x logs after performing my most recent reboot.

-Sam

bmercier · September 3, 2023

Hello everyone,

We found that a system update is causing issues with node server startup on eisy.

We are working on a permanent fix.

But for now, here's a solution:

ssh to your system (on Windows, you can use putty)
Run these 2 commands:
- sudo pip3 uninstall aioquic
- sudo pip3 install aioquic

You can ignore the warnings.

This will reinstall aioquic at the same version (0.9.21). However it does check dependancies. On my system, this uninstalled pyOpenSSL 21.0.0 and reinstalled it at 23.2.0. This solved the problem.

SamM · September 3, 2023

Thanks @bmercier - followed the suggested steps and my node servers are now connected.

One note, on my system, the pip install of the aioquic resulted in more than warnings. I actually ended up with a number of errors while building wheel for aioquic. However, pyOpenSSL did update to 23.2.0 as expected.

-Sam

bmercier · September 3, 2023

3 minutes ago, SamM said:

Thanks @bmercier - followed the suggested steps and my node servers are now connected.

One note, on my system, the pip install of the aioquic resulted in more than warnings. I actually ended up with a number of errors while building wheel for aioquic. However, pyOpenSSL did update to 23.2.0 as expected.

-Sam

Thanks for the feedback.

On my system, I only had warning.

This is the expected output:

[admin@eisy /var/polyglot/pg3/ns]$ sudo pip3 uninstall aioquic
Found existing installation: aioquic 0.9.21
Uninstalling aioquic-0.9.21:
Would remove:
/usr/local/lib/python3.9/site-packages/aioquic-0.9.21.dist-info/*
/usr/local/lib/python3.9/site-packages/aioquic/*
Proceed (Y/n)? y
Successfully uninstalled aioquic-0.9.21
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

[admin@eisy /var/polyglot/pg3/ns]$ sudo pip3 install aioquic
Collecting aioquic
Downloading aioquic-0.9.21.tar.gz (153 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 153.4/153.4 kB 1.4 MB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: certifi in /usr/local/lib/python3.9/site-packages (from aioquic) (2023.7.22)
Requirement already satisfied: pylsqpack<0.4.0,>=0.3.3 in /usr/local/lib/python3.9/site-packages (from aioquic) (0.3.17)
Collecting pyopenssl>=22 (from aioquic)
Obtaining dependency information for pyopenssl>=22 from https://files.pythonhosted.org/packages/f0/e2/f8b4f1c67933a4907e52228241f4bd52169f3196b70af04403b29c63238a/pyOpenSSL-23.2.0-py3-none-any.whl.metadata
Downloading pyOpenSSL-23.2.0-py3-none-any.whl.metadata (10 kB)
Requirement already satisfied: cryptography!=40.0.0,!=40.0.1,<42,>=38.0.0 in /usr/local/lib/python3.9/site-packages (from pyopenssl>=22->aioquic) (41.0.3)
Requirement already satisfied: cffi>=1.12 in /usr/local/lib/python3.9/site-packages (from cryptography!=40.0.0,!=40.0.1,<42,>=38.0.0->pyopenssl>=22->aioquic) (1.15.1)
Requirement already satisfied: pycparser in /usr/local/lib/python3.9/site-packages (from cffi>=1.12->cryptography!=40.0.0,!=40.0.1,<42,>=38.0.0->pyopenssl>=22->aioquic) (2.21)
Downloading pyOpenSSL-23.2.0-py3-none-any.whl (59 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 59.0/59.0 kB 2.9 MB/s eta 0:00:00
Building wheels for collected packages: aioquic
Building wheel for aioquic (pyproject.toml) ... done
Created wheel for aioquic: filename=aioquic-0.9.21-cp37-abi3-freebsd_13_1_release_p7_amd64.whl size=92308 sha256=38f9a1084a60c2ecf26499995128b9a4d2ecaac0462ae4583e52ecc153327630
Stored in directory: /root/.cache/pip/wheels/ac/a8/24/70b950af1c5ceb452388b3562e6c80b085bc5f71c799f7e813
Successfully built aioquic
Installing collected packages: pyopenssl, aioquic
Attempting uninstall: pyopenssl
Found existing installation: pyOpenSSL 21.0.0
Uninstalling pyOpenSSL-21.0.0:
Successfully uninstalled pyOpenSSL-21.0.0
Successfully installed aioquic-0.9.21 pyopenssl-23.2.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

There is probably a more direct command to update pyopenssl to 23.2.0 but could not test it.

Xathros · September 3, 2023

I also have performed the reinstall of aioquic and also had build errors along the way (log excerpt below). My node servers are also now reconnected and appear to be working as expected.

Thanks!

-Xathros

Quote

Downloading pyOpenSSL-23.2.0-py3-none-any.whl (59 kB)

   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 59.0/59.0 kB 1.8 MB/s eta 0:00:00

Building wheels for collected packages: aioquic

Building wheel for aioquic (pyproject.toml) ... error

error: subprocess-exited-with-error



× Building wheel for aioquic (pyproject.toml) did not run successfully.

│ exit code: 1

╰─> [62 lines of output]

No `packages` or `py_modules` configuration, performing automatic discovery.

`src-layout` detected -- analysing ./src

discovered packages -- ['aioquic', 'aioquic.quic', 'aioquic.asyncio', 'aioquic.h0', 'aioquic.h3']

discovered py_modules -- []

running bdist_wheel

running build

running build_py

creating build

creating build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39

creating build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic

copying src/aioquic/buffer.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic

copying src/aioquic/tls.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic

copying src/aioquic/__init__.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic

creating build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/events.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/configuration.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/__init__.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/packet.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/crypto.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/logger.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/packet_builder.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/recovery.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/rangeset.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/connection.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/stream.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

copying src/aioquic/quic/retry.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/quic

creating build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/asyncio

copying src/aioquic/asyncio/protocol.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/asyncio

copying src/aioquic/asyncio/__init__.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/asyncio

copying src/aioquic/asyncio/client.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/asyncio

copying src/aioquic/asyncio/server.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/asyncio

creating build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/h0

copying src/aioquic/h0/__init__.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/h0

copying src/aioquic/h0/connection.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/h0

creating build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/h3

copying src/aioquic/h3/events.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/h3

copying src/aioquic/h3/connection.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/h3

copying src/aioquic/h3/__init__.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/h3

copying src/aioquic/h3/exceptions.py -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic/h3

running egg_info

writing src/aioquic.egg-info/PKG-INFO

writing dependency_links to src/aioquic.egg-info/dependency_links.txt

writing requirements to src/aioquic.egg-info/requires.txt

writing top-level names to src/aioquic.egg-info/top_level.txt

reading manifest file 'src/aioquic.egg-info/SOURCES.txt'

reading manifest template 'MANIFEST.in'

adding license file 'LICENSE'

writing manifest file 'src/aioquic.egg-info/SOURCES.txt'

copying src/aioquic/_buffer.c -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic

copying src/aioquic/_crypto.c -> build/lib.freebsd-13.1-RELEASE-p7-amd64-cpython-39/aioquic

running build_ext

building 'aioquic._buffer' extension

creating build/temp.freebsd-13.1-RELEASE-p7-amd64-cpython-39

creating build/temp.freebsd-13.1-RELEASE-p7-amd64-cpython-39/src

creating build/temp.freebsd-13.1-RELEASE-p7-amd64-cpython-39/src/aioquic

cc -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -DPy_LIMITED_API=0x03070000 -I/usr/local/include/python3.9 -c src/aioquic/_buffer.c -o build/temp.freebsd-13.1-RELEASE-p7-amd64-cpython-39/src/aioquic/_buffer.o -std=c99

In file included from src/aioquic/_buffer.c:3:

/usr/local/include/python3.9/Python.h:11:10: fatal error: 'limits.h' file not found

#include <limits.h>

   ^~~~~~~~~~

1 error generated.

error: command '/usr/bin/cc' failed with exit code 1

[end of output]



note: This error originates from a subprocess, and is likely not a problem with pip.

ERROR: Failed building wheel for aioquic

Failed to build aioquic

ERROR: Could not build wheels for aioquic, which is required to install pyproject.toml-based projects

Edited September 3, 2023 by Xathros

MBell · September 3, 2023

Quote

39 minutes ago, bmercier said:

Hello everyone,

We found that a system update is causing issues with node server startup on eisy.

We are working on a permanent fix.

But for now, here's a solution:

ssh to your system (on Windows, you can use putty)

Run these 2 commands:
sudo pip3 uninstall aioquic

sudo pip3 install aioquic

You can ignore the warnings.

This will reinstall aioquic at the same version (0.9.21). However it does check dependancies. On my system, this uninstalled pyOpenSSL 21.0.0 and reinstalled it at 23.2.0. This solved the problem.

Followed these suggestions and all nodes are connected and working. Did return some errors after re-installing aioquic?

Do let us know if you all need anymore logs?

Thanks,

garybixler · September 3, 2023

All nodes now connected. Thanks

GSutherland · September 3, 2023

I am also having the same problem with all Polyglot Current Status: Disconnected.... HELP

DennisC · September 3, 2023

15 minutes ago, GSutherland said:

I am also having the same problem with all Polyglot Current Status: Disconnected.... HELP

The temporary fix was listed several posts up.

sjpbailey · September 3, 2023

polisy one node server cane back up cannot install any node servers,

eisy completely down on all node servers!!!

All nodes servers are still down re-install all node servers does nothing!

i am leaving for Bodega Bay and my house is down!

one sprinkler was ON all night.

so idk who else is experiencing this but i am not happy

sjpbailey · September 3, 2023

Still looping in basic configuration?

GSutherland · September 3, 2023

11 minutes ago, DennisC said:

The temporary fix was listed several posts up.

I have never ssh from my Mac have no idea how to do it..... Can you give me some suggestions from Terminal to make sure I do it, right

Xathros · September 3, 2023

54 minutes ago, GSutherland said:

I have never ssh from my Mac have no idea how to do it..... Can you give me some suggestions from Terminal to make sure I do it, right

Hello GSutherland,

Open the Terminal app on you Mac. It's a native app provided with MacOS.

Type: ssh admin@<the-ip-address-of-your-eisy> (and press return)

Password is admin unless you have changed it. You wont see the password characters as you type them. (and press return)

From there, enter the commands that bmercier posted above. (followed by the return key) There may be errors or warnings reported, don't worry.

When completed, type: exit (and press return)

Then, return to the PG3x dashboard and start your noderserver(s)

Hope this helps.

-Xathros

Edited September 3, 2023 by Xathros

GSutherland · September 3, 2023

THAT WORKED GREAT>>>>>Thank You for your time

Michel Kohanim · September 3, 2023

@everyone,

Apologies for the weekend fire. This is now fixed in udx-3.5.1_4. In short, there were some python packages that depended on the newer version of pyopenssl. Now, udx makes sure those packages are installed.

1. Admin Console | Configuration tab | Upgrade Packages, or

2. Click on the power button once

3. Wait for the reboot notification in the Admin Console

- Admin Console | Configuration tab | Reboot, or

2. Click the power button 5 times

Techman · September 3, 2023

Did the update packages, then rebooted.

Now every time I open the admin console I get a need to reboot window.

Removing power from the eisy stopped the reboot notices, but I'm still showing 3.2.3

Michel Kohanim · September 3, 2023

@Techman,

3.2.3 is the correct version for PG3x.

With kind regards,

Michel

hart2hart · September 4, 2023

@Michel Kohanim I upgraded to latest version on eISY a few days ago snd all is working well. Should I perform another update or simply wait for next update?

sjpbailey · September 4, 2023

@bgrubb1

Did you install any node servers after you updated? I had one node server installed on my Development Polisy and it is running after 3.2.3. Try to install a new node server and they do not run.

Eisy all Nodes 17 of my Node servers all show basic configuration in their log and all of them are down.

I am in Bodega Bay "the birds" 60 years and art

btreinders · September 4, 2023

Upgrade wasn't straight forward, waited for the beeps and then waiting for the reboot to happen I saw MQTT errors scrolling in the tail of log so fast it could not keep up. I don't have the MQTT node server installed either. ISY was not responsive, could not open PG3x or AC. After an hour of this I rebooted from command line. Everything came up and everything seems ok.

Edited September 4, 2023 by btreinders

bgrubb1 · September 4, 2023

@sjpbailey

@bmercier

I just tried installing one and it errors out on purchase

...Barry

bmercier · September 5, 2023

18 hours ago, bgrubb1 said:

@sjpbailey

@bmercier

I just tried installing one and it errors out on purchase

...Barry

@bgrubb1, which node server did you try to purchase, and what was the error?

bgrubb1 · September 5, 2023

I tried to purchase the free wemo NS red error box saying failed and returned me to purchase page

Sign In

Support thread for: PG3x v3.2.3 (August 29th, 2023)

Recommended Posts

sjpbailey

DennisC

SamM

bmercier

SamM

bmercier

Xathros

MBell

garybixler

GSutherland

DennisC

sjpbailey

sjpbailey

GSutherland

Xathros

GSutherland

Michel Kohanim

Techman

Michel Kohanim

hart2hart

sjpbailey

btreinders

bgrubb1

bmercier

bgrubb1

Recently Browsing

Who's Online (See full list)

Forum Statistics

Browse

Activity