[mythtv-users] Need help debugging python bindings

[Doug Vaughan]

Jack,
    I am not sure what version of Jamu you are running. In your next 
post please include the information from:
 > /where ever Jamu is path/jamu.py -v

    Do you know what type of database engine you are using in MySQL for 
the " mythconverg" data base. I only ask this as a long while ago a user 
had the "InnoDB" engine instead of the usual "MyISAM". Apparently 
"InnoDB" supported database roll-back so every jamu write to the data 
base was being rolled back.
    
    Now this was fixed a long time ago in the Python bindings (since 
Mythtv 0.22+fixes) but I wonder if this is related as no other users do 
not seem to have this issue.
    
    As for debugging information output "-b, --debug Show debugging 
info" but you better be prepared for a lot of output. Assuming you will 
not be using an interactive option like "-I" and "-R" then you should 
pipe the output to a log file. Typically I only use the "-V" (verbose) 
option during problem analysis.
    
Example:
 > /where ever Jamu is path/jamu.py -MWV -d > issue1.log

or

 > /where ever Jamu is path/jamu.py -MV -d > issue2.log

Doug