MWareman Posted September 24, 2022 Share Posted September 24, 2022 (edited) Issuing a 'Stop' 'Start' or 'Restart' does not appear to do anything in the GUI. Bulbs that were working are not working. This appears to affect all node servers on PG3... When starting LiFX - I see this in the debug log: 9/24/2022, 11:12:18 [pg3] info: startNs:: LiFX 9/24/2022, 11:12:18 [pg3] info: startNs:: LiFX is valid 9/24/2022, 11:12:18 [pg3] debug: checkLicense:: LiFX Getting node server store entry 9/24/2022, 11:12:18 [pg3] debug: checkLicense:: LiFX Getting node server purchase record 9/24/2022, 11:12:18 [pg3] debug: Getting status for LiFX {MAC} {GUID} 9/24/2022, 11:12:18 [pg3] info: checkLicense:: LiFX No license found for Free node server. 9/24/2022, 11:12:18 [pg3] info: startNs:: LiFX finished update check 9/24/2022, 11:12:18 [pg3] info: [LiFX(6)] :: Starting Node server - Version 2.1.26 9/24/2022, 11:12:18 [pg3] info: startNs:: LiFX updating database (enabled, timestarted) 9/24/2022, 11:12:18 [pg3] error: [LiFX(6)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/24/2022, 11:12:18 [pg3] debug: [LiFX(6)] :: Exit cause code: 1 - signal: null Seems a library is missing (!). Not sure how that happened. Any ideas to resolve? It was working prior to the last 'pkg update && pkg upgrade' where the latest udx (among some other items) were updated. Edited September 24, 2022 by MWareman Link to comment
MWareman Posted September 24, 2022 Author Share Posted September 24, 2022 Maybe a bug in FreeBSD? Or the update process?https://forums.freebsd.org/threads/version-fbsd_1-7-required-by-usr-local-lib-libpython3-9-so-1-0.86449/ Not sure if Polisy is using jails - so don't want to 'try' the workaround without guidance. Link to comment
MWareman Posted September 25, 2022 Author Share Posted September 25, 2022 More from the log - during a reboot: 9/25/2022, 11:06:13 [pg3] error: [Sonos(14)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] debug: [Sonos(14)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] info: startNs:: Sonos starting polls 9/25/2022, 11:06:13 [pg3] info: Starting Node server Info timer 0 9/25/2022, 11:06:13 [pg3] error: [Timedata(9)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [ELK(10)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [LiFX(6)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [Sun(11)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [Ping(8)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [Plex-WebHook(12)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [WirelessTag(4)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [NOAA(5)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [UnifiPresence(15)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [MQTT(13)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [WeatherFlow(7)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] debug: [Timedata(9)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [ELK(10)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [LiFX(6)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [Sun(11)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [Ping(8)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [Plex-WebHook(12)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [WirelessTag(4)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [NOAA(5)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:14 [pg3] debug: [UnifiPresence(15)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:14 [pg3] debug: [MQTT(13)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:14 [pg3] debug: [WeatherFlow(7)] :: Exit cause code: 1 - signal: null Looking at everything that updated a couple of days ago: Quote Sep 23 20:33:05 polisy pkg[2395]: python39 upgraded: 3.9.13 -> 3.9.14 Sep 23 20:33:05 polisy pkg[2395]: ca_root_nss upgraded: 3.81 -> 3.83 Sep 23 20:33:06 polisy pkg[2395]: py39-tzdata-2022.2 installed Sep 23 20:33:06 polisy pkg[2395]: py39-acme upgraded: 1.29.0,1 -> 1.30.0,1 Sep 23 20:33:08 polisy pkg[2395]: nspr upgraded: 4.34.1 -> 4.35 Sep 23 20:33:08 polisy pkg[2395]: sqlite3 upgraded: 3.39.2,1 -> 3.39.3,1 Sep 23 20:33:11 polisy pkg[2395]: nss upgraded: 3.82 -> 3.83 Sep 23 20:33:12 polisy pkg[2395]: libdeflate upgraded: 1.13 -> 1.14 Sep 23 20:33:12 polisy pkg[2395]: py39-sqlite3 upgraded: 3.9.13_7 -> 3.9.14_7 Sep 23 20:33:12 polisy pkg[2395]: libXft upgraded: 2.3.5 -> 2.3.6 Sep 23 20:33:12 polisy pkg[2395]: dmidecode upgraded: 3.4_1 -> 3.4_2 Sep 23 20:33:49 polisy pkg[2395]: pg3 upgraded: 3.1.6 -> 3.1.10 Sep 23 20:33:50 polisy pkg[2395]: harfbuzz upgraded: 5.1.0 -> 5.2.0 Sep 23 20:33:51 polisy pkg[2395]: py39-certbot upgraded: 1.29.0,1 -> 1.30.0,1 Sep 23 20:33:53 polisy pkg[2395]: avahi-app upgraded: 0.8 -> 0.8_1 Sep 23 20:33:53 polisy pkg[2395]: py39-pytz-deprecation-shim upgraded: 0.1.0.post0 -> 0.1.0.post0_1 Sep 23 20:34:22 polisy pkg[2395]: perl5 upgraded: 5.32.1_1 -> 5.32.1_3 Sep 23 20:34:23 polisy pkg[2395]: udx upgraded: 3.3.0_2 -> 3.3.0_6 I tried reverting pg3 and udx - but this did not resolve the issue at all. I have a feeling there is a missing dependency in the updated python39. Link to comment
Geddy Posted September 25, 2022 Share Posted September 25, 2022 @MWareman you might be better off getting help through a support ticket. This way @Michel Kohanim and/or @bpwwer can look into the logs a little better and perhaps have a better idea of what happened and how to fix. What update process did you attempt? Link to comment
bpwwer Posted September 25, 2022 Share Posted September 25, 2022 Yes, this is a known issue. For a period of time, the update wasn't updating one of the dependencies (that library it complains about). It should be fixed now if you do another update. The recommended way to update is to use the "Update Packages" button in the Admin Console configuration screen. 2 Link to comment
MWareman Posted September 25, 2022 Author Share Posted September 25, 2022 15 minutes ago, bpwwer said: Yes, this is a known issue. For a period of time, the update wasn't updating one of the dependencies (that library it complains about). It should be fixed now if you do another update. The recommended way to update is to use the "Update Packages" button in the Admin Console configuration screen. No updates yet: Should I be expecting to see something thru the 'pkg update && pkg upgrade' process? Link to comment
MWareman Posted September 25, 2022 Author Share Posted September 25, 2022 22 minutes ago, bpwwer said: The recommended way to update is to use the "Update Packages" button in the Admin Console configuration screen. Interesting. I had not been doing this - rather 'pkg update && pkg upgrade' at the cli. Opening the admin console - I hit this button and immediately the admin console (and finder) closed. As if it crashed. Thru SSH - I was watching /var/log/messages and nothing. After a few mins - I started the admin console again - and all of a sudden I see events like this in /var/log/messages: Sep 25 13:38:04 polisy pkg[4779]: FreeBSD-runtime-13.0p11 deinstalled Sep 25 13:38:08 polisy pkg[4779]: FreeBSD-utilities-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-libbsdxml-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-libregex-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-libregex-dev-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-utilities-dev-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-libbsdxml-dev-13.0p11 deinstalled Sep 25 13:38:14 polisy pkg[4779]: FreeBSD-runtime-13.1p2 installed Sep 25 13:38:14 polisy pkg[4779]: FreeBSD-libmagic-13.0p11 deinstalled Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-runtime-dev-13.0p11 deinstalled Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-rc-13.0p11 deinstalled Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-liblzma-13.0p11 deinstalled Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libthread_db upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libbsm upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libsmb upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libbsdstat upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libucl upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:16 polisy pkg[4779]: FreeBSD-bluetooth upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:16 polisy pkg[4779]: FreeBSD-libvgl upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:16 polisy pkg[4779]: FreeBSD-libcuse upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:16 polisy pkg[4779]: FreeBSD-libarchive upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:19 polisy pkg[4779]: FreeBSD-openssl-13.1p2 installed Sep 25 13:38:19 polisy pkg[4779]: FreeBSD-libmagic-13.1p2 installed ..... I suspect these are the dependencies being spoke of (at some point I did earlier see a 'running kernel mismatch' error). At the end of the upgrades - Polisy auto-rebooted: Sep 25 13:40:02 polisy reboot[5956]: rebooted by admin Link to comment
bpwwer Posted September 25, 2022 Share Posted September 25, 2022 For some things, the pkg update commands can still be used, but the admin console update packages is doing some additional stuff to make sure everything is right and dependencies are correct (don't ask me what, I don't know). 1 Link to comment
MWareman Posted September 25, 2022 Author Share Posted September 25, 2022 Update: *MUCH* better. Polys all started. Problem looks solved. Still don't know why the admin console update did things beyond the pkg package manager. Thank you @bpwwerfor the solution! Link to comment
MWareman Posted September 25, 2022 Author Share Posted September 25, 2022 14 minutes ago, bpwwer said: For some things, the pkg update commands can still be used, but the admin console update packages is doing some additional stuff to make sure everything is right and dependencies are correct (don't ask me what, I don't know). Good to know - thank you! Link to comment
Michel Kohanim Posted September 25, 2022 Share Posted September 25, 2022 @MWareman, Pkg update does not go between revisions such as 13.0 to 13.1. So, the button also calls a script that makes those updates and cleans up after itself. With kind regards, Michel Link to comment
MWareman Posted October 1, 2022 Author Share Posted October 1, 2022 On 9/25/2022 at 3:12 PM, Michel Kohanim said: @MWareman, Pkg update does not go between revisions such as 13.0 to 13.1. So, the button also calls a script that makes those updates and cleans up after itself. With kind regards, Michel That makes sense now. It was odd at the time because 'pkg update' updated something that had a dependancy on a newer library that had not yet been updated. Is there a cli way of (for instance) going from 13.0 to 13.1 safely? Link to comment
Michel Kohanim Posted October 2, 2022 Share Posted October 2, 2022 Hi @MWareman, Yes: Through ISY: sudo /usr/local/etc/udx.d/static/udxop.sh upgrade.polisy (this is what's called from the Admin Console) Or, brute force: curl -s https://pkg.isy.io/script/update131.sh | sudo bash The first is preferred because it also checks other things such as python upgrade and node servers. With kind regards, Michel 1 Link to comment
MWareman Posted October 2, 2022 Author Share Posted October 2, 2022 35 minutes ago, Michel Kohanim said: Hi @MWareman, Yes: Through ISY: sudo /usr/local/etc/udx.d/static/udxop.sh upgrade.polisy (this is what's called from the Admin Console) Or, brute force: curl -s https://pkg.isy.io/script/update131.sh | sudo bash The first is preferred because it also checks other things such as python upgrade and node servers. With kind regards, Michel This has let me down a rabbithole now.. I have been having trouble witht he BIOS update - it just seemed to fail from the GUI. Of course - I noticed the 'update.bios' command in the script.. [admin@polisy ~]$ sudo /usr/local/etc/udx.d/static/udxops.sh update.bios executing from /usr/local/etc/udx.d/static Sun Oct 2 18:28:03 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: starting bios update Sun Oct 2 18:28:04 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios mfr: Universal Devices Sun Oct 2 18:28:04 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios product: Polisy Sun Oct 2 18:28:04 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios ver: 1.0.0 Sun Oct 2 18:28:04 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios version 100 is old and needs to be upgraded flashrom on FreeBSD 13.1-RELEASE-p2 (amd64) flashrom is free software, get the source code at https://flashrom.org Using default programmer "internal" with arguments "". Using clock_gettime for delay loops (clk_id: 4, resolution: 2ns). coreboot table found at 0xcfec5000. Found chipset "AMD FCH". Enabling flash write... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. Using regions: "RW_SECTION_A", "RW_SECTION_B", "PSPDIR". Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00030000! Expected=0xff, Found=0x24, failed byte count from 0x00030000-0x00030fff: 0xd d2 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00030000! Expected=0xff, Found=0x24, failed byte count from 0x00030000-0x00037fff: 0x7c92 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00030000! Expected=0xff, Found=0x24, failed byte count from 0x00030000-0x0003ffff: 0xf708 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x2f, failed byte count from 0x00000000-0x007fffff: 0x555677 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x2f, failed byte count from 0x00000000-0x007fffff: 0x555677 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Looking for another erase function. Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom@flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! Sun Oct 2 18:29:37 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios update ... rebooting POLISY then rebooted - and (fortunately) it came back. Seems the BIOS update process is failing on my POLISY and thru the CLI there is at least some detail as to why. How would I go about addressing this? Thank you! Link to comment
Michel Kohanim Posted October 3, 2022 Share Posted October 3, 2022 @MWareman, do NOT poweroff. Please send your address to sales@universal-devices.com and request for a flash chip. With kind regards, Michel 1 Link to comment
MWareman Posted October 3, 2022 Author Share Posted October 3, 2022 21 minutes ago, Michel Kohanim said: @MWareman, do NOT poweroff. Please send your address to sales@universal-devices.com and request for a flash chip. With kind regards, Michel Request sent! Thank you. Link to comment
Recommended Posts