Time Nick Message 18:34 cait oh the quiet 14:21 huginn` cait: The operation succeeded. 14:21 cait @later tell kidclamp still having issues with Elasticsearch - maybe if you got a moment ping me? 03:46 pablo cait, the problem was memcached, flush_all solve it. Thanks for your time :) 01:23 huginn` kidclamp: The operation succeeded. 01:23 kidclamp @later tell oleonard - maybe 3137 should be expanded to individual fields as well and replace the quick add? 01:02 stpjhlibrary Location: /etc/mysql/mariadb.conf.d/50-server.cnf 01:01 stpjhlibrary This is where I found the file in case anyone is having a hard time finding it 01:00 stpjhlibrary it took me doing some research to find that the [mysqld] section in the cnf file. Since I am using mariadb it is in a different location than what was in the walkthrough in that URL 00:56 stpjhlibrary Pianohacker I think i got it working I have Mariadb but is there a script or something that can clean up the existing errors in the about page data errors? 00:47 pianohacker stpjhlibrary: https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix 00:07 stpjhlibrary Some of your tables have problems with their auto_increment values which may lead to data loss. You should not ignore this warning. The problem is that InnoDB does not keep auto_increment across SQL server restarts (it is only set in memory). So on server startup the auto_increment values are set to max(table.id)+1. 00:07 stpjhlibrary Has anyone else been able to fix the error: