Open PerrineGilloteaux opened 4 years ago
I have truncated Cache data table from biii test database again today . Symptom was non functional test.biii.website, with messages such as
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42000]: Syntax error or access violation: 1142 INSERT command denied to user 'biiieudinmtest'@'10.10.111.177' for table 'watchdog': INSERT INTO {watchdog} (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7, :db_insert_placeholder_8, :db_insert_placeholder_9); Array ( [:db_insert_placeholder_0] => 0 [:db_insert_placeholder_1] => php [:db_insert_placeholder_2] => %type: @message in %function (line %line of %file). [:db_insert_placeholder_3] => a:6:{s:5:"%type";s:45:"Drupal\Core\Dat
.
I do not get why this one is going over quota when the prod one is ok.
Solution for now for admin is to o in phpmyadmin and empty (truncate) cache_* entries from the biii test database. But still an open and worrying problem.
Similar error is discussed here: https://drupal.stackexchange.com/questions/203292/site-got-an-error-after-moving-from-local-to-a-server
But probably the source of the problem is more due to the test site is in developer mode, and that somehow causes a huge cache in the database - which then block the insertion of more data. I switched off the developer mode for the test site, so let’s see.
@PerrineGilloteaux do you still see this as an issue?
yes but only for test database
In any case, the server should me moved out from OVH
our test database (name not displayed here for security reasons) goes regularly over quota (which is below the one in prod, but still, it reaches sizes welll above the prod one. From MyPHPAdmin tables, it sounds to come from the cache table. For now I have emptied the cache table (TRUNCATE) but this needs to be further investigated (What are the differences ibetwenn the test database and the prod one? it should be identical? The problem is solved now by empty tabkes CACHE_.. (> 1G of Cache data) but this has to be investigated.