[mythtv-users] Upcoming recordings gone
Bill Meek
keemllib at gmail.com
Sat Oct 30 02:07:26 UTC 2021
On 10/29/21 8:49 PM, Daryl McDonald wrote:
>
>
> On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib at gmail.com <mailto:keemllib at 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 at gmail.com <mailto:keemllib at gmail.com> <mailto:keemllib at gmail.com
> <mailto:keemllib at 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 at mythqml.net <mailto:mythtv at mythqml.net> <mailto:mythtv at mythqml.net
> <mailto:mythtv at mythqml.net>> <mailto:mythtv at mythqml.net <mailto:mythtv at mythqml.net>
> > <mailto:mythtv at mythqml.net <mailto:mythtv at mythqml.net>>>> wrote:
> > >
> > > On 28/10/2021 23:50, Daryl McDonald wrote:
> > >
> > >>
> > >>
> > >> On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <keemllib at gmail.com <mailto:keemllib at gmail.com> <mailto:keemllib at gmail.com
> <mailto:keemllib at gmail.com>> <mailto:keemllib at gmail.com <mailto:keemllib at gmail.com>
> > <mailto:keemllib at gmail.com <mailto:keemllib at 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 at 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 at 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
More information about the mythtv-users
mailing list