Support Forum

We had an interesting issue with Automate today. About 3 or 4 times during the course of the day, Automate became sluggish and died. A reboot fixed it, but took ages to come up.

The only change made was enabling ADMON (it had been installed a couple of days prior).

After working with support, we found and deleted a "root@localhost" account on mySQL, and everything came back up after a reboot.

Could ADMON have created this account? Or possibly caused a different problem related to the account?

No we do not create any accounts , ever, in any plugin we offer.

Some paid for plugins may have user classes added but this is a userclass which is like adding a user group to Automate. The group itself has no power until you join users to it. Then the group gives power over plugin only.

ADMON has no such groups needed.

It just queries LDAP and gets data. Sends email when day = X. That's it.

fgoosen wrote: ↑Thu Mar 17, 2022 9:43 pm We had an interesting issue with Automate today. About 3 or 4 times during the course of the day, Automate became sluggish and died. A reboot fixed it, but took ages to come up.

The only change made was enabling ADMON (it had been installed a couple of days prior).

After working with support, we found and deleted a "root@localhost" account on mySQL, and everything came back up after a reboot.

Could ADMON have created this account? Or possibly caused a different problem related to the account?

Just FYI, "root@localhost" is typically the default account for MYSSQL during a standard install. Its the first account created by the Install of MYSQL. It should exist by default and would of been created at the time of the Automate installation.

Thank you for the clarification, Cubert.

Could the combination of ADMON and the root@localhost account have caused any issues, as far as you're aware? FYI: We're running a separate MySQL server, if that matters.

The timing was curious, but I'm not sure how enabling the plugin would kick off these problems. I'd rather think that most changes occur during installation.

Correct, When you install a plugin and restart the DBagent, this forces the DBagent to reload all plugins. If a new plugin requires some supporting stuff like database tables, scripts, data views, user classes, alarms or other supporting items it will instruct the DBagent to create them at that time. Once created, if they exist they will not be recreated.

There are plugins out there that might change things on Automate or start a set of functions that may weigh down an Automate system causing sluggish performance but ADMON is not one of them.

ADMON is a very simple tool that looks at each location for the agent running a Windows DC and schedules a simple LDAP script to run once a day on it. The script grabs all the users emails that match the given parameters and stores that in Automate.

If each Client under management had 100 users and the MSP had 100 clients. That would result in 10K entries in the SQL database table that ADMON manages. That's a drop in the bucket for a SQL server. Since all ADMON does is collect names and day till expired there is not a lot else needed. Every day it looks to see if any names meet the deadline provided and if so Automate kicks off an email to that user.

That's it... It's the simple things in life...