[mythtv-users] backend still running old user job command line after I changed it

[Stephen Worthington]

On Sun, 13 May 2018 20:41:49 -0500, you wrote:

>On 05/13/2018 07:39 PM, Ian Evans wrote:
>> Was having a problem with mythvidexport.py not exporting one recording.
>> 
>> I decided to increase the logging and changed my user job command line from:
>> 
>> /usr/share/mythtv/mythvidexport.py --delete %VERBOSEMODE% %JOBID%
>> 
>> to:
>> 
>> /usr/share/mythtv/mythvidexport.py --delete --syslog local7 --loglevel
>> debug
>> --verbose all %JOBID%
>> 
>> I restarted the backend and restarted the frontend and ran the job again.
>> However, the log showed it was running the old command line:
>> 
>> May 13 20:31:54 buster mythbackend: mythbackend[1385]: E UserJob_56023
>> jobqueue.cpp:2445 (DoUserJobThread) JobQueue: User Job
>> '/usr/share/mythtv/mythvidexport.py --delete  --verbose general --loglevel
>> info --quiet --syslog local7 56023' failed.
>> 
>> 
>> Running setup again, I could see the command line was the new one I had put
>> in. So why would the logs show it running the old one?
>
>Without seeing the actual commands and output, I can only guess that the initial
>restart of the backend didn't take.
>
>The settings are cached, so you can really get by with just doing a:
>mythutil --clearcache [-q -q] rather that restarting the BE.
>
>Or, your original command line is fine. Just do: mythbackend --setverbose all.
>Then when the backend starts your UserJob, the options will be passed. I'd
>suggest adding ,norefcount to cut down on the noise from all.

How are you starting and stopping mythbackend?  On a systemd system,
the old ways of doing that no longer work properly.  The correct
commands for a systemd system are:

systemctl start mythtv-backend
systemclt stop mythtv-backend

and restarting is:

systemctl restart mythtv-backend

To see what mythbackend's status is:

systemctl status mythtv-backend