[mythtv-users] Mythrename.pl suddenly giving error

[Michael T. Dean]

On 08/26/2008 05:43 PM, Bobby Gill wrote:
> Thanks plenty Mike for the clarification, here's the output from when 
> the episode finished recording and it was trying to run Mythrename.pl. 
> So in rxvt, I ran "mythbackend" (after stopping the master backend 
> daemon of course) and here's the output:
>
> 2008-08-26 17:30:05.048 AFD: Opened codec 0xa09a170, id(MPEG2VIDEO) 
> type(Video)
> 2008-08-26 17:30:05.049 AFD: codec MP2 has 2 channels
> 2008-08-26 17:30:05.049 AFD: Opened codec 0xa09a5e0, id(MP2) type(Audio)
> 2008-08-26 17:30:05.303 Preview: Grabbed preview 
> '/media/mythtv/1052_20080826171500.mpg' 720x480 at 109s
> 2008-08-26 17:30:59.520 JobQueue: Started "Mythrename.pl" for "The 
> Fresh Prince of Bel-Air" recorded from channel 1052 at Tue Aug 26 
> 17:15:00 2008
> Password:
> 2008-08-26 17:33:08.940 MainServer::HandleAnnounce Monitor
> 2008-08-26 17:33:08.941 adding: mythbox as a client (events: 0)
> 2008-08-26 17:33:12.239 JobQueue: Finished "Mythrename.pl" for "The 
> Fresh Prince of Bel-Air" recorded from channel 1052 at Tue Aug 26 
> 17:15:00 2008.
> 2008-08-26 17:34:04.556 JobQueue: Started "Commercial Removal" for 
> "The Fresh Prince of Bel-Air" recorded from channel 1052 at Tue Aug 26 
> 17:15:00 2008
> mythcommflag: Rebuilding seek list
> 2008-08-26 17:34:04.913 Using runtime prefix = /usr, libdir = /usr/lib
> 2008-08-26 17:34:04.914 Empty LocalHostName.
> 2008-08-26 17:34:04.946 New DB connection, total: 1
> 2008-08-26 17:34:04.954 Closing DB connection named 'DBManager0'
>
> As you can see it starts the mythrename.pl and prompts me for my root 
> password, which I entered, and a quick ls shows me the file has indeed 
> been successfully renamed. Hope this helps diagnose what's up here, 
> thanks so much :)

Sounds like you configured the user job to use sudo and you didn't 
configure sudo to allow password-less execution of that script 
(NOPASSWD).  When mythbackend is running as a daemon, you can't supply a 
password.  So, either remove the sudo from the user job command line or 
fix the sudo config.

Mike