PG3 3.0.50 Upgrade Issues

[macjeff]

3.0.54 should fix these issues.  Its pushed now

sudo pkg update

then sudo pkg upgrade

[Bumbershoot]

Running PG3 3.0.54, and version 3.1.4 of this Node server, and I'm getting these errors in the log:

2022-03-29 07:01:21,446 MQTT       udi_interface.interface INFO     interface:_message: Successfully set wtcontroller :: ST to 1 UOM 25
2022-03-29 07:01:24,135 MainThread udi_interface.interface INFO     interface:addNode: Adding node WirelessTagsController(wtcontroller) [None]
2022-03-29 07:01:24,137 MainThread udi_interface.interface INFO     interface:setController: Using node "wtcontroller", driver "ST" for connection status.
2022-03-29 07:01:24,338 Command    udi_interface      ERROR    udi_interface:write: Exception in thread
2022-03-29 07:01:24,339 Command    udi_interface      ERROR    udi_interface:write: Command
2022-03-29 07:01:24,340 Command    udi_interface      ERROR    udi_interface:write: :
2022-03-29 07:01:24,341 Command    udi_interface      ERROR    udi_interface:write: Traceback (most recent call last):
2022-03-29 07:01:24,342 Command    udi_interface      ERROR    udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
2022-03-29 07:01:24,347 Command    udi_interface      ERROR    udi_interface:write: self.run()
2022-03-29 07:01:24,348 Command    udi_interface      ERROR    udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run
2022-03-29 07:01:24,351 Command    udi_interface      ERROR    udi_interface:write: self._target(*self._args, **self._kwargs)
2022-03-29 07:01:24,352 Command    udi_interface      ERROR    udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 678, in _parseInput
2022-03-29 07:01:24,356 Command    udi_interface      ERROR    udi_interface:write: self._handleInput(key, input[key], None)
2022-03-29 07:01:24,357 Command    udi_interface      ERROR    udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 684, in _handleInput
2022-03-29 07:01:24,361 Command    udi_interface      ERROR    udi_interface:write: self._inConfig(item)
2022-03-29 07:01:24,362 Command    udi_interface      ERROR    udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 598, in _inConfig
2022-03-29 07:01:24,365 Command    udi_interface      ERROR    udi_interface:write: LOGGER.setLevel(self.currentLogLevel)
2022-03-29 07:01:24,366 Command    udi_interface      ERROR    udi_interface:write: File "/usr/local/lib/python3.8/logging/__init__.py", line 1421, in setLevel
2022-03-29 07:01:24,373 Command    udi_interface      ERROR    udi_interface:write: self.level = _checkLevel(level)
2022-03-29 07:01:24,374 Command    udi_interface      ERROR    udi_interface:write: File "/usr/local/lib/python3.8/logging/__init__.py", line 198, in _checkLevel
2022-03-29 07:01:24,376 Command    udi_interface      ERROR    udi_interface:write: raise ValueError("Unknown level: %r" % level)
2022-03-29 07:01:24,377 Command    udi_interface      ERROR    udi_interface:write: ValueError
2022-03-29 07:01:24,378 Command    udi_interface      ERROR    udi_interface:write: :
2022-03-29 07:01:24,379 Command    udi_interface      ERROR    udi_interface:write: Unknown level: 'NULL'

 

[Jimbo.Automates]

Change log level, restart NS then it should work, then change log level back to your preference.

Sent from my Pixel 6 Pro using Tapatalk

[Bumbershoot]

1 hour ago, JimboAutomates said:

Change log level, restart NS then it should work, then change log level back to your preference.

Sent from my Pixel 6 Pro using Tapatalk
 

Thanks, that works...

[asbril]

@bpwwer Upgrade to 3.0.55 was not succesful. I first did on Systems - Upgrade and later with SSH, but now I can no longer open PG3. I can still access IoP through launcher but no longer PG3 with XX.XX.XX:3000

Please remind me how to SSH to previous version

[asbril]

9 minutes ago, asbril said:

@bpwwer Upgrade to 3.0.55 was not succesful. I first did on Systems - Upgrade and later with SSH, but now I can no longer open PG3. I can still access IoP through launcher but no longer PG3 with XX.XX.XX:3000

Please remind me how to SSH to previous version

RESOLVED after I found one more update in System-Check for Polisy Updates

[dwengrovitz]

5 minutes ago, asbril said:

Upgrade to 3.0.55 was not succesful. I first did on Systems - Upgrade and later with SSH, but now I can no longer open PG3. I can still access IoP through launcher but no longer PG3 with XX.XX.XX:3000

I was also seeing problems with the upgrade to 3.0.55.  I did the upgrade via SSH.  First time I ran it the system updated to 3.0.55, but I could not access PG3 via browser.  I ran it again and noticed the upgrade to 3.0.55_1 ... but still could not access PG3 via browser.  I ran it again and noticed the upgrade to 3.0.55_2. 

The upgrade via SSH still throws an error after trying to restart PG3 via command line (see below), but I am now able to access PG3 via the URL.  The error I see via SSH is:
 

[admin@polisy ~]$ sudo service pg3 restart
cat: /var/polyglot/pg3.pid: No such file or directory
usage: kill [-s signal_name] pid ...
       kill -l [exit_status]
       kill -signal_name pid ...
       kill -signal_number pid ...
Stopping polyglotcat: /var/polyglot/pg3.pid: No such file or directory
ps: option requires an argument -- p
usage: ps [-aCcdefHhjlmrSTuvwXxZ] [-O fmt | -o fmt] [-G gid[,gid...]]
          [-J jid[,jid...]] [-M core] [-N system]
          [-p pid[,pid...]] [-t tty[,tty...]] [-U user[,user...]]
       ps [-L]
 done
cat: /var/polyglot/pg3_daemon.pid: No such file or directory
usage: kill [-s signal_name] pid ...
       kill -l [exit_status]
       kill -signal_name pid ...
       kill -signal_number pid ...
Starting pg3.

 

[bpwwer]

I screwed up trying to add something new to the startup script.  I thought I'd have a few minutes to get it fixed before anyone tried to update, but man you guys are fast!

[dwengrovitz]

13 minutes ago, bpwwer said:

you guys are fast!

@bpwwer I was going to say the same about you!  Thanks for the quick fix(es).  I've got some more testing to do, but most things seem to be working for me.  The one problem I've seen in my quick round of testing is with a Kasa outdoor plug/switch that the node server sees but cannot seem to control.  I'll have to do some more testing on that one. 

Thanks again!