Attack Signature Update Causing Unexpected Reboot

I had actually deleted the prior work (the day before) as so much has changed since that time and I wanted to start with a clean slate. So ASM itself wasn't doing anything. I keep a close eye on cpu and memory load (had the dashboard up at the time). CPU utilization was ~12% and memory was ~50% (where those stats generally hover). As soon as I hit the button to update attack signatures one CPU spiked to 100 % and the other to 80%. Memory spiked as well. Lost connectivity within a few seconds. It took a little over 2 minutes for the box to come back up. There was nothing unusual in the logs.

 

 

Chris