CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • ACL killing MySQL (!)
Pages: [1]

Author Topic: ACL killing MySQL (!)  (Read 347 times)

artfulrobot.com

  • I post occasionally
  • **
  • Posts: 81
  • Karma: 4
ACL killing MySQL (!)
October 08, 2012, 03:16:11 am
There's a query run by an Activities Report which, when run by a user with restricted access, causes the MySQL server to lock up using all the CPU. It never stops until the server is restarted by root.

I was able to locate the offending SQL, and to isolate the 2 INNER JOIN ACL clauses that cause the problem. But I haven't got my head round quite how the ACL system works behind the scenes, specifically, how civicrm_acl_contact_cache is populated.

I've put the (commented) SQL at http://pastebin.com/KnUzQuvw

(I'm on MySQL 5.1.61, Debian Squeeze)

Any things I should check? The ACLs are not complex - basically one group of users is only allowed access to one particular contact sub-type. The Activities Report should just list activities related to the signed in user for the current month.

It's difficult to debug because the cache table is temporary/has changing content.

Thanks

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • ACL killing MySQL (!)

This forum was archived on 2017-11-26.