since v24, the operating systems agents require OpenJDK 17. We now had the situation that CAU was not able to start the new agent via the ServiceManager.
The situation
The old agent was installed manually.
Because another Java version must be used as the main version, it was not possible to modify the system path and/or JAVA_HOME. So, instead of duplicating the jre folder multiple times, it was decided to install OpenJDK 17 to a central folder and create symbolic links to agent\windows\bin instead. This saves some hundred MB disc space. As far I have seen, the agent starts without errors and operates error-free.
CAU
Now CAU was used to upgrade the windows agent to 24.4.1 HF2. The new agent software was successfully deployed, the old agent was stopped but the new agent did not start.
See what has happened - starting agent using "ucxjwx6 --console" shows the error:
Launcher process 7416 started
Press ENTER key to start...
C:\Automic_v24HF2\Agents\windows\bin is the current working directory
Checking if path C:\Automic_v24HF2\Agents\windows\bin\smgr_deployment.txt exists...
No (The system cannot find the file specified.
)
C:\Automic_v24HF2\Agents\windows\bin is the current working directory
Attempting to delete file C:\Automic_v24HF2\Agents\windows\bin\access_test.txt...
Deleted
Checking if path C:\Automic_v24HF2\Agents\windows\bin\jre.zip exists...
Yes
Checking if path C:\Automic_v24HF2\Agents\windows\bin\jre exists...
Yes
Attempting to delete directory C:\Automic_v24HF2\Agents\windows\bin\jre...
powershell.exe -Command Remove-Item -Recurse -Force C:\Automic_v24HF2\Agents\windows\bin\jre
An error occured: Error while performong initialization: Powrshell returned with exit code 1
Error while performong initialization: Powrshell returned with exit code 1
JAVA_HOME identified as:
>Command execution failed with return code: 1<
Press ENTER key to exit after exception...
As we can see, CAU uses a PowerShell command to remove the old jre folder. This seems not to work with shortcuts/links ...?
Solution
- removed the linked folder
- started the agent manually via ServiceManager Dialog
- waited for the completion of CAU
- removed the physical jre folder (created by CAU)
- recreated the link
I often see customers using symbolic links for various purposes. Sure, it saves disc space.
CAU should also consider this in its design – what do you think?
regards,
Peter
------------------------------
Automic Certified Professional/Expert & Broadcom Knight
------------------------------