Upgrade to 8.2 failed with BESClient hung using 50% CPU

Usage and Config Platform
1

(imported topic written by olsonc5891)

I recently moved datacenters and had to rebuild the Bigfix environment from scratch. I upgraded clients to 8.1 and then to 8.2. The 8.2 upgrade failed for 10 of only 73 clients in various states, “installing” or “pending download”. Logging on to the servers showed the BESCLient using anywhere from 25 to 50% of CPU. Stopping the service failed and timed out. The only option was to use task manager to kill the BESClient process. Fortunately, this was only in our test environment. I am afraid to deploy to production until I can figure out what went wrong here. Any suggestions?

2

(imported comment written by BenKus)

Hi Olson,

I don’t think we have had other reports of this… Have you found any other info on this issue? Has anyone had similar problems?

I suggest you work with support if you haven’t already contacted them to try to find the root cause.

Ben