[mythtv-users] Upgrade (Debian wheezy/sid using KDE) breaks operating Mythtv-backend installation

M D weworama at gmail.com
Mon Aug 1 15:46:07 UTC 2011

My Mythtv-backend (0.24.1+ ) stopped working after an upgrade this weekend.
I have been exploring the issue for a day now, and found the backend will
work after a restart of mysql but not knowing mysql and MythTV very well, I
am a little tentative on what to do now and wonder if someone else has a
more elegant fix than just restarting mysql and then the backend or a
suggestion on where to look for one.

More of the details are below, but the short version is that I think that
something related to an KDE/akonadi installation/upgrade changed the mysql
configuration, which now appears to be working for akonadi on startup.  The
backend at that point will not start as it does not appear to be able to
access its database.    (In that state, however, I can still log into the
database as the mythtv user. )

I am wondering if there is a script in the mythtv installation that might
reset the configuration files or if I have to change something manually.

Thank you for any suggestions.


First apparent symptom: after an "apt-get upgrade"  Mythtv-backend would not

upgrades included(among others):

   the new 3.0 kernel
   mythtv-common:amd64, mythtv-backend:amd64 and associated
files(0.24.1+fixes20110624-0.1, 0.24.1+fixes20110712-0.0)

libakonadi-contact4:amd64 (4.6.4-1, 4.6.5-1)

(5.1.57-3, 5.1.58-1)

error messages from cron - started after the upgrade


       error: error running shared postrotate script for
       '/var/log/mysql.log /var/log/mysql/mysql.log
       /var/log/mysql/mysql-slow.log '
       run-parts: /etc/cron.daily/logrotate exited with return code 1


       /usr/bin/mysqlcheck: Got error: 2002: Can't connect to local
       MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
       when trying to connect
       run-parts: /etc/cron.weekly/mythtv-database exited with return
       code 2

ps -ef | grep mysql   - shows akonadi now using mysql on start up and
suggests to me that akonadi is closely related to this problem as mysql has
never started on boot before this upgrade due to issues with static ip and
the wireless connection.
   xxx      3136  3134  0 08:28 ?        00:00:02 /usr/sbin/mysqld

   root      3520     1  0 08:30 pts/0    00:00:00 /bin/sh
   mysql     3631  3520  0 08:30 pts/0    00:00:02 /usr/sbin/mysqld
--basedir=/usr --datadir=/var/lib/mysql --user=mysql
--socket=/var/run/mysqld/mysqld.sock --port=3306
   root      3632  3520  0 08:30 pts/0    00:00:00 logger -t mysqld -p

$HOME/.local/share/akonadi//mysql.conf is dated on the upgraded date
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20110801/af80a8aa/attachment-0001.html 

More information about the mythtv-users mailing list