cutthroat

I experienced the same thing., was running 5.9.1. My process was: take backup launched UD mobile and kicked off firmware upgrade while watching it upgrade, cleared all JAVA files and cache after about 10 minutes I would say, UD Mobile said firmware update complete BUT then immediately told me another update was available. Decided to wait on applying another update in case it was confused. Went to ISY Web Portal and selected "ISY Web Access" This launched a web version of my EISY. Then went to Settings, "Install Admin Console (internet). This got the EISY Admin Console installed on my PC and was able to login like before. Using local credentials. Then tried to access eisy.local and nothing. Decided to wait the full 60 minutes like the upgrade instructions said. After the full 60 minutes, still no access. Went back to UD Mobile and let it do the other update it mentioned. This updated PG3X to version 3.4.18. This time it said a reboot was required, so let it reboot. Tried to access eisy.local and still no access. Decided to try and do the eisyui install from CLI. SSH'd into the appliance Ran "sudo pkg install eisyui" It did say this package wasn't installed and did I want to install it, said Yes. Monitored it installing and doing numerous migrations. Then restarted ISY "sudo service isy restart" Tried to access eisy.local and still no access. And I could no longer get in with the UD Mobile or the Admin Console. Rebooted the EISY appliance This time the UD Mobile worked and I could access the Admin Console Now the Admin Console required me to use my ISY Portal Credentials, not the local credentials I was using in the past. AND.... FINALLY, I could get access to eisy.local I believe I have seen numerous posts that say the upgrade package installs eisyui, for me it didn't. Anyway, hopes this helps someone else in the future.

I did not reboot my system until I got into the system via ssh and looked at the logs and saw the system crashing with core dumps. Here is the log entry when the system auto rebooted. Mar 8 20:31:31 eisy shutdown[74622]: reboot by udx_installer: Below is when the system came up from the first reboot that the upgrade script did. This is the first log entry of the core dump, note time. Mar 8 20:32:21 eisy kernel: pid 1723 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) ... Mar 8 20:45:31 eisy kernel: pid 36451 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 8 20:45:51 eisy kernel: pid 37202 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 8 20:46:12 eisy kernel: pid 38065 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 8 20:46:20 eisy reboot[38293]: rebooted by admin I didn't reboot this system too soon. Note the 14-minute time gap with constant core dumps and when I rebooted it. The upgrade process failed. Are you saying the system should core dump constantly for 2 hours?

This fixed mine that wasn't working after the upgrade.

ok, was able to get mine back up and working. I ssh'd in and reran the package install. sudo pkg install -f isy then rebooted.

Add me to the list of an upgrade failure. Everything was working fine, did the upgrade package and after waiting around 45 minutes still can't get into anything. Tried a reboot. debug.log is showing this. 2025-03-08 20:51:04 - DBG3|SysCall [T:40422088974336] issuing system call /usr/local/etc/isy.d/static/isy_startup.sh (../src/Kernel/SystemCall.cpp@67:execOnly()) 2025-03-08 20:51:04 - Info|Config [T:40422088974336] starting to parse file /var/isy/.env, delim = = (../src/Config/UDXConfig.cpp@20:parse()) 2025-03-08 20:51:04 - Info|UDXThread [T:40422088974336] initializing (../src/System/UDXThread.cpp@494:init()) 2025-03-08 20:51:04 - Info|UDXThread [T:40422088974336] setting scope to 2 successful (../src/System/UDXThread.cpp@186:setThreadScope()) 2025-03-08 20:51:04 - Info|UDXThread [T:40422088974336] setting joinable to true for [0] (../src/System/UDXThread.cpp@229:setJoinable()) 2025-03-08 20:51:04 - Info|UDXThread [T:40422088974336] setting joinable successful for [0] (../src/System/UDXThread.cpp@237:setJoinable()) 2025-03-08 20:51:04 - Error|Config [T:40422088974336] invalid value length (../src/Config/UDXConfigRecord.cpp@141:parse()) 2025-03-08 20:51:04 - Error|Config [T:40422088974336] could not add line: IFS= (../src/Config/UDXConfigRecords.cpp@35:parse()) 2025-03-08 20:51:04 - Info|RunConfig [T:40422088974336] changing directory to /var/isy (../src/System/UDXMain.cpp@135:main()) 2025-03-08 20:51:04 - Info|RunConfig [T:40422088974336] the system is "eisy" v.5.9.1_11, running from /var/isy (../src/System/UDXMain.cpp@143:main()) 2025-03-08 20:51:04 - Error|RunConfig [T:40422088974336] failed verifying signature (../src/System/UDXMain.cpp@147:main())

Mine is offline as well. Wonder if there is a backend issue.