Ubuntu
cacti package

  1. Bug #1578144
  2. Comment #8

Comment 8 for bug 1578144

Revision history for this message
Hans Rönnbäck (6ans) wrote : Re: Cacti causes high CPU load via MySQL after upgrade to Ubuntu 16.04

Ran the commands, which returned this;

@@global.sql_mode = ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

@@session.sql_mode = ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

@sql_mode = ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

And these values seem to be the default as of MySQL 5.7

I've scanned the cacti forums, where its repeatedly stated that cacti is incompatible with "strict mode" (which implies NO_ZERO_IN_DATE/NO_ZERO_DATE). I've also tried to modify the cacti php files to clear the sql_mode, but it doesn't seem to work (still get errors in logs about invalid dates)

And my upgrade path is similar to Andrews, i.e. started out on Ubuntu 13.10, upgraded to 14.04 followed by 15.10 then went to 16.04 (last step introduced the problem)

Did the apport-collect as asked (it stated that my cacti cron-job was modified, but I have no memory of ever manipulating that file)