Upcoming recordings not displaying unless recording in progress

[Dave Johansen]

I just updated my Mythbuntu 9.04 install a few days ago and then I noticed that nothing was showing up in my Upcoming Recordings. I assumed that something went wrong and they all were erased, but then tonight they all showed up again while it was recording 2 shows, but then they all disappeared again after the recordings were over.

[Mario Limonciello (superm1)]

Sounds like you probably dont have enough free space so they are getting
auto expired. Have you looked over mythbackend logs in /var/log/mythtv
already?

On Tue, Apr 7, 2009 at 00:02, daveisfera <email address hidden> wrote:

> Public bug reported:
>
> I just updated my Mythbuntu 9.04 install a few days ago and then I
> noticed that nothing was showing up in my Upcoming Recordings. I assumed
> that something went wrong and they all were erased, but then tonight
> they all showed up again while it was recording 2 shows, but then they
> all disappeared again after the recordings were over.
>
> ** Affects: mythbuntu
> Importance: Undecided
> Status: New
>
> --
> Upcoming recordings not displaying unless recording in progress
> https://bugs.launchpad.net/bugs/356789
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

--
Mario Limonciello
<email address hidden>

[Dave Johansen (davejohansen)]

df says that I have almost 900G available, so there should be plenty of space to record things.

Here's the last few lines of output in the mythbackend log:

2009-04-06 21:49:58.484 Scheduled 0 items in 1.1 = 1.12 match + 0.01 place
2009-04-06 21:49:58.487 Seem to be woken up by USER
2009-04-06 21:49:58.421 DB Error (StorageGroup::CheckAllStorageGroupDirs()):
Query was:
SELECT groupname, dirname FROM storagegroup WHERE hostname = 'JohansenDVR';
Driver error was [2/2006]:
QMYSQL3: Unable to execute query
Database error was:
MySQL server has gone away

2009-04-06 21:50:04.803 DB Error (Error in JobQueue::GetJobs(), Unable to query list of Jobs in Queue.):
Query was:
SELECT j.id, j.chanid, j.starttime, j.inserttime, j.type, j.cmds, j.flags, j.status, j.statustime, j.hostname, j.args, j.comment, r.endtime, j.schedruntime FROM jobqueue j, recorded r WHERE j.chanid = r.chanid AND j.starttime = r.starttime ORDER BY j.schedruntime, j.id;
Driver error was [2/2006]:
QMYSQL3: Unable to execute query
Database error was:
MySQL server has gone away

2009-04-06 21:50:31.219 MainServer::HandleAnnounce Monitor
2009-04-06 21:50:31.230 adding: JohansenDVR as a client (events: 0)
2009-04-06 21:50:31.232 MainServer::HandleAnnounce Monitor
2009-04-06 21:50:31.233 adding: JohansenDVR as a client (events: 1)
2009-04-06 21:51:14.696 AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min
2009-04-06 22:07:14.948 AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min
2009-04-06 22:22:14.993 AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min

[Mario Limonciello (superm1)]

So then that looks like possible database corruption. Repair/optimize your
tables, clean up the logs, and try again..

On Tue, Apr 7, 2009 at 00:31, daveisfera <email address hidden> wrote:

> df says that I have almost 900G available, so there should be plenty of
> space to record things.
>
> Here's the last few lines of output in the mythbackend log:
>
> 2009-04-06 21:49:58.484 Scheduled 0 items in 1.1 = 1.12 match + 0.01 place
> 2009-04-06 21:49:58.487 Seem to be woken up by USER
> 2009-04-06 21:49:58.421 DB Error
> (StorageGroup::CheckAllStorageGroupDirs()):
> Query was:
> SELECT groupname, dirname FROM storagegroup WHERE hostname = 'JohansenDVR';
> Driver error was [2/2006]:
> QMYSQL3: Unable to execute query
> Database error was:
> MySQL server has gone away
>
> 2009-04-06 21:50:04.803 DB Error (Error in JobQueue::GetJobs(), Unable to
> query list of Jobs in Queue.):
> Query was:
> SELECT j.id, j.chanid, j.starttime, j.inserttime, j.type, j.cmds, j.flags,
> j.status, j.statustime, j.hostname, j.args, j.comment, r.endtime,
> j.schedruntime FROM jobqueue j, recorded r WHERE j.chanid = r.chanid AND
> j.starttime = r.starttime ORDER BY j.schedruntime, j.id;
> Driver error was [2/2006]:
> QMYSQL3: Unable to execute query
> Database error was:
> MySQL server has gone away
>
> 2009-04-06 21:50:31.219 MainServer::HandleAnnounce Monitor
> 2009-04-06 21:50:31.230 adding: JohansenDVR as a client (events: 0)
> 2009-04-06 21:50:31.232 MainServer::HandleAnnounce Monitor
> 2009-04-06 21:50:31.233 adding: JohansenDVR as a client (events: 1)
> 2009-04-06 21:51:14.696 AutoExpire: CalcParams(): Max required Free Space:
> 1.0 GB w/freq: 15 min
> 2009-04-06 22:07:14.948 AutoExpire: CalcParams(): Max required Free Space:
> 1.0 GB w/freq: 15 min
> 2009-04-06 22:22:14.993 AutoExpire: CalcParams(): Max required Free Space:
> 1.0 GB w/freq: 15 min
>
> --
> Upcoming recordings not displaying unless recording in progress
> https://bugs.launchpad.net/bugs/356789
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

--
Mario Limonciello
<email address hidden>
Sent from Austin, Texas, United States

[Dave Johansen (davejohansen)]

I ran the mysqlcheck and the repair/optimize from the Control Center and I still have the same problem.

I have attached the backend log and it has several errors regarding database access.

[Dave Johansen (davejohansen)]

It appears that this bug actually may not be a duplicate, because after my clean install of the daily build from 4-12-09 which appears to have resolved the database connection issues ( https://bugs.launchpad.net/mythbuntu/+bug/358173/comments/9 ), I am still having the problem with my upcoming recording being empty even though there is valid data available.

I can always make the data in upcoming recording appear/show up by adding a new "dummy" recording of some random show and then going to the upcoming recordings (with the data now visible) and deleting the recording.

I currently don't see any of the database connection errors that I reported in the other bug report ( https://bugs.launchpad.net/mythbuntu/+bug/358173/comments/1 ), but I will keep my eye open.

[MarcRandolph (mrand)]

Thank you for reporting back on your issue, however we will need more information before being able to help in any way.

As a first order of business, do your frontend or backend logs show anything when you go to view the upcoming recordings (both when it shows nothing, and when it shows correctly)? Also, do the upcoming recordings show up correctly via mythweb?

[Dave Johansen (davejohansen)]

So it appears that this actually is a duplicate, because when I went to generate clean log files on a fresh restart the database connection issues appeared again and the frontend said it couldn't connect to the backend.

However, the proposed fix from the other bug report ( https://lists.ubuntu.com/archives/ubuntu-server-bugs/2009-February/009799.html which says to remove the "& wait" from the $NOHUP_NICENESS command in the /usr/bin/mysqld_safe script) seems to have fixed this issue and the root cause (the database connection errors https://bugs.launchpad.net/mythbuntu/+bug/358173) because now when I restart the backend starts up and the upcoming recordings show up.