Mailing List Archive

Upcoming recordings gone
I scratched my head when the six o'clock news didn't record tonight, and as
I poked around I noticed that although my recording rules are in place, in
upcoming recordings there are no rules defined. I tried restoring
yesterday's database, no joy, I ran mythfilldatabase, no joy. Any
suggestions? Maybe a clue in mythfilldatabase:

$ mythfilldatabase
2021-10-25 20:08:18.628920 C mythfilldatabase version: fixes/31
[v31.0+fixes.202108081239.5da2523154~ubuntu20.04.1] www.mythtv.org
2021-10-25 20:08:18.628940 C Qt version: compile: 5.12.8, runtime: 5.12.8
2021-10-25 20:08:18.628967 I Ubuntu 20.04.3 LTS (x86_64)
2021-10-25 20:08:18.628972 N Enabled verbose msgs: general
2021-10-25 20:08:18.628984 N Setting Log Level to LOG_INFO
2021-10-25 20:08:18.639613 I Added logging to the console
2021-10-25 20:08:18.640908 I Setup Interrupt handler
2021-10-25 20:08:18.640930 I Setup Terminated handler
2021-10-25 20:08:18.640969 I Setup Segmentation fault handler
2021-10-25 20:08:18.640991 I Setup Aborted handler
2021-10-25 20:08:18.641010 I Setup Bus error handler
2021-10-25 20:08:18.641035 I Setup Floating point exception handler
2021-10-25 20:08:18.641061 I Setup Illegal instruction handler
2021-10-25 20:08:18.641085 I Setup Real-time signal 0 handler
2021-10-25 20:08:18.641108 I Setup Hangup handler
2021-10-25 20:08:18.641365 N Using runtime prefix = /usr
2021-10-25 20:08:18.641383 N Using configuration directory =
/home/mythtv/.mythtv
2021-10-25 20:08:18.641466 I Assumed character encoding: en_CA.UTF-8
2021-10-25 20:08:18.642173 I Empty LocalHostName. This is typical.
2021-10-25 20:08:18.642189 I Using a profile name of: 'trieli' (Usually
the same as this host's name.)
2021-10-25 20:08:18.642304 I Start up testing connections. DB localhost,
BE , attempt 0, status dbAwake, Delay: 2000
2021-10-25 20:08:19.669627 N Setting QT default locale to en_CA
2021-10-25 20:08:19.669641 I Current locale en_CA
2021-10-25 20:08:19.669700 N Reading locale defaults from
/usr/share/mythtv//locales/en_ca.xml
2021-10-25 20:08:19.703312 I PowerDBus: Added UPower.Device
'/org/freedesktop/UPower/devices/keyboard_hidpp_battery_0'
2021-10-25 20:08:19.703759 I Power: On AC power
2021-10-25 20:08:19.705382 I PowerDBus: Added UPower.Device
'/org/freedesktop/UPower/devices/mouse_hidpp_battery_1'
2021-10-25 20:08:19.740054 I Power: Supported actions:
Suspend,Restart,Shutdown
2021-10-25 20:08:19.741747 I Loading en_ca translation for module
mythfrontend
2021-10-25 20:08:19.744105 I Current MythTV Schema Version (DBSchemaVer):
1361
2021-10-25 20:08:19.749410 I MythCoreContext::ConnectCommandSocket():
Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
2021-10-25 20:08:19.751137 I MythCoreContext::CheckProtoVersion(): Using
protocol version 91 BuzzOff
2021-10-25 20:08:19.751588 I Opening blocking connection to master backend
2021-10-25 20:08:19.840041 I Updating source #1 (antenna) with grabber
tv_grab_zz_sdjson_sqlite
2021-10-25 20:08:19.840725 I Found 34 channels for source 1 which use
grabber
2021-10-25 20:08:19.841425 I Starting process manager
2021-10-25 20:08:19.841512 I Starting process signal handler
2021-10-25 20:08:19.841599 I Starting IO manager (read)
2021-10-25 20:08:19.845950 I Starting IO manager (write)
2021-10-25 20:08:20.994380 I Grabber has capabilities: baseline
manualconfig preferredmethod lineups apiconfig
2021-10-25 20:08:21.745762 I Grabber prefers method: allatonce
2021-10-25 20:08:21.747173 I XMLTV config file is:
/home/mythtv/.mythtv/antenna.xmltv
2021-10-25 20:08:45.534961 I New static DB connectionChannelCon
2021-10-25 20:08:55.112082 N Unknown xmltv channel identifier:
I115172.json.schedulesdirect.org - Skipping channel.
2021-10-25 20:08:55.112375 N Unknown xmltv channel identifier:
I117254.json.schedulesdirect.org - Skipping channel.
2021-10-25 20:08:55.112651 N Unknown xmltv channel identifier:
I118798.json.schedulesdirect.org - Skipping channel.
2021-10-25 20:08:55.112922 N Unknown xmltv channel identifier:
I118833.json.schedulesdirect.org - Skipping channel.
2021-10-25 20:08:55.113205 N Unknown xmltv channel identifier:
I120307.json.schedulesdirect.org - Skipping channel.
2021-10-25 20:08:55.113482 N Unknown xmltv channel identifier:
I121357.json.schedulesdirect.org - Skipping channel.
2021-10-25 20:08:55.113756 N Unknown xmltv channel identifier:
I121455.json.schedulesdirect.org - Skipping channel.
2021-10-25 20:09:13.139854 N Unknown xmltv channel identifier:
I42612.json.schedulesdirect.org - Skipping channel.
2021-10-25 20:09:28.805836 I Updated programs: 2249 Unchanged programs:
15932
2021-10-25 20:09:29.067193 N Data fetching complete.
2021-10-25 20:09:29.067262 I Adjusting program database end times.
2021-10-25 20:09:29.067603 I 0 replacements made
2021-10-25 20:09:29.067613 I Marking generic episodes.
2021-10-25 20:09:29.196740 I Found 743
2021-10-25 20:09:29.196761 I Extending non-unique programids with multiple
parts.
2021-10-25 20:09:29.266404 I Found 0
2021-10-25 20:09:29.266419 I Fixing missing original airdates.
2021-10-25 20:09:29.547867 I Found 620 with programids
2021-10-25 20:09:29.548697 I Found 0 without programids
2021-10-25 20:09:29.548707 I Marking repeats.
2021-10-25 20:09:29.572302 I Found 601
2021-10-25 20:09:29.572317 I Unmarking new episode rebroadcast repeats.
2021-10-25 20:09:29.664654 I Found 640
2021-10-25 20:09:30.063276 I Marking episode first showings.
2021-10-25 20:09:30.745321 I Found 21102
2021-10-25 20:09:30.745338 I Marking episode last showings.
2021-10-25 20:09:31.428395 I Found 21055
2021-10-25 20:09:31.434851 I
===============================================================
| Attempting to contact the master backend for rescheduling. |
| If the master is not running, rescheduling will happen when |
| the master backend is restarted. |
===============================================================
2021-10-25 20:09:31.436318 N mythfilldatabase run complete.
2021-10-25 20:09:31.436502 I PowerDBus: Closing interfaces
2021-10-25 20:09:31.437739 I Waiting for threads to exit.
2021-10-25 20:09:31.439591 I Exiting

Why the "unknown xmlid's"? TIA Daryl
Re: Upcoming recordings gone [ In reply to ]
I don't know if this is your issue, but there is a know problem with
recordings caused by a database software change:
https://forum.mythtv.org/viewtopic.php?f=36&t=4453

On Mon, Oct 25, 2021 at 7:19 PM Daryl McDonald <darylangela@gmail.com>
wrote:

> I scratched my head when the six o'clock news didn't record tonight, and
> as I poked around I noticed that although my recording rules are in place,
> in upcoming recordings there are no rules defined. I tried restoring
> yesterday's database, no joy, I ran mythfilldatabase, no joy. Any
> suggestions? Maybe a clue in mythfilldatabase:
>
> $ mythfilldatabase
> 2021-10-25 20:08:18.628920 C mythfilldatabase version: fixes/31
> [v31.0+fixes.202108081239.5da2523154~ubuntu20.04.1] www.mythtv.org
> 2021-10-25 20:08:18.628940 C Qt version: compile: 5.12.8, runtime: 5.12.8
> 2021-10-25 20:08:18.628967 I Ubuntu 20.04.3 LTS (x86_64)
> 2021-10-25 20:08:18.628972 N Enabled verbose msgs: general
> 2021-10-25 20:08:18.628984 N Setting Log Level to LOG_INFO
> 2021-10-25 20:08:18.639613 I Added logging to the console
> 2021-10-25 20:08:18.640908 I Setup Interrupt handler
> 2021-10-25 20:08:18.640930 I Setup Terminated handler
> 2021-10-25 20:08:18.640969 I Setup Segmentation fault handler
> 2021-10-25 20:08:18.640991 I Setup Aborted handler
> 2021-10-25 20:08:18.641010 I Setup Bus error handler
> 2021-10-25 20:08:18.641035 I Setup Floating point exception handler
> 2021-10-25 20:08:18.641061 I Setup Illegal instruction handler
> 2021-10-25 20:08:18.641085 I Setup Real-time signal 0 handler
> 2021-10-25 20:08:18.641108 I Setup Hangup handler
> 2021-10-25 20:08:18.641365 N Using runtime prefix = /usr
> 2021-10-25 20:08:18.641383 N Using configuration directory =
> /home/mythtv/.mythtv
> 2021-10-25 20:08:18.641466 I Assumed character encoding: en_CA.UTF-8
> 2021-10-25 20:08:18.642173 I Empty LocalHostName. This is typical.
> 2021-10-25 20:08:18.642189 I Using a profile name of: 'trieli' (Usually
> the same as this host's name.)
> 2021-10-25 20:08:18.642304 I Start up testing connections. DB localhost,
> BE , attempt 0, status dbAwake, Delay: 2000
> 2021-10-25 20:08:19.669627 N Setting QT default locale to en_CA
> 2021-10-25 20:08:19.669641 I Current locale en_CA
> 2021-10-25 20:08:19.669700 N Reading locale defaults from
> /usr/share/mythtv//locales/en_ca.xml
> 2021-10-25 20:08:19.703312 I PowerDBus: Added UPower.Device
> '/org/freedesktop/UPower/devices/keyboard_hidpp_battery_0'
> 2021-10-25 20:08:19.703759 I Power: On AC power
> 2021-10-25 20:08:19.705382 I PowerDBus: Added UPower.Device
> '/org/freedesktop/UPower/devices/mouse_hidpp_battery_1'
> 2021-10-25 20:08:19.740054 I Power: Supported actions:
> Suspend,Restart,Shutdown
> 2021-10-25 20:08:19.741747 I Loading en_ca translation for module
> mythfrontend
> 2021-10-25 20:08:19.744105 I Current MythTV Schema Version (DBSchemaVer):
> 1361
> 2021-10-25 20:08:19.749410 I MythCoreContext::ConnectCommandSocket():
> Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
> 2021-10-25 20:08:19.751137 I MythCoreContext::CheckProtoVersion(): Using
> protocol version 91 BuzzOff
> 2021-10-25 20:08:19.751588 I Opening blocking connection to master backend
> 2021-10-25 20:08:19.840041 I Updating source #1 (antenna) with grabber
> tv_grab_zz_sdjson_sqlite
> 2021-10-25 20:08:19.840725 I Found 34 channels for source 1 which use
> grabber
> 2021-10-25 20:08:19.841425 I Starting process manager
> 2021-10-25 20:08:19.841512 I Starting process signal handler
> 2021-10-25 20:08:19.841599 I Starting IO manager (read)
> 2021-10-25 20:08:19.845950 I Starting IO manager (write)
> 2021-10-25 20:08:20.994380 I Grabber has capabilities: baseline
> manualconfig preferredmethod lineups apiconfig
> 2021-10-25 20:08:21.745762 I Grabber prefers method: allatonce
> 2021-10-25 20:08:21.747173 I XMLTV config file is:
> /home/mythtv/.mythtv/antenna.xmltv
> 2021-10-25 20:08:45.534961 I New static DB connectionChannelCon
> 2021-10-25 20:08:55.112082 N Unknown xmltv channel identifier:
> I115172.json.schedulesdirect.org - Skipping channel.
> 2021-10-25 20:08:55.112375 N Unknown xmltv channel identifier:
> I117254.json.schedulesdirect.org - Skipping channel.
> 2021-10-25 20:08:55.112651 N Unknown xmltv channel identifier:
> I118798.json.schedulesdirect.org - Skipping channel.
> 2021-10-25 20:08:55.112922 N Unknown xmltv channel identifier:
> I118833.json.schedulesdirect.org - Skipping channel.
> 2021-10-25 20:08:55.113205 N Unknown xmltv channel identifier:
> I120307.json.schedulesdirect.org - Skipping channel.
> 2021-10-25 20:08:55.113482 N Unknown xmltv channel identifier:
> I121357.json.schedulesdirect.org - Skipping channel.
> 2021-10-25 20:08:55.113756 N Unknown xmltv channel identifier:
> I121455.json.schedulesdirect.org - Skipping channel.
> 2021-10-25 20:09:13.139854 N Unknown xmltv channel identifier:
> I42612.json.schedulesdirect.org - Skipping channel.
> 2021-10-25 20:09:28.805836 I Updated programs: 2249 Unchanged programs:
> 15932
> 2021-10-25 20:09:29.067193 N Data fetching complete.
> 2021-10-25 20:09:29.067262 I Adjusting program database end times.
> 2021-10-25 20:09:29.067603 I 0 replacements made
> 2021-10-25 20:09:29.067613 I Marking generic episodes.
> 2021-10-25 20:09:29.196740 I Found 743
> 2021-10-25 20:09:29.196761 I Extending non-unique programids with
> multiple parts.
> 2021-10-25 20:09:29.266404 I Found 0
> 2021-10-25 20:09:29.266419 I Fixing missing original airdates.
> 2021-10-25 20:09:29.547867 I Found 620 with programids
> 2021-10-25 20:09:29.548697 I Found 0 without programids
> 2021-10-25 20:09:29.548707 I Marking repeats.
> 2021-10-25 20:09:29.572302 I Found 601
> 2021-10-25 20:09:29.572317 I Unmarking new episode rebroadcast repeats.
> 2021-10-25 20:09:29.664654 I Found 640
> 2021-10-25 20:09:30.063276 I Marking episode first showings.
> 2021-10-25 20:09:30.745321 I Found 21102
> 2021-10-25 20:09:30.745338 I Marking episode last showings.
> 2021-10-25 20:09:31.428395 I Found 21055
> 2021-10-25 20:09:31.434851 I
> ===============================================================
> | Attempting to contact the master backend for rescheduling. |
> | If the master is not running, rescheduling will happen when |
> | the master backend is restarted. |
> ===============================================================
> 2021-10-25 20:09:31.436318 N mythfilldatabase run complete.
> 2021-10-25 20:09:31.436502 I PowerDBus: Closing interfaces
> 2021-10-25 20:09:31.437739 I Waiting for threads to exit.
> 2021-10-25 20:09:31.439591 I Exiting
>
> Why the "unknown xmlid's"? TIA Daryl
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
Re: Upcoming recordings gone [ In reply to ]
On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:

>I don't know if this is your issue, but there is a know problem with
>recordings caused by a database software change:
>https://forum.mythtv.org/viewtopic.php?f=36&t=4453
>

That problem was fixed a while ago, but only if you keep your system
and MythTV up to date.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
I update and upgrade regularly

On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <
stephen_agent@jsw.gen.nz> wrote:

> On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
>
> >I don't know if this is your issue, but there is a know problem with
> >recordings caused by a database software change:
> >https://forum.mythtv.org/viewtopic.php?f=36&t=4453
> >
>
> That problem was fixed a while ago, but only if you keep your system
> and MythTV up to date.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
Re: Upcoming recordings gone [ In reply to ]
On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <darylangela@gmail.com>
wrote:

> I update and upgrade regularly
>
> On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <
> stephen_agent@jsw.gen.nz> wrote:
>
>> On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
>>
>> >I don't know if this is your issue, but there is a know problem with
>> >recordings caused by a database software change:
>> >https://forum.mythtv.org/viewtopic.php?f=36&t=4453
>> >
>>
>> That problem was fixed a while ago, but only if you keep your system
>> and MythTV up to date.
>>
>>
It's different than that, when I look in upcoming recordings, it says "you
have not scheduled any recordings" when I look in recording rules I can see
them all, when I look in info I see 49 rules and two templates. when I try
to schedule a recording from the grid all the correct things show until I
hit enter, then no icon on the show that it will record. I can go through
the motions but the system will not take a new recording. Maybe the
scheduler is broken?
Re: Upcoming recordings gone [ In reply to ]
On Tue, 26 Oct 2021 12:40:39 -0400, you wrote:

>On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <darylangela@gmail.com>
>wrote:
>
>> I update and upgrade regularly
>>
>> On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <
>> stephen_agent@jsw.gen.nz> wrote:
>>
>>> On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
>>>
>>> >I don't know if this is your issue, but there is a know problem with
>>> >recordings caused by a database software change:
>>> >https://forum.mythtv.org/viewtopic.php?f=36&t=4453
>>> >
>>>
>>> That problem was fixed a while ago, but only if you keep your system
>>> and MythTV up to date.
>>>
>>>
>It's different than that, when I look in upcoming recordings, it says "you
>have not scheduled any recordings" when I look in recording rules I can see
>them all, when I look in info I see 49 rules and two templates. when I try
>to schedule a recording from the grid all the correct things show until I
>hit enter, then no icon on the show that it will record. I can go through
>the motions but the system will not take a new recording. Maybe the
>scheduler is broken?

That happens when you try to schedule something that is in the past.
Check if you have got EPG data showing for any future time for that
channel. I suspect that you will only have past data as new EPG data
is not being read into the database properly. The messages like:

Unknown xmltv channel identifier: I115172.json.schedulesdirect.org -
Skipping channel

mean that those channels will not be getting any new data until your
channel database has the same xmltvid value as the SchedulesDirect
download. This line:

Updated programs: 2249 Unchanged programs: 15932

says that some other channels are getting new EPG data as there were
2249 new or updated programmes.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Tue, Oct 26, 2021 at 12:19 AM Daryl McDonald <darylangela@gmail.com> wrote:

> Why the "unknown xmlid's"? TIA Daryl

Previously answered a few years ago, so
you can find the answer in the archives.

For those that are unable to remember,
or do not know how to use a web search
engine, the quick summary is that if one
is in a US OTA market which has RF
translators and are using Schedules
Direct as the data source there is nothing
to see here, move along.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Tue, Oct 26, 2021 at 1:06 PM Stephen Worthington <
stephen_agent@jsw.gen.nz> wrote:

> On Tue, 26 Oct 2021 12:40:39 -0400, you wrote:
>
> >On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <darylangela@gmail.com>
> >wrote:
> >
> >> I update and upgrade regularly
> >>
> >> On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <
> >> stephen_agent@jsw.gen.nz> wrote:
> >>
> >>> On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
> >>>
> >>> >I don't know if this is your issue, but there is a know problem with
> >>> >recordings caused by a database software change:
> >>> >https://forum.mythtv.org/viewtopic.php?f=36&t=4453
> >>> >
> >>>
> >>> That problem was fixed a while ago, but only if you keep your system
> >>> and MythTV up to date.
> >>>
> >>>
> >It's different than that, when I look in upcoming recordings, it says "you
> >have not scheduled any recordings" when I look in recording rules I can
> see
> >them all, when I look in info I see 49 rules and two templates. when I try
> >to schedule a recording from the grid all the correct things show until I
> >hit enter, then no icon on the show that it will record. I can go through
> >the motions but the system will not take a new recording. Maybe the
> >scheduler is broken?
>
> That happens when you try to schedule something that is in the past.
> Check if you have got EPG data showing for any future time for that
> channel. I suspect that you will only have past data as new EPG data
> is not being read into the database properly. The messages like:
>
> Unknown xmltv channel identifier: I115172.json.schedulesdirect.org -
> Skipping channel
>
> mean that those channels will not be getting any new data until your
> channel database has the same xmltvid value as the SchedulesDirect
> download. This line:
>
> Updated programs: 2249 Unchanged programs: 15932
>
> says that some other channels are getting new EPG data as there were
> 2249 new or updated programmes.
>
>
I show guide data until Friday Nov. 12th
Re: Upcoming recordings gone [ In reply to ]
On 10/26/21 11:40 AM, Daryl McDonald wrote:
>
>
> On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <darylangela@gmail.com <mailto:darylangela@gmail.com>> wrote:
>
> I update and upgrade regularly
>
> On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>> wrote:
>
> On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
>
> >I don't know if this is your issue, but there is a know problem with
> >recordings caused by a database software change:
> >https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> >
>
> That problem was fixed a while ago, but only if you keep your system
> and MythTV up to date.
>
>
> It's different than that, when I look in upcoming recordings, it says "you have not scheduled any recordings" when I look in recording rules I
> can see them all, when I look in info I see 49 rules and two templates. when I try to schedule a recording from the grid all the correct things
> show until I hit enter, then no icon on the show that it will record. I can go through the motions but the system will not take a new recording.
> Maybe the scheduler is broken?
Can you watch LiveTV, proving that one or more of your tuners
are available?

This may help: mythbackend --printsched (put the output at pastebin.com please,
it can be long).

IF the above don't show any clues:

curl --header Accept:application/json --silent localhost:6544/Dvr/GetRecordScheduleList | jsonlint --format --nonstrict

You'll probably need to do: sudo apt install jsonlint python3-demjson
first. Also needs to go in a pastebin.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Tue, Oct 26, 2021 at 2:22 PM Bill Meek <keemllib@gmail.com> wrote:

> On 10/26/21 11:40 AM, Daryl McDonald wrote:
> >
> >
> > On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <darylangela@gmail.com
> <mailto:darylangela@gmail.com>> wrote:
> >
> > I update and upgrade regularly
> >
> > On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <
> stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>> wrote:
> >
> > On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
> >
> > >I don't know if this is your issue, but there is a know problem
> with
> > >recordings caused by a database software change:
> > >https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <
> https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> > >
> >
> > That problem was fixed a while ago, but only if you keep your
> system
> > and MythTV up to date.
> >
> >
> > It's different than that, when I look in upcoming recordings, it says
> "you have not scheduled any recordings" when I look in recording rules I
> > can see them all, when I look in info I see 49 rules and two templates.
> when I try to schedule a recording from the grid all the correct things
> > show until I hit enter, then no icon on the show that it will record. I
> can go through the motions but the system will not take a new recording.
> > Maybe the scheduler is broken?
> Can you watch LiveTV, proving that one or more of your tuners
> are available?
>
Yes I can watch live TV

>
> This may help: mythbackend --printsched (put the output at pastebin.com
> please,
> it can be long).
>
https://paste.ubuntu.com/p/zXTnrd9swf/

>
> IF the above don't show any clues:
>
> curl --header Accept:application/json --silent
> localhost:6544/Dvr/GetRecordScheduleList | jsonlint --format --nonstrict
>
> You'll probably need to do: sudo apt install jsonlint python3-demjson
> first. Also needs to go in a pastebin.
>
https://paste.ubuntu.com/p/cGJMVRrPMH/

>
> --
> Bill
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
Re: Upcoming recordings gone [ In reply to ]
On 10/26/21 1:28 PM, Daryl McDonald wrote:
>
>
> On Tue, Oct 26, 2021 at 2:22 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com>> wrote:
>
> On 10/26/21 11:40 AM, Daryl McDonald wrote:
> >
> >
> > On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <darylangela@gmail.com <mailto:darylangela@gmail.com> <mailto:darylangela@gmail.com
> <mailto:darylangela@gmail.com>>> wrote:
> >
> >     I update and upgrade regularly
> >
> >     On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>
> <mailto:stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>>> wrote:
> >
> >         On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
> >
> >         >I don't know if this is your issue, but there is a know problem with
> >         >recordings caused by a database software change:
> >         >https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>
> >         >
> >
> >         That problem was fixed a while ago, but only if you keep your system
> >         and MythTV up to date.
> >
> >
> > It's different than that, when I look in upcoming recordings, it says "you have not scheduled any recordings" when I look in recording rules I
> > can see them all, when I look in info I see 49 rules and two templates. when I try to schedule a recording from the grid all the correct
> things
> > show until I hit enter, then no icon on the show that it will record. I can go through the motions but the system will not take a new
> recording.
> > Maybe the scheduler is broken?
> Can you watch LiveTV, proving that one or more of your tuners
> are available?
>
> Yes I can watch live TV 
>
>
> This may help: mythbackend --printsched (put the output at pastebin.com <http://pastebin.com> please,
> it can be long).
>
>  https://paste.ubuntu.com/p/zXTnrd9swf/ <https://paste.ubuntu.com/p/zXTnrd9swf/>
>
>
> IF the above don't show any clues:
>
> curl --header Accept:application/json --silent localhost:6544/Dvr/GetRecordScheduleList | jsonlint --format --nonstrict
>
> You'll probably need to do: sudo apt install jsonlint python3-demjson
> first. Also needs to go in a pastebin.
>
>  https://paste.ubuntu.com/p/cGJMVRrPMH/ <https://paste.ubuntu.com/p/cGJMVRrPMH/>

https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776

If you just posted on the forum, can you do these two queries:

SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0 ORDER BY cardid;

SELECT chanid,recpriority FROM channel WHERE recpriority != 0 ORDER BY chanid;

If that wasn't you, a fresh backend log may help. Not the entire file, just from
the last line that contains: mythbackend version: master [v31

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Wed, Oct 27, 2021 at 6:43 AM Daryl McDonald <darylangela@gmail.com>
wrote:

>
>
> On Tue, Oct 26, 2021 at 10:48 PM Bill Meek <keemllib@gmail.com> wrote:
>
>> On 10/26/21 1:28 PM, Daryl McDonald wrote:
>> >
>> >
>> > On Tue, Oct 26, 2021 at 2:22 PM Bill Meek <keemllib@gmail.com <mailto:
>> keemllib@gmail.com>> wrote:
>> >
>> > On 10/26/21 11:40 AM, Daryl McDonald wrote:
>> > >
>> > >
>> > > On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <
>> darylangela@gmail.com <mailto:darylangela@gmail.com> <mailto:
>> darylangela@gmail.com
>> > <mailto:darylangela@gmail.com>>> wrote:
>> > >
>> > > I update and upgrade regularly
>> > >
>> > > On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <
>> stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>
>> > <mailto:stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>>>
>> wrote:
>> > >
>> > > On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
>> > >
>> > > >I don't know if this is your issue, but there is a know
>> problem with
>> > > >recordings caused by a database software change:
>> > > >https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <
>> https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
>> > <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <
>> https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>
>> > > >
>> > >
>> > > That problem was fixed a while ago, but only if you keep
>> your system
>> > > and MythTV up to date.
>> > >
>> > >
>> > > It's different than that, when I look in upcoming recordings, it
>> says "you have not scheduled any recordings" when I look in recording rules
>> I
>> > > can see them all, when I look in info I see 49 rules and two
>> templates. when I try to schedule a recording from the grid all the correct
>> > things
>> > > show until I hit enter, then no icon on the show that it will
>> record. I can go through the motions but the system will not take a new
>> > recording.
>> > > Maybe the scheduler is broken?
>> > Can you watch LiveTV, proving that one or more of your tuners
>> > are available?
>> >
>> > Yes I can watch live TV
>> >
>> >
>> > This may help: mythbackend --printsched (put the output at
>> pastebin.com <http://pastebin.com> please,
>> > it can be long).
>> >
>> > https://paste.ubuntu.com/p/zXTnrd9swf/ <
>> https://paste.ubuntu.com/p/zXTnrd9swf/>
>> >
>> >
>> > IF the above don't show any clues:
>> >
>> > curl --header Accept:application/json --silent
>> localhost:6544/Dvr/GetRecordScheduleList | jsonlint --format --nonstrict
>> >
>> > You'll probably need to do: sudo apt install jsonlint
>> python3-demjson
>> > first. Also needs to go in a pastebin.
>> >
>> > https://paste.ubuntu.com/p/cGJMVRrPMH/ <
>> https://paste.ubuntu.com/p/cGJMVRrPMH/>
>>
>> https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776
>>
>> If you just posted on the forum, can you do these two queries:
>>
> It was not I
>
>>
>> SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0 ORDER
>> BY cardid;
>>
>> SELECT chanid,recpriority FROM channel WHERE recpriority != 0 ORDER BY
>> chanid;
>>
>> If that wasn't you, a fresh backend log may help. Not the entire file,
>> just from
>> the last line that contains: mythbackend version: master [v31
>>
> I don't know how to post a log from a certain point, and shortlog only
> goes back to the 27th whereas my system worked on the 24th but not the
> 25th. so here is a short log:
> https://paste.ubuntu.com/p/swcPMBg6Rd/
> and here is a log from the 24th on:
>
It might be the same situation though:

>
>> mysql> SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0
>> ORDER BY cardid;
>> Empty set (0.00 sec)
>>
>> mysql> SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0
>> ORDER BY cardid;
>> Empty set (0.00 sec)
>>
>> mysql> SELECT chanid,recpriority FROM channel WHERE recpriority != 0
>> ORDER BY chanid;
>> +--------+-------------+
>> | chanid | recpriority |
>> +--------+-------------+
>> | 1061 | -3 |
>> | 1161 | -2 |
>> | 1171 | -1 |
>> | 1301 | -5 |
>> +--------+-------------+
>> 4 rows in set (0.00 sec)
>>
>>
Re: Upcoming recordings gone [ In reply to ]
On 10/27/21 6:01 AM, Daryl McDonald wrote:
>
>
> On Wed, Oct 27, 2021 at 6:43 AM Daryl McDonald <darylangela@gmail.com <mailto:darylangela@gmail.com>> wrote:
>
>
>
> On Tue, Oct 26, 2021 at 10:48 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com>> wrote:
>
> On 10/26/21 1:28 PM, Daryl McDonald wrote:
> >
> >
> > On Tue, Oct 26, 2021 at 2:22 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> <mailto:keemllib@gmail.com>>> wrote:
> >
> >     On 10/26/21 11:40 AM, Daryl McDonald wrote:
> >     >
> >     >
> >     > On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <darylangela@gmail.com <mailto:darylangela@gmail.com>
> <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com>> <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com>
> >     <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com>>>> wrote:
> >     >
> >     >     I update and upgrade regularly
> >     >
> >     >     On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>
> <mailto:stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>>
> >     <mailto:stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz> <mailto:stephen_agent@jsw.gen.nz
> <mailto:stephen_agent@jsw.gen.nz>>>> wrote:
> >     >
> >     >         On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
> >     >
> >     >         >I don't know if this is your issue, but there is a know problem with
> >     >         >recordings caused by a database software change:
> >     >         >https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>
> >     <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>>
> >     >         >
> >     >
> >     >         That problem was fixed a while ago, but only if you keep your system
> >     >         and MythTV up to date.
> >     >
> >     >
> >     > It's different than that, when I look in upcoming recordings, it says "you have not scheduled any recordings" when I look in
> recording rules I
> >     > can see them all, when I look in info I see 49 rules and two templates. when I try to schedule a recording from the grid all the
> correct
> >     things
> >     > show until I hit enter, then no icon on the show that it will record. I can go through the motions but the system will not take
> a new
> >     recording.
> >     > Maybe the scheduler is broken?
> >     Can you watch LiveTV, proving that one or more of your tuners
> >     are available?
> >
> > Yes I can watch live TV 
> >
> >
> >     This may help: mythbackend --printsched (put the output at pastebin.com <http://pastebin.com> <http://pastebin.com
> <http://pastebin.com>> please,
> >     it can be long).
> >
> >  https://paste.ubuntu.com/p/zXTnrd9swf/ <https://paste.ubuntu.com/p/zXTnrd9swf/> <https://paste.ubuntu.com/p/zXTnrd9swf/
> <https://paste.ubuntu.com/p/zXTnrd9swf/>>
> >
> >
> >     IF the above don't show any clues:
> >
> >     curl --header Accept:application/json --silent localhost:6544/Dvr/GetRecordScheduleList | jsonlint --format --nonstrict
> >
> >     You'll probably need to do: sudo apt install jsonlint python3-demjson
> >     first. Also needs to go in a pastebin.
> >
> >  https://paste.ubuntu.com/p/cGJMVRrPMH/ <https://paste.ubuntu.com/p/cGJMVRrPMH/> <https://paste.ubuntu.com/p/cGJMVRrPMH/
> <https://paste.ubuntu.com/p/cGJMVRrPMH/>>
>
> https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776 <https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776>
>
> If you just posted on the forum, can you do these two queries:
>
> It was not I 
>
>
>   SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0 ORDER BY cardid;
>
>   SELECT chanid,recpriority FROM channel WHERE recpriority != 0 ORDER BY chanid;
>
> If that wasn't you, a fresh backend log may help. Not the entire file, just from
> the last line that contains:  mythbackend version: master [v31
>
> I don't know how to post a log from a certain point, and shortlog only goes back to the 27th whereas my system worked on the 24th but not
> the 25th. so here is a short log:
> https://paste.ubuntu.com/p/swcPMBg6Rd/ <https://paste.ubuntu.com/p/swcPMBg6Rd/>
> and here is a log from the 24th on:
>
>  It might be the same situation though:
>
>
> mysql> SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0 ORDER BY cardid;
> Empty set (0.00 sec)
>
> mysql> SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0 ORDER BY cardid;
> Empty set (0.00 sec)
>
> mysql> SELECT chanid,recpriority FROM channel WHERE recpriority != 0 ORDER BY chanid;
> +--------+-------------+
> | chanid | recpriority |
> +--------+-------------+
> |   1061 |          -3 |
> |   1161 |          -2 |
> |   1171 |          -1 |
> |   1301 |          -5 |
> +--------+-------------+
> 4 rows in set (0.00 sec)

You can follow this on: https://forum.mythtv.org/viewtopic.php?f=36&t=4628

You'll see that a single negative recpriority will cause the SQL error pasted
earlier. The issue is still open

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
Thanks Bill, halfway there, I was able to neutralize the priority factor on
two of the four that showed from the query. The other two do not show up in
frontend settings because I deleted those channels. How would I go about
making that change from mysql?

On Wed, Oct 27, 2021 at 9:30 PM Bill Meek <keemllib@gmail.com> wrote:

> On 10/27/21 6:01 AM, Daryl McDonald wrote:
> >
> >
> > On Wed, Oct 27, 2021 at 6:43 AM Daryl McDonald <darylangela@gmail.com
> <mailto:darylangela@gmail.com>> wrote:
> >
> >
> >
> > On Tue, Oct 26, 2021 at 10:48 PM Bill Meek <keemllib@gmail.com
> <mailto:keemllib@gmail.com>> wrote:
> >
> > On 10/26/21 1:28 PM, Daryl McDonald wrote:
> > >
> > >
> > > On Tue, Oct 26, 2021 at 2:22 PM Bill Meek <keemllib@gmail.com
> <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> > <mailto:keemllib@gmail.com>>> wrote:
> > >
> > > On 10/26/21 11:40 AM, Daryl McDonald wrote:
> > > >
> > > >
> > > > On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <
> darylangela@gmail.com <mailto:darylangela@gmail.com>
> > <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com>>
> <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com>
> > > <mailto:darylangela@gmail.com <mailto:
> darylangela@gmail.com>>>> wrote:
> > > >
> > > > I update and upgrade regularly
> > > >
> > > > On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <
> stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>
> > <mailto:stephen_agent@jsw.gen.nz <mailto:
> stephen_agent@jsw.gen.nz>>
> > > <mailto:stephen_agent@jsw.gen.nz <mailto:
> stephen_agent@jsw.gen.nz> <mailto:stephen_agent@jsw.gen.nz
> > <mailto:stephen_agent@jsw.gen.nz>>>> wrote:
> > > >
> > > > On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
> > > >
> > > > >I don't know if this is your issue, but there
> is a know problem with
> > > > >recordings caused by a database software change:
> > > > >
> https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <
> https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> > <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <
> https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>
> > > <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <
> https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> > <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <
> https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>>
> > > > >
> > > >
> > > > That problem was fixed a while ago, but only if
> you keep your system
> > > > and MythTV up to date.
> > > >
> > > >
> > > > It's different than that, when I look in upcoming
> recordings, it says "you have not scheduled any recordings" when I look in
> > recording rules I
> > > > can see them all, when I look in info I see 49 rules and
> two templates. when I try to schedule a recording from the grid all the
> > correct
> > > things
> > > > show until I hit enter, then no icon on the show that it
> will record. I can go through the motions but the system will not take
> > a new
> > > recording.
> > > > Maybe the scheduler is broken?
> > > Can you watch LiveTV, proving that one or more of your
> tuners
> > > are available?
> > >
> > > Yes I can watch live TV
> > >
> > >
> > > This may help: mythbackend --printsched (put the output at
> pastebin.com <http://pastebin.com> <http://pastebin.com
> > <http://pastebin.com>> please,
> > > it can be long).
> > >
> > > https://paste.ubuntu.com/p/zXTnrd9swf/ <
> https://paste.ubuntu.com/p/zXTnrd9swf/> <
> https://paste.ubuntu.com/p/zXTnrd9swf/
> > <https://paste.ubuntu.com/p/zXTnrd9swf/>>
> > >
> > >
> > > IF the above don't show any clues:
> > >
> > > curl --header Accept:application/json --silent
> localhost:6544/Dvr/GetRecordScheduleList | jsonlint --format --nonstrict
> > >
> > > You'll probably need to do: sudo apt install jsonlint
> python3-demjson
> > > first. Also needs to go in a pastebin.
> > >
> > > https://paste.ubuntu.com/p/cGJMVRrPMH/ <
> https://paste.ubuntu.com/p/cGJMVRrPMH/> <
> https://paste.ubuntu.com/p/cGJMVRrPMH/
> > <https://paste.ubuntu.com/p/cGJMVRrPMH/>>
> >
> >
> https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776 <
> https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776>
> >
> > If you just posted on the forum, can you do these two queries:
> >
> > It was not I
> >
> >
> > SELECT cardid,recpriority FROM capturecard WHERE recpriority
> != 0 ORDER BY cardid;
> >
> > SELECT chanid,recpriority FROM channel WHERE recpriority != 0
> ORDER BY chanid;
> >
> > If that wasn't you, a fresh backend log may help. Not the entire
> file, just from
> > the last line that contains: mythbackend version: master [v31
> >
> > I don't know how to post a log from a certain point, and shortlog
> only goes back to the 27th whereas my system worked on the 24th but not
> > the 25th. so here is a short log:
> > https://paste.ubuntu.com/p/swcPMBg6Rd/ <
> https://paste.ubuntu.com/p/swcPMBg6Rd/>
> > and here is a log from the 24th on:
> >
> > It might be the same situation though:
> >
> >
> > mysql> SELECT cardid,recpriority FROM capturecard WHERE
> recpriority != 0 ORDER BY cardid;
> > Empty set (0.00 sec)
> >
> > mysql> SELECT cardid,recpriority FROM capturecard WHERE
> recpriority != 0 ORDER BY cardid;
> > Empty set (0.00 sec)
> >
> > mysql> SELECT chanid,recpriority FROM channel WHERE recpriority
> != 0 ORDER BY chanid;
> > +--------+-------------+
> > | chanid | recpriority |
> > +--------+-------------+
> > | 1061 | -3 |
> > | 1161 | -2 |
> > | 1171 | -1 |
> > | 1301 | -5 |
> > +--------+-------------+
> > 4 rows in set (0.00 sec)
>
> You can follow this on: https://forum.mythtv.org/viewtopic.php?f=36&t=4628
>
> You'll see that a single negative recpriority will cause the SQL error
> pasted
> earlier. The issue is still open
>
> --
> Bill
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
Re: Upcoming recordings gone [ In reply to ]
> On Wed, Oct 27, 2021 at 9:30 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com>> wrote:
>
> On 10/27/21 6:01 AM, Daryl McDonald wrote:
> >
> >
> > On Wed, Oct 27, 2021 at 6:43 AM Daryl McDonald <darylangela@gmail.com <mailto:darylangela@gmail.com> <mailto:darylangela@gmail.com
> <mailto:darylangela@gmail.com>>> wrote:
> >
> >
> >
> >     On Tue, Oct 26, 2021 at 10:48 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> <mailto:keemllib@gmail.com>>> wrote:
> >
> >         On 10/26/21 1:28 PM, Daryl McDonald wrote:
> >         >
> >         >
> >         > On Tue, Oct 26, 2021 at 2:22 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> <mailto:keemllib@gmail.com>> <mailto:keemllib@gmail.com <mailto:keemllib@gmail.com>
> >         <mailto:keemllib@gmail.com <mailto:keemllib@gmail.com>>>> wrote:
> >         >
> >         >     On 10/26/21 11:40 AM, Daryl McDonald wrote:
> >         >     >
> >         >     >
> >         >     > On Tue, Oct 26, 2021 at 12:34 PM Daryl McDonald <darylangela@gmail.com <mailto:darylangela@gmail.com>
> <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com>>
> >         <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com> <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com>>>
> <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com> <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com>>
> >         >     <mailto:darylangela@gmail.com <mailto:darylangela@gmail.com> <mailto:darylangela@gmail.com
> <mailto:darylangela@gmail.com>>>>> wrote:
> >         >     >
> >         >     >     I update and upgrade regularly
> >         >     >
> >         >     >     On Tue, Oct 26, 2021 at 8:59 AM Stephen Worthington <stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>
> <mailto:stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>>
> >         <mailto:stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz> <mailto:stephen_agent@jsw.gen.nz
> <mailto:stephen_agent@jsw.gen.nz>>>
> >         >     <mailto:stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz> <mailto:stephen_agent@jsw.gen.nz
> <mailto:stephen_agent@jsw.gen.nz>> <mailto:stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>
> >         <mailto:stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>>>>> wrote:
> >         >     >
> >         >     >         On Tue, 26 Oct 2021 07:45:34 -0500, you wrote:
> >         >     >
> >         >     >         >I don't know if this is your issue, but there is a know problem with
> >         >     >         >recordings caused by a database software change:
> >         >     >         >https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>
> >         <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>>
> >         >     <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>
> >         <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4453 <https://forum.mythtv.org/viewtopic.php?f=36&t=4453>>>>
> >         >     >         >
> >         >     >
> >         >     >         That problem was fixed a while ago, but only if you keep your system
> >         >     >         and MythTV up to date.
> >         >     >
> >         >     >
> >         >     > It's different than that, when I look in upcoming recordings, it says "you have not scheduled any recordings" when I look in
> >         recording rules I
> >         >     > can see them all, when I look in info I see 49 rules and two templates. when I try to schedule a recording from the grid
> all the
> >         correct
> >         >     things
> >         >     > show until I hit enter, then no icon on the show that it will record. I can go through the motions but the system will not
> take
> >         a new
> >         >     recording.
> >         >     > Maybe the scheduler is broken?
> >         >     Can you watch LiveTV, proving that one or more of your tuners
> >         >     are available?
> >         >
> >         > Yes I can watch live TV 
> >         >
> >         >
> >         >     This may help: mythbackend --printsched (put the output at pastebin.com <http://pastebin.com> <http://pastebin.com
> <http://pastebin.com>> <http://pastebin.com <http://pastebin.com>
> >         <http://pastebin.com <http://pastebin.com>>> please,
> >         >     it can be long).
> >         >
> >         >  https://paste.ubuntu.com/p/zXTnrd9swf/ <https://paste.ubuntu.com/p/zXTnrd9swf/> <https://paste.ubuntu.com/p/zXTnrd9swf/
> <https://paste.ubuntu.com/p/zXTnrd9swf/>> <https://paste.ubuntu.com/p/zXTnrd9swf/ <https://paste.ubuntu.com/p/zXTnrd9swf/>
> >         <https://paste.ubuntu.com/p/zXTnrd9swf/ <https://paste.ubuntu.com/p/zXTnrd9swf/>>>
> >         >
> >         >
> >         >     IF the above don't show any clues:
> >         >
> >         >     curl --header Accept:application/json --silent localhost:6544/Dvr/GetRecordScheduleList | jsonlint --format --nonstrict
> >         >
> >         >     You'll probably need to do: sudo apt install jsonlint python3-demjson
> >         >     first. Also needs to go in a pastebin.
> >         >
> >         >  https://paste.ubuntu.com/p/cGJMVRrPMH/ <https://paste.ubuntu.com/p/cGJMVRrPMH/> <https://paste.ubuntu.com/p/cGJMVRrPMH/
> <https://paste.ubuntu.com/p/cGJMVRrPMH/>> <https://paste.ubuntu.com/p/cGJMVRrPMH/ <https://paste.ubuntu.com/p/cGJMVRrPMH/>
> >         <https://paste.ubuntu.com/p/cGJMVRrPMH/ <https://paste.ubuntu.com/p/cGJMVRrPMH/>>>
> >
> >         https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776> <https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4628&p=22776#p22776>>
> >
> >         If you just posted on the forum, can you do these two queries:
> >
> >     It was not I 
> >
> >
> >           SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0 ORDER BY cardid;
> >
> >           SELECT chanid,recpriority FROM channel WHERE recpriority != 0 ORDER BY chanid;
> >
> >         If that wasn't you, a fresh backend log may help. Not the entire file, just from
> >         the last line that contains:  mythbackend version: master [v31
> >
> >     I don't know how to post a log from a certain point, and shortlog only goes back to the 27th whereas my system worked on the 24th but not
> >     the 25th. so here is a short log:
> >     https://paste.ubuntu.com/p/swcPMBg6Rd/ <https://paste.ubuntu.com/p/swcPMBg6Rd/> <https://paste.ubuntu.com/p/swcPMBg6Rd/
> <https://paste.ubuntu.com/p/swcPMBg6Rd/>>
> >     and here is a log from the 24th on:
> >
> >  It might be the same situation though:
> >
> >
> >         mysql> SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0 ORDER BY cardid;
> >         Empty set (0.00 sec)
> >
> >         mysql> SELECT cardid,recpriority FROM capturecard WHERE recpriority != 0 ORDER BY cardid;
> >         Empty set (0.00 sec)
> >
> >         mysql> SELECT chanid,recpriority FROM channel WHERE recpriority != 0 ORDER BY chanid;
> >         +--------+-------------+
> >         | chanid | recpriority |
> >         +--------+-------------+
> >         |   1061 |          -3 |
> >         |   1161 |          -2 |
> >         |   1171 |          -1 |
> >         |   1301 |          -5 |
> >         +--------+-------------+
> >         4 rows in set (0.00 sec)
>
> You can follow this on: https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <https://forum.mythtv.org/viewtopic.php?f=36&t=4628>
>
> You'll see that a single negative recpriority will cause the SQL error pasted
> earlier. The issue is still open
On 10/28/21 6:08 AM, Daryl McDonald wrote:
> Thanks Bill, halfway there, I was able to neutralize the priority factor on two of the four that showed from the query. The other two do not
> show up in frontend settings because I deleted those channels. How would I go about making that change from mysql?

This is a safe way, just change the chanid:

mysql --user=mythtv --password --execute="UPDATE channel SET recpriority=0 WHERE chanid=98765 LIMIT 1" mythconverg

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
>
> > >
> > > mysql> SELECT chanid,recpriority FROM channel WHERE
> recpriority != 0 ORDER BY chanid;
> > > +--------+-------------+
> > > | chanid | recpriority |
> > > +--------+-------------+
> > > | 1061 | -3 |
> > > | 1161 | -2 |
> > > | 1171 | -1 |
> > > | 1301 | -5 |
> > > +--------+-------------+
> > > 4 rows in set (0.00 sec)
> >
> > You can follow this on:
> https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <
> https://forum.mythtv.org/viewtopic.php?f=36&t=4628>
> >
> > You'll see that a single negative recpriority will cause the SQL
> error pasted
> > earlier. The issue is still open
> On 10/28/21 6:08 AM, Daryl McDonald wrote:
> > Thanks Bill, halfway there, I was able to neutralize the priority factor
> on two of the four that showed from the query. The other two do not
> > show up in frontend settings because I deleted those channels. How would
> I go about making that change from mysql?
>
> This is a safe way, just change the chanid:
>
> mysql --user=mythtv --password --execute="UPDATE channel SET
> recpriority=0 WHERE chanid=98765 LIMIT 1" mythconverg
>
> --
> Bill
>
The above command does not look like a mysql command because it does not
end with a semicolon.
This shows the two remaining:
BY chanid;
+--------+-------------+
| chanid | recpriority |
+--------+-------------+
| 1061 | -3 |
| 1301 | -5 |
+--------+-------------+
2 rows in set (0.01 sec)

I just want to be certain before I mess with mysql, I don't see how your
command, Bill, targets my remaining channel priorities?
Do I need to make substitutes in the command, like the actual password?

> _______________________________________________
>
>
Re: Upcoming recordings gone [ In reply to ]
On 10/28/21 2:38 PM, Daryl McDonald wrote:
>
>
>
>
> >     >
> >     >         mysql> SELECT chanid,recpriority FROM channel WHERE recpriority != 0 ORDER BY chanid;
> >     >         +--------+-------------+
> >     >         | chanid | recpriority |
> >     >         +--------+-------------+
> >     >         |   1061 |          -3 |
> >     >         |   1161 |          -2 |
> >     >         |   1171 |          -1 |
> >     >         |   1301 |          -5 |
> >     >         +--------+-------------+
> >     >         4 rows in set (0.00 sec)
> >
> >     You can follow this on: https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <https://forum.mythtv.org/viewtopic.php?f=36&t=4628>
> <https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <https://forum.mythtv.org/viewtopic.php?f=36&t=4628>>
> >
> >     You'll see that a single negative recpriority will cause the SQL error pasted
> >     earlier. The issue is still open
> On 10/28/21 6:08 AM, Daryl McDonald wrote:
> > Thanks Bill, halfway there, I was able to neutralize the priority factor on two of the four that showed from the query. The other two do not
> > show up in frontend settings because I deleted those channels. How would I go about making that change from mysql?
>
> This is a safe way, just change the chanid:
>
>   mysql --user=mythtv --password --execute="UPDATE channel SET recpriority=0 WHERE chanid=98765 LIMIT 1" mythconverg
>
> --
> Bill
>
> The above command does not look like a mysql command because it does not end with a semicolon.

It was intended to be run from the shell command line, you don't need to enter mysql.

> This shows the two remaining:
> mysql> SELECT chanid,recpriority FROM channel WHERE recpriority != 0 ORDER BY chanid;
> +--------+-------------+
> | chanid | recpriority |
> +--------+-------------+
> |   1061 |          -3 |
> |   1301 |          -5 |
> +--------+-------------+
> 2 rows in set (0.01 sec)
>
> I just want to be certain before I mess with mysql, I don't see how your command, Bill, targets my remaining channel priorities? 
> Do I need to make substitutes in the command, like the actual password?


In your case, you'd run the above twice, replacing 98765 with 1061 and again with 1301.
There are other ways to do it, but this works.

The actual fix was just tested and pushed for master and fixes/31, by the way.
(by gigem)

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
Thanks Bill, that rendered an empty set, Yeah! I'm going to reboot and have
a look.

On Thu, Oct 28, 2021 at 3:50 PM Bill Meek <keemllib@gmail.com> wrote:

> On 10/28/21 2:38 PM, Daryl McDonald wrote:
> >
> >
> >
> >
> > > >
> > > > mysql> SELECT chanid,recpriority FROM channel WHERE
> recpriority != 0 ORDER BY chanid;
> > > > +--------+-------------+
> > > > | chanid | recpriority |
> > > > +--------+-------------+
> > > > | 1061 | -3 |
> > > > | 1161 | -2 |
> > > > | 1171 | -1 |
> > > > | 1301 | -5 |
> > > > +--------+-------------+
> > > > 4 rows in set (0.00 sec)
> > >
> > > You can follow this on:
> https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <
> https://forum.mythtv.org/viewtopic.php?f=36&t=4628>
> > <https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <
> https://forum.mythtv.org/viewtopic.php?f=36&t=4628>>
> > >
> > > You'll see that a single negative recpriority will cause the
> SQL error pasted
> > > earlier. The issue is still open
> > On 10/28/21 6:08 AM, Daryl McDonald wrote:
> > > Thanks Bill, halfway there, I was able to neutralize the priority
> factor on two of the four that showed from the query. The other two do not
> > > show up in frontend settings because I deleted those channels. How
> would I go about making that change from mysql?
> >
> > This is a safe way, just change the chanid:
> >
> > mysql --user=mythtv --password --execute="UPDATE channel SET
> recpriority=0 WHERE chanid=98765 LIMIT 1" mythconverg
> >
> > --
> > Bill
> >
> > The above command does not look like a mysql command because it does not
> end with a semicolon.
>
> It was intended to be run from the shell command line, you don't need to
> enter mysql.
>
> > This shows the two remaining:
> > mysql> SELECT chanid,recpriority FROM channel WHERE recpriority != 0
> ORDER BY chanid;
> > +--------+-------------+
> > | chanid | recpriority |
> > +--------+-------------+
> > | 1061 | -3 |
> > | 1301 | -5 |
> > +--------+-------------+
> > 2 rows in set (0.01 sec)
> >
> > I just want to be certain before I mess with mysql, I don't see how your
> command, Bill, targets my remaining channel priorities?
> > Do I need to make substitutes in the command, like the actual password?
>
>
> In your case, you'd run the above twice, replacing 98765 with 1061 and
> again with 1301.
> There are other ways to do it, but this works.
>
> The actual fix was just tested and pushed for master and fixes/31, by the
> way.
> (by gigem)
>
> --
> Bill
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
Re: Upcoming recordings gone [ In reply to ]
On Thu, Oct 28, 2021 at 4:57 PM Daryl McDonald <darylangela@gmail.com>
wrote:

> Thanks Bill, that rendered an empty set, Yeah! I'm going to reboot and
> have a look.
>
> On Thu, Oct 28, 2021 at 3:50 PM Bill Meek <keemllib@gmail.com> wrote:
>
>> On 10/28/21 2:38 PM, Daryl McDonald wrote:
>> >
>> >
>> >
>> >
>> > > >
>> > > > mysql> SELECT chanid,recpriority FROM channel WHERE
>> recpriority != 0 ORDER BY chanid;
>> > > > +--------+-------------+
>> > > > | chanid | recpriority |
>> > > > +--------+-------------+
>> > > > | 1061 | -3 |
>> > > > | 1161 | -2 |
>> > > > | 1171 | -1 |
>> > > > | 1301 | -5 |
>> > > > +--------+-------------+
>> > > > 4 rows in set (0.00 sec)
>> > >
>> > > You can follow this on:
>> https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <
>> https://forum.mythtv.org/viewtopic.php?f=36&t=4628>
>> > <https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <
>> https://forum.mythtv.org/viewtopic.php?f=36&t=4628>>
>> > >
>> > > You'll see that a single negative recpriority will cause the
>> SQL error pasted
>> > > earlier. The issue is still open
>> > On 10/28/21 6:08 AM, Daryl McDonald wrote:
>> > > Thanks Bill, halfway there, I was able to neutralize the priority
>> factor on two of the four that showed from the query. The other two do not
>> > > show up in frontend settings because I deleted those channels.
>> How would I go about making that change from mysql?
>> >
>> > This is a safe way, just change the chanid:
>> >
>> > mysql --user=mythtv --password --execute="UPDATE channel SET
>> recpriority=0 WHERE chanid=98765 LIMIT 1" mythconverg
>> >
>> > --
>> > Bill
>> >
>> > The above command does not look like a mysql command because it does
>> not end with a semicolon.
>>
>> It was intended to be run from the shell command line, you don't need to
>> enter mysql.
>>
>> > This shows the two remaining:
>> > mysql> SELECT chanid,recpriority FROM channel WHERE recpriority != 0
>> ORDER BY chanid;
>> > +--------+-------------+
>> > | chanid | recpriority |
>> > +--------+-------------+
>> > | 1061 | -3 |
>> > | 1301 | -5 |
>> > +--------+-------------+
>> > 2 rows in set (0.01 sec)
>> >
>> > I just want to be certain before I mess with mysql, I don't see how
>> your command, Bill, targets my remaining channel priorities?
>> > Do I need to make substitutes in the command, like the actual password?
>>
>>
>> In your case, you'd run the above twice, replacing 98765 with 1061 and
>> again with 1301.
>> There are other ways to do it, but this works.
>>
>> The actual fix was just tested and pushed for master and fixes/31, by the
>> way.
>> (by gigem)
>>
>> --
>> Bill
>>
>>
Still no upcoming recordings? I just upgraded and nothing for myth or
mysql that I saw
Re: Upcoming recordings gone [ In reply to ]
On 10/28/21 4:03 PM, Daryl McDonald wrote:
> I just upgraded and nothing for myth or mysql that I saw

It usually takes a day or so. Look in your backend log to see if
the same error is still there. If you see: BIGINT, for example,
that's a clue.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib@gmail.com> wrote:

> On 10/28/21 4:03 PM, Daryl McDonald wrote:
> > I just upgraded and nothing for myth or mysql that I saw
>
> It usually takes a day or so. Look in your backend log to see if
> the same error is still there. If you see: BIGINT, for example,
> that's a clue.
>
> --
> Bill
> _______________________________________________
>
> OK, practicing patience here. Thanks, again.
Re: Upcoming recordings gone [ In reply to ]
On 28/10/2021 23:50, Daryl McDonald wrote:

>
>
> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib@gmail.com
> <mailto:keemllib@gmail.com>> wrote:
>
> On 10/28/21 4:03 PM, Daryl McDonald wrote:
> > I just upgraded and nothing for myth or mysql that I saw
>
> It usually takes a day or so. Look in your backend log to see if
> the same error is still there. If you see: BIGINT, for example,
> that's a clue.
>
> --
> Bill
> _______________________________________________
>
> OK, practicing patience here. Thanks, again.
>
>

For any Ubuntu users using the PPA's both mythbuntu/31 (fixes/31) and
mythbuntu/32 (master) have now been updated with the fix.


Paul H.
Re: Upcoming recordings gone [ In reply to ]
On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <mythtv@mythqml.net> wrote:

> On 28/10/2021 23:50, Daryl McDonald wrote:
>
>
>
> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib@gmail.com> wrote:
>
>> On 10/28/21 4:03 PM, Daryl McDonald wrote:
>> > I just upgraded and nothing for myth or mysql that I saw
>>
>> It usually takes a day or so. Look in your backend log to see if
>> the same error is still there. If you see: BIGINT, for example,
>> that's a clue.
>>
>> --
>> Bill
>> _______________________________________________
>>
>> OK, practicing patience here. Thanks, again.
>
>
>
> For any Ubuntu users using the PPA's both mythbuntu/31 (fixes/31) and
> mythbuntu/32 (master) have now been updated with the fix.
>
>
> Paul H.
>
I got the updates this morning, but still no recordings being scheduled.
When might things get back to functional?
Re: Upcoming recordings gone [ In reply to ]
On 10/29/21 2:44 PM, Daryl McDonald wrote:
>
>
> On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <mythtv@mythqml.net <mailto:mythtv@mythqml.net>> wrote:
>
> On 28/10/2021 23:50, Daryl McDonald wrote:
>
>>
>>
>> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com>> wrote:
>>
>> On 10/28/21 4:03 PM, Daryl McDonald wrote:
>> > I just upgraded and nothing for myth or mysql that I saw
>>
>> It usually takes a day or so. Look in your backend log to see if
>> the same error is still there. If you see: BIGINT, for example,
>> that's a clue.
>>
>> --
>> Bill
>> _______________________________________________
>>
>> OK, practicing patience here. Thanks, again. 
>>
>>
>
> For any Ubuntu users using the PPA's both mythbuntu/31 (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
>
>
> Paul H.
>
> I got the updates this morning, but still no recordings being scheduled.  When might things get back to functional? 

When you try to schedule a new recording, look in the backend log. Is the same SQL error
message there?

Look for this:

BIGINT UNSIGNED value is out of range in '((`mythconverg`.`c`.`recpriority` + `mythconverg`.`capturecard`.`recpriority`) +
((`mythconverg`.`capturecard`.`cardid` = `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'

It's issue fixed for me and others reporting on the Forum.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com> wrote:

> On 10/29/21 2:44 PM, Daryl McDonald wrote:
> >
> >
> > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <mythtv@mythqml.net
> <mailto:mythtv@mythqml.net>> wrote:
> >
> > On 28/10/2021 23:50, Daryl McDonald wrote:
> >
> >>
> >>
> >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib@gmail.com
> <mailto:keemllib@gmail.com>> wrote:
> >>
> >> On 10/28/21 4:03 PM, Daryl McDonald wrote:
> >> > I just upgraded and nothing for myth or mysql that I saw
> >>
> >> It usually takes a day or so. Look in your backend log to see if
> >> the same error is still there. If you see: BIGINT, for example,
> >> that's a clue.
> >>
> >> --
> >> Bill
> >> _______________________________________________
> >>
> >> OK, practicing patience here. Thanks, again.
> >>
> >>
> >
> > For any Ubuntu users using the PPA's both mythbuntu/31 (fixes/31)
> and mythbuntu/32 (master) have now been updated with the fix.
> >
> >
> > Paul H.
> >
> > I got the updates this morning, but still no recordings being
> scheduled. When might things get back to functional?
>
> When you try to schedule a new recording, look in the backend log. Is the
> same SQL error
> message there?
>
> Look for this:
>
> BIGINT UNSIGNED value is out of range in
> '((`mythconverg`.`c`.`recpriority` +
> `mythconverg`.`capturecard`.`recpriority`) +
> ((`mythconverg`.`capturecard`.`cardid` =
> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
>
> It's issue fixed for me and others reporting on the Forum.
>
> --
> Bill
> __

There seems to be some kind of dberror, here is a short log from the
backend :

https://paste.ubuntu.com/p/VBVtxZJzPK/
Re: Upcoming recordings gone [ In reply to ]
On 10/29/21 4:04 PM, Daryl McDonald wrote:
>
>
> On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com>> wrote:
>
> On 10/29/21 2:44 PM, Daryl McDonald wrote:
> >
> >
> > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <mythtv@mythqml.net <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
> <mailto:mythtv@mythqml.net>>> wrote:
> >
> >     On 28/10/2021 23:50, Daryl McDonald wrote:
> >
> >>
> >>
> >>     On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> <mailto:keemllib@gmail.com>>> wrote:
> >>
> >>         On 10/28/21 4:03 PM, Daryl McDonald wrote:
> >>         > I just upgraded and nothing for myth or mysql that I saw
> >>
> >>         It usually takes a day or so. Look in your backend log to see if
> >>         the same error is still there. If you see: BIGINT, for example,
> >>         that's a clue.
> >>
> >>         --
> >>         Bill
> >>         _______________________________________________
> >>
> >>     OK, practicing patience here. Thanks, again. 
> >>
> >>
> >
> >     For any Ubuntu users using the PPA's both mythbuntu/31 (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
> >
> >
> >     Paul H.
> >
> > I got the updates this morning, but still no recordings being scheduled.  When might things get back to functional? 
>
> When you try to schedule a new recording, look in the backend log. Is the same SQL error
> message there?
>
> Look for this:
>
> BIGINT UNSIGNED value is out of range in '((`mythconverg`.`c`.`recpriority` + `mythconverg`.`capturecard`.`recpriority`) +
> ((`mythconverg`.`capturecard`.`cardid` = `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
>
> It's issue fixed for me and others reporting on the Forum.
>
> --
> Bill
> __
>
> There seems to be some kind of dberror, here is a short log from the backend :
>
>  https://paste.ubuntu.com/p/VBVtxZJzPK/ <https://paste.ubuntu.com/p/VBVtxZJzPK/>

Any Custom Priority rules:

mysql --user=mythtv --password --host=localhost --execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib@gmail.com> wrote:

> On 10/29/21 4:04 PM, Daryl McDonald wrote:
> >
> >
> > On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com <mailto:
> keemllib@gmail.com>> wrote:
> >
> > On 10/29/21 2:44 PM, Daryl McDonald wrote:
> > >
> > >
> > > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <mythtv@mythqml.net
> <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
> > <mailto:mythtv@mythqml.net>>> wrote:
> > >
> > > On 28/10/2021 23:50, Daryl McDonald wrote:
> > >
> > >>
> > >>
> > >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib@gmail.com
> <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> > <mailto:keemllib@gmail.com>>> wrote:
> > >>
> > >> On 10/28/21 4:03 PM, Daryl McDonald wrote:
> > >> > I just upgraded and nothing for myth or mysql that I saw
> > >>
> > >> It usually takes a day or so. Look in your backend log to
> see if
> > >> the same error is still there. If you see: BIGINT, for
> example,
> > >> that's a clue.
> > >>
> > >> --
> > >> Bill
> > >> _______________________________________________
> > >>
> > >> OK, practicing patience here. Thanks, again.
> > >>
> > >>
> > >
> > > For any Ubuntu users using the PPA's both mythbuntu/31
> (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
> > >
> > >
> > > Paul H.
> > >
> > > I got the updates this morning, but still no recordings being
> scheduled. When might things get back to functional?
> >
> > When you try to schedule a new recording, look in the backend log.
> Is the same SQL error
> > message there?
> >
> > Look for this:
> >
> > BIGINT UNSIGNED value is out of range in
> '((`mythconverg`.`c`.`recpriority` +
> `mythconverg`.`capturecard`.`recpriority`) +
> > ((`mythconverg`.`capturecard`.`cardid` =
> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
> >
> > It's issue fixed for me and others reporting on the Forum.
> >
> > --
> > Bill
> > __
> >
> > There seems to be some kind of dberror, here is a short log from the
> backend :
> >
> > https://paste.ubuntu.com/p/VBVtxZJzPK/ <
> https://paste.ubuntu.com/p/VBVtxZJzPK/>
>
> Any Custom Priority rules:
>
> mysql --user=mythtv --password --host=localhost --execute="SELECT * FROM
> powerpriority,powerpriority_tmp" mythconverg
>
> --
> Bill
>
>
daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
--execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
Enter password:
+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
| priorityname | recpriority | selectclause |
priorityname | recpriority | selectclause |
+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
| CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
daryl@trieli:~$

Stephen and I just put this one in due to a less sensitive tuner card
Re: Upcoming recordings gone [ In reply to ]
On 10/29/21 8:49 PM, Daryl McDonald wrote:
>
>
> On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com>> wrote:
>
> On 10/29/21 4:04 PM, Daryl McDonald wrote:
> >
> >
> > On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> <mailto:keemllib@gmail.com>>> wrote:
> >
> >     On 10/29/21 2:44 PM, Daryl McDonald wrote:
> >     >
> >     >
> >     > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <mythtv@mythqml.net <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
> <mailto:mythtv@mythqml.net>> <mailto:mythtv@mythqml.net <mailto:mythtv@mythqml.net>
> >     <mailto:mythtv@mythqml.net <mailto:mythtv@mythqml.net>>>> wrote:
> >     >
> >     >     On 28/10/2021 23:50, Daryl McDonald wrote:
> >     >
> >     >>
> >     >>
> >     >>     On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib@gmail.com <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> <mailto:keemllib@gmail.com>> <mailto:keemllib@gmail.com <mailto:keemllib@gmail.com>
> >     <mailto:keemllib@gmail.com <mailto:keemllib@gmail.com>>>> wrote:
> >     >>
> >     >>         On 10/28/21 4:03 PM, Daryl McDonald wrote:
> >     >>         > I just upgraded and nothing for myth or mysql that I saw
> >     >>
> >     >>         It usually takes a day or so. Look in your backend log to see if
> >     >>         the same error is still there. If you see: BIGINT, for example,
> >     >>         that's a clue.
> >     >>
> >     >>         --
> >     >>         Bill
> >     >>         _______________________________________________
> >     >>
> >     >>     OK, practicing patience here. Thanks, again. 
> >     >>
> >     >>
> >     >
> >     >     For any Ubuntu users using the PPA's both mythbuntu/31 (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
> >     >
> >     >
> >     >     Paul H.
> >     >
> >     > I got the updates this morning, but still no recordings being scheduled.  When might things get back to functional? 
> >
> >     When you try to schedule a new recording, look in the backend log. Is the same SQL error
> >     message there?
> >
> >     Look for this:
> >
> >     BIGINT UNSIGNED value is out of range in '((`mythconverg`.`c`.`recpriority` + `mythconverg`.`capturecard`.`recpriority`) +
> >     ((`mythconverg`.`capturecard`.`cardid` = `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
> >
> >     It's issue fixed for me and others reporting on the Forum.
> >
> >     --
> >     Bill
> >     __
> >
> > There seems to be some kind of dberror, here is a short log from the backend :
> >
> >  https://paste.ubuntu.com/p/VBVtxZJzPK/ <https://paste.ubuntu.com/p/VBVtxZJzPK/> <https://paste.ubuntu.com/p/VBVtxZJzPK/
> <https://paste.ubuntu.com/p/VBVtxZJzPK/>>
>
> Any Custom Priority rules:
>
>   mysql --user=mythtv --password --host=localhost --execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
>
> --
> Bill
>
>
>  daryl@trieli:~$ mysql --user=mythtv --password --host=localhost --execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
> Enter password:
> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
> | priorityname | recpriority | selectclause                          | priorityname | recpriority | selectclause                          |
> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
> | CBSnotADP#0  |         -50 | channel.mplexid=6 and cardid in (1,5) | CBSnotADP#0  |         -50 | channel.mplexid=6 and cardid in (1,5) |
> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
> daryl@trieli:~$ 
>
> Stephen and I just put this one in due to a less sensitive tuner card

If you can live with it temporarily, change the recpriority in the Custom Priority to 0 from -50.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Fri, 29 Oct 2021 21:49:29 -0400, you wrote:

>On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib@gmail.com> wrote:
>
>> On 10/29/21 4:04 PM, Daryl McDonald wrote:
>> >
>> >
>> > On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com <mailto:
>> keemllib@gmail.com>> wrote:
>> >
>> > On 10/29/21 2:44 PM, Daryl McDonald wrote:
>> > >
>> > >
>> > > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <mythtv@mythqml.net
>> <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
>> > <mailto:mythtv@mythqml.net>>> wrote:
>> > >
>> > > On 28/10/2021 23:50, Daryl McDonald wrote:
>> > >
>> > >>
>> > >>
>> > >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib@gmail.com
>> <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
>> > <mailto:keemllib@gmail.com>>> wrote:
>> > >>
>> > >> On 10/28/21 4:03 PM, Daryl McDonald wrote:
>> > >> > I just upgraded and nothing for myth or mysql that I saw
>> > >>
>> > >> It usually takes a day or so. Look in your backend log to
>> see if
>> > >> the same error is still there. If you see: BIGINT, for
>> example,
>> > >> that's a clue.
>> > >>
>> > >> --
>> > >> Bill
>> > >> _______________________________________________
>> > >>
>> > >> OK, practicing patience here. Thanks, again.
>> > >>
>> > >>
>> > >
>> > > For any Ubuntu users using the PPA's both mythbuntu/31
>> (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
>> > >
>> > >
>> > > Paul H.
>> > >
>> > > I got the updates this morning, but still no recordings being
>> scheduled. When might things get back to functional?
>> >
>> > When you try to schedule a new recording, look in the backend log.
>> Is the same SQL error
>> > message there?
>> >
>> > Look for this:
>> >
>> > BIGINT UNSIGNED value is out of range in
>> '((`mythconverg`.`c`.`recpriority` +
>> `mythconverg`.`capturecard`.`recpriority`) +
>> > ((`mythconverg`.`capturecard`.`cardid` =
>> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
>> >
>> > It's issue fixed for me and others reporting on the Forum.
>> >
>> > --
>> > Bill
>> > __
>> >
>> > There seems to be some kind of dberror, here is a short log from the
>> backend :
>> >
>> > https://paste.ubuntu.com/p/VBVtxZJzPK/ <
>> https://paste.ubuntu.com/p/VBVtxZJzPK/>
>>
>> Any Custom Priority rules:
>>
>> mysql --user=mythtv --password --host=localhost --execute="SELECT * FROM
>> powerpriority,powerpriority_tmp" mythconverg
>>
>> --
>> Bill
>>
>>
> daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
>--execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
>Enter password:
>+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>| priorityname | recpriority | selectclause |
>priorityname | recpriority | selectclause |
>+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>| CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>daryl@trieli:~$
>
>Stephen and I just put this one in due to a less sensitive tuner card

It might be an idea to reverse that rule - add 50 when the opposite of
the condition applies:

update powerpriority set
recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
(1,5)' where priorityname='CBSnotADP#0';

(or change it via mythfrontend).

That should have the same effect without causing negative priorities.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Fri, Oct 29, 2021 at 10:52 PM Stephen Worthington <
stephen_agent@jsw.gen.nz> wrote:

> On Fri, 29 Oct 2021 21:49:29 -0400, you wrote:
>
> >On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib@gmail.com> wrote:
> >
> >> On 10/29/21 4:04 PM, Daryl McDonald wrote:
> >> >
> >> >
> >> > On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com
> <mailto:
> >> keemllib@gmail.com>> wrote:
> >> >
> >> > On 10/29/21 2:44 PM, Daryl McDonald wrote:
> >> > >
> >> > >
> >> > > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <
> mythtv@mythqml.net
> >> <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
> >> > <mailto:mythtv@mythqml.net>>> wrote:
> >> > >
> >> > > On 28/10/2021 23:50, Daryl McDonald wrote:
> >> > >
> >> > >>
> >> > >>
> >> > >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <
> keemllib@gmail.com
> >> <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> >> > <mailto:keemllib@gmail.com>>> wrote:
> >> > >>
> >> > >> On 10/28/21 4:03 PM, Daryl McDonald wrote:
> >> > >> > I just upgraded and nothing for myth or mysql that I
> saw
> >> > >>
> >> > >> It usually takes a day or so. Look in your backend log
> to
> >> see if
> >> > >> the same error is still there. If you see: BIGINT, for
> >> example,
> >> > >> that's a clue.
> >> > >>
> >> > >> --
> >> > >> Bill
> >> > >> _______________________________________________
> >> > >>
> >> > >> OK, practicing patience here. Thanks, again.
> >> > >>
> >> > >>
> >> > >
> >> > > For any Ubuntu users using the PPA's both mythbuntu/31
> >> (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
> >> > >
> >> > >
> >> > > Paul H.
> >> > >
> >> > > I got the updates this morning, but still no recordings being
> >> scheduled. When might things get back to functional?
> >> >
> >> > When you try to schedule a new recording, look in the backend log.
> >> Is the same SQL error
> >> > message there?
> >> >
> >> > Look for this:
> >> >
> >> > BIGINT UNSIGNED value is out of range in
> >> '((`mythconverg`.`c`.`recpriority` +
> >> `mythconverg`.`capturecard`.`recpriority`) +
> >> > ((`mythconverg`.`capturecard`.`cardid` =
> >> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
> >> >
> >> > It's issue fixed for me and others reporting on the Forum.
> >> >
> >> > --
> >> > Bill
> >> > __
> >> >
> >> > There seems to be some kind of dberror, here is a short log from the
> >> backend :
> >> >
> >> > https://paste.ubuntu.com/p/VBVtxZJzPK/ <
> >> https://paste.ubuntu.com/p/VBVtxZJzPK/>
> >>
> >> Any Custom Priority rules:
> >>
> >> mysql --user=mythtv --password --host=localhost --execute="SELECT *
> FROM
> >> powerpriority,powerpriority_tmp" mythconverg
> >>
> >> --
> >> Bill
> >>
> >>
> > daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
> >--execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
> >Enter password:
>
> >+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
> >| priorityname | recpriority | selectclause |
> >priorityname | recpriority | selectclause |
>
> >+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
> >| CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
> >CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>
> >+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
> >daryl@trieli:~$
> >
> >Stephen and I just put this one in due to a less sensitive tuner card
>
> It might be an idea to reverse that rule - add 50 when the opposite of
> the condition applies:
>
> update powerpriority set
> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
> (1,5)' where priorityname='CBSnotADP#0';
>
> (or change it via mythfrontend).
>
> That should have the same effect without causing negative priorities.
>
> mysql> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
(1,5)' where priorityname='CBSnotADP#0';
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use
near 'recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
(1,5)' where pr' at line 1
mysql>
Re: Upcoming recordings gone [ In reply to ]
On 30/10/2021 09:35, Daryl McDonald wrote:
> On Fri, Oct 29, 2021 at 10:52 PM Stephen Worthington <
> stephen_agent@jsw.gen.nz> wrote:
>
>> On Fri, 29 Oct 2021 21:49:29 -0400, you wrote:
>>
>>> On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib@gmail.com> wrote:
>>>
>>>> On 10/29/21 4:04 PM, Daryl McDonald wrote:
>>>>>
>>>>>
>>>>> On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com
>> <mailto:
>>>> keemllib@gmail.com>> wrote:
>>>>>
>>>>> On 10/29/21 2:44 PM, Daryl McDonald wrote:
>>>>> >
>>>>> >
>>>>> > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <
>> mythtv@mythqml.net
>>>> <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
>>>>> <mailto:mythtv@mythqml.net>>> wrote:
>>>>> >
>>>>> > On 28/10/2021 23:50, Daryl McDonald wrote:
>>>>> >
>>>>> >>
>>>>> >>
>>>>> >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <
>> keemllib@gmail.com
>>>> <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
>>>>> <mailto:keemllib@gmail.com>>> wrote:
>>>>> >>
>>>>> >> On 10/28/21 4:03 PM, Daryl McDonald wrote:
>>>>> >> > I just upgraded and nothing for myth or mysql that I
>> saw
>>>>> >>
>>>>> >> It usually takes a day or so. Look in your backend log
>> to
>>>> see if
>>>>> >> the same error is still there. If you see: BIGINT, for
>>>> example,
>>>>> >> that's a clue.
>>>>> >>
>>>>> >> --
>>>>> >> Bill
>>>>> >> _______________________________________________
>>>>> >>
>>>>> >> OK, practicing patience here. Thanks, again.
>>>>> >>
>>>>> >>
>>>>> >
>>>>> > For any Ubuntu users using the PPA's both mythbuntu/31
>>>> (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
>>>>> >
>>>>> >
>>>>> > Paul H.
>>>>> >
>>>>> > I got the updates this morning, but still no recordings being
>>>> scheduled. When might things get back to functional?
>>>>>
>>>>> When you try to schedule a new recording, look in the backend log.
>>>> Is the same SQL error
>>>>> message there?
>>>>>
>>>>> Look for this:
>>>>>
>>>>> BIGINT UNSIGNED value is out of range in
>>>> '((`mythconverg`.`c`.`recpriority` +
>>>> `mythconverg`.`capturecard`.`recpriority`) +
>>>>> ((`mythconverg`.`capturecard`.`cardid` =
>>>> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
>>>>>
>>>>> It's issue fixed for me and others reporting on the Forum.
>>>>>
>>>>> --
>>>>> Bill
>>>>> __
>>>>>
>>>>> There seems to be some kind of dberror, here is a short log from the
>>>> backend :
>>>>>
>>>>> https://paste.ubuntu.com/p/VBVtxZJzPK/ <
>>>> https://paste.ubuntu.com/p/VBVtxZJzPK/>
>>>>
>>>> Any Custom Priority rules:
>>>>
>>>> mysql --user=mythtv --password --host=localhost --execute="SELECT *
>> FROM
>>>> powerpriority,powerpriority_tmp" mythconverg
>>>>
>>>> --
>>>> Bill
>>>>
>>>>
>>> daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
>>> --execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
>>> Enter password:
>>
>>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>>> | priorityname | recpriority | selectclause |
>>> priorityname | recpriority | selectclause |
>>
>>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>>> | CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>>> CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>>
>>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>>> daryl@trieli:~$
>>>
>>> Stephen and I just put this one in due to a less sensitive tuner card
>>
>> It might be an idea to reverse that rule - add 50 when the opposite of
>> the condition applies:
>>
>> update powerpriority set
>> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> (1,5)' where priorityname='CBSnotADP#0';
>>
>> (or change it via mythfrontend).
>>
>> That should have the same effect without causing negative priorities.
>>
>> mysql> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
> (1,5)' where priorityname='CBSnotADP#0';
> ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
> that corresponds to your MySQL server version for the right syntax to use
> near 'recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
> (1,5)' where pr' at line 1
> mysql>
>
You overlooked the previous line. That command should all read:

mysql> update powerpriority set recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> (1,5)' where priorityname='CBSnotADP#0';

(all on one line, of course)

That all looks horrible to me and easy to get wrong. I'd do the changes using the front end,
manually tweaking the rules individually. Of course, that depends on how many rules you have to do.

--

Mike Perkins

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Sat, 30 Oct 2021 04:35:38 -0400, you wrote:

>On Fri, Oct 29, 2021 at 10:52 PM Stephen Worthington <
>stephen_agent@jsw.gen.nz> wrote:
>
>> On Fri, 29 Oct 2021 21:49:29 -0400, you wrote:
>>
>> >On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib@gmail.com> wrote:
>> >
>> >> On 10/29/21 4:04 PM, Daryl McDonald wrote:
>> >> >
>> >> >
>> >> > On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com
>> <mailto:
>> >> keemllib@gmail.com>> wrote:
>> >> >
>> >> > On 10/29/21 2:44 PM, Daryl McDonald wrote:
>> >> > >
>> >> > >
>> >> > > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <
>> mythtv@mythqml.net
>> >> <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
>> >> > <mailto:mythtv@mythqml.net>>> wrote:
>> >> > >
>> >> > > On 28/10/2021 23:50, Daryl McDonald wrote:
>> >> > >
>> >> > >>
>> >> > >>
>> >> > >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <
>> keemllib@gmail.com
>> >> <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
>> >> > <mailto:keemllib@gmail.com>>> wrote:
>> >> > >>
>> >> > >> On 10/28/21 4:03 PM, Daryl McDonald wrote:
>> >> > >> > I just upgraded and nothing for myth or mysql that I
>> saw
>> >> > >>
>> >> > >> It usually takes a day or so. Look in your backend log
>> to
>> >> see if
>> >> > >> the same error is still there. If you see: BIGINT, for
>> >> example,
>> >> > >> that's a clue.
>> >> > >>
>> >> > >> --
>> >> > >> Bill
>> >> > >> _______________________________________________
>> >> > >>
>> >> > >> OK, practicing patience here. Thanks, again.
>> >> > >>
>> >> > >>
>> >> > >
>> >> > > For any Ubuntu users using the PPA's both mythbuntu/31
>> >> (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
>> >> > >
>> >> > >
>> >> > > Paul H.
>> >> > >
>> >> > > I got the updates this morning, but still no recordings being
>> >> scheduled. When might things get back to functional?
>> >> >
>> >> > When you try to schedule a new recording, look in the backend log.
>> >> Is the same SQL error
>> >> > message there?
>> >> >
>> >> > Look for this:
>> >> >
>> >> > BIGINT UNSIGNED value is out of range in
>> >> '((`mythconverg`.`c`.`recpriority` +
>> >> `mythconverg`.`capturecard`.`recpriority`) +
>> >> > ((`mythconverg`.`capturecard`.`cardid` =
>> >> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
>> >> >
>> >> > It's issue fixed for me and others reporting on the Forum.
>> >> >
>> >> > --
>> >> > Bill
>> >> > __
>> >> >
>> >> > There seems to be some kind of dberror, here is a short log from the
>> >> backend :
>> >> >
>> >> > https://paste.ubuntu.com/p/VBVtxZJzPK/ <
>> >> https://paste.ubuntu.com/p/VBVtxZJzPK/>
>> >>
>> >> Any Custom Priority rules:
>> >>
>> >> mysql --user=mythtv --password --host=localhost --execute="SELECT *
>> FROM
>> >> powerpriority,powerpriority_tmp" mythconverg
>> >>
>> >> --
>> >> Bill
>> >>
>> >>
>> > daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
>> >--execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
>> >Enter password:
>>
>> >+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>> >| priorityname | recpriority | selectclause |
>> >priorityname | recpriority | selectclause |
>>
>> >+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>> >| CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>> >CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>>
>> >+--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>> >daryl@trieli:~$
>> >
>> >Stephen and I just put this one in due to a less sensitive tuner card
>>
>> It might be an idea to reverse that rule - add 50 when the opposite of
>> the condition applies:
>>
>> update powerpriority set
>> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> (1,5)' where priorityname='CBSnotADP#0';
>>
>> (or change it via mythfrontend).
>>
>> That should have the same effect without causing negative priorities.
>>
>> mysql> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>(1,5)' where priorityname='CBSnotADP#0';
>ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
>that corresponds to your MySQL server version for the right syntax to use
>near 'recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>(1,5)' where pr' at line 1
>mysql>

It looks like you missed the first line ("update powerpriority set").
Try again, with a different line layout:

update powerpriority set recpriority=50,
selectclause='channel.mplexid!=6 or cardid not in (1,5)'
where priorityname='CBSnotADP#0';
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Sat, 30 Oct 2021 10:21:38 +0100, you wrote:

>On 30/10/2021 09:35, Daryl McDonald wrote:
>> On Fri, Oct 29, 2021 at 10:52 PM Stephen Worthington <
>> stephen_agent@jsw.gen.nz> wrote:
>>
>>> On Fri, 29 Oct 2021 21:49:29 -0400, you wrote:
>>>
>>>> On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib@gmail.com> wrote:
>>>>
>>>>> On 10/29/21 4:04 PM, Daryl McDonald wrote:
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com
>>> <mailto:
>>>>> keemllib@gmail.com>> wrote:
>>>>>>
>>>>>> On 10/29/21 2:44 PM, Daryl McDonald wrote:
>>>>>> >
>>>>>> >
>>>>>> > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <
>>> mythtv@mythqml.net
>>>>> <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
>>>>>> <mailto:mythtv@mythqml.net>>> wrote:
>>>>>> >
>>>>>> > On 28/10/2021 23:50, Daryl McDonald wrote:
>>>>>> >
>>>>>> >>
>>>>>> >>
>>>>>> >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <
>>> keemllib@gmail.com
>>>>> <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
>>>>>> <mailto:keemllib@gmail.com>>> wrote:
>>>>>> >>
>>>>>> >> On 10/28/21 4:03 PM, Daryl McDonald wrote:
>>>>>> >> > I just upgraded and nothing for myth or mysql that I
>>> saw
>>>>>> >>
>>>>>> >> It usually takes a day or so. Look in your backend log
>>> to
>>>>> see if
>>>>>> >> the same error is still there. If you see: BIGINT, for
>>>>> example,
>>>>>> >> that's a clue.
>>>>>> >>
>>>>>> >> --
>>>>>> >> Bill
>>>>>> >> _______________________________________________
>>>>>> >>
>>>>>> >> OK, practicing patience here. Thanks, again.
>>>>>> >>
>>>>>> >>
>>>>>> >
>>>>>> > For any Ubuntu users using the PPA's both mythbuntu/31
>>>>> (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
>>>>>> >
>>>>>> >
>>>>>> > Paul H.
>>>>>> >
>>>>>> > I got the updates this morning, but still no recordings being
>>>>> scheduled. When might things get back to functional?
>>>>>>
>>>>>> When you try to schedule a new recording, look in the backend log.
>>>>> Is the same SQL error
>>>>>> message there?
>>>>>>
>>>>>> Look for this:
>>>>>>
>>>>>> BIGINT UNSIGNED value is out of range in
>>>>> '((`mythconverg`.`c`.`recpriority` +
>>>>> `mythconverg`.`capturecard`.`recpriority`) +
>>>>>> ((`mythconverg`.`capturecard`.`cardid` =
>>>>> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
>>>>>>
>>>>>> It's issue fixed for me and others reporting on the Forum.
>>>>>>
>>>>>> --
>>>>>> Bill
>>>>>> __
>>>>>>
>>>>>> There seems to be some kind of dberror, here is a short log from the
>>>>> backend :
>>>>>>
>>>>>> https://paste.ubuntu.com/p/VBVtxZJzPK/ <
>>>>> https://paste.ubuntu.com/p/VBVtxZJzPK/>
>>>>>
>>>>> Any Custom Priority rules:
>>>>>
>>>>> mysql --user=mythtv --password --host=localhost --execute="SELECT *
>>> FROM
>>>>> powerpriority,powerpriority_tmp" mythconverg
>>>>>
>>>>> --
>>>>> Bill
>>>>>
>>>>>
>>>> daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
>>>> --execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
>>>> Enter password:
>>>
>>>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>>>> | priorityname | recpriority | selectclause |
>>>> priorityname | recpriority | selectclause |
>>>
>>>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>>>> | CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>>>> CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>>>
>>>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>>>> daryl@trieli:~$
>>>>
>>>> Stephen and I just put this one in due to a less sensitive tuner card
>>>
>>> It might be an idea to reverse that rule - add 50 when the opposite of
>>> the condition applies:
>>>
>>> update powerpriority set
>>> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>>> (1,5)' where priorityname='CBSnotADP#0';
>>>
>>> (or change it via mythfrontend).
>>>
>>> That should have the same effect without causing negative priorities.
>>>
>>> mysql> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> (1,5)' where priorityname='CBSnotADP#0';
>> ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
>> that corresponds to your MySQL server version for the right syntax to use
>> near 'recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> (1,5)' where pr' at line 1
>> mysql>
>>
>You overlooked the previous line. That command should all read:
>
>mysql> update powerpriority set recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
> >> (1,5)' where priorityname='CBSnotADP#0';
>
>(all on one line, of course)
>
>That all looks horrible to me and easy to get wrong. I'd do the changes using the front end,
>manually tweaking the rules individually. Of course, that depends on how many rules you have to do.

There is just the one rule. It adjusts the tuner priorities so that
the two virtual tuners on the physical tuner that has problems
recording from one multiplex are much lower priority for use when that
multiplex is being recorded from. So that multiplex will only be
recorded on the other three tuners.

Changing the settings from mythfrontend has the problem that
mythfrontend (and all MythTV programs) do not allow pasting of text,
so you have to manually type it in.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Sat, Oct 30, 2021 at 5:34 AM Stephen Worthington <
stephen_agent@jsw.gen.nz> wrote:

> On Sat, 30 Oct 2021 10:21:38 +0100, you wrote:
>
> >On 30/10/2021 09:35, Daryl McDonald wrote:
> >> On Fri, Oct 29, 2021 at 10:52 PM Stephen Worthington <
> >> stephen_agent@jsw.gen.nz> wrote:
> >>
> >>> On Fri, 29 Oct 2021 21:49:29 -0400, you wrote:
> >>>
> >>>> On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib@gmail.com> wrote:
> >>>>
> >>>>> On 10/29/21 4:04 PM, Daryl McDonald wrote:
> >>>>>>
> >>>>>>
> >>>>>> On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com
> >>> <mailto:
> >>>>> keemllib@gmail.com>> wrote:
> >>>>>>
> >>>>>> On 10/29/21 2:44 PM, Daryl McDonald wrote:
> >>>>>> >
> >>>>>> >
> >>>>>> > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <
> >>> mythtv@mythqml.net
> >>>>> <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
> >>>>>> <mailto:mythtv@mythqml.net>>> wrote:
> >>>>>> >
> >>>>>> > On 28/10/2021 23:50, Daryl McDonald wrote:
> >>>>>> >
> >>>>>> >>
> >>>>>> >>
> >>>>>> >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <
> >>> keemllib@gmail.com
> >>>>> <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
> >>>>>> <mailto:keemllib@gmail.com>>> wrote:
> >>>>>> >>
> >>>>>> >> On 10/28/21 4:03 PM, Daryl McDonald wrote:
> >>>>>> >> > I just upgraded and nothing for myth or mysql
> that I
> >>> saw
> >>>>>> >>
> >>>>>> >> It usually takes a day or so. Look in your backend
> log
> >>> to
> >>>>> see if
> >>>>>> >> the same error is still there. If you see: BIGINT,
> for
> >>>>> example,
> >>>>>> >> that's a clue.
> >>>>>> >>
> >>>>>> >> --
> >>>>>> >> Bill
> >>>>>> >> _______________________________________________
> >>>>>> >>
> >>>>>> >> OK, practicing patience here. Thanks, again.
> >>>>>> >>
> >>>>>> >>
> >>>>>> >
> >>>>>> > For any Ubuntu users using the PPA's both mythbuntu/31
> >>>>> (fixes/31) and mythbuntu/32 (master) have now been updated with the
> fix.
> >>>>>> >
> >>>>>> >
> >>>>>> > Paul H.
> >>>>>> >
> >>>>>> > I got the updates this morning, but still no recordings being
> >>>>> scheduled. When might things get back to functional?
> >>>>>>
> >>>>>> When you try to schedule a new recording, look in the backend
> log.
> >>>>> Is the same SQL error
> >>>>>> message there?
> >>>>>>
> >>>>>> Look for this:
> >>>>>>
> >>>>>> BIGINT UNSIGNED value is out of range in
> >>>>> '((`mythconverg`.`c`.`recpriority` +
> >>>>> `mythconverg`.`capturecard`.`recpriority`) +
> >>>>>> ((`mythconverg`.`capturecard`.`cardid` =
> >>>>> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
> >>>>>>
> >>>>>> It's issue fixed for me and others reporting on the Forum.
> >>>>>>
> >>>>>> --
> >>>>>> Bill
> >>>>>> __
> >>>>>>
> >>>>>> There seems to be some kind of dberror, here is a short log from the
> >>>>> backend :
> >>>>>>
> >>>>>> https://paste.ubuntu.com/p/VBVtxZJzPK/ <
> >>>>> https://paste.ubuntu.com/p/VBVtxZJzPK/>
> >>>>>
> >>>>> Any Custom Priority rules:
> >>>>>
> >>>>> mysql --user=mythtv --password --host=localhost --execute="SELECT
> *
> >>> FROM
> >>>>> powerpriority,powerpriority_tmp" mythconverg
> >>>>>
> >>>>> --
> >>>>> Bill
> >>>>>
> >>>>>
> >>>> daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
> >>>> --execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
> >>>> Enter password:
> >>>
> >>>>
> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
> >>>> | priorityname | recpriority | selectclause |
> >>>> priorityname | recpriority | selectclause |
> >>>
> >>>>
> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
> >>>> | CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
> >>>> CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
> >>>
> >>>>
> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
> >>>> daryl@trieli:~$
> >>>>
> >>>> Stephen and I just put this one in due to a less sensitive tuner card
> >>>
> >>> It might be an idea to reverse that rule - add 50 when the opposite of
> >>> the condition applies:
> >>>
> >>> update powerpriority set
> >>> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
> >>> (1,5)' where priorityname='CBSnotADP#0';
> >>>
> >>> (or change it via mythfrontend).
> >>>
> >>> That should have the same effect without causing negative priorities.
> >>>
> >>> mysql> recpriority=50,selectclause='channel.mplexid!=6 or cardid not
> in
> >> (1,5)' where priorityname='CBSnotADP#0';
> >> ERROR 1064 (42000): You have an error in your SQL syntax; check the
> manual
> >> that corresponds to your MySQL server version for the right syntax to
> use
> >> near 'recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
> >> (1,5)' where pr' at line 1
> >> mysql>
> >>
> >You overlooked the previous line. That command should all read:
> >
> >mysql> update powerpriority set
> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
> > >> (1,5)' where priorityname='CBSnotADP#0';
>
OK, I didn't realize.

> >
> >(all on one line, of course)
> >
> >That all looks horrible to me and easy to get wrong. I'd do the changes
> using the front end,
> >manually tweaking the rules individually. Of course, that depends on how
> many rules you have to do.
>
> There is just the one rule. It adjusts the tuner priorities so that
> the two virtual tuners on the physical tuner that has problems
> recording from one multiplex are much lower priority for use when that
> multiplex is being recorded from. So that multiplex will only be
> recorded on the other three tuners.
>
> Changing the settings from mythfrontend has the problem that
> mythfrontend (and all MythTV programs) do not allow pasting of text,
> so you have to manually type it in.
>
What I did do was delete the rule and remove the card from the scheduler's
reach. Three tuners is enough for now. Now it occurs to me that I could
apply the positive rule to use cardid=2,5 (or 2,3,4,6,7,8). I'll look into
all possibilities, thanks again men!
Re: Upcoming recordings gone [ In reply to ]
On Sat, Oct 30, 2021 at 7:43 AM Daryl McDonald <darylangela@gmail.com>
wrote:

>
>
> On Sat, Oct 30, 2021 at 5:34 AM Stephen Worthington <
> stephen_agent@jsw.gen.nz> wrote:
>
>> On Sat, 30 Oct 2021 10:21:38 +0100, you wrote:
>>
>> >On 30/10/2021 09:35, Daryl McDonald wrote:
>> >> On Fri, Oct 29, 2021 at 10:52 PM Stephen Worthington <
>> >> stephen_agent@jsw.gen.nz> wrote:
>> >>
>> >>> On Fri, 29 Oct 2021 21:49:29 -0400, you wrote:
>> >>>
>> >>>> On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib@gmail.com>
>> wrote:
>> >>>>
>> >>>>> On 10/29/21 4:04 PM, Daryl McDonald wrote:
>> >>>>>>
>> >>>>>>
>> >>>>>> On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib@gmail.com
>> >>> <mailto:
>> >>>>> keemllib@gmail.com>> wrote:
>> >>>>>>
>> >>>>>> On 10/29/21 2:44 PM, Daryl McDonald wrote:
>> >>>>>> >
>> >>>>>> >
>> >>>>>> > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <
>> >>> mythtv@mythqml.net
>> >>>>> <mailto:mythtv@mythqml.net> <mailto:mythtv@mythqml.net
>> >>>>>> <mailto:mythtv@mythqml.net>>> wrote:
>> >>>>>> >
>> >>>>>> > On 28/10/2021 23:50, Daryl McDonald wrote:
>> >>>>>> >
>> >>>>>> >>
>> >>>>>> >>
>> >>>>>> >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <
>> >>> keemllib@gmail.com
>> >>>>> <mailto:keemllib@gmail.com> <mailto:keemllib@gmail.com
>> >>>>>> <mailto:keemllib@gmail.com>>> wrote:
>> >>>>>> >>
>> >>>>>> >> On 10/28/21 4:03 PM, Daryl McDonald wrote:
>> >>>>>> >> > I just upgraded and nothing for myth or mysql
>> that I
>> >>> saw
>> >>>>>> >>
>> >>>>>> >> It usually takes a day or so. Look in your backend
>> log
>> >>> to
>> >>>>> see if
>> >>>>>> >> the same error is still there. If you see: BIGINT,
>> for
>> >>>>> example,
>> >>>>>> >> that's a clue.
>> >>>>>> >>
>> >>>>>> >> --
>> >>>>>> >> Bill
>> >>>>>> >> _______________________________________________
>> >>>>>> >>
>> >>>>>> >> OK, practicing patience here. Thanks, again.
>> >>>>>> >>
>> >>>>>> >>
>> >>>>>> >
>> >>>>>> > For any Ubuntu users using the PPA's both mythbuntu/31
>> >>>>> (fixes/31) and mythbuntu/32 (master) have now been updated with the
>> fix.
>> >>>>>> >
>> >>>>>> >
>> >>>>>> > Paul H.
>> >>>>>> >
>> >>>>>> > I got the updates this morning, but still no recordings
>> being
>> >>>>> scheduled. When might things get back to functional?
>> >>>>>>
>> >>>>>> When you try to schedule a new recording, look in the backend
>> log.
>> >>>>> Is the same SQL error
>> >>>>>> message there?
>> >>>>>>
>> >>>>>> Look for this:
>> >>>>>>
>> >>>>>> BIGINT UNSIGNED value is out of range in
>> >>>>> '((`mythconverg`.`c`.`recpriority` +
>> >>>>> `mythconverg`.`capturecard`.`recpriority`) +
>> >>>>>> ((`mythconverg`.`capturecard`.`cardid` =
>> >>>>> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
>> >>>>>>
>> >>>>>> It's issue fixed for me and others reporting on the Forum.
>> >>>>>>
>> >>>>>> --
>> >>>>>> Bill
>> >>>>>> __
>> >>>>>>
>> >>>>>> There seems to be some kind of dberror, here is a short log from
>> the
>> >>>>> backend :
>> >>>>>>
>> >>>>>> https://paste.ubuntu.com/p/VBVtxZJzPK/ <
>> >>>>> https://paste.ubuntu.com/p/VBVtxZJzPK/>
>> >>>>>
>> >>>>> Any Custom Priority rules:
>> >>>>>
>> >>>>> mysql --user=mythtv --password --host=localhost
>> --execute="SELECT *
>> >>> FROM
>> >>>>> powerpriority,powerpriority_tmp" mythconverg
>> >>>>>
>> >>>>> --
>> >>>>> Bill
>> >>>>>
>> >>>>>
>> >>>> daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
>> >>>> --execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
>> >>>> Enter password:
>> >>>
>> >>>>
>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>> |
>> >>>> priorityname | recpriority | selectclause |
>> >>>
>> >>>>
>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>> |
>> >>>> CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in (1,5) |
>> >>>
>> >>>>
>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>> >>>> daryl@trieli:~$
>> >>>>
>> >>>> Stephen and I just put this one in due to a less sensitive tuner card
>> >>>
>> >>> It might be an idea to reverse that rule - add 50 when the opposite of
>> >>> the condition applies:
>> >>>
>> >>> update powerpriority set
>> >>> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> >>> (1,5)' where priorityname='CBSnotADP#0';
>> >>>
>> >>> (or change it via mythfrontend).
>> >>>
>> >>> That should have the same effect without causing negative priorities.
>> >>>
>> >>> mysql> recpriority=50,selectclause='channel.mplexid!=6 or cardid
>> not in
>> >> (1,5)' where priorityname='CBSnotADP#0';
>> >> ERROR 1064 (42000): You have an error in your SQL syntax; check the
>> manual
>> >> that corresponds to your MySQL server version for the right syntax to
>> use
>> >> near 'recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> >> (1,5)' where pr' at line 1
>> >> mysql>
>> >>
>> >You overlooked the previous line. That command should all read:
>> >
>> >mysql> update powerpriority set
>> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> > >> (1,5)' where priorityname='CBSnotADP#0';
>>
> OK, I didn't realize.
>
>> >
>> >(all on one line, of course)
>> >
>> >That all looks horrible to me and easy to get wrong. I'd do the changes
>> using the front end,
>> >manually tweaking the rules individually. Of course, that depends on how
>> many rules you have to do.
>>
>> There is just the one rule. It adjusts the tuner priorities so that
>> the two virtual tuners on the physical tuner that has problems
>> recording from one multiplex are much lower priority for use when that
>> multiplex is being recorded from. So that multiplex will only be
>> recorded on the other three tuners.
>>
>> Changing the settings from mythfrontend has the problem that
>> mythfrontend (and all MythTV programs) do not allow pasting of text,
>> so you have to manually type it in.
>>
> What I did do was delete the rule and remove the card from the scheduler's
> reach. Three tuners is enough for now. Now it occurs to me that I could
> apply the positive rule to use cardid=2,5 (or 2,3,4,6,7,8). I'll look into
> all possibilities, thanks again men!
>

I think this will be much better:
daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
--execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
Enter password:
+--------------+-------------+-------------------------------------------+--------------+-------------+-------------------------------------------+
| priorityname | recpriority | selectclause |
priorityname | recpriority | selectclause |
+--------------+-------------+-------------------------------------------+--------------+-------------+-------------------------------------------+
| CBSnotADP#0 | 50 | channel.mplexid!=6 or cardid not in (1,5) |
CBSnotADP#0 | 50 | channel.mplexid!=6 or cardid not in (1,5) |
+--------------+-------------+-------------------------------------------+--------------+-------------+-------------------------------------------+
daryl@trieli:~$
All with plenty of time before Kick-Off tomorrow, much obliged!
Re: Upcoming recordings gone [ In reply to ]
On 30/10/2021 10:33, Stephen Worthington wrote:
> On Sat, 30 Oct 2021 10:21:38 +0100, you wrote:
>
> Changing the settings from mythfrontend has the problem that
> mythfrontend (and all MythTV programs) do not allow pasting of text,
> so you have to manually type it in.


You can if you have a keyboard connected the normal CTRL-V will paste
text into a text editor in Myth. CTRL-C will cut all the text in a text
editor as well.


Generally we don't encourage users to manually chnage the database
unless they know exactly what they are doing and what the consequences
can be if you get it wrong. Always best to use the frontend if possible.


Paul H.

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Sat, Oct 30, 2021 at 12:11 PM Paul Harrison <mythtv@mythqml.net> wrote:

> On 30/10/2021 10:33, Stephen Worthington wrote:
> > On Sat, 30 Oct 2021 10:21:38 +0100, you wrote:
> >
> > Changing the settings from mythfrontend has the problem that
> > mythfrontend (and all MythTV programs) do not allow pasting of text,
> > so you have to manually type it in.
>
>
> You can if you have a keyboard connected the normal CTRL-V will paste
> text into a text editor in Myth. CTRL-C will cut all the text in a text
> editor as well.
>
>
> Generally we don't encourage users to manually chnage the database
> unless they know exactly what they are doing and what the consequences
> can be if you get it wrong. Always best to use the frontend if possible.
>
>
> Paul H.
>
> _______________________________________________
>
> After deleting the original rule, I re-read my notes and used the FE to
get the new rule. The reply to the terminal query was the easier way to
show what I had done to those who had helped me.
Re: Upcoming recordings gone [ In reply to ]
On 10/30/21 6:43 AM, Daryl McDonald wrote:

...

> >>>> daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
> >>>> --execute="SELECT * FROM powerpriority" mythconverg
> >>>> +--------------+-------------+---------------------------------------+
> >>>> | priorityname | recpriority | selectclause                          |
> >>>> +--------------+-------------+---------------------------------------+
> >>>> | CBSnotADP#0  |         -50 | channel.mplexid=6 and cardid in (1,5) |
> >>>> +--------------+-------------+---------------------------------------+

...

The fix for Custom Priorities was pushed this afternoon. It should show up tomorrow
and you can restore the above.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upcoming recordings gone [ In reply to ]
On Mon, Nov 1, 2021 at 9:33 PM Bill Meek <keemllib@gmail.com> wrote:

> On 10/30/21 6:43 AM, Daryl McDonald wrote:
>
> ...
>
> > >>>> daryl@trieli:~$ mysql --user=mythtv --password --host=localhost
> > >>>> --execute="SELECT * FROM powerpriority" mythconverg
> > >>>>
> +--------------+-------------+---------------------------------------+
> > >>>> | priorityname | recpriority | selectclause
> |
> > >>>>
> +--------------+-------------+---------------------------------------+
> > >>>> | CBSnotADP#0 | -50 | channel.mplexid=6 and cardid in
> (1,5) |
> > >>>>
> +--------------+-------------+---------------------------------------+
>
> ...
>
> The fix for Custom Priorities was pushed this afternoon. It should show up
> tomorrow
> and you can restore the above.
>
> --
> Bill
>
> Stephen's suggestion to flip it to a positive rule is just as effective, I
guess what I'm saying is "it aint broke"
Also the other two channel priority rules I flipped to say DO use this
channel instead of DONT use those, so I'm a pretty happy camper, but thanks
for keeping me in mind just the same Bill.