Hello,
I'm a new user to this program. I use a Raspberry Pi 3 and have tried to install it but get an error regarding MySQL not starting. The error codes are shown below.
Any pointers would be gratefully received.
Thanks
Version: '10.1.37-MariaDB-0+deb9u1' socket: '/home/pi/.config/cqrlog/database/sock' port: 64000 Raspbian 9.0
2018-11-27 20:20:59 1503045440 [Note] /usr/sbin/mysqld: Normal shutdown
2018-11-27 20:20:59 1447031616 [Note] InnoDB: FTS optimize thread exiting.
2018-11-27 20:20:59 1503045440 [Note] InnoDB: Starting shutdown...
2018-11-27 20:21:00 1503045440 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
2018-11-27 20:21:02 1503045440 [Note] InnoDB: Shutdown completed; log sequence number 1600617
2018-11-27 20:21:02 1503045440 [Note] /usr/sbin/mysqld: Shutdown complete
2018-11-30 12:38:40 1995759616 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-30 12:38:40 1995759616 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-11-30 12:38:40 1995759616 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Using Linux native AIO
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Using generic crc32 instructions
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Completed initialization of buffer pool
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Highest supported file format is Barracuda.
2018-11-30 12:38:40 1995759616 [Note] InnoDB: 128 rollback segment(s) are active.
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Waiting for purge to start
2018-11-30 12:38:40 1995759616 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 1600617
2018-11-30 12:38:40 1392505664 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-11-30 12:38:40 1995759616 [Note] Plugin 'FEEDBACK' is disabled.
2018-11-30 12:38:40 1995759616 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
2018-11-30 12:38:40 1995759616 [Note] Server socket created on IP: '::'.
2018-11-30 12:38:40 1995759616 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
2018-11-30 12:38:40 1502742336 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
2018-11-30 12:38:40 1995759616 [Note] Reading of all Master_info entries succeded
2018-11-30 12:38:40 1995759616 [Note] Added new Master_info '' to hash table
2018-11-30 12:38:40 1995759616 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.37-MariaDB-0+deb9u1' socket: '/home/pi/.config/cqrlog/database/sock' port: 64000 Raspbian 9.0
Hi!
Could you start cqrlog from command console
cqrlog debug=1 > /tmp/debug.txt
Then upload /tmp/debug.txt with your message that we see errors from cqrlog start.
--
Saku
OH1KH
This is the content of debug.txt
Closing GrayLine window
Closing dDXCC
Closing dData
/home/pi/.config/cqrlog/database/raspberrypi.pid
Command:
kill 31763
WARNING: TLCLComponent.Destroy with LCLRefCount>0. Hint: Maybe the component is processing an event?
WARNING: TLCLComponent.Destroy with LCLRefCount>0. Hint: Maybe the component is processing an event?
Closing ini file ...
This is not complete debug. It is just the end of it.
The start of debug, when cqrlog starts, is more interesting.
If mysql server is running ok (before trying to start cqrlog) it can also be used directly. Normal cqrlog start tries to start new protected instance of mysql and that might need too big slice of ram on small computers like rasp or neopi.
Please read this message
https://cqrlog.com/comment/6776#comment-6776
--
Saku
OH1KH