[mythtv-users] jobs queuing, not running

jack snodgrass mrlinuxgroups at gmail.com
Tue Oct 24 01:41:00 UTC 2006


On 10/23/06, Chris Pinkham <cpinkham at bc2va.org> wrote:
> * On Mon Oct 23, 2006 at 02:33:59PM -0500, jack snodgrass wrote:
> > > I ran
> > > mythjobqueue -v all
>
> This should be telling you in the logs what the statuses are of the jobs
> it is finding and why it isn't running them.
>
> Let it run for 10-15 minutes (or longer than whatever time you set on
> the JobQueue setup page) and then grep for "JobQueue" in the logs and
> you should see lots of debug info.
>
> --
> Chris
> _______________________________________________

2006-10-23 20:10:42.374 Connecting to backend server: 192.168.1.1:6543
(try 1 of 5)
2006-10-23 20:10:42.374 MythSocket(56da60:5): new socket
2006-10-23 20:10:42.375 MythSocket(56da60:5): attempting connect() to
(192.168.1.1:6543)
2006-10-23 20:10:42.375 MythSocket(56da60:5): state change Idle -> Connected
2006-10-23 20:10:42.376 write ->  5 21      MYTH_PROTO_VERSION 31
2006-10-23 20:10:42.378 read  <-  5 13      ACCEPT[]:[]31
2006-10-23 20:10:42.379 Using protocol version 31
2006-10-23 20:10:42.379 write ->  5 30      ANN Playback amd.private.net 0
2006-10-23 20:10:42.381 read  <-  5 2       OK
2006-10-23 20:10:42.382 MythSocket(56df90:4): attempting connect() to
(192.168.1.1:6543)
2006-10-23 20:10:42.391 MythSocket(56df90:4): state change Idle -> Connected
2006-10-23 20:10:42.391 write ->  4 29      ANN Monitor amd.private.net 1
2006-10-23 20:10:42.394 read  <-  4 2       OK
2006-10-23 20:10:42.395 MythSocket(56df90:4): UpRef: 1
2006-10-23 20:10:42.396 MythSocket: readyread thread start
2006-10-23 20:10:42.396 MSqlQuery: SELECT data FROM settings WHERE
value = 'JobQueueCPU' AND hostname = 'amd.private.net' ;
2006-10-23 20:11:12.690 MythSocket(56df90:4): socket is readable
2006-10-23 20:11:12.690 MythSocket(56df90:4): cb->readyRead()
2006-10-23 20:11:12.690 read  <-  4 51
BACKEND_MESSAGE[]:[]RECORDING_LIST_CHANGE[]:[]empty
2006-10-23 20:11:12.690 MythEvent: RECORDING_LIST_CHANGE
2006-10-23 20:11:19.654 MythSocket(56df90:4): socket is readable
2006-10-23 20:11:19.654 MythSocket(56df90:4): cb->readyRead()
2006-10-23 20:11:19.654 read  <-  4 51
BACKEND_MESSAGE[]:[]RECORDING_LIST_CHANGE[]:[]empty
2006-10-23 20:11:19.654 MythEvent: RECORDING_LIST_CHANGE
2006-10-23 20:11:23.108 MythSocket(56df90:4): socket is readable
2006-10-23 20:11:23.108 MythSocket(56df90:4): cb->readyRead()
2006-10-23 20:11:23.108 read  <-  4 45
BACKEND_MESSAGE[]:[]SCHEDULE_CHANGE[]:[]empty
2006-10-23 20:11:23.108 MythEvent: SCHEDULE_CHANGE
2006-10-23 20:32:05.405 MythSocket(56df90:4): socket is readable
2006-10-23 20:32:05.405 MythSocket(56df90:4): cb->readyRead()
2006-10-23 20:32:05.405 read  <-  4 51
BACKEND_MESSAGE[]:[]DONE_RECORDING 1 1856[]:[]empty
2006-10-23 20:32:05.405 MythEvent: DONE_RECORDING 1 1856
2006-10-23 20:32:05.711 MythSocket(56df90:4): socket is readable
2006-10-23 20:32:05.711 MythSocket(56df90:4): cb->readyRead()
2006-10-23 20:32:05.711 read  <-  4 51
BACKEND_MESSAGE[]:[]RECORDING_LIST_CHANGE[]:[]empty
2006-10-23 20:32:05.712 MythEvent: RECORDING_LIST_CHANGE
2006-10-23 20:32:05.845 MythSocket(56df90:4): socket is readable
2006-10-23 20:32:05.845 MythSocket(56df90:4): cb->readyRead()
2006-10-23 20:32:05.845 read  <-  4 45
BACKEND_MESSAGE[]:[]SCHEDULE_CHANGE[]:[]empty
2006-10-23 20:32:05.845 MythEvent: SCHEDULE_CHANGE

... you'd think it would show something useful.... I don't see any
attempts at running mythcommflag on my box. I have 4 commerical
flag jobs in my job queue.

jack


More information about the mythtv-users mailing list