whywork

Bah and Ugh! Following migration to PG3x two daya ago, I get constant Node/App up down messages and PG3 starting messages. Background: Polisy Pro 5.7 via ethernet with PG2 and PG3 running for months with no Polyglot errors/messages. End of life - updated to PG3x two days ago After several reboots - PG3x 3.2.16 finally seemed up and running ALL - Old installed node servers were up and running. BUT Got 37 messages in UD mobile last night about all installed node servers starting and stopping. Also got several messages about PG3 starting. Tried soft reboot, Cold reboot and "update packages" - No Joy. Now when I try to logon to PG3x, get http error auth failure then try again immediately and do get to logon to PG3x but some node servers are disconnected. (see PG3x log snippet below) ALSO - from java IoX launcher - still get offered ability to logon to PG2 (yes PG2) - it does go nowhere but still it is offered. Bah Went from working PG2 and PG3 to buggy PG3x installation Suggestions? 11/12/2023, 24:00:45 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:00:45 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:00:47 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1212003/report/status/GV3/4/45 11/12/2023, 24:00:47 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 324.423465ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1212003/report/status/GV3/4/45 11/12/2023, 24:00:47 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:00:48 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:00:49 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_645646/report/status/GV3/4/45 11/12/2023, 24:00:49 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 289.859629ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_645646/report/status/GV3/4/45 11/12/2023, 24:00:50 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:00:51 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:00:52 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_645954/report/status/GV3/4/45 11/12/2023, 24:00:52 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 187.748774ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_645954/report/status/GV3/4/45 11/12/2023, 24:00:53 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:00:54 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:00:54 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_646253/report/status/GV3/4/45 11/12/2023, 24:00:55 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 208.306427ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_646253/report/status/GV3/4/45 11/12/2023, 24:00:56 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:00:56 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:00:58 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_842242/report/status/GV3/4/45 11/12/2023, 24:00:58 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 186.951931ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_842242/report/status/GV3/4/45 11/12/2023, 24:00:59 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:01:00 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:01:00 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1207309/report/status/GV3/4/45 11/12/2023, 24:01:00 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 168.404506ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1207309/report/status/GV3/4/45 11/12/2023, 24:01:02 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:01:02 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:01:02 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1448163/report/status/GV3/4/45 11/12/2023, 24:01:03 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 19.262084ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1448163/report/status/GV3/4/45 11/12/2023, 24:01:16 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:01:17 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:01:18 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:01:18 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:01:19 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:01:19 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:01:19 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1212003/report/status/CLIHUM/77/22 11/12/2023, 24:01:20 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 358.756243ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1212003/report/status/CLIHUM/77/22 11/12/2023, 24:01:20 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1212003/report/status/DEWPT/26/17 11/12/2023, 24:01:21 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1212003/report/status/GV3/0/45 11/12/2023, 24:01:21 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:00:f1:ee_1: set 11/12/2023, 24:01:21 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 429.390843ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1212003/report/status/DEWPT/26/17 11/12/2023, 24:01:21 [pg3] info: IoX Response: [Try: 1] [00:0d:b9:53:36:9c] :: [200] :: 204.519976ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_1212003/report/status/GV3/0/45 11/12/2023, 24:01:22 [pg3] info: Received commands on topic udi/pg3/ns/status/00:0d:b9:53:36:9c_1: set 11/12/2023, 24:01:23 [pg3] info: IoX Request: [Try: 1] [00:0d:b9:53:36:9c] :: - http://127.0.0.1:8080/rest/ns/1/nodes/n001_645646/report/status/GV3/0/45 11/12/2023, 24:01:23 [pg3] info: IoX Response: [Try: 1]

Found the place in UD mobile that seems about setting up Eisy Wifi credentials. 1) no mention of Polisy 2) does mention barcode on Eisy, my PolisyPro has no barcode Ticket opened.

Hi, Thanks for the reply. It seems I was not clear about what I meant by configuring wifi. (not just DHCP) To get Polisy to connect to my wifi somewhere the SSID and password need to be entered/configured. The only place to enter SSID and password on my Polisy Pro is under PG2/System/Configure Polisy then things like timezone, Ethernet and Wifi settings are exposed. The java Admin console offers nothing about wifi. PG3 has no "settings" for Polisy and thus no ethernet nor wifi settings available. So - If I migrate to PG3x (killing PG2 and PG3) and need to change my PolisyPro wifi settings (SSID) does PG3x expose wifi settings? Where?

Can Polisy Wifi be configured in PG3x? Seems like PG2 and PG3 are end-of-life. I have a PolisyPro (with wifi) running PG2 and PG3; and am thinking of migrating to PG3x. To configure Polisy wifi, I need to use PG2, there is no setting in PG3 (nor the admin console) to configure wifi settings. I looked at the wiki (could not find info) but, if I migrate to PG3x (killing both PG2 and PG3): Where and how do/can I use to PGx3 to configure Wifi on PolisyPro? Thanks

