macjeff Posted February 11, 2023 Posted February 11, 2023 (edited) I ran update packages a week ago and all was fine. Ran it today and polisy is dead. After two hours I rebooted it. I have a backup developer unit. Tried - NEW OUT OF THE BOX- to log in and update packages (without any backup restored) and it killed too. I can SSH in and If I check ISY, Polyglot. pg3 they all show running Have a feeling something is broken with the upgrade process yet again. Since I have a backup polisy I have that hooked up now (broken too as I already said) so I can try anything on it. I did open a ticket. I did get some confirmation from others that they have been fine tuning the upgrade process so I would NOT upgrade packages anytime soon until this is fixed. Jeff Just FYI see below. Not sure what the = and < mean [admin@polisy ~]$ pk version -bash: pk: command not found [admin@polisy ~]$ pkg version FreeBSD-acct-13.1p5 = FreeBSD-acpi-13.1p5 = FreeBSD-apm-13.1p5 = FreeBSD-at-13.1p5 = FreeBSD-autofs-13.1p5 = FreeBSD-bluetooth-13.1p5 = FreeBSD-bluetooth-dev-13.1p5 = FreeBSD-bootloader-13.1p5 = FreeBSD-bsnmp-13.1p5 = FreeBSD-bsnmp-dev-13.1p5 = FreeBSD-caroot-13.1p5 = FreeBSD-ccdconfig-13.1p5 = FreeBSD-clang-13.1p5 = FreeBSD-clibs-13.1p5 = FreeBSD-clibs-dev-13.1p5 = FreeBSD-cxgbe-tools-13.1p5 = FreeBSD-dma-13.1p5 = FreeBSD-dpv-13.1p5 = FreeBSD-dpv-dev-13.1p5 = FreeBSD-dtrace-13.1p5 = FreeBSD-dtrace-dev-13.1p5 = FreeBSD-dwatch-13.1p5 = FreeBSD-ee-13.1p5 = FreeBSD-efi-tools-13.1p5 = FreeBSD-efi-tools-dev-13.1p5 = FreeBSD-fetch-13.1p5 = FreeBSD-fetch-dev-13.1p5 = FreeBSD-ggate-13.1p5 = FreeBSD-hast-13.1p5 = FreeBSD-hostapd-13.1p5 = FreeBSD-iscsi-13.1p5 = FreeBSD-iscsilegacy-13.1p5 = FreeBSD-jail-13.1p5 = FreeBSD-kerberos-13.1p5 = FreeBSD-kernel-polisy-13.1p5 = FreeBSD-lib9p-13.1p5 = FreeBSD-lib9p-dev-13.1p5 = FreeBSD-libarchive-13.1p5 = FreeBSD-libarchive-dev-13.1p5 = FreeBSD-libbegemot-13.1p5 = FreeBSD-libbegemot-dev-13.1p5 = FreeBSD-libblocksruntime-13.1p5 = FreeBSD-libblocksruntime-dev-13.1p5 = FreeBSD-libbsdstat-13.1p5 = FreeBSD-libbsdstat-dev-13.1p5 = FreeBSD-libbsm-13.1p5 = FreeBSD-libbsm-dev-13.1p5 = FreeBSD-libbz2-13.1p5 = FreeBSD-libbz2-dev-13.1p5 = FreeBSD-libcasper-13.1p5 = FreeBSD-libcasper-dev-13.1p5 = FreeBSD-libcompat-13.1p5 = FreeBSD-libcompat-dev-13.1p5 = FreeBSD-libcompiler_rt-13.1p5 = FreeBSD-libcompiler_rt-dev-13.1p5 = FreeBSD-libcuse-13.1p5 = FreeBSD-libcuse-dev-13.1p5 = FreeBSD-libdwarf-13.1p5 = FreeBSD-libdwarf-dev-13.1p5 = FreeBSD-libelftc-13.1p5 = FreeBSD-libevent1-13.1p5 = FreeBSD-libevent1-dev-13.1p5 = FreeBSD-libexecinfo-13.1p5 = FreeBSD-libexecinfo-dev-13.1p5 = FreeBSD-libipt-13.1p5 = FreeBSD-libipt-dev-13.1p5 = FreeBSD-libldns-13.1p5 = FreeBSD-libldns-dev-13.1p5 = FreeBSD-liblzma-13.1p5 = FreeBSD-liblzma-dev-13.1p5 = FreeBSD-libmagic-13.1p5 = FreeBSD-libmagic-dev-13.1p5 = FreeBSD-libnetmap-13.1p5 = FreeBSD-libnetmap-dev-13.1p5 = FreeBSD-libopie-13.1p5 = FreeBSD-libopie-dev-13.1p5 = FreeBSD-libpathconv-13.1p5 = FreeBSD-libpathconv-dev-13.1p5 = FreeBSD-librss-13.1p5 = FreeBSD-librss-dev-13.1p5 = FreeBSD-libsdp-13.1p5 = FreeBSD-libsdp-dev-13.1p5 = FreeBSD-libsmb-13.1p5 = FreeBSD-libsmb-dev-13.1p5 = FreeBSD-libsqlite3-13.1p5 = FreeBSD-libsqlite3-dev-13.1p5 = FreeBSD-libstdbuf-13.1p5 = FreeBSD-libstdbuf-dev-13.1p5 = FreeBSD-libstdthreads-13.1p5 = FreeBSD-libstdthreads-dev-13.1p5 = FreeBSD-libthread_db-13.1p5 = FreeBSD-libthread_db-dev-13.1p5 = FreeBSD-libucl-13.1p5 = FreeBSD-libucl-dev-13.1p5 = FreeBSD-libvgl-13.1p5 = FreeBSD-libvgl-dev-13.1p5 = FreeBSD-liby-dev-13.1p5 = FreeBSD-lld-13.1p5 = FreeBSD-lldb-13.1p5 = FreeBSD-mlx-tools-13.1p5 = FreeBSD-mtree-13.1p5 = FreeBSD-natd-13.1p5 = FreeBSD-natd-dev-13.1p5 = FreeBSD-newsyslog-13.1p5 = FreeBSD-nfs-13.1p5 = FreeBSD-openssl-13.1p5 = FreeBSD-openssl-dev-13.1p5 = FreeBSD-periodic-13.1p5 = FreeBSD-pf-13.1p5 = FreeBSD-pf-dev-13.1p5 = FreeBSD-pkg-bootstrap-13.1p5 = FreeBSD-ppp-13.1p5 = FreeBSD-quotacheck-13.1p5 = FreeBSD-rc-13.1p5 = FreeBSD-rcmds-13.1p5 = FreeBSD-rdma-13.1p5 = FreeBSD-runtime-13.1p5 = FreeBSD-runtime-dev-13.1p5 = FreeBSD-ssh-13.1p5 = FreeBSD-ssh-dev-13.1p5 = FreeBSD-syslogd-13.1p5 = FreeBSD-tcpd-13.1p5 = FreeBSD-tests-13.1p5 = FreeBSD-unbound-13.1p5 = FreeBSD-utilities-13.1p5 = FreeBSD-utilities-dev-13.1p5 = FreeBSD-vi-13.1p5 = FreeBSD-vt-data-13.1p5 = FreeBSD-wpa-13.1p5 = FreeBSD-yp-13.1p5 = FreeBSD-zoneinfo-13.1p5 = bash-5.1.16 < brotli-1.0.9,1 = c-ares-1.19.0 = ca_root_nss-3.87 = curl-7.87.0_1 = cyrus-sasl-2.1.28 = dmidecode-3.3 < dual-dhclient-1.0_1 = e2fsprogs-libuuid-1.47.0 > expat-2.5.0 = fontconfig-2.13.94_2,1 < freetype2-2.12.1 < fribidi-1.0.12 = gettext-runtime-0.21.1 = giflib-5.2.1 = git-2.37.0 < glib-2.72.2,2 < gmake-4.3_2 = graphite2-1.3.14 = harfbuzz-4.4.0 < icu-72.1,1 = indexinfo-0.3.1 = isc-dhcp44-client-4.4.2P1 < isy-5.5.5_2 = jbigkit-2.1_1 = jpeg-turbo-2.1.3 < json-c-0.16 = lcms2-2.13.1 = libX11-1.7.2,1 = libXScrnSaver-1.2.3_2 < libXau-1.0.9 = libXdmcp-1.1.3 = libXext-1.3.4,1 = libXft-2.3.4 < libXrender-0.9.10_2 = libarchive-3.6.2,1 = libbson-1.23.2_1 > libcjson-1.7.15 = libedit-3.1.20210910,1 < libffi-3.4.4 = libgcrypt-1.9.4_1 = libgpg-error-1.45 < libiconv-1.17 = libidn2-2.3.4 = libimagequant-2.17.0 < libltdl-2.4.7 = liblz4-1.9.4,1 = libnghttp2-1.51.0_1 = libpsl-0.21.2_1 = libpthread-stubs-0.4 = libraqm-0.9.0 = libssh2-1.10.0_1,3 = libunistring-1.1 = libuv-1.44.2 = libwebsockets-4.2.2_1 = libxcb-1.14_1 < libxml2-2.10.3_1 = libxslt-1.1.35_3 < libyaml-0.2.5 = mDNSResponder-1310.140.1 = mongo-c-driver-1.8.1 = mongodb36-3.6.23_1 = mosquitto-2.0.15 = mpdecimal-2.5.1 = node18-18.13.0 = npm-node18-9.4.1 = nspr-4.34 < nss-3.80 < openjpeg-2.5.0 = p5-Authen-SASL-2.16_1 = p5-CGI-4.54 < p5-Clone-0.45 < p5-Digest-HMAC-1.04 = p5-Encode-Locale-1.05 = p5-Error-0.17029 = p5-HTML-Parser-3.78 < p5-HTML-Tagset-3.20_1 = p5-HTTP-Date-6.05 = p5-HTTP-Message-6.37 < p5-IO-HTML-1.004 = p5-IO-Socket-INET6-2.72_1 = p5-IO-Socket-SSL-2.074 < p5-LWP-MediaTypes-6.04 = p5-Mozilla-CA-20211001 < p5-Net-SSLeay-1.92 = p5-Socket6-0.29 = p5-TimeDate-2.33,1 = p5-URI-5.10 < pcre-8.45_3 = pcre2-10.40 < perl5-5.32.1_3 = pg3-3.1.17_1 = pkg-1.19.1 = png-1.6.37_1 < polyglot-2.2.11_3 > powerdxx-0.4.4_1 = py39-acme-1.27.0,1 < py39-aiohttp-3.8.1_1 < py39-aiosignal-1.2.0 = py39-appdirs-1.4.4 = py39-async_timeout-4.0.2 = py39-attrs-21.4.0 < py39-cached-property-1.5.2 = py39-certbot-1.27.0,1 < py39-certifi-2022.5.18.1 < py39-cffi-1.15.0_1 < py39-charset-normalizer-2.0.12 < py39-configargparse-1.5.3 = py39-configobj-5.0.6_1 = py39-cryptography-3.4.8 < py39-dateparser-1.1.0 < py39-dateutil-2.8.2 = py39-defusedxml-0.7.1 = py39-distro-1.7.0 < py39-frozenlist-1.3.0 < py39-holidays-0.9.12 = py39-idna-3.3 < py39-isodate-0.6.1 = py39-josepy-1.13.0 = py39-lxml-4.9.0 < py39-multidict-6.0.2 < py39-netifaces-0.11.0 = py39-olefile-0.46 = py39-openssl-20.0.1,1 = py39-parsedatetime-2.6 = py39-pillow-9.1.1 < py39-pip-22.1.2 < py39-pycparser-2.21 = py39-pycryptodome-3.12.0 < py39-pyrfc3339-1.1 = py39-pysocks-1.7.1 = py39-pytz-2021.3,1 < py39-regex-2020.7.14 < py39-requests-2.28.0 < py39-requests-toolbelt-0.9.1_1 < py39-setuptools-62.1.0_1 < py39-six-1.16.0 = py39-sqlite3-3.9.13_7 < py39-tkinter-3.9.13_6 < py39-tornado4-4.5.3 = py39-tzlocal-1.5.1 < py39-urllib3-1.26.9,1 < py39-xmlsec-1.3.12_2 < py39-yaml-5.4.1 < py39-yarl-1.7.2 < py39-zeep-4.1.0 < py39-zope.component-4.2.2 = py39-zope.event-4.1.0 = py39-zope.interface-5.3.0 = python3-3_3 = python38-3.8.13_2 < python39-3.9.16 = rapidjson-1.1.0.524 < readline-8.2.0 = snappy-1.1.9_1 = sqlite3-3.38.5,1 < sudo-1.9.11p3 < tcl86-8.6.12 < tiff-4.3.0 < tk86-8.6.12 < tpm2-tools-5.2 < tpm2-tss-2.4.5 < udx-3.3.6 = webp-1.2.2 < xmlsec1-1.2.34 < xorgproto-2021.5 < zstd-1.5.2_1 = Edited February 11, 2023 by macjeff
macjeff Posted February 11, 2023 Author Posted February 11, 2023 I CAN get into Pg2. I cant get into PG3 or ISY but SSH shows they are both running.
joeria Posted February 11, 2023 Posted February 11, 2023 Same thing happed to me. How can you check in ssh if PG3 and IOP are running.
macjeff Posted February 11, 2023 Author Posted February 11, 2023 10 minutes ago, joeria said: Same thing happed to me. How can you check in ssh if PG3 and IOP are running. first you should see pg2 is running https://YOUR IP/ then if you know how to SSH then, you can do so but if you dont I would not go any further without support. I just did sudo service isy start sudo service pg3 start both replied its already running. Also try doing pkg version not sure what the = and < mean next to each one. Something has lost links to something else. I think we are OK but I think tech support will have to jump in. Hoping people see this post before they knock themselves out for the weekend like we both just did!!
macjeff Posted February 11, 2023 Author Posted February 11, 2023 12 minutes ago, bgrubb1 said: too late I am in same boat, ticket in If the fix is just a bunch of SSH commands to re-install or re-link things PLEASE post them here. I will do the same.
joeria Posted February 11, 2023 Posted February 11, 2023 Thanks, I got already running to icy and pg 3 as well, yet I would have gotten a text on icy restart which I did not so all is not running I have ticket in as well
macjeff Posted February 11, 2023 Author Posted February 11, 2023 Did any of you have your wife or someone at home tell you how stupid you are to do an update on a Saturday when there is most likely no tech support? LOL I know it was and I am sure Michel agrees. But I was working on a Node Server issue with another developer and wanted to make sure it was all up to date.
macjeff Posted February 11, 2023 Author Posted February 11, 2023 Just now, macjeff said: Did any of you have your wife or someone at home tell you how stupid you are to do an update on a Saturday when there is most likely no tech support? LOL I know it was and I am sure Michel agrees. But I was working on a Node Server issue with another developer and wanted to make sure it was all up to date. and worse this broke Alexa so now I am the Devil!!!
firstone Posted February 11, 2023 Posted February 11, 2023 Can you guys be more specific on what is "dead"? Seems like you can ssh and package are there? Are you unable to open AC or something else? Do you see isy service running? [admin@polisy ~]$ sudo service isy status isy is running as pid 29385. [admin@polisy ~]$ ps aux|grep isy isy 29386 3.9 3.5 292336 146852 - S Wed10 154:04.05 /usr/local/bin/isy-freebsd-x64 -w /var/isy isy 29385 0.0 0.1 12848 2292 - Is Wed10 0:00.06 daemon: /usr/local/bin/isy-freebsd-x64[293 admin 41314 0.0 0.1 12840 2404 0 S+ 15:04 0:00.01 grep isy If so, maybe just advertising doesn't work?
bgrubb1 Posted February 11, 2023 Posted February 11, 2023 isy 1324 0.0 0.1 12848 2192 - Ss 11:27 0:05.44 daemon: /usr
macjeff Posted February 11, 2023 Author Posted February 11, 2023 Pg3 wont open ISY wont show up in admin console at all.
macjeff Posted February 11, 2023 Author Posted February 11, 2023 isy is running as pid 1290 nothing in admin console maybe you are correct that its advertising but if you are correct wouldnt the portal see it running? Its like its getting hung up One important thing which I am sure the others can confirm...when you reboot you get NO BEEP like usual. The LED on the front only the far left is on. If I open it up every 20 seconds or so I see the LED on far right on the board (hidden by case) light up and every 10 seconds or so the LED closes to the expansion slots on the right lights up
firstone Posted February 11, 2023 Posted February 11, 2023 can you hit it by ip from browser? https://<ip>:8443/desc
joeria Posted February 11, 2023 Posted February 11, 2023 (edited) both ports 8443 and 3000 return not found Edited February 11, 2023 by joeria
macjeff Posted February 11, 2023 Author Posted February 11, 2023 3 minutes ago, joeria said: both ports 8443 and 3000 return not found same here but if I just go to https://<IP>/ I get the Pg2 website
firstone Posted February 11, 2023 Posted February 11, 2023 You'll have to wait for UDI unfortunately. You can check isy or udx service log files but it's not like you can do anything to fix it. Here are my versions for the reference. Not sure if it's possible or a good idea to try to downgrade. I would wait udx-3.3.5_4 = isy-5.5.5_1 = pg3-3.1.17 =
macjeff Posted February 11, 2023 Author Posted February 11, 2023 24 minutes ago, firstone said: Try restarting udx Already tried that. I think it’s some sort of permissions issue where the files aren’t linked correctly
Red Posted February 11, 2023 Posted February 11, 2023 Exact same issue on Polisy. Upgrade packages through IoX. Submitted a ticket about an hour ago. I've power cycled a few times, tried restarting udx (for what that's worth), with no change. Switches to single left light illuminated about 10 seconds of plugin, never beeps, and then just sits there. It's accessible by SSH but no web interface, no IoX, etc. It reset my admin to admin/admin.
macjeff Posted February 11, 2023 Author Posted February 11, 2023 1 minute ago, joeria said: how do you restart udx? Rebooting should restart it but I also did sudo pkg udx restart
macjeff Posted February 11, 2023 Author Posted February 11, 2023 Just now, macjeff said: Rebooting should restart it but I also did sudo pkg udx restart Also tried a stop and start
joeria Posted February 11, 2023 Posted February 11, 2023 thanks. I also saw on an older thread where something similar was reported that restarting polisy without plm attached resolved the issue. I just tried that - no change.
Red Posted February 11, 2023 Posted February 11, 2023 1 hour ago, macjeff said: same here but if I just go to https://<IP>/ I get the Pg2 website Same. Pg2 site seems to work okay. But no Pg3 or IoX.
Recommended Posts