[mythtv-users] mythweb backend status page 0.25 timing out

[Raymond Wagner]

On 2/22/2012 18:09, Dan Smith wrote:
> On Wed, Feb 22, 2012 at 2:11 PM, Raymond Wagner<raymond at wagnerrp.com>  wrote:
>> On 2/22/2012 15:43, Dan Smith wrote:
>>> On Tue, Feb 21, 2012 at 7:06 AM, Dan Smith<mrplowdan at gmail.com>    wrote:
>>>> On Tue, Feb 21, 2012 at 12:58 AM, Raymond Wagner<raymond at wagnerrp.com>    wrote:
>>>>> On 2/21/2012 03:06, Dan Smith wrote:
>>>>>> I took the plunge to try out 0.25 using mythbuntu's repo after making
>>>>>> a fresh backup. Everything seems to be working fine in mythweb except
>>>>>> for the backend status page which just times out, as well as the
>>>>>> recorded programs page which has the preview images missing.
>>>>> Is the backend actually timing out, or is this a mythweb issue?  Recall,
>>>>> the status page is not actually generated by mythweb, but is proxied
>>>>> through from the backend.  Can you access....
>>>>>
>>>>> http://<your backend IP>:6544/Status/GetStatusHTML
>>>> Your right, http://192.168.1.10:6544/Status/GetStatusHTML results in
>>>> The connection was reset
>>>> The connection to the server was reset while the page was loading.
>>>>
>>>> sshing to my server and running mythtv-status gives me
>>>> mrplow at mythtv-server:~/4nec/models/mine/91XG-mod$ mythtv-status
>>>> Sorry, failed to fetch http://localhost:6544/xml:
>>>> 500 alarm
>>>> I dpkg-reconfigured mythtv-status and changed localhost to
>>>> 192.168.1.10 which didn't help.
>>> fixed itself magically by rebooting
>> If available, I wouldn't mind seeing your backend logs from when it
>> wasn't working.  In particular, I would be interested in the first few
>> seconds worth where it's building its runtime configuration, and
>> starting up the various listen servers.
> took me a minute to realize that the logs are now in the syslog, here you go
> http://pastebin.com/6HQG7VEZ

Did you keep terminating the backend, or was there some system script 
that was doing so?  It appears upstart terminated the first instance of 
the backend.  The problem is that it didn't actually terminate it, it 
terminated some wrapper script (mythtv-backend), which closed 
immediately and left the actual running backend hanging.  With the 
wrapper gone, upstart tried to start a new instance of mythbackend, 
while the old instance was still running and listening on the HTTP 
ports, blocking the new instance from setting up its web server.