I use and enjoy my Universal Devices ISY/Polisy every day (37 devices, 48 programs, 7 node servers). My setup works so well, I sometimes forget how to logon, because i don't often need to change or check anything. "It just works." Had a problem with recent upgrade on my Polisy Pro going awry - device unreachable. Opened a trouble ticket. Within 24 hrs of receipt of Polisy data, Michel had resolved the issue. I am now up and running again, as though nothing had happened. Excellent support. Thank you

I use and enjoy my ISY 994 and Polisy every day. Can't offer any insight about freeing up ports 80 & 443 for IoX. One potential caveat: Wifi configuration I believe that removing PG2 may be problematic for managing settings for Polisy Wifi - I have not found any way to configure Polisy Wifi settings in PG3 to date, nor the the Admin Console; only available in PG2. SSH/command line editing is not encouraged by mangement. Your mileage may vary.

Thank you both for feedback/insights. Consummated purchase of Yolink nodeserver on PG3. Shows date and time of purchase and the expected no-expiry date. Seems to be working on my ISY. Thanks,

Yolink Speaker Hub downside it that it requires connection to the "cloud" to work. Yolink has "announced" that a new hub is under development with local API, no cloud required. I hope it will also be able to do text-to-speech (might be a lot of computing unless pre-loaded soundfiles were created and stored locally, from text into speech). We will see.

Hi, Thanks to both of you for your quick and helpful replies. To avoid potential troubles/conflicts, I deleted the Yolink nodeserver from my Polisy and left only the Yolink nodeserver connected to my ISY. Onward - The Good: I went to PG3 Custom Configuration Parameters and saw TTSn and NBR_TTS. Incremented NBR_TTS from 1 to 2. Restarted Yolink Nodeserver and was presented with a new blank TTS field (labeled TTS1 because the first one is TTS0) Added new text and saved. Restarted Yolink Nodeserver and rebooted ISY. The Admin Console Device page now shows Select Message dropdown with the actual new words I typed as each of the two message text(s). Choosing a particular message and hitting the play button; Sound Hub speaks the message! Yay. The learning: I have a program that emails me and rings X10 power horn if the garage door closes. Added then statement Set 'Speaker Hub 1' Play Message. Tried it and got nothing. Had to add Set 'Speaker Hub 1' Select Message Test 2 - See below Girl Garage Email Closed - [ID 004C][Parent 0001] If 'Girl Garage Door-Sensor' Status is On Then Send Notification to 'Default' Run Program 'PowerHornDongDongA5' (Then Path) Set 'Speaker Hub 1' Select Message Test 2 Set 'Speaker Hub 1' Play Message Else - No Actions - (To add one, press 'Action') It Works! Now all I have to do is put in more appropriate text (not Test 2) in the custom TTS fields. Yolink Speaker Hub is a wifi $25 configurable dinger/alarm/MP3/text-to-speech device that works with PG3 Yolink nodeserver and ISY/Polisy programs. Thanks again for the Yolink nodeserver. I look forward to actually paying for the license (see my question in the PG3 Polyglot forum about UUIDs)

Hi, I use and enjoy my ISY and Polisy every day. Wanted to purchase Yolink nodeserver but was confused about where/to which device, a license would be bound. See below. I have an ISY 994 in production and Polisy as test mule on the same network. PG3 running on Polisy. - Under PG3 Version 3.1.2, ISY tab, see both devices with their respective UUIDs. Installed trial Yolink nodeserver on both ISY and Polisy. Works on both. Chose ISY in PG3, went to nodeserver store to purchase Yolink license, was presented with a pop up with (correct) ISY UUID and description of Yolink version to be purchased. Clicked through to logon to ISY Portal and was then presented with popup Paypal for UUID of POLISY -NOT- the UUID of ISY (can see both ISY an Polisy in portal below/under popup window) I cannot edit this popup window to change UUID or select different device. Confused. Started fresh to make sure I was choosing ISY, not Polisy before starting, same result. Is a nodeserver license tied to the UUID of the device where it is being used (ISY for me) or is it OK to be tied to the UUID of the server machine (Polisy in my case)? What am I doing wrong? Your help and education will be appreciated.

Hi, Nice job with the Yolink (YL) node server (installed trial v0.8.89) I am primarily interested in using speaker hub for alerts/custom messages; not happy with Alexa/Google spoken alerts as they seemed to break often and require lots of fiddling to get working again. Install of YL node server went well. Of note: I have ISY 944 in production and Polisy as a test mule on my same local network and used the same UAID and Secret Key on both. Had to reboot everything to get all/both connected to Speaker Hub and working. Testing messages - if both ISY and Polisy try to send message at the same time, one message gets backed up and comes in a few minutes (yes minutes) later. Now to the tricky stuff (at least for me) - How to actually have Speaker Hub text to speech something other than the exact words "Message 0"? I see in your post https://forum.universal-devices.com/topic/37458-announcements-with-yolink-and-speaker/ you say "The latest YoLink node server does support the speaker - not as elegant as I would like, but there are some limitations with regarding to text in the AC (you basically need to predefine you text (announcements) and then you can pick them in the AC) - " I'm confused, where exactly would I predefine a message? In my Administrative Console Device Speaker Hub there is a dropdown menu for Select Message, but only Message 0 appears. Is this something that needs to be predefined via the Yolink App? Or where on the ISY? Thanks PS Not sure if that matters, nor is it your problem. Tried to pay for license but ISY portal kept trying to use UUID of my Polisy not ISY994 and would not let me change it.

