Our Foglight Experience Monitor (FxM) CPU Utilization went from less than 10% to almost 100% within a few hours and has remained there. Except when we rebooted the box it fell to 50% or less but within hours increased back to almost 100%. The individual CPU "cores" are also at almost 100%. We don't see any other symptoms of overloading though.
We looked through the ecrit log files for anything odd going on right around the time when the CPU Utilization started going higher. Found something. The log entry below is the first occurrence of it:
May 24 04:46:47 fxm
And after this, this error keeps reoccurring.
An issue with the FxM 5.5.0 agent that under certain conditions would leave database connections open. It would occur when there was no data to monitor along with some other condtions also occuring. It was a combination of at least three issues happening that could cause problems. This issue was never logged as a defect with a tracking number asssociated to it.
Found the below on the web:
If you run a fairly busy and/or badly configured MySQL server, you may receive something like this when attempting to connect: