Mailing List Archive

On Thu, Jan 6, 2022 at 9:49 AM James Abernathy <jfabernathy@gmail.com>
wrote:

> On my test mythtv- BE/FE combo on Archlinux with Master pre32 3305 I
> noticed that over the last several days the Schedules Direct EPG has not
> updated. I can sudo su mythtv and run it and the guide is updated but it
> doesn't seem to be running automatically. I have mythtv-setup set the way I
> would normally for Ubuntu so It should be updating between 0 and 5am, but
> isn't. I just rebooted to see if that would help overnight.
>

I'm still having this issue with mythfilldatabase not running
automatically, even if I reboot the PC. I have the backend settings to run
mythfilldatabase at the SchedulesDirect recommended times, but I have
tired picking a range of times. I know this is Arch, but I don't thing
there is a service for this and it's part of the mythtv-backend.service??

Jim A

On Wed, 12 Jan 2022 07:16:14 -0500, you wrote:

>On Thu, Jan 6, 2022 at 9:49 AM James Abernathy <jfabernathy@gmail.com>
>wrote:
>
>> On my test mythtv- BE/FE combo on Archlinux with Master pre32 3305 I
>> noticed that over the last several days the Schedules Direct EPG has not
>> updated. I can sudo su mythtv and run it and the guide is updated but it
>> doesn't seem to be running automatically. I have mythtv-setup set the way I
>> would normally for Ubuntu so It should be updating between 0 and 5am, but
>> isn't. I just rebooted to see if that would help overnight.
>>
>
>I'm still having this issue with mythfilldatabase not running
>automatically, even if I reboot the PC. I have the backend settings to run
>mythfilldatabase at the SchedulesDirect recommended times, but I have
>tired picking a range of times. I know this is Arch, but I don't thing
>there is a service for this and it's part of the mythtv-backend.service??
>
>Jim A

So what do all your mythfilldatabase settings look like? These are
from my mother's MythTV box, which runs mythfilldatabase automatically
from mythbackend at 16:00 each day:

MariaDB [mythconverg]> select * from settings where value like
'mythfill%';
+---------------------------------+---------------------------+----------+
| value | data | hostname |
+---------------------------------+---------------------------+----------+
| MythFillDatabaseArgs | --only-update-guide | NULL |
| mythfilldatabaseLastRunEnd | 2022-01-12T03:00:51Z | NULL |
| mythfilldatabaseLastRunStart | 2022-01-12T03:00:51Z | NULL |
| mythfilldatabaseLastRunStatus | Successful. | NULL |
| MythFillDatabaseLog | /var/log/mythtv | NULL |
| MythFillDatabasePath | /usr/bin/mythfilldatabase | NULL |
| MythFillEnabled | 1 | NULL |
| MythFillFixProgramIDsHasRunOnce | 1 | crw-pvr |
| MythFillFixProgramIDsHasRunOnce | 1 | crw-pvr |
| MythFillGrabberSuggestsTime | 0 | NULL |
| MythFillMaxHour | 16 | NULL |
| MythFillMinHour | 16 | NULL |
| MythFillPeriod | 1 | NULL |
| MythFillSuggestedRunTime | 2022-01-13T03:00:51Z | NULL |
+---------------------------------+---------------------------+----------+
14 rows in set (0.000 sec)

And these are from my MythTV box where mythfilldatabase is run
externally from a user cron job at 15:10 each day:

MariaDB [mythconverg]> select * from settings where value like
'mythfill%';
+---------------------------------+---------------------------+----------+
| value | data | hostname |
+---------------------------------+---------------------------+----------+
| MythFillDatabaseArgs | --only-update-guide | NULL |
| mythfilldatabaseLastRunEnd | 2022-01-12T02:11:32Z | NULL |
| mythfilldatabaseLastRunStart | 2022-01-12T02:11:30Z | NULL |
| mythfilldatabaseLastRunStatus | Successful. | NULL |
| MythFillDatabaseLog | /var/log/mythtv | NULL |
| MythFillDatabasePath | /usr/bin/mythfilldatabase | NULL |
| MythFillEnabled | 0 | NULL |
| MythFillFixProgramIDsHasRunOnce | 1 | mypvr |
| MythFillGrabberSuggestsTime | 1 | NULL |
| MythFillMaxHour | 23 | NULL |
| MythFillMinHour | | NULL |
| MythFillPeriod | 1 | NULL |
| MythFillSuggestedRunTime | 2022-01-13T02:11:30Z | NULL |
+---------------------------------+---------------------------+----------+
13 rows in set (0.002 sec)
_______________________________________________
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

