eGroupware stopped working due to large egw_access_log table

fnielsen 2012-09-17 15:07:59 UTC #1

We have used eGroupware for about two years for a small team. Recently excessive CPU loads have been observed and a week ago eGroupware stopped working. From the administrative interface restore to earlier backup was attempted several times but it never completed and would just hang. As a result the MySQL database became corrupted.

I simulated our ISP’s environment in a VM; installed eGroupware and was able to import the database through the admin interface. Still it was not possible to log into user accounts.

A check of the database showed that the table egw_access_log had grown to almost 200 MB. I emptied the table and optimized all tables. Instead of using eGroupware’s backup & restore the table was exported from MySQL on the VM and transferred to the ISP. After this eGroupware is working again.

Is this expected behaviour? Are there ways of limiting the size of the log table automatically?

Flemming from Banana hill

shri-4 2012-09-26 07:55:31 UTC #2

Check if egw backup script is running when you observe high load

i think in latest patch it is resolved.

Shri.

Ralf_Becker_Stylite 2012-09-26 08:10:19 UTC #3

We have used eGroupware for about two years for a small team. Recently
excessive CPU loads have been observed and a week ago eGroupware stopped
working. From the administrative interface restore to earlier backup was
attempted several times but it never completed and would just hang. As a
result the MySQL database became corrupted.

I simulated our ISP’s environment in a VM; installed eGroupware and was able
to import the database through the admin interface. Still it was not
possible to log into user accounts.

A check of the database showed that the table egw_access_log had grown to
almost 200 MB. I emptied the table and optimized all tables. Instead of
using eGroupware’s backup & restore the table was exported from MySQL on the
VM and transferred to the ISP. After this eGroupware is working again.

Is this expected behaviour? Are there ways of limiting the size of the log
table automatically?

Admin >> Site configuration: How many days should entries remain in the
access log before they get deleted. Default = 90

Ralf

Ralf Becker
Director Software Development

Stylite AG

Morschheimer Strasse 15 | Tel. +49 6352 70629 0
D-67292 Kirchheimbolanden | Fax. +49 6352 70629 30

Email: rb@stylite.de

www.stylite.de | www.egroupware.org

Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller
Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer

VAT DE214280951 | Registered HRB 31158 Kaiserslautern Germany

Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

el_es 2012-09-26 08:56:19 UTC #4

[…]

Is this expected behaviour? Are there ways of limiting the size of the log
table automatically?

Admin >> Site configuration: How many days should entries remain in the
access log before they get deleted. Default = 90

Ralf

Thank you, I was looking for this as well …

Lukasz

eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

el_es 2012-09-26 09:12:32 UTC #5

[…]

Is this expected behaviour? Are there ways of limiting the size of the log
table automatically?

Admin >> Site configuration: How many days should entries remain in the
access log before they get deleted. Default = 90

Ralf

How about this idea:

The access log for certain system requirements should be backed up daily and kept
for extended period of time - the idea is that there could be another section
in the Backup that only takes care of this - to clear the access log (remove non-active
entries) after backing it up, prefreably to a different file than regular db backups
(to prevent backup buildup) and then same mechanism as in Backup be applied to
keep access log backup files for set period of time.

Example: my reqular backup runs every hour during working hours in the working days.
I have (now) set the length of time the access log entries be kept to 7 days.
So I’d like now to back up the access log every 7 days, and clear it after backup.

It probably could be written as a script (bash or perl or php doing raw db access or
using the eGroupware API ?) but I don’t know it that much.

Kind Regards
Lukasz

eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

fnielsen 2012-09-26 11:55:00 UTC #6

Thank you Ralph,

I had overlooked the setting. I have adjusted it down and will see what happens.

Flemming