On 10/26/11 14:03, Michael Sullivan wrote: > On 10/26/11 13:31, Michael Sullivan wrote: >> On 10/26/11 11:36, Mark Knecht wrote: >>> On Wed, Oct 26, 2011 at 9:29 AM, Michael Sullivan <msulli1...@gmail.com> >>> wrote: >>>> On 10/26/11 11:07, Neil Bothwick wrote: >>>>> On Wed, 26 Oct 2011 09:23:30 -0500, Michael Sullivan wrote: >>>>> >>>>>> At first I thought that sometime that installed since Oct 12 was causing >>>>>> the segfault, so I tried unmerging the 350+ packages that had installed >>>>>> since then and listing them in package.mask, but that blew up in my face >>>>>> because I don't know a command that forces portage to ignore masked >>>>>> packages and install next-highest stable versions. >>>>> >>>>> Mask higher versions in package mask >>>>> >>>>>> cat/pkg-version.you.want >>>>> >>>>> >>>> >>>> I did, but as I said there where 350+ of them. And every time I tried >>>> to emerge anything else, I couldn't because some package I needed was >>>> listed in package mask. I got the package list that I added to >>>> package.mask from /var/log/portage-logs for files dated from October 12 >>>> till 24. It was an epic fail. I couldn't even emerge -e world because >>>> of those stupid masked package versions... >>> >>> OK, I haven't used Myth now in over a year so take this with a grain >>> of salt. From the log file it appears that your client isn't >>> connecting to the server which likely explains why you don't see the >>> programs. I wonder if you've tested connecting to mythconverg manually >>> via a terminal? Maybe something like /etc/my.cnf or one of the Myth >>> config files got messed up in the update. >>> >>> Good luck, >>> Mark >>> >> >> Mysql on camille is broken: >> >> camille ~ # mysql -u root -p >> mysql: unknown variable 'expire_logs_days=10' >> >> I'll do some googling, but I thinmichael@camille ~ $ sudo mythbackend > 2011-10-26 13:48:02.094 mythbackend version: branches/release-0-23-fixes > [27077] www.mythtv.org > 2011-10-26 13:48:02.094 Using runtime prefix = /usr > 2011-10-26 13:48:02.094 Using configuration directory = /root/.mythtv > 2011-10-26 13:48:02.124 Unable to read configuration file mysql.txt > 2011-10-26 13:48:02.124 Empty LocalHostName. > 2011-10-26 13:48:02.124 Using localhost value of camille > 2011-10-26 13:48:02.176 New DB connection, total: 1 > 2011-10-26 13:48:02.223 Connected to database 'mythconverg' at host: > localhost > 2011-10-26 13:48:02.223 Closing DB connection named 'DBManager0' > 2011-10-26 13:48:02.231 Connected to database 'mythconverg' at host: > localhost > 2011-10-26 13:48:02.344 Current MythTV Schema Version (DBSchemaVer): 1254 > 2011-10-26 13:48:02.348 MythBackend: Running as a slave backend. > 2011-10-26 13:48:02.384 mythbackend: MythBackend started as a slave backend > 2011-10-26 13:48:02.390 New DB connection, total: 2 > 2011-10-26 13:48:02.401 Connected to database 'mythconverg' at host: > localhost > 2011-10-26 13:48:02.426 New DB connection, total: 3 > 2011-10-26 13:48:02.462 Connected to database 'mythconverg' at host: > localhost > 2011-10-26 13:48:02.728 MediaServer:: Loopback address specified - > 127.0.0.1. Disabling UPnP > 2011-10-26 13:48:02.728 Main::Registering HttpStatus Extension > 2011-10-26 13:48:02.728 Enabled verbose msgs: important general > 2011-10-26 13:48:03.773 Connecting to master server: 192.168.2.3:6543 > 2011-10-26 13:48:03.773 Connected successfully > 2011-10-26 13:48:12.673 mythbackend: Running housekeeping thread > 2011-10-26 13:48:33.781 MythSocket(8219290:23): readStringList: Error, > timed out after 30000 ms. > QMutex::unlock: mutex lock failure: Invalid argument > k that sounds like a config file > > It's been up for about 20 minutes and it hasn't crashed. None of the > things I mentioned before work, but at least it's not crashing, right? > This is a good step forward... >> directive. I'll probably do a rebuild of mysql as well... > > > I googled the expire_logs thing and what I found said to comment it out > and restart mysql. I did that, and now the output of mythbackend says: > > > I forgot that I was going to post the output of mythbackend to see if any of the changes provide hints to solving any of my other myth problems:
michael@camille ~ $ sudo mythbackend 2011-10-26 13:48:02.094 mythbackend version: branches/release-0-23-fixes [27077] www.mythtv.org 2011-10-26 13:48:02.094 Using runtime prefix = /usr 2011-10-26 13:48:02.094 Using configuration directory = /root/.mythtv 2011-10-26 13:48:02.124 Unable to read configuration file mysql.txt 2011-10-26 13:48:02.124 Empty LocalHostName. 2011-10-26 13:48:02.124 Using localhost value of camille 2011-10-26 13:48:02.176 New DB connection, total: 1 2011-10-26 13:48:02.223 Connected to database 'mythconverg' at host: localhost 2011-10-26 13:48:02.223 Closing DB connection named 'DBManager0' 2011-10-26 13:48:02.231 Connected to database 'mythconverg' at host: localhost 2011-10-26 13:48:02.344 Current MythTV Schema Version (DBSchemaVer): 1254 2011-10-26 13:48:02.348 MythBackend: Running as a slave backend. 2011-10-26 13:48:02.384 mythbackend: MythBackend started as a slave backend 2011-10-26 13:48:02.390 New DB connection, total: 2 2011-10-26 13:48:02.401 Connected to database 'mythconverg' at host: localhost 2011-10-26 13:48:02.426 New DB connection, total: 3 2011-10-26 13:48:02.462 Connected to database 'mythconverg' at host: localhost 2011-10-26 13:48:02.728 MediaServer:: Loopback address specified - 127.0.0.1. Disabling UPnP 2011-10-26 13:48:02.728 Main::Registering HttpStatus Extension 2011-10-26 13:48:02.728 Enabled verbose msgs: important general 2011-10-26 13:48:03.773 Connecting to master server: 192.168.2.3:6543 2011-10-26 13:48:03.773 Connected successfully 2011-10-26 13:48:12.673 mythbackend: Running housekeeping thread 2011-10-26 13:48:33.781 MythSocket(8219290:23): readStringList: Error, timed out after 30000 ms. QMutex::unlock: mutex lock failure: Invalid argument
