One of my customers has encountered a severe problem with regards to the his BES server. The server is absolutely normal as long as the console is not open on the server. As soon as the console is opened, the CPU utlization of the sever goes up to 99% and remains there slowing down the complete server. Even other remote consoles fail to connect to the server at the given moment.
The customer is trying to deploy certain actions and it results in an error stating that is cannot connect to the root server at the present point of time.
All the points mentioned in the performance tuning of the BES server have been executed.
please find attached the screen shots of the same.
i suspect a sql slammer attack, but the cpu is absolutely normal when the console is not open.
Which version of BES are you running. We find as a best practice for performance and security is not to run the console on the same machine as the BES erver. The console is a memory hog, but I’ve found in 6.0 the memory utilization is much better.
Sounds like your starving SQL while running the console on the same machine. That’s why users can’t connect. I’d say run the console from another machine.
Running the BES Console on the BES Server will cause issues if you run out of memory, which is very likely because the BES Console, BES Web Reports, and SQL Server all like to use lots of memory.
As soon as you run out of memory with the BES Console, you will see performance of the whole system degrade dramatically.
It sounds like something is very wrong. The BES Root Server should normally only use a small amount of CPU. Please open a support ticket to figure this one out.