mythweb "Forget Old" fails

For discussion of topics specific to MythTV on linux
Post Reply
wmarler
Newcomer
Posts: 3
Joined: Tue Apr 18, 2017 3:07 pm
United States of America

mythweb "Forget Old" fails

Post by wmarler » Tue Apr 18, 2017 3:50 pm

I'm having a hard time getting mythweb to schedule NHL recordings. Mythweb says that a show is marked as never to be recorded, and clicking the "Forget Old" button doesn't have any effect.

Here's a screenshot of what comes up when I search "^NHL": https://goo.gl/photos/Gjs9PbHSU71ADAqZA
The games are in the schedule, found by search, but they all have the dotted line around them, which I believe means "there's a schedule defined for this to never record this show." When I click on one I get a view like this: https://goo.gl/photos/WFB8h2n6eenwb7g5A

This is where clicking on the "Forget Old" old has no effect. Using the "Record this specific showing" button in the Schedule Override section I can override specific games to schedule them to be recorded, but that's a workaround; I want to schedule recording of all NHL games, and have them record automatically, without manual intervention.

This is the output to mysql's general_log_file when when I click on the "Forget Old" button: https://pastebin.com/ACdK1z2y
And this is what's ouput to the console from "mythtvbackend --loglevel debug" while I searched for "NHL", and tried to get the games to schedule: https://pastebin.com/BcxBGpp8