On Wed, Jan 12, 2022 at 8:45 AM Stephen Worthington <
stephen_agent@jsw.gen.nz> wrote:

> On Wed, 12 Jan 2022 07:16:14 -0500, you wrote:
>
> >On Thu, Jan 6, 2022 at 9:49 AM James Abernathy <jfabernathy@gmail.com>
> >wrote:
> >
> >> On my test mythtv- BE/FE combo on Archlinux with Master pre32 3305 I
> >> noticed that over the last several days the Schedules Direct EPG has not
> >> updated. I can sudo su mythtv and run it and the guide is updated but
> it
> >> doesn't seem to be running automatically. I have mythtv-setup set the
> way I
> >> would normally for Ubuntu so It should be updating between 0 and 5am,
> but
> >> isn't. I just rebooted to see if that would help overnight.
> >>
> >
> >I'm still having this issue with mythfilldatabase not running
> >automatically, even if I reboot the PC. I have the backend settings to run
> >mythfilldatabase at the SchedulesDirect recommended times, but I have
> >tired picking a range of times. I know this is Arch, but I don't thing
> >there is a service for this and it's part of the mythtv-backend.service??
> >
> >Jim A
>
> So what do all your mythfilldatabase settings look like? These are
> from my mother's MythTV box, which runs mythfilldatabase automatically
> from mythbackend at 16:00 each day:
>
> MariaDB [mythconverg]> select * from settings where value like
> 'mythfill%';
> +---------------------------------+---------------------------+----------+
> | value | data | hostname |
> +---------------------------------+---------------------------+----------+
> | MythFillDatabaseArgs | --only-update-guide | NULL |
> | mythfilldatabaseLastRunEnd | 2022-01-12T03:00:51Z | NULL |
> | mythfilldatabaseLastRunStart | 2022-01-12T03:00:51Z | NULL |
> | mythfilldatabaseLastRunStatus | Successful. | NULL |
> | MythFillDatabaseLog | /var/log/mythtv | NULL |
> | MythFillDatabasePath | /usr/bin/mythfilldatabase | NULL |
> | MythFillEnabled | 1 | NULL |
> | MythFillFixProgramIDsHasRunOnce | 1 | crw-pvr |
> | MythFillFixProgramIDsHasRunOnce | 1 | crw-pvr |
> | MythFillGrabberSuggestsTime | 0 | NULL |
> | MythFillMaxHour | 16 | NULL |
> | MythFillMinHour | 16 | NULL |
> | MythFillPeriod | 1 | NULL |
> | MythFillSuggestedRunTime | 2022-01-13T03:00:51Z | NULL |
> +---------------------------------+---------------------------+----------+
> 14 rows in set (0.000 sec)
>
> And these are from my MythTV box where mythfilldatabase is run
> externally from a user cron job at 15:10 each day:
>
> MariaDB [mythconverg]> select * from settings where value like
> 'mythfill%';
> +---------------------------------+---------------------------+----------+
> | value | data | hostname |
> +---------------------------------+---------------------------+----------+
> | MythFillDatabaseArgs | --only-update-guide | NULL |
> | mythfilldatabaseLastRunEnd | 2022-01-12T02:11:32Z | NULL |
> | mythfilldatabaseLastRunStart | 2022-01-12T02:11:30Z | NULL |
> | mythfilldatabaseLastRunStatus | Successful. | NULL |
> | MythFillDatabaseLog | /var/log/mythtv | NULL |
> | MythFillDatabasePath | /usr/bin/mythfilldatabase | NULL |
> | MythFillEnabled | 0 | NULL |
> | MythFillFixProgramIDsHasRunOnce | 1 | mypvr |
> | MythFillGrabberSuggestsTime | 1 | NULL |
> | MythFillMaxHour | 23 | NULL |
> | MythFillMinHour | | NULL |
> | MythFillPeriod | 1 | NULL |
> | MythFillSuggestedRunTime | 2022-01-13T02:11:30Z | NULL |
> +---------------------------------+---------------------------+----------+
> 13 rows in set (0.002 sec)
>

