[mythtv-users] Upgraded to 0.23, now the backend server dies

Bob Sully rcs at malibyte.net
Sat Apr 10 17:40:12 UTC 2010


Hi all -

Just upgraded to 0.23 via JYA's repo.  After the upgrade, did the DB
updates.  Since then, the backend won't stay up:


[mythtv at vader: ~]$ sudo start mythtv-backend
mythtv-backend start/running, process 13353

[mythtv at vader: ~]$ ps aux | grep back
root      8416  0.0  0.0   9688  1192 pts/0    S+   10:03   0:00 watch
tail -n 35 /var/log/mythtv/mythbackend.log
mythtv   13400  0.0  0.0   7336   868 pts/1    R+   10:28   0:00 grep back

[mythtv at vader: ~]$ ps aux | grep 13353
mythtv   13513  0.0  0.0   7336   880 pts/1    S+   10:29   0:00 grep 13353


Here's the relevant stuff from mythbackend.log:

2010-04-10 10:00:38.964 mythbackend version: branches/release-0-23-fixes
[24009] www.mythtv.org
2010-04-10 10:00:38.966 Using runtime prefix = /usr
2010-04-10 10:00:38.967 Using configuration directory = /.mythtv
2010-04-10 10:00:38.968 Unable to read configuration file mysql.txt
2010-04-10 10:00:38.968 Empty LocalHostName.
2010-04-10 10:00:38.969 Using localhost value of vader
2010-04-10 10:00:38.975 New DB connection, total: 1
2010-04-10 10:00:38.978 Connected to database 'mythconverg' at host:
localhost
2010-04-10 10:00:38.979 Closing DB connection named 'DBManager0'
2010-04-10 10:00:38.980 Connected to database 'mythconverg' at host:
localhost
2010-04-10 10:00:38.983 Current MythTV Schema Version (DBSchemaVer): 1254
No setting found for this machine's BackendServerIP.
Please run setup on this machine and modify the first page
of the general settings.


It says it can't read ~/.mythtv/mysql.txt, but I have no problem reading
it.  Here are the file details and the settings in the file.

[mythtv at vader: ~]$ lsl .mythtv/
total 196
<snip>
-rw-r--r--  1 mythtv mythtv    1097 2009-11-13 08:02 mysql.txt
<snip>

DBHostName=192.168.1.9
#DBHostPing=no
DBUserName=mythtv
DBPassword=xxxxxxxxx
DBName=mythconverg
DBType=QMYSQL3
LocalHostName=vader.malibyte.net
WOLsqlReconnectWaitTime=20
WOLsqlConnectRetry=5
WOLsqlCommand=/etc/init.d/mysql start


I ran mythtv-setup as the log entry suggests,and the server's IP and port
numbers are correct.  Looking at the settings table in the database with
Webmin, all looks good also:

DBSchemaVer 	1254
MythFillFixProgramIDsHasRunOnce 	1 	vader.malibyte.net
BackupDBLastRunStart 	2010-04-10 09:05:14
BackupDBLastRunEnd 	2010-04-10 09:05:27
StorageScheduler 	BalancedFreeSpace
Language 	EN_US 	vader.malibyte.net
BackendServerIP 	192.168.1.9 	vader.malibyte.net
BackendServerPort 	6543 	vader.malibyte.net
BackendStatusPort 	6544 	vader.malibyte.net
MasterServerIP 	192.168.1.9
MasterServerPort 	6543
TVFormat 	NTSC
VbiFormat 	None
FreqTable 	us-cable
TimeOffset 	Auto
MasterBackendOverride 	0
DeletesFollowLinks 	0
TruncateDeletesSlowly 	0 	vader.malibyte.net
HDRingbufferSize 	9400
DisableAutomaticBackup 	0
DisableFirewireReset 	0 	vader.malibyte.net
EITTransportTimeout 	5
EITIgnoresSource 	0
EITCrawIdleStart 	60
blockSDWUwithoutClient 	1


Restarting mysqld didn't solve it, either.  Anyone have a cause and a fix
for this?

Thanks!
Bob

-- 
________________________________________
Bob Sully - Simi Valley, California, USA
http://www.malibyte.net
http://www.malibyte.com



More information about the mythtv-users mailing list