Difference between revisions of "High DB Load"
From Kolmisoft Wiki
Jump to navigationJump to search
Line 4: | Line 4: | ||
[[File:ac_hgc302.png]] | [[File:ac_hgc302.png]] | ||
As an example we see that load started to grow at ~09:46 | |||
We can check log files at the similar time. | |||
Here in /var/log/m2/gui_crash.log we can find: | |||
-------------------------------------------------------------------------------- | |||
ID: 20181008094632 | |||
Class: Mysql2::Error | |||
Message: Lock wait timeout exceeded; try restarting transaction | |||
Controller: tariffs | |||
Action: import_csv2 | |||
---------------------------------------- | |||
Which clearly shows us that problem was caused by importing CSV Tariff file. | |||
We can find such file in /tmp folder by the Modify Time and with name import_csv......csv |
Revision as of 16:21, 9 October 2018
High DB load usually is the cause of the 302 Global Call Limit reached problem for M2.
It looks like this:
As an example we see that load started to grow at ~09:46
We can check log files at the similar time.
Here in /var/log/m2/gui_crash.log we can find:
-------------------------------------------------------------------------------- ID: 20181008094632 Class: Mysql2::Error Message: Lock wait timeout exceeded; try restarting transaction Controller: tariffs Action: import_csv2 ----------------------------------------
Which clearly shows us that problem was caused by importing CSV Tariff file.
We can find such file in /tmp folder by the Modify Time and with name import_csv......csv