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.
<br><br>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.
)<br><br>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.
<br>
<br>Thank you for any suggestions.
<br>
<br>
<br>Wayne
<br>
<br>
<br>
<br>First apparent symptom: after an "apt-get upgrade" Mythtv-backend would
not start
<br>
<br>upgrades included(among others):
<br>
<br> the new 3.0 kernel
<br> mythtv-common:amd64, mythtv-backend:amd64 and associated files(0.24.1+fixes20110624-0.1, 0.24.1+fixes20110712-0.0)
<br> libakonadi-kmime4:amd64,libakonadi-kabc4:amd64,libakonadi-kcal4:amd64,libakonadi-kde4:amd64, libakonadi-contact4:amd64 (4.6.4-1, 4.6.5-1)
<br> mysql-server:amd64,mysql-server-core-5.1:amd64,libmysqlclient16:amd64,mysql-client:amd64 (5.1.57-3, 5.1.58-1)
<br>
<br>
<br>error messages from cron - started after the upgrade
<br>
<br> /etc/cron.daily/logrotate:
<br>
<br> error: error running shared postrotate script for
<br> '/var/log/mysql.log /var/log/mysql/mysql.log
<br> /var/log/mysql/mysql-slow.log '
<br> run-parts: /etc/cron.daily/logrotate exited with return code 1
<br>
<br>
<br> /etc/cron.weekly/mythtv-database:
<br>
<br> /usr/bin/mysqlcheck: Got error: 2002: Can't connect to local
<br> MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
<br> when trying to connect
<br> run-parts: /etc/cron.weekly/mythtv-database exited with return
<br> code 2
<br>
<br>
<br>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.
<br> xxx 3136 3134 0 08:28 ? 00:00:02 /usr/sbin/mysqld --defaults-file=<i class="moz-txt-slash"><span class="moz-txt-tag">/</span>home/xxx<span class="moz-txt-tag">/</span></i>.local/share/akonadi//mysql.conf
<br> --datadir=<i class="moz-txt-slash"><span class="moz-txt-tag">/</span>home/xxx<span class="moz-txt-tag">/</span></i>.local/share/akonadi/db_data/ --socket=<i class="moz-txt-slash"><span class="moz-txt-tag">/</span>home/xxx<span class="moz-txt-tag">/</span></i>.local/share/akonadi/socket-debian/mysql.socket
<br> root 3520 1 0 08:30 pts/0 00:00:00 /bin/sh<br> /usr/bin/mysqld_safe
<br> mysql 3631 3520 0 08:30 pts/0 00:00:02 /usr/sbin/mysqld
--basedir=/usr --datadir=/var/lib/mysql --user=mysql
<br> --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306
<br> root 3632 3520 0 08:30 pts/0 00:00:00 logger -t mysqld -p
<br> daemon.error
<br>
<br>$HOME/.local/share/akonadi//mysql.conf is dated on the upgraded date
<br>
<br>