[mythtv-users] ticket 10504 and php-5.4.8-1.fc17.x86_64

Bill Meek keemllib at gmail.com
Wed Dec 5 18:15:49 UTC 2012


On 12/05/2012 11:37 AM, Udo van den Heuvel wrote:
> On 2012-12-05 17:21, Bill Meek wrote:

>> Is it possible that you were checking the another copy of the database?
>
> Another copy?
> I have just one mythconverg. (?!)

I know, sounds weird, but I was trying to
think of reasons that the settings were
visible to you in mysql, but not to the
backend.

...

> # LC_ALL=en_US.UTF-8  MYTHCONFDIR=/home/mythtv/.mythtv
> /usr/bin/mythbackend --user mythtv  --logpath /var/log/mythtv/
> --loglevel debug
> No setting found for this machine's BackendServerIP.
...
> 2012-12-05 18:34:10.142931 D  FindDatabase() - Success!
...
> 2012-12-05 18:34:10.147540 I  Loading en_us translation for module
> mythfrontend

> The ordering of the messages is weird.

Yes, but probably because the 1st from the cerr line and
the others from 'regular' logging. I'm not worried about
it, at least for now.

> First is the complaint which appears to be non-valid, then the setup of
> the backend application, connection to the database and an abrupt end.
> No mythbackend running.
> No extra debug logging.

OK, lets drop back. From a terminal, type: tailf /var/log/syslog
(or wherever your system logs are.)

Then in another terminal, fire up the backend. Does anything print
in the first window?

I'm looking for a segfault or abort, for example. In 0.26, they should
have been caught and printed, but I've seen cases where they weren't.

-- 
Bill


More information about the mythtv-users mailing list