Modify ↓
Ticket #4129 (closed defect: invalid)
Opened 5 years ago
Last modified 4 years ago
mythtv trakes very long... (or recorded list is empty)
| Reported by: | markus | Owned by: | ijr |
|---|---|---|---|
| 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?
Attachments
Change History
comment:1 Changed 5 years ago by megadave@…
comment:2 Changed 4 years ago by nigel
Can someone provide the backend output in these situations? (e.g. tail /var/log/mythtv/mythbackend.log)
comment:4 Changed 4 years ago by stuartm
- Status changed from infoneeded_new to closed
- Resolution set to invalid
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.