Thanks for the clarification. No worries

I use and enjoy my ISY and Polisy every day. Polisy Pro - Stuck on PG3 3.1.17_1 Name : pg3 Version : 3.1.17_1 Installed on : Thu Feb 9 17:02:58 2023 EST Tried sudo /usr/local/etc/udx.d/static/udxops.sh upgrade.polisy updates isy to 5.57 and udx to 3.3.6_5 BUT get these two error messages Thu Feb 23 13:11:24 EST 2023|/usr/local/etc/udx.d/static/udxops.sh: upgrading polisy complete ... UDX_UPGRADE_STATUS: active -> inactive sysrc: unknown variable 'pg3x_on_polisy' Thu Feb 23 13:11:27 EST 2023|/usr/local/etc/udx.d/static/udxops.sh: need pg3x capabilities to publish mqtt messages ... Tried Admin console package update, restart pg3, cold boot, java cache clear. and command line sudo /usr/local/etc/udx.d/static/udxops.sh upgrade.polisy again. Stuck at 3.1.17_1 sudo pkg info pg3 pg3-3.1.17_1 Name : pg3 Version : 3.1.17_1 PG3 web page says 3.1.18 available, but I can't seem to move past 3.1.17_1 Suggestions? Hah! User ERROR I see that Polisy users are still on 3.1.17 and EISY are on 3.2x. I was confused by PG3 web page telling me about 3.18

I use and enjoy my ISY 994 and Polisy every day. Upgrade 5.5.4 to 5.5.5 problems for me Working well until now - Polisy Pro Zmatter, multi-homed (both ethernet and wifi active) after upgrade to 5.5.5 Sat Feb 4 06:05:46 EST 2023|/usr/local/etc/udx.d/static/udxops.sh: starting upg rading polisy ... UDX_UPGRADE_STATUS: available -> active sysrc: unknown variable 'pg3x_on_polisy' Sat Feb 4 06:06:32 EST 2023|/usr/local/etc/udx.d/static/udxops.sh: upgrading polisy complete ... UDX_UPGRADE_STATUS: active -> inactive sysrc: unknown variable 'pg3x_on_polisy' Sat Feb 4 06:06:35 EST 2023|/usr/local/etc/udx.d/static/udxops.sh: need pg3x capabilities to publish mqtt messages ... Now SSH works fine and can log onto Polisy IoX finder sees Polisy on Ethernet but not Wifi (can add manually) Admin console shows 5.5.5 PG3 web page is available/running but reports version is still 5.5.4 sudo service pg3 restart Cold boot: no joy Suggestions?

While I'm at it. I LOVE the UD Mobile app. Works and is getting better every day. Maybe UD Mobile could: Allow user to check status of Polisy for updates/upgrade. Allow user to intiate Polisy upgrade. Allow user to configure Polisy timezone, network, wifi

Seems like PG2 "Polisy Settings" just points to https://192.168.1.194/polisyconf Perhaps PG3 could point there, too?

Hi, Recently reset my Polisy wifi and had to rejoin my wifi SSID. PG2 offers "Polisy Settings" where I can enable wifi and scan/connect. (Also allows me to set PG2 timezone) I could find NO options in PG3 to manage wifi (nor timezone) Confused, (if PG2 is to be deprecated).

My Polisy is back up and running. Thanks to UDI support. Instructions to, "Please click on the button on the front only once and wait for 4 + 1 beeps, then reboot." Worked. Back up and running. Thank you for your efforts

Hi, Sorry for delay. Traveling. Have responded to ticket.

Ticket submitted. https://www.universal-devices.com/my-tickets/?wpsc-section=ticket-list works Thanks

