See my topic from 28/10/14 :
In the meanwhile, I desinstalled Kubuntu and installed instead Xbuntu (14.04) and CQRLOG (1.7.3). Nothing new. Edit time : 15 sec before the chosen call appears in the edit window and again 15 sec before you are able to edit the QSO.
Reading the topics on the forum, I found a post by OH1KH and followed his proposal (he had the same performance issue) : loading a first log, then closing it and loading the log you want to work with. It works, is not very practical and may point a problem with the SQL server.
Any idea ?
73
Luc F6HJO/HB9ABB
Wed, 2014-10-29 16:39
#1
CQRLOG very slow
Hi Luc,
run the cqrlog for the first time, choose the log. Close it. Go to ~/.config/cqrlog/database. There is a file named mysql.err. Paste here what is in it or send it to my email. Thank you!
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Hi Petr thank you for your message,
I did what you said, but the mysql.err file in ~/.config/cqrlog/database is empty. Nevertheless, I found an error.log in /var/log/mysql. Please note that the error messages in this log file are not from today (3/11/2014, when I did the test you said) but are from the day I installed cqrlog and mysql. Here the file :
141029 13:53:15 [Note] Plugin 'InnoDB' is disabled.141029 13:53:15 [Note] Plugin 'FEEDBACK' is disabled.141029 13:53:15 [Note] Plugin 'InnoDB' is disabled.141029 13:53:15 [Note] Plugin 'FEEDBACK' is disabled.141029 13:53:15 [Note] Plugin 'InnoDB' is disabled.141029 13:53:15 [Note] Plugin 'FEEDBACK' is disabled.141029 13:53:15 [Note] Plugin 'InnoDB' is disabled.141029 13:53:15 [Note] Plugin 'FEEDBACK' is disabled.141029 13:53:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql141029 13:53:17 InnoDB: The InnoDB memory heap is disabled141029 13:53:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins141029 13:53:17 InnoDB: Compressed tables use zlib 1.2.8141029 13:53:17 InnoDB: Using Linux native AIO141029 13:53:17 InnoDB: Initializing buffer pool, size = 128.0M141029 13:53:18 InnoDB: Completed initialization of buffer poolInnoDB: The first specified data file ./ibdata1 did not exist:InnoDB: a new database to be created!141029 13:53:18 InnoDB: Setting file ./ibdata1 size to 10 MBInnoDB: Database physically writes the file full: wait...141029 13:53:18 InnoDB: Log file ./ib_logfile0 did not exist: new to be createdInnoDB: Setting log file ./ib_logfile0 size to 5 MBInnoDB: Database physically writes the file full: wait...141029 13:53:18 InnoDB: Log file ./ib_logfile1 did not exist: new to be createdInnoDB: Setting log file ./ib_logfile1 size to 5 MBInnoDB: Database physically writes the file full: wait...InnoDB: Doublewrite buffer not found: creating newInnoDB: Doublewrite buffer createdInnoDB: 127 rollback segment(s) active.InnoDB: Creating foreign key constraint system tablesInnoDB: Foreign key constraint system tables created141029 13:53:19 InnoDB: Waiting for the background threads to start141029 13:53:20 Percona XtraDB (http://www.percona.com) 5.5.38-MariaDB-35.2 started; log sequence number 0141029 13:53:20 [Note] Plugin 'FEEDBACK' is disabled.141029 13:53:20 [Note] Server socket created on IP: '127.0.0.1'.141029 13:53:20 [Note] Event Scheduler: Loaded 0 events141029 13:53:20 [Note] /usr/sbin/mysqld: ready for connections.Version: '5.5.39-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)Status information:Current dir: /var/lib/mysql/Running threads: 1 Stack size: 196608Current locks:lock: 0xb5c75264: readread : 0xa1f8322c (7:5); lock: 0xaa760264:lock: 0x9bb65a64:lock: 0xb5c41a64:lock: 0x9bbd3b34:lock: 0x9bbd3834:lock: 0x9bbc1f64:lock: 0xb5c8f864:lock: 0xb5c73a64:
Thank you, to read you is a pleasure.
Luc F6HJO/HB9ABB
Hi Luc !
Is it bossible for you to make following test:
At preferences: "Callbook support" add QRZ.COM username and password (make one if you do not have)Then at "New qso" select "Enable auto search on HamQTH.COM/QRZ.COM"
Of course you need internet connection for that so that auto search will work at least on one go.
I had this QRZ.COM account done before, but after I first time enabled auto search at "New qso" settings my problem went away and I have not been able to reproduce it any more with or without auto search and with old or just created log.
I do not know was it an accident, but the fix was clearly releated on enabling auto search.
73 Saku OH1KH
--
Saku
OH1KH
Hi Saku,
I made the test you proose, but no deal, no change !
Thank you
Luc