I have LMS split on two servers.
Server 1: CM, IPM (DCR master)
Server 2: RME, DFM
Dual processor, 8G RAM
Managing ~370 devices
While conducting a small group training class where 8 simultaneous users were logged in and perusing the interface, the server was ridiculously slow to respond. Task Manager was showing 100% CPU usage with provisioneer.exe consuming nearly all of it.
Searching this forum I was advised that this process was for the CiscoWorks Assistant and that a reboot would fix the issue.
I rebooted the servers and as expected the CPU usage returned to normal (0-3%).
However, the problem came back. Since this is a production system I am simply unable to down the server every time this process decided to go 'wonky'.
Is there any more information on why this happens or other solutions besides reboot the server?
Restarting these daemons is like a reboot only in terms of CWA. It is obviously not the same, though, as a reboot will definitely terminate any errant subprocesses (and the database is not restarted).
CWA is more than just one process. It consists of three Daemon Manager controlled daemons (ProcSysBus, OpsXMLRuntime, and OpsxmlDbEngine), and a number of subprocesses like the GG*.exe and Provisioneer processes. All of these processes must be in sync in order for CWA to function properly. None of these processes should take much CPU, especially if a CWA workflow is not being executed. But as I pointed out, there is at least one CPU hog issue in your version of LMS which has been fixed in the latest version.