Now I'm not even sure that it's the start of a recording. Here it died
for no apparent reason:
stream: start_time: 0.289 duration: 3656.664 bitrate=6478 kb/s
2005-12-12 22:02:01.234 New DB connection, total: 3
2005-12-12 22:30:45.290 Unknown socket closing
2005-12-13 07:00:53.254 adding: mythbe01
Another update, it only seems to be unable to connect to the schedules
tables... specifically the upcoming recordings. Everything else seems
to work just fine, listings, recorded programs, job queue history,
etc.
What could possibly be going on?
On 12/11/05, Sasha Z <[EMAIL PROTECTED]> wrote:
> O
OK, it seems to really happen at two times. One right at the start of
a recording, and again at the end of (some) listings updates.
On 12/9/05, Sasha Z <[EMAIL PROTECTED]> wrote:
> Anybody have further information on this? (ie, bump)
>
> > On 12/3/05, Michael Eldridge <[EMAIL PROTECTED]> wrote:
>
Anybody have further information on this? (ie, bump)
> On 12/3/05, Michael Eldridge <[EMAIL PROTECTED]> wrote:
>
> > I have to restart the backend about once a day for things to work
> > properly. Should we open a ticket about this issue?
> >
> > On 11/28/05, Sasha Z <[EMAIL PROTECTED]> wrote:
> >
I really don't know what we would put in the ticket... backtraces and
log files aren't of much help on this one.
On 12/3/05, Michael Eldridge <[EMAIL PROTECTED]> wrote:
> I have to restart the backend about once a day for things to work
> properly. Should we open a ticket about this issue?
>
> On
Count me in as another user that's having the exact problem you're
having with mythbackend and mysql 5(.0.16 on gentoo for me).
I have to restart the backend about once a day for things to work
properly. Should we open a ticket about this issue?
On 11/28/05, Sasha Z <[EMAIL PROTECTED]> wrot
*sigh* it sounds like I might rebuild everything on my system for mysql4.
On 12/1/05, Xamindar <[EMAIL PROTECTED]> wrote:
> I have been having this problem recently as well. Only I don't have to
> restart mythbackend, I just have to wait a little while and it will come
> back. Mythfrontend on th
I have been having this problem recently as well. Only I don't have to
restart mythbackend, I just have to wait a little while and it will come
back. Mythfrontend on the otherhand needs to be restarted. I am using
mysql5 now, it didn't happen with mysql4. But then again I have
reinstalled t
I have been having this same problem for about 2 months now. I have to
restart MythBackend and everything works again for .5 day to 3 days,
then next time you go to check scheduled programs, you get nothing.
It is not necassarily after a mythfilldatabase update, as I usually
don't run mythfil
Some more information, it can't access the scheduled recordings list,
but it has no problems getting the recorded programs table. This is
seriously strange, and I have no possible explanation.
Someone... anyone... help?
On 11/28/05, Sasha Z <[EMAIL PROTECTED]> wrote:
> I seem to be losing the dat
10 matches
Mail list logo