Opened 18 years ago
Closed 17 years ago
#4129 closed defect (invalid)
mythtv trakes very long... (or recorded list is empty)
| Reported by: | markus | Owned by: | Isaac Richards |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | mythtv | Version: | unknown |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
sometimes when my backend runs for a long time and (more than two days or so) and i connect with a frontend, the recordings list is empty even if i have a lot of recordings on my disk! when i then restart the backend, and try it again, all of my recordings apeer on the frontend!
any ideas?
Change History (4)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
Can someone provide the backend output in these situations? (e.g. tail /var/log/mythtv/mythbackend.log)
comment:3 by , 18 years ago
| Status: | new → infoneeded_new |
|---|
comment:4 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | infoneeded_new → closed |
Requested information not provided.
Note:
See TracTickets
for help on using tickets.
I can confirm this at least, as it is happening to me as well. The backend, while not crashing, seems to stop responding to the frontend. If I start the backend with -v all, and then go look at the logfile once the be has gone into this state, there appears to still be some recurring activity (mostly auto-expire checking), but until the BE is restarted it will not talk to the FE. Trying http://localhost:6544/ directly gets a connection, but no response either.