I have a fairly large site with thousands of visitors a day and a database over 1GB. It appears the database just crashed and I notice it is stuck on REPAIR TABLE `elggsystem_log`. As a result my site will probably be down for several hours or possibly even the whole day while it is repaired. I have a backup but it's a few weeks old and I'd rather not do that.
Given that I really don't use Elgg's logs and find the information to be pretty much useless is there any way that I can either disable the log entirely or at least make it far less verbose? I definitely don't need multiple entries for every time a user accesses content or when a view counter is incremented, for example. I have a feeling that doing this will increase performance too by reducing the Elgg database size and disk accesses.
Is it an option?
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- gts fan9@gtsfan
gts fan9 - 0 likes
- gts fan9@gtsfan
gts fan9 - 0 likes
You must log in to post replies.Hmmm. I see Dhrup's suggestion here: http://community.elgg.org/discussion/view/607339
but it is almost 3 years old. Is this still safe?
It would seem this would be a good user option since it appears I'm not alone in finding most of the Elgg logging to be essentially without much use. I shudder to think of all the unneccessary writes and the database size it causes. I do use Spam_login_filter but I notice it uses the separate IP_tracker plugin.
edit: It's still going after 30 minutes on that table so I think I will cancel it, backup the database, delete elggsystem_log, and move from there.
Just a note for future searchers.
1. It doesn't appear my main problem was due to a crash in elggsystem_log
2. I was able to 'truncate table elggsystem_log' with my version 1.8.15 install apparently without side effects or consequences. This then eleminated many entries although it will say it affected zero rows on myisam. YMMV. Back up first to be safe. But this might make a lot of sense to do if that table has crashed for whatever reason and you have a large site and it will take a while to repair otherwise.