(P.S.: I don't think the errors "DVBChan[4](/dev/dvb/adapter1/frontend0): Opening DVB frontend device failed. eno: Permission denied (13)" messages here are a problem: in getting the debug level output I ran mythtvbackend in a shell in the foreground using a different user from the one in the mythtv systemd service configuration. When mythtvbackend is started via systemd, recording works fine).

I'm not sure how to proceed. Something seems broken in the database, but I'm at a loss of how to fix it : (. Can anyone offer some help?

At this point I'm leaning towards dropping the mythconverg database and creating it from scratch :-/.

Here are the package versions in play (OS is Ubuntu 17.04):
% apt-cache policy mythweb
mythweb:
Installed: 2:0.28.1+fixes.20170329.0037461-0ubuntu0mythbuntu2
Candidate: 2:0.28.1+fixes.20170329.0037461-0ubuntu0mythbuntu2
Version table:
*** 2:0.28.1+fixes.20170329.0037461-0ubuntu0mythbuntu2 100
100 /var/lib/dpkg/status
2:0.28.0+fixes.20170206.03f4403-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu zesty/multiverse amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu zesty/multiverse i386 Packages

% apt-cache policy mythtv-backend
mythtv-backend:
Installed: 2:0.28.1+fixes.20170329.0037461-0ubuntu0mythbuntu2
Candidate: 2:0.28.1+fixes.20170329.0037461-0ubuntu0mythbuntu2
Version table:
*** 2:0.28.1+fixes.20170329.0037461-0ubuntu0mythbuntu2 100
100 /var/lib/dpkg/status
2:0.28.0+fixes.20170206.03f4403-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu zesty/multiverse amd64 Packages

Thanks in advance,

User avatar
bill6502
Developer
Posts: 1374
Joined: Fri Feb 07, 2014 5:28 pm
United States of America

Re: mythweb "Forget Old" fails

Post by bill6502 » Wed Apr 19, 2017 1:03 pm

Hi,

In mythweb, go to Upcoming Recordings and check the Duplicates/Ignored box, then
see if the show you're interested in is displayed (probably with the 'Never Record' status on
the left. On the right, see if pressing 'Activate' helps. I tried it on 29-pre and it worked.

I think you're right about the permissions issue. You could add your user to the video group,
or just start the backend with --user mythtv the command line (although the log showed
... Using configuration directory = /home/mythtv/.mythtv.)

wmarler
Newcomer
Posts: 3
Joined: Tue Apr 18, 2017 3:07 pm
United States of America

Re: mythweb "Forget Old" fails

Post by wmarler » Thu Apr 20, 2017 6:22 pm

Thanks, this is what I get if I go where you suggest: https://goo.gl/photos/JK39h7wzrGPZmau26.
And it helps -- using the "Activate" button will cause the game to be marked to be recorded (note that I did that for the 1PM April 22 game). Unfortunately it doesn't affect the "Never Record" that the schedule is tagged with; as you can see, future shows that match the schedule continue to be "Never Record." The "Forget Old" button here continues to not work.

Out of curiosity, are you able to reproduce the behavior I'm describing?

I can't reproduce with another show on demand. I searched, found a show, created a schedule. Then I tried the "Never Record" button -- it had no effect. I could delete the schedule, re-create it, and the shows would all be set to record.

I posted this question on the mailing list and the only response I got was that the error messages suggested a mismatch between mythweb versions and mythtv versions. The system has been victim of some migrations ... I think it's entirely possible that I have a version mismatch, or bizarre database corruption issue that's lurking in the shadows.

Seems the most fruitful way forward might be to drop & recreate the mythconverg database. Will the mythtv-backend process make the database if it doesn't exist, or do the mythtv packages need to be completely uninstalled and reinstalled to go this route?

User avatar
dizygotheca
Developer
Posts: 266
Joined: Wed Sep 03, 2014 9:02 am
Great Britain

Re: mythweb "Forget Old" fails

Post by dizygotheca » Thu Apr 20, 2017 7:29 pm

Dropping the database won't help. MythWeb is just sending an outdated message to the backend.
There are some devs who still use MythWeb but they don't seem to be 'back' from their Easter break yet...

You could expedite a fix by capturing the errant message.

1. Turn on logging of the running backend

Code: Select all

$ mythbackend --setverbose network
2. Hit MythWeb Forget Old

3. Turn off logging

Code: Select all

$ mythbackend --setverbose general
In the backend log, you'll (hopefully) see a dump of the messages just before the 'wrong number of fields' error.
Add those lines to https://code.mythtv.org/trac/ticket/13005 (or paste them here) and we should be able to track down the issue.

wmarler
Newcomer
Posts: 3
Joined: Tue Apr 18, 2017 3:07 pm
United States of America

Re: mythweb "Forget Old" fails

Post by wmarler » Thu Apr 20, 2017 8:13 pm

Ok, here's the output for that:

Code: Select all

% Apr 20 14:04:57 ginny mythbackend: mythbackend[14184]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Playback
Apr 20 14:04:57 ginny mythbackend: mythbackend[14184]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: ginny(55e89c4aa400) as a client (events: 0)
Apr 20 14:04:57 ginny mythbackend: mythbackend[14184]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Monitor
Apr 20 14:04:57 ginny mythbackend: mythbackend[14184]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: ginny(55e89c4aaa30) as a client (events: 1)
Apr 20 14:04:57 ginny mythbackend: mythbackend[14184]: N ProcessRequest mainserver.cpp:7098 (HandleSetVerbose) MainServer: Verbose mask changed, new mask is:  general network
Apr 20 14:04:57 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:789 (WriteStringListReal) MythSocket(55e89c4aa400:76): write -> 76 2       OK
Apr 20 14:04:57 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mainserver.cpp:7656 (connectionClosed) Playback sock(55e89c4aa400) 'ginny' disconnected
Apr 20 14:04:57 ginny mythbackend: mythbackend[14184]: I MythSocketThread(83) mainserver.cpp:7656 (connectionClosed) Monitor sock(55e89c4aaa30) 'ginny' disconnected
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:990 (ReadStringListReal) MythSocket(55e89c4ad870:76): read  <- 76 19      ANN Monitor ginny 0
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Monitor
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: ginny(55e89c4ad870) as a client (events: 0)
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:789 (WriteStringListReal) MythSocket(55e89c4ad870:76): write -> 76 2       OK
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:990 (ReadStringListReal) MythSocket(55e89c4ad870:76): read  <- 76 19      QUERY_GETALLPENDING
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:789 (WriteStringListReal) MythSocket(55e89c4ad870:76): write -> 76 6605    0[]:[]14[]:[]Jeopardy![]:[][]:[][]:[]0[]:[]0[]:[]0[]:[]7514[]:[]G...
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:990 (ReadStringListReal) MythSocket(55e89c4ad870:76): read  <- 76 374     FORGET_RECORDING[]:[]NHL Hockey[]:[]Conference Quarterfinal: Team...
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: E ProcessRequest programinfo.cpp:1549 (FromStringList) ProgramInfo(): FromStringList, not enough items in list.
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:789 (WriteStringListReal) MythSocket(55e89c4ad870:76): write -> 76 1       0
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:990 (ReadStringListReal) MythSocket(55e89c4ad870:76): read  <- 76 4       DONE
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mainserver.cpp:7656 (connectionClosed) Monitor sock(55e89c4ad870) 'ginny' disconnected
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:990 (ReadStringListReal) MythSocket(55e89c4ae3b0:76): read  <- 76 19      ANN Monitor ginny 2
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Monitor
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: ginny(55e89c4ae3b0) as a client (events: 2)
Apr 20 14:05:02 ginny mythbackend: mythbackend[14184]: I MythSocketThread(76) mythsocket.cpp:789 (WriteStringListReal) MythSocket(55e89c4ae3b0:76): write -> 76 2       OK
Doesn't look like this level of logging really exposes anything more

Post Reply