All, I think the simplest solution is to use the planned outage, as we have a lot of $U uprocs that run polling loops which themselves kick off a uxsleep process..... hence when the scheduled outage function within $U is used the uprgrades work flawlessly.... just something to be aware of!
Original Message:
Sent: 07-30-2019 10:17 AM
From: Frederic Caloone-Thuillier
Subject: automated upgrade of $U issue
Hi,
Not really. in 6.10, we introduce an ANTE and POST PATCH which are launched before the patch and after it. Perhaps It could be used to do something about the uxsleep in the machine.
regards,
Frédéric Caloone
Original Message:
Sent: 07-11-2019 09:29 AM
From: neil rogers
Subject: automated upgrade of $U issue
Currently we are using univiewer to upgrade multiple $U installations from windows version 6.7 to version 6.9 via the autopatch packages. However when doing so the deployment fails each time. The cause of this is that there are multiple uxsleep commands running on the windows side and a corresponding cmd.exe task running on the node that are not killed off when $U is shutdown. When the cmd.exe is killed manually this also kills off the uxsleep command and when there are no uxsleep commands running and we deploy the update it then completes successfully. Is there a workaround for this as it makes the upgrade through univiewer more complicated than it needs to be, or do we need to modify our uxshutdown script to cater for this?