Here are my settings:
select * from settings where value like
-> 'mythfill%';
+-------------------------------+--------------------------------------------------------------------------------------------------------------
---------------------------+----------+
| value | data

| hostname |
+-------------------------------+--------------------------------------------------------------------------------------------------------------
---------------------------+----------+
| mythfilldatabaseLastRunEnd | 2022-01-10T21:03:37Z

| NULL |
| mythfilldatabaseLastRunStart | 2022-01-10T21:02:42Z

| NULL |
| mythfilldatabaseLastRunStatus | mythfilldatabase ran, but did not insert
any new data into the Guide for 1 of 1 sources. This can indicate a
potential grabber failure. | NULL |
| MythFillDatabasePath | mythfilldatabase

| NULL |
| MythFillEnabled | 1

| NULL |
| MythFillGrabberSuggestsTime | 0

| NULL |
| MythFillMaxHour | 5

| NULL |
| MythFillMinHour | 0

| NULL |
| MythFillSuggestedRunTime | 2022-01-11T21:02:42Z

| NULL |
+-------------------------------+--------------------------------------------------------------------------------------------------------------
---------------------------+----------+
9 rows in set (0.001 sec)

On 12/01/2022 20:16, James Abernathy wrote:
> On Thu, Jan 6, 2022 at 9:49 AM James Abernathy <jfabernathy@gmail.com>
> wrote:
>
> On my test mythtv- BE/FE combo on Archlinux with Master pre32 3305
> I noticed that over the last several days the Schedules Direct EPG
> has not updated.  I can sudo su mythtv and run it and the guide is
> updated but it doesn't seem to be running automatically. I have
> mythtv-setup set the way I would normally for Ubuntu so It should
> be updating between 0 and 5am, but isn't. I just rebooted to see
> if that would help overnight.
>
>
> I'm still having this issue with mythfilldatabase not running
> automatically, even if I reboot the PC. I have the backend settings to
> run mythfilldatabase  at the SchedulesDirect recommended times, but I
> have tired picking a range of times.  I know this is Arch, but I don't
> thing there is a service for this and it's part of the
> mythtv-backend.service??
>
I could not get it to work either, gave up and just ran it from cron.

as mythtv user
00 03 * * * /home/mythtv/run_mythfilldatabase.sh


#!/bin/bash

logger -i "exiting run_mythfilldatabase.sh"

cd $HOME

exec >> ~/run_mythfilldatabase.log
exec 2>&1

#UK stuff
#/usr/bin/mythfilldatabase --sourceid 3 --file --xmlfile /backup/sd.xml
#/usr/bin/mythfilldatabase --sourceid 5 --file --xmlfile /backup/sd.xml

/usr/bin/tv_grab_zz_sdjson --output SD.xml
/usr/bin/mythfilldatabase --sourceid 8 --file --xmlfile SD.xml

--
'ooroo

Stinga...(:)-)
---------------------------------------------------
Email: stinga+mythtv@wolf-rock.com o
You need only two tools. o /////
A hammer and duct tape. If it /@ `\ /) ~
doesn't move and it should use > (O) X< ~ Fish!!
the hammer. If it moves and `\___/' \) ~
shouldn't, use the tape. \\\
---------------------------------------------------

_______________________________________________
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

On Wed, Jan 12, 2022 at 9:13 AM stinga <stinga+mythtv@wolf-rock.com> wrote:

