Vijit Singhal

Request you to kindly schedule a call on Tuesday next week, to go over the issue and discuss the path forward.

Wrapper service is failed to start Post Windows Upgrade

Hi Maxime, thanks for your response. So, we identified the issue. We are spawning a child process which runs the script that stops and reinstalls our collector. But once the stop command is triggered, the child process is also killed along with the main process and the wrapper stays in stopped state. Is there a way to run the script as a totally independent process so that it can stop the wrapper and reinstall with the upgraded wrapper? Thanks

@maxime-tsl thanks for the quick reply. Yes, we have our own version in jfrog artifactory with the version set as 3.5.49.1 and therefore we added this version in our script. The thing is, we have a restart script which does the restart automatically, but that fails. And doing a manual restart right after failure, the wrapper gets upgraded and works fine.

INFO | jvm 2 | 2022/05/23 23:42:50 | WrapperManager: ERROR - The version of the Wrapper which launched this JVM is "3.5.33" INFO | jvm 2 | 2022/05/23 23:42:50 | WrapperManager: while the version of the Wrapper jar file currently in use INFO | jvm 2 | 2022/05/23 23:42:50 | WrapperManager: is "3.5.49". INFO | jvm 2 | 2022/05/23 23:42:50 | WrapperManager: INFO | jvm 2 | 2022/05/23 23:42:50 | WrapperManager: ERROR - The version of the Wrapper which launched this JVM is INFO | jvm 2 | 2022/05/23 23:42:50...

Hi Leif, could you please guide on how to update and make sure that all the three files are from the same release? Once we see the error and do a manual restart, everything works fine. So not sure, what needs to be changed.

Hi Leif, could you please guide on how to make sure that all the three files are from the same release? Once we see the error and do a manual restart, everything works fine. So not sure, what needs to be changed.