Kevin Kuphal wrote: > Steve Malenfant wrote: >> I couldn't find the answer anywhere... "service mythbackend start" >> don't work on my salve... It's not an IP configuration issue... >> mythfrontend works as root and mythtv user on the slave. Also when I >> execute manually everything works fine. >> >> So if do "/usr/bin/mythbackend --daemon --logfile >> /var/log/mythtv/mythbackend.log --pidfile /var/run/mythbackend.pid" >> the server starts just fine (minus the problem with the channel here): >> >> Running as a slave backend. >> 2006-01-13 20:48:46.281 New DB connection, total: 2 >> 2006-01-13 20:48:46.288 mythbackend: MythBackend started as a slave backend >> 2006-01-13 20:48:46.326 DVB#0 DVB SI Table Parser Started >> 2006-01-13 20:48:46.361 DVB#0 Using DVB card 0, with frontend Broadcom >> BCM3510 VSB/QAM frontend. >> 2006-01-13 20:48:46.368 DVB#0 ERROR - Unable to find channel in database. >> 2006-01-13 20:48:46.370 DVB#0 ERROR - Failed to get channel options >> for channel 5-1. >> 2006-01-13 20:48:46.374 Closing DVB channel >> 2006-01-13 20:48:47.357 mythbackend version: 0.18.2.20051227-1 www.mythtv.org >> 2006-01-13 20:48:47.362 Enabled verbose msgs : important general >> 2006-01-13 20:48:48.379 Connecting to master server: 192.168.11.24:6543 >> 2006-01-13 20:48:48.397 Connected successfully >> >> And when I use "service mythbackend start" : >> >> 2006-01-13 20:44:16.104 New DB connection, total: 1 >> 2006-01-13 20:44:16.112 Unable to connect to database! >> 2006-01-13 20:44:16.114 Driver error was [1/2002]: >> QMYSQL3: Unable to connect >> Database error was: >> Can't connect to local MySQL server through socket >> '/var/lib/mysql/mysql.sock' (2) >> >> I'm not sure what's the difference but it doesn't work using the >> "service" with remote database. >> > I'm guessing when you run it manually you do not run it as root? It > sounds like you have not followed all the steps in the documentation at > mythtv.org for running a slave backend, specifically about the > database. Remember: You need to have your slave backend connect to the > *same* database your master backend connects to. It is quite common > for the distribution of linux chosen to run mythtv will install a > database server on each installation so it is also quite common for > people running slave backends to end up connecting their slave to the > local database rather than the master. Read the documentation careful > and check your config.
Well, the problem is clearly that it is finding a valid mysql.txt when start from the commandline but not when started in the init script. This is most likely the $HOME environment variable and not a lack of reading mythtv docs ;-). Root's $HOME may be /root when logged in but may be / during init. You could "export $HOME=/root" in the script or make a synlink for /mysql.txt or copy mysql.txt to / or whatever. -- bjm _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