> On 12/01/2022 20:16, James Abernathy wrote:
> > On Thu, Jan 6, 2022 at 9:49 AM James Abernathy <jfabernathy@gmail.com>
> > wrote:
> >
> > On my test mythtv- BE/FE combo on Archlinux with Master pre32 3305
> > I noticed that over the last several days the Schedules Direct EPG
> > has not updated. I can sudo su mythtv and run it and the guide is
> > updated but it doesn't seem to be running automatically. I have
> > mythtv-setup set the way I would normally for Ubuntu so It should
> > be updating between 0 and 5am, but isn't. I just rebooted to see
> > if that would help overnight.
> >
> >
> > I'm still having this issue with mythfilldatabase not running
> > automatically, even if I reboot the PC. I have the backend settings to
> > run mythfilldatabase at the SchedulesDirect recommended times, but I
> > have tired picking a range of times. I know this is Arch, but I don't
> > thing there is a service for this and it's part of the
> > mythtv-backend.service??
> >
> I could not get it to work either, gave up and just ran it from cron.
>
> as mythtv user
> 00 03 * * * /home/mythtv/run_mythfilldatabase.sh
>
>
> #!/bin/bash
>
> logger -i "exiting run_mythfilldatabase.sh"
>
> cd $HOME
>
> exec >> ~/run_mythfilldatabase.log
> exec 2>&1
>
> #UK stuff
> #/usr/bin/mythfilldatabase --sourceid 3 --file --xmlfile /backup/sd.xml
> #/usr/bin/mythfilldatabase --sourceid 5 --file --xmlfile /backup/sd.xml
>
> /usr/bin/tv_grab_zz_sdjson --output SD.xml
> /usr/bin/mythfilldatabase --sourceid 8 --file --xmlfile SD.xml
>
> --
> 'ooroo
>
> Stinga...(:)-)
> ---------------------------------------------------
> Email: stinga+mythtv@wolf-rock.com o
> You need only two tools. o /////
> A hammer and duct tape. If it /@ `\ /) ~
> doesn't move and it should use > (O) X< ~ Fish!!
> the hammer. If it moves and `\___/' \) ~
> shouldn't, use the tape. \\\
> ---------------------------------------------------
>
> I was going to set up a systemd timer to run it as mythtv, but I was just
wondering how the Ubuntu packaging set it up so it always works. It's not
a big deal as this is a test system, but I'm learning that the packaging in
the Ubuntu version of mythtv fixes a lot of stuff.

Jim A

On 1/12/22 7:56 AM, James Abernathy wrote:

MythFillDatabaseLog doesn't exist, at least in the v32Pre code base, harmless

MythFillDatabasePath must be mythfilldatabase, any other value, like a full
path name will *prevent* mythfilldatabase logging.

MythFillFixProgramIDsHasRunOnce, I've only got one. Probably harmless.

MythFillMaxHour and Min are the same, that looks like a change just for
testing. Not the original 0-5AM.

I'd also look at the timestamps in housekeeping:

mysql> SELECT * FROM housekeeping WHERE tag='MythFillDB';
+------------+----------+---------------------+---------------------+
| tag | hostname | lastrun | lastsuccess |
+------------+----------+---------------------+---------------------+
| MythFillDB | NULL | 2022-01-12 09:00:02 | 2022-01-12 09:00:02 |
+------------+----------+---------------------+---------------------+

Once MythFillDatabasePath is corrected, I'd run the backend with -v system,xmltv
and there may be clues in the mythfilldatabase.log (or wherever you log to).

--
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

On Wed, Jan 12, 2022 at 10:38 AM Bill Meek <keemllib@gmail.com> wrote:

