After my last "Upgrade packages" attempt required me to reflash my eisy, I figured I would try again, having the latest version. When I select it, I get a popup warning to wait until it's done before restarting the eisy... but then that's it. No other status. How do I know it's actually doing anything, or when it's done? Every time I launch the UI, it warns me again that an upgrade is in progress, but that's not especially useful.

I saw in another post that reccommended sshing in, and I get this:

[admin@eisy ~]$  sudo tail -f /var/udx/logs/log
Fri Dec 26 11:40:04 EST 2025|/usr/local/etc/udx.d/static/udxops_main.sh: udi.conf no signature is AOK ...
Fri Dec 26 11:40:04 EST 2025|/usr/local/etc/udx.d/static/udxops_main.sh: udi.conf is AOK ...
Fri Dec 26 11:40:07 EST 2025|/usr/local/etc/udx.d/static/udxops_main.sh: making sure we have the right pkg version ...
Fri Dec 26 11:40:07 EST 2025|/usr/local/etc/udx.d/static/udxops_main.sh: pkg pkg is current ...
Fri Dec 26 11:40:07 EST 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking whether or not we have a new version for udx ...
Fri Dec 26 11:40:07 EST 2025|/usr/local/etc/udx.d/static/udxops_main.sh: need to upgrade to 4.4.0 ...
Fri Dec 26 11:40:10 EST 2025|/usr/local/etc/rc.d/udx_cmd_processor: emptying command processor ...
Fri Dec 26 11:40:10 EST 2025|/usr/local/etc/udx.d/static/udx.utils: wifi.ops is not being called as a comamnd
Fri Dec 26 11:40:12 EST 2025|/usr/local/etc/udx.d/static/udxops_main.sh: restarting after udx restarts  ...
Fri Dec 26 11:47:04 EST 2025|/usr/local/etc/udx.d/static/udxops.sh: command discarded since udx_cmd_processor service is not running ...

which hasn't changed in almost the last hour.

Any suggestions?

@mullercentral not sure if you were still having issues when you posted this as you had several posts about this time that seemed to indicate you had a successful update.

I just ran the 6.0.4_1 update (coming from 6.0.3_3). The last few times I have updated I just pay attention to the alerts on UD Mobile. It will tell you that the system has been updated and should be rebooted. I run 100% of the update process through Admin Console (the trusted Java access process). In the past there would also be an alert on the admin console, but I think that's gone away as of late...at least I haven't seen it.

But once the UD Mobile app sends a notification to the phone (iPhone) I probably wait another 5 minutes then press the reboot button in admin console. Then after a bit of time UD Mobile will say PG3 is stopping and system rebooting then I get some alerts that it's come back up. I wait another few minutes then clear java cache, download a fresh start.jnlp and run that to access admin console. All seems well. Every now and then another reboot might be needed, but it's not been a common occurrence.

I think somebody posted recently that the updates can sometimes take a while, but certainly not hours. This seemed to be a very minor update from 6.0.3_3. While I didn't time it seemed to be less than 5 minutes. I was busy doing other things while it ran.

Since eisy.ui is still being developed I have been cautious to try to update from that side. I rely more on the tried (and true) admin console process to update the device. Until UD publishes something that says different that's the way I'll continue to update.

One thing I wouldn't suggest is just pulling power. Either attempt a reboot in admin console or press and hold the power button to force a shutdown of the device.

I don't ever remember seeing a notification in admin console saying that an update was finished. What I do remember seeing is a notification that a reboot is needed, if the update involved updating the OS (FreeBSD version). Otherwise, it will usually just restart the udx and isy services.

3 hours ago, Geddy said:

Since eisy.ui is still being developed I have been cautious to try to update from that side.

FYI, the last two updates I have done were done using eisy.local on advice from UD support. Both worked fine and eisy.local provides notice of upgrade in progress and reboot required similar to UD Mobile.

There has been a few mentions of people getting updates getting "automatically" installed. I had a hard time believing that, until yesterday when I seem to have been bestowed the privilege of experiencing one myself. As I've mention on these forums a few times, I have two Polisys that I use for testing. I had disconnected one for over a month for various reasons and when I plugged it back in a few days ago, it wouldn't boot up. Reflashing the SSD failed, Rufus couldn't write to the drive. Obtained a few spare SSDs and flashed one with a Polisy image file that I had created on Sept 29th, a file I named polisypro_600 because it was a 6.0.0 system. Put that in the Polisy and it booted back up just fine, and IoX finder showed it as...6.0.4! I sshed into it to view the sysconfig.txt file and yup, it has 6.0.4_1. Interesting.

@DennisC thanks for the info. Maybe it's progressed far enough to be reliable. Too many moving parts to keep up when things are moving this quickly. I know it's the ultimate goal to have eisy.ui replace the Java admin console. I've just experienced enough issues with the web ui to not find it reliable for my comfort level. Maybe someday...but I've not had issues running admin console and updates from there so works for me. Currently every time I log into eisy.ui I have to refresh the browser (Chrome) because it just goes to a blank page. It's a minor annoyance, but that's the unreliability that is just enough not to want to use such an interface. I guess more have issues with Java and admin console so UD is finally (after many, many years) going to a web ui, but the growing pains (for me) with that system outweigh the reliability I've had with the Java interface. By a long shot!

1 hour ago, Guy Lavoie said:

I had a hard time believing that, until yesterday when I seem to have been bestowed the privilege of experiencing one myself.

I'm with you! There was debate several years ago about allowing automatic updates when the device reboots. I was told then, and numerous times since that UD would not implement "automatic updates". However then @bmercier indicated there was indeed an automatic update after 6.0.x came out due to an underlying issue that required an update of an apparent "minor" part. I would hazard a guess that something in 6.0 triggered the auto update to the current 6.0.4_1. The issue remains that an unexpected update could crash somebody's system. If they were away from home it could be days/weeks/months before they returned to get the system working again. That's the underlying concern that UD addressed in the past by not having an automated update process. Sadly, I think the error that was caused recently was an unavoidable situation that forced an automated update somewhere, but even then that's seeming causing issues for some users.

I would suggest opening a support ticket to let them know of the issues you faced. Even though you've fixed it on your own for now maybe there was something they could review with you to see what happened to cause a failure. This is the time that when issues are experienced during an update that tickets are best for both UD and the users as a whole to potentially fix what could break everybody's systems.

Well it didn't cause me any issues, being a test system. On my production eisy, I went straight from 5.9.1 to 6.0.3, then to 6.0.4.

Another thing is that it did it as I was booting it up. A Polisy beeps when it starts up. This time it beeped again, a few minutes after the first time. I don't think they'd do updates on a running system.

They probably evaluate the risks on a case by case basis. This was likely a minor bug fix. Maybe UDI could let the user decide, by adding a "Allow automatic updates" check box in the Configuration screen.

Edited 22 minutes ago22 min by Guy Lavoie