MySQL Appliance log file

[rgilchrist]

Hi
I have a MySQL Appliance running in a live environment and the log file

/var/log/appliance/log

is filling up with

ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)

I assume this is because I reset the root@localhost password and this is part of the monitoring checking that MySQL is alive

So two questions,
1. Can I simply rotate the log file or do I need to restart a process?
2. How do I change the login details for the process or stop it altogether?

Thanks
Rob

[Jsmart]

Rob,

It is fine to rotate the log, we will have someone look at this in the morning and let you know the correct way to stop the error.

--Jessie

[rgilchrist]

Hi Jessie
I tried rotating the log over the weekend, but the output continued to append to the old log and I wasn't sure which process was writing to it. In a fit of madness I then deleted the old log, and although the log file seemed to be removed, the df command was still showing the disk usage as unchanged.

I have checked the disk usage this morning and it amount of free space is continuing to drop, could it still be writing to the file?

Cheers
Rob

[PavelGeorgiev]

Rob,

The process that dumps the errors is the custom counters collector: /appliance/feed_mysql_counters.sh, killing it will stop the errors and will free your space.

Generally, modifying the root@localhost account is not a good idea as:
1) it is used by many mysql tools (like myisamchk)
2) it does not add any security holes in applogic appliances, as no connections are comming from localhost, all connections come from another appliance through the in terminal.

That said, I would suggest removing the password from the root@localhost account, which will stop the errors from the custom counters (they will be started on next restart of the appliance). To get your free space back, either restart the appliance or kill '/appliance/feed_mysql_counters.sh' and start it again with '/appliance/feed_mysql_counters.sh &' (you can actually not start it if you dont monitor mysql custom counters).

However, if you have a reason to keep root@localhost with password, here is how to get rid of the errors:

You can either modify /appliance/feed_mysql_counters.sh to use the new password or disable the custom counters at all. To do so, comment the line that starts /appliance/feed_mysql_counters.sh in /appliance/appliance.sh (or just remove the executable flag from /appliance/feed_mysql_counters.sh). All changes will only work for as long as the boot volume is not wiped (app clean; app migrate), so if you want to make these change permanent, branch the appliance.


Let me know if that solves your problem.

[rgilchrist]

Hi
Thanks for the reply, it was very helpful.

I found the process feed_mysql_counters.sh and killed it and the disk space was returned.

Cheers
Rob