> On 1/12/22 7:56 AM, James Abernathy wrote:
> |
> |
> |
> |
> |
> |
> |
> |
>
> MythFillDatabaseLog doesn't exist, at least in the v32Pre code base,
> harmless
>
> MythFillDatabasePath must be mythfilldatabase, any other value, like a full
> path name will *prevent* mythfilldatabase logging.
>
> MythFillFixProgramIDsHasRunOnce, I've only got one. Probably harmless.
>
> MythFillMaxHour and Min are the same, that looks like a change just for
> testing. Not the original 0-5AM.
>
> I'd also look at the timestamps in housekeeping:
>
> mysql> SELECT * FROM housekeeping WHERE tag='MythFillDB';
> +------------+----------+---------------------+---------------------+
> | tag | hostname | lastrun | lastsuccess |
> +------------+----------+---------------------+---------------------+
> | MythFillDB | NULL | 2022-01-12 09:00:02 | 2022-01-12 09:00:02 |
> +------------+----------+---------------------+---------------------+
>
> Once MythFillDatabasePath is corrected, I'd run the backend with -v
> system,xmltv
> and there may be clues in the mythfilldatabase.log (or wherever you log
> to).
>
> --
> Bill
>

I took a look at the mythtv-backend.service file and fixed the logging from
syslog to systemd-journal and added the -v system,xmltv.

I found some odd things about the grabbers. I get an error on
tv_grab_zz_sdjson_sqlite when it runs from the backend service, but I do
not get the error if I run it manually as user 'mythtv'.

I wonder if the backend has a hard coded path for the grabbers and not
using the default path. My path puts the grabbers at:
/usr/bin/site_perl/tv_grab_zz_sdjson_sqlite
which is where the xmltv make install puts it under arch linux.