Here is what I see Universal Devices Polisy coreboot build 20192108 BIOS version v1.0.0 4080 MB ECC DRAM ________ ________ ___ ___ ________ ___ ___ |\ __ \|\ __ \|\ \ |\ \|\ ____\ |\ \ / /| \ \ \_\ \ \ \|\ \ \ \ \ \ \ \ \___|_ \ \ \/ / / \ \ ____\ \ \ \ \ \ \ \ \ \ \_____ \ \ \ / / \ \ \___|\ \ \_\ \ \ \____\ \ \|____|\ \ \/ / / \ \__\ \ \_______\ \_______\ \__\____\_\ \ _/ / / \|__| \|_______|\|_______|\|__|\_________\|___/ / \|_________\|___|/ Press F9 to enter Boot Manager Menu ________ ________ ___ ___ ________ ___ ___ |\ __ \|\ __ \|\ \ |\ \|\ ____\ |\ \ / /| \ \ \_\ \ \ \|\ \ \ \ \ \ \ \ \___|_ \ \ \/ / / \ \ ____\ \ \ \ \ \ \ \ \ \ \_____ \ \ \ / / \ \ \___|\ \ \_\ \ \ \____\ \ \|____|\ \ \/ / / \ \__\ \ \_______\ \_______\ \__\____\_\ \ _/ / / \|__| \|_______|\|_______|\|__|\_________\|___/ / \|_________\|___|/ >> FreeBSD EFI boot block Loader path: /boot/loader.efi Initializing modules: ZFS UFS Load Path: \EFI\BOOT\BOOTX64.EFI Load Device: PciRoot(0x0)/Pci(0x11,0x0)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,57AC038 8-220D-11EA-B769-598ECAF57D7D,0x428,0x640) BootCurrent: 0001 BootOrder: 0000 0001[*] Probing 5 block devices......*. done ZFS found the following pools: zudi UFS found no partitions Consoles: EFI console Reading loader env vars from /efi/freebsd/loader.env Setting currdev to disk0p3: FreeBSD/amd64 EFI loader, Revision 1.1 Command line arguments: loader.efi Image base: 0xccc28000 EFI version: 2.70 EFI Firmware: EDK II (rev 1.00) Console: efi (0x1000) Load Path: HD(3,GPT,57AEA4AD-220D-11EA-B769-598ECAF57D7D,0xA68,0x3390000) Load Device: PciRoot(0x0)/Pci(0x11,0x0)/Sata(0x0,0xFFFF,0x0)/HD(3,GPT,57AEA4A D-220D-11EA-B769-598ECAF57D7D,0xA68,0x3390000) BootCurrent: 0001 BootOrder: 0000 0001[*] BootInfo Path: PciRoot(0x0)/Pci(0x11,0x0)/Sata(0x0,0xFFFF,0x0) Ignoring Boot0001: Only one DP found Trying ZFS pool Setting currdev to zfs:zudi/ROOT/default: Loading /boot/defaults/loader.conf Loading /boot/defaults/loader.conf Loading /boot/device.hints Loading /boot/loader.conf Loading /boot/loader.conf.local \ Loading kernel... /boot/kernel/kernel text=0x110348 text=0x8ff500 text=0x15b30c data=0x140 data=0x15a8fc+0x2a4704 syms=[0x8+0x11da38+0x8+0x13d790] Loading configured modules... /boot/kernel/nctgpio.ko size 0x5328 at 0x145c000 loading required module 'superio' /boot/kernel/superio.ko size 0x6c80 at 0x1462000 /boot/kernel/zfs.ko size 0x5bb320 at 0x1469000 /boot/entropy size=0x1000 /etc/hostid size=0x25 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... staging 0xc4000000 (not copying) tramp 0xcef5e000 PT4 0xcef55000 Start @ 0xffffffff80310360 ... EFI framebuffer information: addr, size 0x0, 0x0 dimensions 0 x 0 stride 0 masks 0x00000000, 0x00000000, 0x00000000, 0x00000000 ---<<BOOT>>--- Copyright (c) 1992-2021 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 13.1-RELEASE-p1 releng/13.1-n250155-514a191356c1 POLISY amd64 FreeBSD clang version 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303) VT(vga): resolution 640x480 CPU: AMD GX-412TC SOC (998.32-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x730f01 Family=0x16 Model=0x30 Stepping=1 Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x3ed8220b<SSE3,PCLMULQDQ,MON,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C> AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM> AMD Features2=0x1d4037ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,Topology,PNXC,DBE,PTSC,PL2I> Structured Extended Features=0x8<BMI1> XSAVE Features=0x1<XSAVEOPT> SVM: NP,NRIP,AFlush,DAssist,NAsids=8 TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 4098949120 (3909 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: <COREv4 COREBOOT> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) random: unblocking device. ioapic1: MADT APIC ID 5 != hw id 0 ioapic0 <Version 2.1> irqs 0-23 ioapic1 <Version 2.1> irqs 24-55 Launching APs: 2 1 3 random: entropy device external interface WARNING: Device "spkr" is Giant locked and may be deleted before FreeBSD 14.0. vtvga0: <VT VGA driver> efirtc0: <EFI Realtime Clock> efirtc0: registered as a time-of-day clock, resolution 1.000000s smbios0: <System Management BIOS> at iomem 0xcf7c9000-0xcf7c901e smbios0: Version: 3.3, BCD Revision: 3.3 aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS> acpi0: <COREv4 COREBOOT> acpi0: Power Button (fixed) atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.000000s Event timer "RTC" frequency 32768 Hz quality 0 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x818-0x81b on acpi0 apei0: <ACPI Platform Error Interface> on acpi0 cpu0: <ACPI CPU> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pcib0: could not evaluate _ADR - AE_NOT_FOUND pci0: <ACPI PCI bus> on pcib0 pci0: <base peripheral, IOMMU> at device 0.2 (no driver attached) pcib1: <ACPI PCI-PCI bridge> at device 2.1 on pci0 pci1: <ACPI PCI bus> on pcib1 ath0: <Atheros AR946x/AR948x> mem 0xf7900000-0xf797ffff at device 0.0 on pci1 ar9300_flash_map: unimplemented for now Restoring Cal data from DRAM Restoring Cal data from EEPROM Restoring Cal data from Flash Restoring Cal data from Flash Restoring Cal data from OTP ar9300_hw_attach: ar9300_eeprom_attach returned 0 ath0: [HT] enabling HT modes ath0: [HT] enabling short-GI in 20MHz mode ath0: [HT] 1 stream STBC receive enabled ath0: [HT] 1 stream STBC transmit enabled ath0: [HT] LDPC transmit/receive enabled ath0: [HT] 2 RX streams; 2 TX streams ath0: AR9460 mac 640.2 RF5110 phy 1158.6 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000 pcib2: <ACPI PCI-PCI bridge> at device 2.2 on pci0 pcib2: failed to allocate initial I/O port window: 0x1000-0x1fff pci2: <ACPI PCI bus> on pcib2 igb0: <Intel(R) I210 Flashless (Copper)> port 0x2000-0x201f mem 0xf7a00000-0xf7a1ffff,0xf7a20000-0xf7a23fff at device 0.0 on pci2 igb0: NVM V0.6 imgtype5 igb0: Using 1024 TX descriptors and 1024 RX descriptors igb0: Using 4 RX queues 4 TX queues igb0: Using MSI-X interrupts with 5 vectors igb0: Ethernet address: 00:0d:b9:53:36:9c igb0: netmap queues/slots: TX 4/1024, RX 4/1024 pcib3: <ACPI PCI-PCI bridge> at device 2.3 on pci0 pcib3: failed to allocate initial I/O port window: 0x2000-0x2fff pci3: <ACPI PCI bus> on pcib3 igb1: <Intel(R) I210 Flashless (Copper)> port 0x3000-0x301f mem 0xf7b00000-0xf7b1ffff,0xf7b20000-0xf7b23fff at device 0.0 on pci3 igb1: NVM V0.6 imgtype5 igb1: Using 1024 TX descriptors and 1024 RX descriptors igb1: Using 4 RX queues 4 TX queues igb1: Using MSI-X interrupts with 5 vectors igb1: Ethernet address: 00:0d:b9:53:36:9d igb1: netmap queues/slots: TX 4/1024, RX 4/1024 pcib4: <ACPI PCI-PCI bridge> at device 2.4 on pci0 pcib4: failed to allocate initial I/O port window: 0x3000-0x3fff pci4: <ACPI PCI bus> on pcib4 igb2: <Intel(R) I210 Flashless (Copper)> port 0x5000-0x501f mem 0xf7c00000-0xf7c1ffff,0xf7c20000-0xf7c23fff at device 0.0 on pci4 igb2: NVM V0.6 imgtype5 igb2: Using 1024 TX descriptors and 1024 RX descriptors igb2: Using 4 RX queues 4 TX queues igb2: Using MSI-X interrupts with 5 vectors igb2: Ethernet address: 00:0d:b9:53:36:9e igb2: netmap queues/slots: TX 4/1024, RX 4/1024 pci0: <encrypt/decrypt> at device 8.0 (no driver attached) xhci0: <AMD FCH USB 3.0 controller> mem 0xf7fa2000-0xf7fa3fff at device 16.0 on pci0 xhci0: 32 bytes context size, 64-bit DMA usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 ahci0: <AMD Hudson-2 AHCI SATA controller> port 0x4010-0x4017,0x4020-0x4023,0x4018-0x401f,0x4024-0x4027,0x4000-0x400f mem 0xf7fa5000-0xf7fa53ff at device 17.0 on pci0 ahci0: AHCI v1.30 with 2 6Gbps ports, Port Multiplier supported with FBS ahcich0: <AHCI channel> at channel 0 on ahci0 ahcich1: <AHCI channel> at channel 1 on ahci0 ehci0: <AMD FCH USB 2.0 controller> mem 0xf7fa6000-0xf7fa60ff at device 19.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci0 usbus1: 480Mbps High Speed USB v2.0 intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0 smbus0: <System Management Bus> on intsmb0 smb0: <SMBus generic I/O> on smbus0 isab0: <PCI-ISA bridge> at device 20.3 on pci0 isa0: <ISA bus> on isab0 sdhci_pci0: <Generic SD HCI> mem 0xf7fa7000-0xf7fa70ff at device 20.7 on pci0 sdhci_pci0: 1 slot(s) allocated amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb5 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 uart1: console (115200,n,8,1) tpm0: <Trusted Platform Module> port 0xc31-0xc32 iomem 0xfed40000-0xfed44fff on acpi0 tpm: device 0x001a15d1 rev 0x10 WARNING: Device "tpm" is Giant locked and may be deleted before FreeBSD 14.0. superio0: <Nuvoton NCT5104D/NCT6102D/NCT6106D (rev. B+)> at port 0x2e-0x2f on isa0 gpio0: <Nuvoton GPIO controller> at GPIO ldn 0x07 on superio0 gpiobus0: <GPIO bus> on gpio0 gpioc0: <GPIO controller> on gpio0 hwpstate0: <Cool`n'Quiet 2.0> on cpu0 Timecounter "TSC" frequency 998127822 Hz quality 1000 Timecounters tick every 1.000 msec ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Trying to mount root from zfs:zudi/ROOT/default []... ugen1.1: <AMD EHCI root HUB> at usbus1 ugen0.1: <AMD XHCI root HUB> at usbus0 uhub0 on usbus1 uhub0: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 uhub1 on usbus0 uhub1: <AMD XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 uhub1: 4 ports with 4 removable, self powered ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: <SATA SSD SBFM61.2> ACS-4 ATA SATA 3.x device ada0: Serial Number A45A0797068601319278 ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 30533MB (62533296 512 byte sectors) Root mount waiting for: usbus1 uhub0: 2 ports with 2 removable, self powered ugen1.2: <vendor 0x0438 product 0x7900> at usbus1 uhub2 on uhub0 uhub2: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus1 uhub2: 4 ports with 4 removable, self powered Root mount waiting for: usbus1 Root mount waiting for: usbus1 ugen1.3: <vendor 0x0cf3 product 0xe003> at usbus1 Dual Console: Serial Primary, Video Secondary Setting hostuuid: 4ee43bd5-9195-11e7-9e62-000db953369c. Setting hostid: 0x7067e1fe. no pools available to import Starting file system checks: Mounting local filesystems:. ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.32/mach/CORE 32-bit compatibility ldconfig path: Setting hostname: polisy. Additional TCP/IP options: ipv4-mapped-ipv6=YES. Setting up harvesting: [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED Feeding entropy: . Loading kernel modules: apuled0: <APU2> at iomem 0xfed81610-0xfed8161b,0xfed81664-0xfed81667 on isa0 resetsw0: <UDXRSW-2> at iomem 0xfed81664-0xfed81667 on isa0 wlan0: Ethernet address: 90:48:9a:33:8d:49 Created wlan(4) interfaces: wlan0. lo0: link state changed to UP Starting wpa_supplicant. wlan0: link state changed to UP Starting Network: lo0 igb0 wlan0. lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=4e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP> ether 00:0d:b9:53:36:9c inet6 fe80::20d:b9ff:fe53:369c%igb0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect status: no carrier nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 90:48:9a:33:8d:49 inet6 fe80::9248:9aff:fe33:8d49%wlan0 prefixlen 64 scopeid 0x7 groups: wlan ssid Galefront channel 1 (2412 MHz 11g ht/20) bssid b4:fb:e4:d2:94:56 regdomain FCC country US indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 4 shortgi -uapsd wme burst roaming MANUAL parent interface: ath0 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> Starting rtsold. Starting devd. Autoloading module: ng_ubt ubt0 on uhub2 ubt0: <vendor 0x0cf3 product 0xe003, class 224/1, rev 1.10/0.01, addr 3> on usbus1 Starting dhclient. WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() add host 127.0.0.1: gateway lo0 fib 0: route already in table add host ::1: gateway lo0 fib 0: route already in table add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Starting pg3. 2022-08-17T10:11:33.553860-04:00 polisy su 846 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:33.555840-04:00 polisy su 846 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:33.556464-04:00 polisy su 846 - - pam_start: System error su: pam_start: System error /etc/rc: WARNING: failed to start pg3 Starting mongod. 2022-08-17T10:11:33.591735-04:00 polisy su 854 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:33.592878-04:00 polisy su 854 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:33.593267-04:00 polisy su 854 - - pam_start: System error su: pam_start: System error /etc/rc: WARNING: failed to start mongod Allowing polyglot to listen on port 443... net.inet.ip.portrange.reservedhigh: 1023 -> 442 Starting polyglot. 2022-08-17T10:11:33.691137-04:00 polisy su 870 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:33.692199-04:00 polisy su 870 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:33.692605-04:00 polisy su 870 - - pam_start: System error su: pam_start: System error /etc/rc: WARNING: failed to start polyglot /etc/rc: WARNING: /etc/newsyslog.conf is not readable. Clearing /tmp. Updating motd:. Updating /var/run/os-release done. /etc/rc: WARNING: run_rc_command: cannot run /usr/sbin/syslogd Starting powerdxx. Starting hcsecd. Mounting late filesystems:. Security policy loaded: MAC/ntpd (mac_ntpd) Starting ntpd. 2022-08-17T10:11:34.261841-04:00 polisy su 1073 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:34.262890-04:00 polisy su 1073 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:34.263327-04:00 polisy su 1073 - - pam_start: System error su: pam_start: System error /etc/rc: WARNING: failed to start ntpd Starting sdpd. Wed Aug 17 10:11:34 EDT 2022|/etc/rc: making sure all prereqs are installed ... Wed Aug 17 10:11:34 EDT 2022|/etc/rc: pkg already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: ca_root_nss already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: dual-dhclient already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: bash already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: mongodb36 already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: p5-IO-Socket-SSL already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: git already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: sudo already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: polyglot already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: mosquitto already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: libwebsockets already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: powerdxx already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: e2fsprogs-libuuid already installed Wed Aug 17 10:11:34 EDT 2022|/etc/rc: c-ares already installed Wed Aug 17 10:11:35 EDT 2022|/etc/rc: rapidjson already installed Wed Aug 17 10:11:35 EDT 2022|/etc/rc: mongo-c-driver already installed Wed Aug 17 10:11:35 EDT 2022|/etc/rc: npm already installed Wed Aug 17 10:11:35 EDT 2022|/etc/rc: isy already installed Wed Aug 17 10:11:35 EDT 2022|/etc/rc: tpm2-tools already installed Wed Aug 17 10:11:35 EDT 2022|/etc/rc: dmidecode already installed Wed Aug 17 10:11:35 EDT 2022|/etc/rc: pg3 already installed Starting udx. Checking to see whether or not we need to migrate from 994 ... Setting permissions for ISY directories/files Setting permissions for LEDs checking udx version = 3120 for possible upgrade udx is upto date udx is running as pid 1199. you can disable uftdi driver by adding isy_load_uftdi=NO in /etc/rc.conf Starting isy. 2022-08-17T10:11:35.476580-04:00 polisy su 1265 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:35.477995-04:00 polisy su 1265 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:35.478605-04:00 polisy su 1265 - - pam_start: System error su: pam_start: System error /etc/rc: WARNING: failed to start isy Starting cron. Performing sanity check on sshd configuration. Starting sshd. Starting background file system checks in 60 seconds. Wed Aug 17 10:11:35 EDT 2022 FreeBSD/amd64 (polisy) (ttyu1) login: 2022-08-17T10:11:41.976295-04:00 polisy su 2052 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:41.977312-04:00 polisy su 2052 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:41.977724-04:00 polisy su 2052 - - pam_start: System error 2022-08-17T10:11:42.162701-04:00 polisy su 2074 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:42.163738-04:00 polisy su 2074 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:42.164121-04:00 polisy su 2074 - - pam_start: System error 2022-08-17T10:11:47.384717-04:00 polisy su 2093 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:47.386279-04:00 polisy su 2093 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:47.386935-04:00 polisy su 2093 - - pam_start: System error 2022-08-17T10:11:47.667287-04:00 polisy su 2115 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:47.668856-04:00 polisy su 2115 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:47.669472-04:00 polisy su 2115 - - pam_start: System error 2022-08-17T10:11:52.929073-04:00 polisy su 2134 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:52.930650-04:00 polisy su 2134 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:52.931288-04:00 polisy su 2134 - - pam_start: System error 2022-08-17T10:11:53.211790-04:00 polisy su 2156 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:53.213362-04:00 polisy su 2156 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:53.213995-04:00 polisy su 2156 - - pam_start: System error 2022-08-17T10:11:58.434372-04:00 polisy su 2175 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:58.435934-04:00 polisy su 2175 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:58.436578-04:00 polisy su 2175 - - pam_start: System error 2022-08-17T10:11:58.716178-04:00 polisy su 2197 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:11:58.717760-04:00 polisy su 2197 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:11:58.718376-04:00 polisy su 2197 - - pam_start: System error wlan0: link state changed to DOWN wlan0: link state changed to UP 2022-08-17T10:12:04.044699-04:00 polisy su 2343 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:04.046351-04:00 polisy su 2343 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:04.047011-04:00 polisy su 2343 - - pam_start: System error 2022-08-17T10:12:04.330348-04:00 polisy su 2382 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:04.331928-04:00 polisy su 2382 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:04.332552-04:00 polisy su 2382 - - pam_start: System error 2022-08-17T10:12:09.599811-04:00 polisy su 2401 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:09.601376-04:00 polisy su 2401 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:09.602023-04:00 polisy su 2401 - - pam_start: System error 2022-08-17T10:12:09.881682-04:00 polisy su 2423 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:09.883270-04:00 polisy su 2423 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:09.883871-04:00 polisy su 2423 - - pam_start: System error 2022-08-17T10:12:15.114927-04:00 polisy su 2442 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:15.116526-04:00 polisy su 2442 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:15.117194-04:00 polisy su 2442 - - pam_start: System error 2022-08-17T10:12:15.396940-04:00 polisy su 2464 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:15.398521-04:00 polisy su 2464 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:15.399142-04:00 polisy su 2464 - - pam_start: System error 2022-08-17T10:12:20.632205-04:00 polisy su 2483 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:20.633763-04:00 polisy su 2483 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:20.634420-04:00 polisy su 2483 - - pam_start: System error 2022-08-17T10:12:20.914764-04:00 polisy su 2505 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:20.916328-04:00 polisy su 2505 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:20.916917-04:00 polisy su 2505 - - pam_start: System error 2022-08-17T10:12:26.142940-04:00 polisy su 2524 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:26.144540-04:00 polisy su 2524 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:26.145192-04:00 polisy su 2524 - - pam_start: System error 2022-08-17T10:12:26.424866-04:00 polisy su 2546 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:26.426468-04:00 polisy su 2546 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:26.427076-04:00 polisy su 2546 - - pam_start: System error 2022-08-17T10:12:31.646966-04:00 polisy su 2565 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:31.648542-04:00 polisy su 2565 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:31.649201-04:00 polisy su 2565 - - pam_start: System error 2022-08-17T10:12:31.929096-04:00 polisy su 2587 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:31.930668-04:00 polisy su 2587 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:31.931289-04:00 polisy su 2587 - - pam_start: System error 2022-08-17T10:12:37.149166-04:00 polisy su 2606 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:37.150773-04:00 polisy su 2606 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:37.151426-04:00 polisy su 2606 - - pam_start: System error 2022-08-17T10:12:37.431308-04:00 polisy su 2628 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:12:37.432880-04:00 polisy su 2628 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:12:37.433494-04:00 polisy su 2628 - - pam_start: System error

Hi, As usual, Michel, thanks for the quick reply. Polisy Pro. No joy. One button press to upgrade Polisy packages, gives immediate one boop and six beeps. ttyul console still with error messages. Waited 10 minutes. Never received 4 beeps + 1. No change. Cold boot. No change. Polisy completes boot, error message about unable to start iSY, ttyul shows logon, then repeating error messages preventing logon. Ticket generation I think my universal devices "account" is broken too. https://www.universal-devices.com/my-tickets I go to create ticket, tells me to login via isy portal. Complete logon using my https://my.isy.io/ credentials. Then I get RE prompted by MyTickets to logon, click button and just refreshes saying logon. When logged on to https://www.universal-devices.com/my-account/ as directed by https://www.universal-devices.com/my-tickets There are TWO Polisy Pro's registered to me. NEITHER has the UUID of my Polisy but the numbers listed seem to be the mac address of the ethernet and wifi adapters. Clicking on either device in https://www.universal-devices.com/my-account/ Says Not a valid serial number. I can logon to https://my.isy.io/ and see a valid UUID for my Polisy. But I cannot create ticket on https://www.universal-devices.com/my-tickets with same credentials. Tried Chrome, Firefox, Edge and in private mode and turned off Pihole. I use and enjoy my ISY and Polisy. UDI support is excellent. I still seem to have a broken Polisy Pro. Thanks

Opened up Polisy and connected to serial console port ala mwester (Thank you!) For future information serial port is 115200 8n1 Watched Polisy Boot - got a few error messages and then a login prompt. Any keyboard input then generates repeat SD_1.0" 2022-08-17T10:50:51.160880-04:00 polisy su 8607 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:50:51.161517-04:00 polisy su 8607 - - pam_start: System error 2022-08-17T10:50:51.440353-04:00 polisy su 8629 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:50:51.441921-04:00 polisy su 8629 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:50:51.442541-04:00 polisy su 8629 - - pam_start: System error 2022-08-17T10:50:56.721626-04:00 polisy su 8648 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:50:56.723202-04:00 polisy su 8648 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:50:56.723830-04:00 polisy su 8648 - - pam_start: System error 2022-08-17T10:50:57.001788-04:00 polisy su 8670 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:50:57.003369-04:00 polisy su 8670 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:50:57.003970-04:00 polisy su 8670 - - pam_start: System error 2022-08-17T10:51:02.285111-04:00 polisy su 8689 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:51:02.286681-04:00 polisy su 8689 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:51:02.287322-04:00 polisy su 8689 - - pam_start: System error 2022-08-17T10:51:02.566529-04:00 polisy su 8711 - - in try_dlopen(): /usr/lib/pam_unix.so.6: /usr/lib/libypclnt.so.4: Undefined symbol "xdr_domainname@FBSD_1.0" 2022-08-17T10:51:02.568102-04:00 polisy su 8711 - - in openpam_load_module(): no pam_unix.so found 2022-08-17T10:51:02.568713-04:00 polisy su 8711 - - pam_start: System error Tried Factory Reset hardware button. No change. Polisy still borked. (this after using recommended admin console upgrade path) Tried to open ticket - More frustration - told to login via portal, logged in and can see my devices, tried to open ticket, told to logon again, and again. Tried with Chrome incognito, and pihole disabled. Still cant get to place to create ticket. Frustrated!

I use and enjoy my ISY and Polisy every day. A recent update seems to have broken my Polisy. I cannot find the admin console or login via SSH. (My Polisy is still a test mule, still with default user/password admin, My ISY is production. The polisy was already running fairly recent updates) A couple of days ago I used the Admin Console to Upgrade Packages on my working Polisy. Without any real feedback, the Polisy went off and did something. My polisy is in the basement so I can't hear beeps. (I really really really miss sudo pkg update/upgrade, with all that verbose logging information.) Today I tried to logon with ISY finder/java. My ISY showed up, but my Polisy was missing. I reserve an ip address for my Polisy and tried to SSH and did get connected to the standard login terminal prompt. However, login as: admin after hitting "enter" I get "Remote side unexpectedly closed network connection." Several cold reboots, single solid green light, single beep. Still no Polisy admin console, no SSH. Polisy does show up as acquiring IP in router. SSH connects but closes connection. Suggestions? Thanks

From the 2448A7 QuickStart guide Stores over 1,023 INSTEON Links in 64KB of non-volatile memory