Barney - could you clarify your comment for me?
You say Running mythtv-setup, removing all encoder cards and adding
them again fixes this. Is this a permanent fix, or does the problem
recur if you reboot?
If this is only a fix for that boot, there are easier ones. Anything
that causes
I believe I am also encountering this bug. Running Mythbuntu 9.04 Beta
I find my recording schedule on mythtv is empty after reboot. Running
mythtv-setup, removing all encoder cards and adding them again fixes
this.
Output of cat syslog | grep mysqld:
Apr 19 11:54:05 barney mysqld[3497]:
Since I upgraded to Jaunty RC, my mythtv database gets corrupted after
almost every new boot. This results into a confused mythtv-backend which
fails to record the scheduled recordings. After a repair table command
everything returns back as normal. I'm trying the wait fix
mentioned above, hope
** Also affects: mythbuntu
Importance: Undecided
Status: New
--
mysql thinks it has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
--
Adding mythbuntu. It seems to me that the wait should make things
more reliable and predictable rather than less, so I must be missing
something. Any danger in removing the wait?
** Changed in: mythbuntu
Importance: Undecided = Critical
** Changed in: mythbuntu
Status: New =
Yeah - it looks to me like Bug 358173 is the same bug.
I find it very strange that this bug only affects mythbackend (all the
possible duplicates seem to reference mythtv). I suspect that it is
doing something strange. I reported a mysql bug because I figured that
the mysql server shouldn't
Bug 358173 may be a duplicate of this.
Thanks to the original reporter for proposing a solution.
** Changed in: mysql-dfsg-5.0 (Ubuntu)
Status: Incomplete = Confirmed
--
mysql thinks it has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better. When you're running into the issue, does mysqld_safe
takes up 100% of the cpu?
** Changed in: mysql-dfsg-5.0 (Ubuntu)
Status: New = Incomplete
--
mysql thinks it has crashed when it hasn't
I can confirm this behavior.
--
mysql thinks it has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
--
Ubuntu-server-bugs mailing list