PhillyPhotog Posted October 20, 2016 ID:1067568 Share Posted October 20, 2016 My management console is failing after about 24 hours of uptime. Specifically, I am getting an error with ID 7034 from source Service Control Manager Eventlog Provider, with the detial Quote The Malwarebytes Mangement Service service terminated unexpectedly. It has done this 2 time(s). I am running Management Console version 1.7.0.3208 I am not sure where to begin troubleshooting this one. Search of forums came up blank for me. Any guidance would be appreciated. Link to post Share on other sites More sharing options...
PhillyPhotog Posted October 20, 2016 Author ID:1067569 Share Posted October 20, 2016 Interesting note, began a database cleanup and the service just crashed on me. Server had just been rebooted about 45 minutes prior... Database corrupt? How can I confirm / rebuild? I have been able to repeat this and get the same result. Database size is currently .9 GB. Too large? Link to post Share on other sites More sharing options...
PhillyPhotog Posted October 20, 2016 Author ID:1067570 Share Posted October 20, 2016 Correction, Database now shows as .54 GB in MBMC, but when looking @ app_Data folder in Malwarebytes Management Server folder, scdb shows as .978 GB and SCDB_Log shows as 2.1 GB Link to post Share on other sites More sharing options...
PhillyPhotog Posted October 21, 2016 Author ID:1067666 Share Posted October 21, 2016 More information on this. I disabled the cleanup settings for Obselete logs / clients. This allowed the management service to stay alive and collect data from clients. I have been running manual cleanups for the past day, and the log keeps getting a bit smaller (as reported by console, but not realized in app_data folder in MBMC install path), but still fails eventually and kills the service. Link to post Share on other sites More sharing options...
djacobson Posted October 21, 2016 ID:1067775 Share Posted October 21, 2016 PhillyPhotog, are you using embedded SQL Express or an external full SQL? Link to post Share on other sites More sharing options...
PhillyPhotog Posted November 9, 2016 Author ID:1071242 Share Posted November 9, 2016 Embeded, sorry for delay, did not see the reply. Error went away for a bit, but just popped again. Link to post Share on other sites More sharing options...
djacobson Posted November 10, 2016 ID:1071412 Share Posted November 10, 2016 That is much too large for embedded. We'd need to review how many machines you have deployed and if your policy is setup properly to deal with infections. If you take no action on certain items you can blow you database out pretty quickly with repeated detections that are not being removed. Create a ticket by emailing corporate-support@malwarebytes.com and I'll pick it up out of the queue there to continue working with you. Link to post Share on other sites More sharing options...
PhillyPhotog Posted November 14, 2016 Author ID:1071987 Share Posted November 14, 2016 Submitted. What is the upper limit for embedded? At what point does MB recommend that a deployment team consider utilizing SQL for database rather than embedded (# of clients, record length, etc.) Link to post Share on other sites More sharing options...
djacobson Posted November 14, 2016 ID:1072001 Share Posted November 14, 2016 We've found the limit of embedded express to be at 250 deployed clients. Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now