Upgrade to Ubuntu 16.04 LTS - CQRlog error connecting to database

9 posts / 0 new
Last post
K5LY
K5LY's picture
Upgrade to Ubuntu 16.04 LTS - CQRlog error connecting to database

Removed CQRlog, attempting to re-install CQRlog fails.

Received following erros message when attempting to install in Synaptic file manager

An Error Occurred
E: mysql-common subprocess installed post-instalation script returned error exit status2
E: mariadb-common dependency problems leaving unconfigured.

ok2cqr
ok2cqr's picture
Re: Upgrade to Ubuntu 16.04 LTS - CQRlog error connecting to dat

This is known bug in Ubuntu 16.04. I tried to upgrade a few machines and always had this problem. Upgrade of MySQL packages always failed. The only solution was to remove MySQL before the upgrade.

DL2KI
Hi,

Hi,

when installing CQRLOG with Kubuntu 16.04, mysql is uninstalled . Then there are problems with Aconadi and KDE Korganizer. Apparently the KDE programs do not run with MariaDB.

Here, therefore, would have to find a solution to continue to work with CQRLOG under KDE and 16.04 LTS.

73, Wolfgang
DL2KI

ok2cqr
ok2cqr's picture
Re: Hi,

Hi Wolfgang,

it seems this is a problem with Debian apt utility. In the dependencies there are mysql-server OR mariadb-server. I have no idea why apt doesn't understand that.

You can use binaries from tar.gz file, it will work.

73 Petr, OK2CQR

DL2KI
Hi Petr,

Hi Petr,

thank you for the information. I will then use the binaries until the problem is probably resolved.

73, Wolfgang
DL2KI

PY2ZA
Rescue LOG

In the last months I have used the log (Excellent job!!!).

In recent days, simply connect to MySQL server no longer appears. How do I get access to my QSOs again?

Best 73 de Jr

Ubuntu 16.04lts

ok2cqr
ok2cqr's picture
Re: Rescue LOG

What error do you see? What is in the mysql error log?

PY2ZA
Re: Rescue LOG

All server information and my log are gone.
This is the first mysql error log (@ Ubuntu 14), in the date that has the problem :

161030 2:06:13 [Note] /usr/sbin/mysqld: Normal shutdown
161030 2:06:13 [Note] Event Scheduler: Purging the queue. 0 events
161030 2:06:14 InnoDB: Starting shutdown...
161030 2:06:15 InnoDB: Shutdown completed; log sequence number 2816821
161030 2:06:15 [Note] /usr/sbin/mysqld: Shutdown complete
161030 10:05:59 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
161030 10:05:59 [Note] Plugin 'FEDERATED' is disabled.
161030 10:06:00 InnoDB: The InnoDB memory heap is disabled
161030 10:06:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161030 10:06:00 InnoDB: Compressed tables use zlib 1.2.8
161030 10:06:00 InnoDB: Using Linux native AIO
161030 10:06:00 InnoDB: Initializing buffer pool, size = 128.0M
161030 10:06:00 InnoDB: Completed initialization of buffer pool
161030 10:06:00 InnoDB: highest supported file format is Barracuda.
161030 10:06:05 InnoDB: Waiting for the background threads to start
161030 10:06:06 InnoDB: 5.5.52 started; log sequence number 2816821
161030 10:06:06 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
161030 10:06:06 [Note] - '127.0.0.1' resolves to '127.0.0.1';
161030 10:06:06 [Note] Server socket created on IP: '127.0.0.1'.
161030 10:06:09 [Note] Event Scheduler: Loaded 0 events
161030 10:06:09 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.52-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)

PY2ZA
Updated the version of Linux

Updated the version of Linux (Ubuntu 16.04) and the problem continues. I uninstalled and reinstalled the log and the problem continued. I deleted the .config folder and reinstalled log, now worked. I recovered the automatic backup of another drive.
normal life ... thanks!