BMT 4.8 / Phoenix 2.2 - The Metadata Fixes

[stuckless]

Originally Posted by dead_ferrets

That did it! Very much obliged for your help Sean.

I'm glad it's working.

[dead_ferrets]

Me too! I love this community. So many talented folks like yourself make this product so much better! Thanks again!

[nissse]

Originally Posted by stuckless

In looking at your SageTV classpath, I can see that you've upgraded from 6 to 7. Did you run the BMT upgrade tool that was posted in the sticky? If you did, then for some reason, it did not correctly clean out some jars... here's a list of you jars... I've bolded the ones that you need to remove, manually.

C:\Program Files\SageTV\SageTV\
C:\Program Files\SageTV\SageTV\plugin.jar
C:\Program Files\SageTV\SageTV\Sage.jar
C:\Program Files\SageTV\SageTV\xerces.jar
JARs\ant-1.6.5.jar
JARs\commons-codec-1.3.jar
JARs\commons-dbutils-1.3.jar
JARs\commons-io-1.4.jar
JARs\commons-jxpath-1.1.jar
JARs\commons-lang-2.4.jar
JARs\commons-logging-1.1.1.jar
JARs\commons-net-1.4.1.jar
JARs\commons-vfs-20070823.jar
JARs\core-3.1.1.jar
JARs\dom4j-1.6.1.jar
JARs\gkusnick.sagetv.jar
JARs\h2-1.2.139.jar
JARs\htmlparser-1.6.jar
JARs\htmlparser.jar
JARs\InControl_1.3.6.jar
JARs\jcifs-1.1.6.jar
JARs\jdic.jar
JARs\jetty-6.1.19.jar
JARs\jetty-ajp-6.1.19.jar
JARs\jetty-rewrite-handler-6.1.19.jar
JARs\jetty-sslengine-6.1.19.jar
JARs\jetty-starter.jar
JARs\jetty-util-6.1.19.jar
JARs\json.jar
JARs\jsp-2.1.jar
JARs\jsp-2.1-jetty-6.1.19.jar
JARs\jsp-api-2.1.jar
JARs\log4j-1.2.15.jar
JARs\lucene-core-2.3.2.jar
JARs\lucene-core-3.0.1.jar
JARs\metadata-updater.jar
JARs\nielm_sageutls.jar
JARs\nielm_sagewebserver.jar
JARs\nielm_sagexmlinfo.jar
JARs\phoenix.jar
JARs\sagex-api.jar
JARs\sagex.api.jar (note: remove the sagex dot api not the sagex dash api)
JARs\sagex-h2.jar
JARs\sbbi-upnplib-1.0.3.jar
JARs\servlet-api-2.5-6.1.19.jar
JARs\servlet.jar
JARs\sqlitejdbc-v056.jar
JARs\vecmath.jar

There are some duplicate Jetty jars in there as well, but that's not my area, so I'm not sure if they should be there or not.

Once you remove those jars, you'll need to restart the sagetv server.

After i run the BMT upgrade tool that was posted in the sticky. The only jar file left that i removed manauly was JARs\commons-vfs-20070823.jar

I still have the same problem after a restart =(
Please check you email metadatatools at gmail dot com

[stuckless]

Originally Posted by nissse

After i run the BMT upgrade tool that was posted in the sticky. The only jar file left that i removed manauly was JARs\commons-vfs-20070823.jar

I still have the same problem after a restart =(
Please check you email metadatatools at gmail dot com

Could you email another set of logs, so that I can review that the jars are correct, and see if there are any other issues, that I might have missed. Thing is, there's no point in me even looking at the other logs if there are duplicate jars, etc, since things will not run if there are dups in there. If I see that the jars look correct then i can start looking through the the other logs to see if anything stands out.

[nissse]

First i like to thank you for taking the time to look at my logs.
I have mailed you the new logfiles and some other info.

[dead_ferrets]

Hmmm... During the course of the upgrade something odd seems to have happened.

A number of TV shows that were recorded by SageTV no longer appear in the TV recordings menu. When I use the BMT webUI I see that they are flagged as missing metadata and they are no longer marked as SageTV recordings?

Do I have to go through each one and reset the TV flag? Or could I just reload the Wiz.bin back up?

[stuckless]

Originally Posted by dead_ferrets

Hmmm... During the course of the upgrade something odd seems to have happened.

A number of TV shows that were recorded by SageTV no longer appear in the TV recordings menu. When I use the BMT webUI I see that they are flagged as missing metadata and they are no longer marked as SageTV recordings?

Do I have to go through each one and reset the TV flag? Or could I just reload the Wiz.bin back up?

This isn't a BMT issue. I'm not sure why an upgrade would cause the wiz.bin to forget about some recordings. If you have the old wiz.bin, then you can try to upgrade again. I think the preferred way to upgrade sage7 is simply to install over top of the existing.