[mythtv-users] Schedules Direct DataDirect replacement service testing

[Tom Dexter]

On Sun, Oct 5, 2014 at 1:39 PM, Bill Meek <keemllib at gmail.com> wrote:
> On 10/05/2014 12:05 PM, Tom Dexter wrote:
>>
>> On Sun, Oct 5, 2014 at 12:53 PM, Bill Meek <keemllib at gmail.com> wrote:
>>>
>>> On 10/05/2014 11:47 AM, Tom Dexter wrote:
>>> ...
>>>>
>>>>
>>>> One question however:  I'm running 0.27.3.  I was surprised to see
>>>> that my automatic mythfilldatabase runs don't create separate log
>>>> files under /var/log/mythtv.  Is that supposed to happen, or does it
>>>> require changing the parameters used by the mythfilldatabase command?
>>>> It seems crazy that I get separate logs for stuff like mythpreviewgen
>>>> (those drive me nuts BTW) but not for mythfilldatabase.  My backend
>>>> itself is currently set just for -v general.  I'd like to get good
>>>> logging of mythfilldatabase, but I'd rather not enable verbose logging
>>>
>>>
>>>
>>> Use  mythtv-setup page and see if you're using something like:
>>> /usr/bin/mythfilldatabase, as opposed to just mythfilldatabase.
>>>
>>> The full path won't honor the logging parameters passed by the
>>> backend. https://code.mythtv.org/trac/ticket/12169 .
>>>
>>> --
>>> Bill
>>>
>>
>> I have the full path in there as /usr/bin/mythfilldatabase, however
>> currently the only option I have set for the automatic run is
>> --dd-grab-all.
>
>
> That's what I have, without the full path.
>
>> Do I have to add --logpath in there as well to get separate logs under
>> /var/log/mythtv?  Like I said, given that I basically get spammed with
>> logs from mythpreviewgen that sort of seemed strange.
>
>
> You don't need to add --logpath. mythfilldatabase will inherit whatever
> log arguments mythbackend is using. Including those set on-the-fly with:
>
>     mythbackend --setverbose blah and/or mythbackend --setloglevel blah
>
> If you're running the backend with --syslog and have something like
> rsyslog.d/mythtv that creates individual logs, then you'll get logs
> for mythfilldatabase too. If your backend is started with --logpath,
> then that will be passed to mythfilldatabase.
>
>
> --
> Bill
You see...what you're describing is *exactly* what I'd expect and that
is NOT happening.  Here's my running backend from ps right now:

mythtv    6099  1.6  2.3 477608 36884 ?        Ssl  Sep21 339:34
/usr/bin/mythbackend --daemon --pidfile /var/run/mythbackend.pid
--user mythtv --verbose general --logpath /var/log/mythtv/

I'm not using syslog at all.  I get no mythfilldatabase log files in
/var/log/mythtv, even though I get them for mythbackend, mythcommflag,
mythlogserver, mythmetadatalookup,  and mythpreviewgen.  The only
trace I see of any logging from that are these entries in the current
mythbackend log:

grep -i mythfill mythbackend.20140921143057.6099.log
2014-10-05 10:31:58.514102 I [6099/6099] CoreContext
housekeeper.cpp:674 (Run) - Queueing HouseKeeperTask 'MythFillDB'.
2014-10-05 10:31:58.515884 I [6099/6212] HouseKeeping
housekeeper.cpp:133 (Run) - Running HouseKeeperTask 'MythFillDB'.
2014-10-05 10:33:07.021600 I [6099/6151] Scheduler scheduler.cpp:2140
(HandleReschedule) - Reschedule requested for MATCH 0 0 0 -
MythFillDatabase
2014-10-05 10:33:07.471415 I [6099/6212] HouseKeeping
housekeeper.cpp:151 (Run) - HouseKeeperTask 'MythFillDB' Finished
Successfully.

I'm running 0.27.3 under Gentoo.  What on earth am I missing here??

Tom