mythbuntu-bugs team mailing list archive

[Steve Netting <steve@xxxxxxxxxxxxxx>]

No longer an issue.  I don't understand what changed here - but it would
appear the master backend IP in the database (192.168.0.200) no longer
matched the IP configured in mythtv-setup (127.0.0.1).  Hence
mythbackend was assuming itself a slave.   Changed IP in mythtv-setup to
the public 192.168.0.200 address and the backend now starts without
issue.

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

Title:
  mythbackend will segfault about 10 minutes after starting. "segfault
  at 50 ip 0209d2dc sp bff215c0 error 4 in
  libQtCore.so.4.7.0[2041000+290000]"

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Invalid

Bug description:
  After performing an apt-get update && apt-get upgrade today (1/19),
  mythbackend is no longer stable. There is no exiting information
  contained in the mythbackend.log file, however there are numerous
  reports of "MainServer, Warning: Unknown socket closing MythSocket"
  and "MainServer, Error: Failed t oopen master server socket, timeout."
  The segfault is recorded in /var/log/messages as follows: "kernel:
  [10921.030926] mythbackend[5755]: segfault at 50 ip 0209d2dc sp
  bff215c0 error 4 in libQtCore.so.4.7.0[2041000+290000]"

  This issue was not present in the earlier package, which I updated to
  earlier this week when I upgraded from 10.04 to 10.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: mythtv-backend 2:0.24.0+fixes.20110119.40df4b6-0ubuntu0mythbuntu2
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  CrashDB: mythbuntu
  Date: Wed Jan 19 14:18:35 2011
  InstallationMedia: Mythbuntu 9.10 "Karmic Koala" - Release i386 (20091028.4)
  Installed_mythtv_dbg: 0.0
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mythtv