Opened 13 years ago
Closed 13 years ago
#9368 closed Bug Report (Unverified)
MBE segfaults daily, readStringList: Error also MySQL server has gone away
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | MythTV - General | Version: | 0.23-fixes |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description (last modified by )
I'm seeing daily or every couple of days crashes of the MBE. See myth.log for specifics of the crash. MBE becomes unresponsive.
I've tried several things in order to resolve, mysql checks of the database, backup/restore (full only). I have followed the TicketHowTo wiki page and searched the existing bugs, I can't see that any of the existing or past tickets is this exact issue. I have looking at the mailing lists (esp. long reschedule issues with mysql). I've rebuilt with debug flags per the backtrace wiki and docs pages. Enclosed is the backtrace and myth log. Happy to switch the mythbackend -v logging options or reproduce anything else thats needed to help find the problem. Thanks Dave.
source build on debian squeeze (2.6.32-5) from git pull 9th december.
gdbcommands file:
mythtv@bradford:~/build$ cat gdbcommands handle SIGPIPE nostop noprint handle SIG33 nostop noprint set logging on set pagination off set breakpoint pending on break qFatal set args -l myth.log -v record,channel,siparser run thread apply all bt full set logging off
mysql version and process list at crash/pre-backtrace time
Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 395 Server version: 5.1.49-3-log (Debian) Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved. This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL v2 license Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> show processlist; +-----+--------+---------------------+-------------+---------+------+-------+------------------+ | Id | User | Host | db | Command | Time | State | Info | +-----+--------+---------------------+-------------+---------+------+-------+------------------+ | 122 | mythtv | mythdb.napier:46769 | mythconverg | Sleep | 2026 | | NULL | | 123 | mythtv | mythdb.napier:46770 | mythconverg | Sleep | 2026 | | NULL | | 125 | mythtv | mythdb.napier:46772 | mythconverg | Sleep | 2027 | | NULL | | 133 | mythtv | mythdb.napier:33025 | mythconverg | Sleep | 2026 | | NULL | | 134 | mythtv | mythdb.napier:33026 | mythconverg | Sleep | 2026 | | NULL | | 246 | mythtv | leeds.napier:46090 | mythconverg | Sleep | 1919 | | NULL | | 263 | mythtv | leeds.napier:38216 | mythconverg | Sleep | 1919 | | NULL | | 395 | mythtv | localhost | mythconverg | Query | 0 | NULL | show processlist | +-----+--------+---------------------+-------------+---------+------+-------+------------------+ 8 rows in set (0.00 sec)
Attachments (3)
Change History (7)
comment:2 Changed 13 years ago by
This looks a lot like the mysql server went AWOL for a time, but when it came back, mythbackend didn't reconnect. This bug was fixed in 0.24.
There may be more to it than than, but I would strongly suggest using a newer version, where this is likely already fixed, or mostly so.
comment:3 Changed 13 years ago by
Thank you very much. I'll upgrade, thinking outloud, wonder if I dare before the end of this week? Its actually been reasonably stable since reattaching the SBE and disabling mythfilldatabase. Happy if you want to close this, I can always re-open once on .24.
comment:4 Changed 13 years ago by
Resolution: | → Unverified |
---|---|
Status: | new → closed |
Closing at user request
zip of myth.log+gdb.txt