On 04/30/2006 12:52 PM, Rich Kadel wrote:

>2. Mike - You said:
>
>>You do realize you just upgraded to SVN head, right?  That means you
>>can't (with this database) go back to 0.19 or 0.19-fixes or 0.19.1 (when
>>released), etc.  If you run SVN head, make sure you read the -dev and
>>-commits lists.
>>
>I didn't realize I can't go back, and I'm not 100% sure what this
>means.  Except for CC, so far it seems to be working with 0.19.
>

You're not using 0.19...

>  I'm
>probably OK going back to the SVN version or sticking with 0.19 if one
>option is better.
>

SVN head is "newer" than 0.19.

>  Are there instructions for clearing out the
>database so I can rebuild it?
>  
>

Other than "DROP DATABASE mythconverg;" not really (but don't execute
this command unless you understand the consequences).

The issue is that you're now using "SVN" (more properly called SVN
head--the "newest" version in SVN--as opposed to 0.19-fixes SVN, which
is basically 0.19, but with bug fixes).  When you used SVN head the
first time, it upgraded your database (those were the lines of the log I
pointed out), and there are enough differences in there that 0.19 won't
work properly any more.  Therefore, you have to a) stay with SVN head
(on /all/ your machines, both frontends and backends must have identical
versions), b) use a backup of your database from just before you went to
SVN head to start over, c) start a new database and import recordings
with myth.rebuilddatabase.pl, or d) manually adjust a backup of SVN head
to "undo" the changes that were made since 0.19.

>3. I'm still seeing a lot of this in mythfrontend:
>
>2006-04-30 09:49:33.548 rebuffering (12289 32768)
>2006-04-30 09:49:34.452 rebuffering (2049 32768)
>2006-04-30 09:49:34.708 rebuffering (10241 32768)
>2006-04-30 09:49:35.160 rebuffering (20481 32768)
>2006-04-30 09:49:35.868 rebuffering (20481 32768)
>2006-04-30 09:49:36.388 rebuffering (20481 32768)
>2006-04-30 09:49:36.836 rebuffering (22529 32768)
>2006-04-30 09:49:36.972 rebuffering (30721 32768)
>2006-04-30 09:49:38.328 rebuffering (18433 32768)
>2006-04-30 09:49:38.852 rebuffering (8193 32768)
>
>Someone suggested COMMFLAGGING is too agressive?  It doesn't start
>happening until after I change channels though.
>  
>

If you're not noticing issues when the messages appear, don't worry
about it.  It's just Myth trying to ensure it will be able to play back
the video smoothly.

>4. mythbackend is giving me this error:
>
>2006-04-30 09:44:39.061 Running HouseKeeping
>2006-04-30 09:44:49.501 AutoExpire: ERROR when trying to autoexpire
>file: /var/store/2001_20060429211953.mpg. File doesn't exist.
>Database metadata will not be removed.
>2006-04-30 09:46:49.539 AutoExpire: ERROR when trying to autoexpire
>file: /var/store/2001_20060429211953.mpg. File doesn't exist.
>Database metadata will not be removed.
>2006-04-30 09:48:49.566 AutoExpire: ERROR when trying to autoexpire
>file: /var/store/2001_20060429211953.mpg. File doesn't exist.
>Database metadata will not be removed.
>  
>

You need to delete the metadata for the non-existent file (find the show
in Watch/Delete Recordings and hit D).  Or, you could do:

touch /var/store/2001_20060429211953.mpg

and let the autoexpirer take care of it.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users@myth...
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users