ludo1960 Posted May 14, 2019 Author Share Posted May 14, 2019 I have no idea what you mean by general log Quote Link to comment Share on other sites More sharing options...
gw1500se Posted May 14, 2019 Share Posted May 14, 2019 https://mariadb.com/kb/en/library/general-query-log/ Quote Link to comment Share on other sites More sharing options...
ludo1960 Posted May 14, 2019 Author Share Posted May 14, 2019 Ok, after trying it all again ie truncate, load page again, still double entries. Here's the maria.err log 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffe$ 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: The InnoDB memory heap is disabled 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: Compressed tables use zlib 1.2.8 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: Using Linux native AIO 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: Using SSE crc32 instructions 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: Completed initialization of buffer pool 2019-05-14 20:37:23 139840968318336 [Note] InnoDB: Highest supported file format is Barracuda. 2019-05-14 20:37:24 139840968318336 [Note] InnoDB: 128 rollback segment(s) are active. 2019-05-14 20:37:24 139840968318336 [Note] InnoDB: Waiting for purge to start 2019-05-14 20:37:24 139840968318336 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number $ 2019-05-14 20:37:24 139840301561600 [Note] InnoDB: Dumping buffer pool(s) not yet started 2019-05-14 20:37:24 139840968318336 [Note] Plugin 'FEEDBACK' is disabled. 2019-05-14 20:37:24 139840968318336 [Note] Server socket created on IP: '127.0.0.1'. 2019-05-14 20:37:24 139840968318336 [Note] Reading of all Master_info entries succeded 2019-05-14 20:37:24 139840968318336 [Note] Added new Master_info '' to hash table 2019-05-14 20:37:24 139840968318336 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.1.38-MariaDB-0+deb9u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian 9.8 Quote Link to comment Share on other sites More sharing options...
Barand Posted May 14, 2019 Share Posted May 14, 2019 The id sequence of your data (article is id 1 and 24) seems to imply that records are not being written twice (that would give article as ids 1 and 2), rather that the process is being run twice somehow. Quote Link to comment Share on other sites More sharing options...
ludo1960 Posted May 14, 2019 Author Share Posted May 14, 2019 (edited) only because I sorted the table by item, here it is sorted by id: Edited May 14, 2019 by ludo1960 Quote Link to comment Share on other sites More sharing options...
Barand Posted May 14, 2019 Share Posted May 14, 2019 Doesn't make any difference to the ids what order you sort the records into. The point is that the two ids for any item have a difference of 23 Quote Link to comment Share on other sites More sharing options...
ludo1960 Posted May 16, 2019 Author Share Posted May 16, 2019 Good news guys, found the error: I was having a tough time trying to install xdebug, I used the output from php -v and put it in here: https://xdebug.org/wizard.php The output from my php.ini was PHP 7.2.18-..... Then the wizard gave me the steps to follow. The script needs phpize from the php-dev bundle seemingly. As I had just rebuilt my dev box, I was watching the xdebug install doing its thing and I noticed that php7.0 and php7.3 kept whizzing by as the script progressed. Strange I thought, i've got php7.2 why is xdebug downloading all this stuff?? Needless to say when i tried to get xdebug working by adding zend_extension=/usr/lib/php/20170718/xdebug.so to the php.ini, and you guessed it, it didn't work! Plan B was called for, re-installed my dev box from scratch. Then installed php7.2-dev so that I had the right version of phpize, and it all went to plan. No more double entries in the database, and all errors are displayed...Result!!! Moral of the tale, dont trust the xdebug wizard! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.