[mythtv-users] Scheduling new recordings requires mythtv restart

[Michael T. Dean]

On 04/22/2009 06:18 PM, Joel wrote:
>  I have been running mythfilldatabase out of cron.daily, rather than
>  having the backend call it.  If it's better to have the backend run
>  it for some reason, I can switch to that method.

I recommend switching and letting the backend call it.

>  I get emailed if
>  there is any output on stderr, and I have only occasionally seen
>  mythfilldatabase segfault, though it did it 2 days in a row earlier
>  this month.  For now, I've added -v most to mythfilldatabase and
>  redirected to a log file which I'll monitor more closely.  I ran it
>  once now, but I can't confirm whether it worked or failed since the
>  data was up to date, and I recently restarted mythbackend.  I do see
>  some error's in mythsocket as well as the message "Error rescheduling
>  id -1 in ScheduledRecording::signalChange"  I'm not sure how to
>  interpret these errors though, as it doesn't seem to match any of
>  your suggested problem.  You may look to see if you notice anything
>  odd here: http://ebel.mybox.org/mythfilldatabase.log  Or you can wait
>  until tomorrow and I'll collect a log run in a normal environment for
>  which I can confirm success or failure.


The errors you're getting are due to the socket errors.  A lot of people 
seem to get them.  I don't know that anyone knows any specific reasons 
why some people get them a lot and others don't.

> 2009-04-22 11:48:43.601 MythSocket(8187d90:-1): writeStringList: Error, called with unconnected socket.
> 2009-04-22 11:48:43.601 MythSocket(8187d90:-1): readStringList: Error, called with unconnected socket.

Those socket errors are preventing mythfilldatabase from telling 
mythbackend to run a reschedule (thus the error you quoted).  I'd ask 
other users of your distro if they've seen similar socket errors and 
whether they've found a way to fix them.

It's also possible that mythfilldatabase running in the same environment 
as your mythbackend will fix the issue--another good reason to let 
mythbackend run mythfilldatabase.

Mike