Jan 12 11:58:38 den-pc mythbackend[4235]: Managed child (PID: 4289) has
started! * command=/usr/bin/mythfilldatabase --verbose general,system,xml
tv --loglevel info --systemd-journal --quiet, timeout=0
Jan 12 11:58:38 den-pc mythbackend[4235]: Starting IO manager (read)
Jan 12 11:58:38 den-pc mythbackend[4235]: Starting process signal handler
Jan 12 11:58:38 den-pc mythbackend[4235]: Starting IO manager (write)
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: mythfilldatabase version:
master [v32-Pre-3361-gba401e1ea9] www.mythtv.org
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Qt version: compile: 5.15.2,
runtime: 5.15.2
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Arch Linux (x86_64)
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Enabled verbose msgs:
general system xmltv
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setting Log Level to
LOG_INFO
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setup Interrupt handler
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Added logging to the console
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setup Terminated handler
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setup Segmentation fault
handler
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setup Aborted handler
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setup Bus error handler
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setup Floating point
exception handler
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setup Illegal instruction
handler
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setup Real-time signal 0
handler
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Setup Hangup handler
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Using runtime prefix = /usr
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Using configuration
directory = /home/mythtv/.mythtv
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Assumed character encoding:
en_US.UTF-8
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Empty LocalHostName. This is
typical.
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Using a profile name of:
'den-pc' (Usually the same as this host's name.)
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Start up testing
connections. DB localhost, BE , attempt 0, status dbAwake, Delay: 2000
Jan 12 11:58:38 den-pc mythfilldatabase[4289]: Added journal logging
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Setting QT default locale to
en_US
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Current locale en_US
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Reading locale defaults from
/usr/share/mythtv//locales/en_us.xml
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: PowerDBus: Failed to delay
sleep,shutdown: Permission denied
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: PowerDBus: Added
UPower.Device '/org/freedesktop/UPower/devices/mouse_hidpp_battery_0'
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Power: On AC power
Jan 12 11:58:39 den-pc mythbackend[4235]: 2022-01-12 11:58:39.701231 I
MainServer: MainServer::ANN Playback
Jan 12 11:58:39 den-pc mythbackend[4235]: 2022-01-12 11:58:39.701238 I
MainServer: adding: den-pc(556d85a4d430) as a client (events: 0)
Jan 12 11:58:39 den-pc mythbackend[4235]: MainServer: MainServer::ANN
Playback
Jan 12 11:58:39 den-pc mythbackend[4235]: MainServer: adding:
den-pc(556d85a4d430) as a client (events: 0)
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Power: Supported actions:
None
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Loading en_us translation
for module mythfrontend
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Current MythTV Schema
Version (DBSchemaVer): 1372
Jan 12 11:58:39 den-pc mythfilldatabase[4289]:
MythCoreContext::ConnectCommandSocket(): Connecting to backend server:
192.168.0.100:6543 (try 1 o
f 1)
Jan 12 11:58:39 den-pc mythfilldatabase[4289]:
MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Opening blocking connection
to master backend
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Updating source #1 (SD) with
grabber tv_grab_zz_sdjson_sqlite
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Found 30 channels for source
1 which use grabber
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Starting process manager
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Starting process signal
handler
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Starting IO manager (read)
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Starting IO manager (write)
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Managed child (PID: 4305)
has started! * command=tv_grab_zz_sdjson_sqlite --capabilities, timeout=
25
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Managed child (PID: 4305)
has exited! command=tv_grab_zz_sdjson_sqlite --capabilities, status=3251
2, result=127
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: tv_grab_zz_sdjson_sqlite
--capabilities failed or we timed out waiting. You may need to upgrade y
our xmltv grabber
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Grabbing XMLTV data using
tv_grab_zz_sdjson_sqlite is not supported. You may need to upgrade to th
e latest version of XMLTV.
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Data fetching complete.
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Adjusting program database
end times.
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: 0 replacements made
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Marking generic episodes.
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Found 0
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Extending non-unique
programids with multiple parts.
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Found 0
Jan 12 11:58:39 den-pc mythfilldatabase[4289]: Fixing missing original
airdates.
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Found 0 with programids
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Found 0 without
programids
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Marking repeats.
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Found 0
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Unmarking new episode
rebroadcast repeats.
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Found 0
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Marking episode first
showings.
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Found 15971
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Marking episode last
showings.
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Found 15965
Jan 12 11:58:40 den-pc mythfilldatabase[4289]:

===============================================================

| Attempting to contact the
master backend for rescheduling. |
| If the master is not
running, rescheduling will happen when |
| the master backend is
restarted. |

===============================================================

Jan 12 11:58:40 den-pc mythfilldatabase[4289]: mythfilldatabase run
complete.
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: PowerDBus: Closing
interfaces
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Waiting for threads to exit.
Jan 12 11:58:40 den-pc mythfilldatabase[4289]: Exiting

On 1/12/22 11:08 AM, James Abernathy wrote:
> I wonder if the backend has a hard coded path for the grabbers and not
> using the default path. My path puts the grabbers at:
> /usr/bin/site_perl/tv_grab_zz_sdjson_sqlite
> which is where the xmltv make install puts it under arch linux

Guessing that /usr/bin/site_perl isn't in the backend's PATH.

I'd copy it to /usr/bin and try again.

At least my grabber name is just the file, not a full path:

mysql --user=mythtv --password=yourPW mythconverg --execute="SELECT xmltvgrabber FROM videosource"

--
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

On Thu, Jan 13, 2022 at 5:47 PM Bill Meek <keemllib@gmail.com> wrote:

> On 1/12/22 11:08 AM, James Abernathy wrote:
> > I wonder if the backend has a hard coded path for the grabbers and not
> > using the default path. My path puts the grabbers at:
> > /usr/bin/site_perl/tv_grab_zz_sdjson_sqlite
> > which is where the xmltv make install puts it under arch linux
>
> Guessing that /usr/bin/site_perl isn't in the backend's PATH.
>
> I'd copy it to /usr/bin and try again.
>
> At least my grabber name is just the file, not a full path:
>
> mysql --user=mythtv --password=yourPW mythconverg --execute="SELECT
> xmltvgrabber FROM videosource"
>
> --
> Bill
>

I took the coward's way out and installed Kubuntu 21.10 and then the ppa
for mythbuntu. I grew tired of all the little things that are so different
on Archlinux. I learned a lot, but in the long run Ubuntu is where you
should be for ease of use for MythTV, IMHO.

Thanks for your assistance.

Jim A

On Wed, Jan 12, 2022 at 09:37:36AM -0600, Bill Meek wrote:
> On 1/12/22 7:56 AM, James Abernathy wrote:
> > | MythFillDatabaseLog? ? ? ? ? ? ?| /var/log/mythtv? ? ? ? ? ?| NULL? ? ?|
> > | MythFillDatabasePath? ? ? ? ? ? | /usr/bin/mythfilldatabase | NULL? ? ?|

> MythFillDatabasePath must be mythfilldatabase, any other value, like a full
> path name will *prevent* mythfilldatabase logging.

OMG thanks for sharing those details I had the full path and could not figure out
WTF was wrong for the last 1+ years after I set up things again (or maybe when I had
to switch to another grabber).

"Path" is such the wrong word to use there, and the GUI does not seem to specify
that it should not be the full path.

-- Patrick

_______________________________________________
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

On 1/22/22 12:33, Patrick Mansfield via mythtv-users wrote:
> On Wed, Jan 12, 2022 at 09:37:36AM -0600, Bill Meek wrote:
>> On 1/12/22 7:56 AM, James Abernathy wrote:
>>> | MythFillDatabaseLog� � � � � � �| /var/log/mythtv� � � � � �| NULL� � �|
>>> | MythFillDatabasePath� � � � � � | /usr/bin/mythfilldatabase | NULL� � �|
>
>> MythFillDatabasePath must be mythfilldatabase, any other value, like a full
>> path name will *prevent* mythfilldatabase logging.
>
> OMG thanks for sharing those details I had the full path and could not figure out
> WTF was wrong for the last 1+ years after I set up things again (or maybe when I had
> to switch to another grabber).
>
> "Path" is such the wrong word to use there, and the GUI does not seem to specify
> that it should not be the full path.
>
> -- Patrick

The help text is good, but I admit that long ago I created a ticket in Trac for
the issue. But there had already been debate about the security of putting a
full path there. The program-name-only won.

"Use 'mythfilldatabase' or the name of a custom script that will populate
the program guide info for all your video sources."

--
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

We can add another sentence to the help text, e.g. "Do NOT use a full or
partial path name, only the name of an executable." I think there is just
enough space for that. Of course, this does not help against the confusion
when reading names from the settings table and drawing conclusions from
them.

Klaas.

On Sat, 22 Jan 2022 at 21:03, Bill Meek <keemllib@gmail.com> wrote:

> On 1/22/22 12:33, Patrick Mansfield via mythtv-users wrote:
> > On Wed, Jan 12, 2022 at 09:37:36AM -0600, Bill Meek wrote:
> >> On 1/12/22 7:56 AM, James Abernathy wrote:
> >>> | MythFillDatabaseLog� � � � � � �| /var/log/mythtv�
> � � � � �| NULL� � �|
> >>> | MythFillDatabasePath� � � � � � |
> /usr/bin/mythfilldatabase | NULL� � �|
> >
> >> MythFillDatabasePath must be mythfilldatabase, any other value, like a
> full
> >> path name will *prevent* mythfilldatabase logging.
> >
> > OMG thanks for sharing those details I had the full path and could not
> figure out
> > WTF was wrong for the last 1+ years after I set up things again (or
> maybe when I had
> > to switch to another grabber).
> >
> > "Path" is such the wrong word to use there, and the GUI does not seem to
> specify
> > that it should not be the full path.
> >
> > -- Patrick
>
> The help text is good, but I admit that long ago I created a ticket in
> Trac for
> the issue. But there had already been debate about the security of putting
> a
> full path there. The program-name-only won.
>
> "Use 'mythfilldatabase' or the name of a custom script that will populate
> the program guide info for all your video sources."
>
> --
> 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
>

On 01/22/2022 05:29 PM, Klaas de Waal wrote:
> We can add another sentence to the help text, e.g. "Do NOT use a full
> or partial path name, only the name of an executable." I think there
> is just enough space for that. Of course, this does not help against
> the confusion when reading names from the settings table and drawing
> conclusions from them.

But it can (and, if not in the PATH of the user running mythbackend,
should) be a full path for anything that is not the "built-in"
mythfilldatabase executable (if some user wants to run a value-added or
workaround script). Perhaps better would be to change the special value
"mythfilldatabase" to "default" or "built in", which is more easily
understandable to be a special value saying there's no need to use any
special program for it rather than using mythfilldatabase, which is also
the name of a program/executable, as that special value.

Mike
_______________________________________________
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