[mythtv-users] mythweb in 0.18

[James Armstrong]

Shawn Asmussen wrote:
>  
> I'm still experiencing problems in 0.18 with mythweb causing the 
> mythbackend process on my master box to die. The simplest way for me to 
> make it break, is to try and delete a recording. I deleted 5 or 6 
> programs using mythweb after upgrading to 0.18, and each attempt caused 
> the mythbackend process to die. I also made it crash once by canceling 
> an upcomping recording from the scheduled recordings page. I did once 
> successfully cancel an upcoming recording though, so that doesn't seem 
> to as reliably crash mythbackend as deleting a program, which seems to 
> kill mythbackend every single time I do it. There wasn't anything 
> helpful at all in the log file from mythbackend, so I turned on -v all 
> and tried it again, and got the output listed at the end of this 
> message. The JobQueue line is the last line that was in the log before I 
> clicked the delete button in mythweb, and the "2    -1" line is the last 
> thing in the log after mythbackend dies. I tried it a couple of times, 
> and got pretty much the same results each time. Since everywhere else 
> that there is a " 2 " as the first field after the timestamp the next 
> thing listed is 'OK', I'm guessing that the -1 is some sort of error 
> code? I'm running mythweb on a separate box than my backend/frontend 
> combo, if that makes any difference...

I have been having this for awhile. I recompiled with debug and got a 
trace but need to do it again with the latest version. The last thing in 
my log is always the RESCHEDULED -1 command. The dump showed a few 
threads dealing with delete_thread and stuff related to the show delete. 
I have a script that keeps mythbackend going but it is getting old and 
will try some more debugging this weekend.

- James