mythbuntu-bugs team mailing list archive

[Mario Limonciello <superm1@xxxxxxxxxx>]

So at some point we did add in code that will ping mysql continually
until it's running and then start mythbackend.  I suspect that's what
fixed it for you.

If someone else encounters this and has the same problem please feel
free to reopen the bug with relevant details.

** Changed in: mythbuntu
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1027561

Title:
  mysql doesn't start, but myth frontend & backend partially start, then
  fail when I manually start mysql

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Fix Released

Bug description:
  I upgraded to Mythbuntu 12.04 in late May (from 10.10, quickly through
  11.04 & 11.10).

  I have been using MythTV for 4 years, but this is the longest period
  that problems have persisted.

  I use a combined Myth BE & FE PC, although last week I started
  exploring (successfully) using a slave BE, but that is not in
  operation.

  A few weeks after the upgrade, mysql no longer started during the boot up process.
  The Mythfrontend first menu does not appear.

  I am an end user, so it took a while to work out the problem & how to
  work around it.

  Now, after I boot the MythPC , I use Systems Monitor to confirm which apps are running ( mythtvbackend, mythtvfrontend, mythtvfrontend.real) & that mysql is not.
  In the meantime, the system tells me that Myth apps have crashed.
  I then open a terminal & start mysql (sudo start mysql).
  After a little while the first menu screen of Myth frontend appears, but the window is locked.
  After a little while a crash notice appears & the menu disappears.
  A little while later, the menu reappears & is functional.
  Another bug report message appears.  Some of the time, I have tried to let the bug reporting system continue, but it usually fails.
  Mostly, I just disregard the crash notices, due to the frequency (multiple per boot), & the failure to continue to a report, but today I thought that I would persevere.

  If someone could tell me how to make sure that mysql would start
  during boot (I assume via upstart), it would eliminate a very
  frustrating sequence of events.  I have seen comments on the internet
  about checking /etc/init.d/mysql, but I have no idea as to what the
  script does.  Perhaps mysql does try to start, but fails, but I don't
  know how to confirm that.

  I have asked several people about upstart, but none of them have had
  any experience with it.

  If I am not home, my dear wife can't do any of the steps that I do.

  So, I do hope that one of you skilled people can make some sense of
  this.

  Regards, Garry.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: mythtv-frontend 2:0.25.1+fixes.20120715.4f6ac2a-0ubuntu0mythbuntu4
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic i686
  NonfreeKernelModules: nvidia
  .var.log.mythtv.mtd.log:
   mtd started at Sun Feb 7 06:46:24 2010
   mtd is running on a host called HTPC1
   06:46:24: Waiting for connections/jobs
   06:46:24: mtd is listening on port 2442
  .var.log.mythtv.mythavtest.log:
   
  .var.log.mythtv.mythccextractor.log:
   
  .var.log.mythtv.mythjobqueue.log:
   
  .var.log.mythtv.mythlcdserver.log:
   
  .var.log.mythtv.mythmediaserver.log:
   
  .var.log.mythtv.mythshutdown.log:
   
  .var.log.mythtv.mythtranscode.log:
   
  .var.log.mythtv.mythutil.log:
   
  .var.log.mythtv.mythwelcome.log:
   
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  CrashCounter: 1
  CrashDB: mythbuntu
  Date: Sun Jul 22 15:05:13 2012
  ExecutablePath: /usr/bin/mythfrontend.real
  Installed_mythtv_dbg: 0.0
  MythTVDirectoryPermissions: lrwxrwxrwx 1 root root 18 Nov  4  2008 /var/lib/mythtv -> /mnt/mythtv/mythtv
  ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x877830b <_ZNK14QFactoryLoader8instanceERK7QString+43>:	testb  $0x1,0x4(%edx)
   PC (0x0877830b) ok
   source "$0x1" ok
   destination "0x4(%edx)" (0x00000004) not located in a known VMA region (needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: mythtv
  StacktraceTop:
   QFactoryLoader::instance(QString const&) const () from /usr/lib/i386-linux-gnu/libQtCore.so.4
   ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
   ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
   QImageReader::read(QImage*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
   QImageReader::read() () from /usr/lib/i386-linux-gnu/libQtGui.so.4
  Title: mythfrontend.real crashed with SIGSEGV in QFactoryLoader::instance()
  UpgradeStatus: Upgraded to precise on 2012-06-13 (38 days ago)
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv nopasswdlogin plugdev video

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1027561/+subscriptions