BMT 4.8 / Phoenix 2.2.1 - After upgrade, Browse function broken

[mkanet]

There really wasn't much to it, I just upgraded Phoenix and BMT from the last immediate versions (which everything worked, including Browse). But, immediately after it asked me to reboot the Server in red and I said yes, when I went to check BMT 4.8's web interface, the first thing I did was put IMDB back in the top of the search order. Then, I tried the browse function which gave me the attached screenshot (Browse-broken-BMT4.8.jpg).

I exited all clients, restarted sageTV service, checked the plugins to make sure they were showing as installed with the new versions.. which they were.

So, next, when I went into the BMT 4.8 web interface, the browse interface gave me the error in the attached Browse-broken-BMT4.8-2.jpg.

Luckily, I know I didnt make any changes to my system.. it was just running quietly along, until I did those updates.

Is there something that's causing the scan to get stuck? Any ideas would help alot. I have no idea how to trouble shoot BMT since it's always worked for me in the last several upgrades.

Thanks!
Michael

[mkanet]

The only thing odder that the issue I reported above is this morning I woke up and tried the browse function again... now it's working. I didnt do anything between last night as this morning except sleep.

Sean, you've made BMT so resilient it recovers from issues on its own now. I'm glad it's working now.

[stuckless]

By the looks of the screen shots it would appear that the vfs was not loaded... i have seen this happen myself, directly after an upgrade. A sagetv server restart usually fixes the issue. I haven't really investigated it much, but appears that somehow files disappear during an upgrade, and then reappear after a restart... even though sagetv does a restart when you upgrade bmt, sometimes, not all the files extracted... or some get removed. I'm not sure which... I just know that an extra restart usually fixes it.

[mkanet]

Hi Sean, it looks like this happened again; or, at least something related when I upgraded. But this time, I have already restarted sageTV service and clients at least 3 times; and, still not been able to recover from it. I even uninstalled the command-line BMT plugin and reinstalled it. Have you been able to figure out a way to prevent this from happening when upgrading? Or, perhaps an easier way to recover from it?

Below is the error message I get:

Thanks,
Michael

[stuckless]

Originally Posted by mkanet

Hi Sean, it looks like this happened again; or, at least something related when I upgraded. But this time, I have already restarted sageTV service and clients at least 3 times; and, still not been able to recover from it. I even uninstalled the command-line BMT plugin and reinstalled it. Have you been able to figure out a way to prevent this from happening when upgrading? Or, perhaps an easier way to recover from it?

Below is the error message I get:

Thanks,
Michael

Are you sure you installed the correct plugin? Or if you did, it would appear that you have some very old residual files lying around. The screen shot that you are sending is stating that you are using bmt 3.x... event he layout of the first page is completely different in 4.x.

This could be a browser cache issue...so you could try to clear your caches.

If that doesn't fix it, then I would uninstall the bmt web plugin, then manually remove jetty/contexts/bmt* and jetty/webapps/bmt* and then install the plugin again.

[mkanet]

I originally had SageTV 6.6.2 with the latest BMT running and configured correctly. Then, I upgraded to sageTV 7 and upgraded BMT and Phoenix. Was there something different I had to do? I would guess that the plugin version of sageTV 7 would detect a BMT version 3; and, upgrade accordingly.

I did the same thing with Phoenix and the rest of all my plugins.

Will I lose any of my settings if I do what you suggested? Hopefully no configuration will be necessary; and only the version changes, not the settings.

Thanks so much,
Michael

Originally Posted by stuckless

Are you sure you installed the correct plugin? Or if you did, it would appear that you have some very old residual files lying around. The screen shot that you are sending is stating that you are using bmt 3.x... event he layout of the first page is completely different in 4.x.

This could be a browser cache issue...so you could try to clear your caches.

If that doesn't fix it, then I would uninstall the bmt web plugin, then manually remove jetty/contexts/bmt* and jetty/webapps/bmt* and then install the plugin again.

[stuckless]

Originally Posted by mkanet

I originally had SageTV 6.6.2 with the latest BMT running and configured correctly. Then, I upgraded to sageTV 7 and upgraded BMT and Phoenix. Was there something different I had to do? I would guess that the plugin version of sageTV 7 would detect a BMT version 3; and, upgrade accordingly.

I did the same thing with Phoenix and the rest of all my plugins.

Will I lose any of my settings if I do what you suggested? Hopefully no configuration will be necessary; and only the version changes, not the settings.

Thanks so much,
Michael

Michael, if you upgraded from 6, then run the upgrade tool in the sticky. SageTV cannot possibly upgrade the plugins from 6 to 7, since SageTV6 had no concepts of plugins.

[mkanet]

Sean, I really screwed up big time. Before seeing this message, I uninstalled the plugin version 4.8, deleted the items you told me to, then installed the 4.8 version again. Now, I can't get to the webpage for BMT anymore.

Edit: I just ran the upgrade tool. But, I'm not sure if it's too late. Heck, I dont even remember where the settings are kept. Maybe they're still safe?

Could you please tell me the quickest possible way to get up and running? All I know is I used to be able to get to: http://localhost:8380/bmt/; but now I can't.



Thanks,
Michael

Originally Posted by stuckless

Michael, if you upgraded from 6, then run the upgrade tool in the sticky. SageTV cannot possibly upgrade the plugins from 6 to 7, since SageTV6 had no concepts of plugins.

[mkanet]

Man, this was a very bad idea. I'm sitting here going through all documentation. I dont even know how to verify if the port is still on 8380 or what else is missing. Sean, if you're there, I'd really appreciate the help.

From what I can see in the instructions, all I have to do is make sure phoenix is installed and running then install the BMT 4.8 plugin. I have always been able to go to http://localhost:8380/bmt/ for BMT and https://localhost:8090/sage/Home for my webserver (both jetty based).

I have no idea how I was getting BMT to work in version 7 (even the webserver); but it was working; even in the last couple of upgrades via the plugin. Anyway, guess I'm stuck until I can get some help. At least I ran the upgrade tool; but it didnt make any difference. I still dont see any newly created jetty based war files for BMT. I even ran a scan on the entire sageTV folder/file hierarchy to see what file might contain the 8380 I need or even 8080 (which I cant use due to another service being on it). *sigh*

[mkanet]

Problem resolved!

Sean, it was late for me last night. I wasn't thinking with a clear head. I hadn't installed Batch Metadata Tools - Web Interface.

Correct me if I'm wrong, but is the reason I was getting that error message because I didnt run the update tool? The instructions say to run that update tool before I install "any" plugins. I must have over 20 plugins installed before running that update. At least, I did uninstall BMT command-line/Web Interface before running the update and installing the BMT plugins again.

[stuckless]

Originally Posted by mkanet

Problem resolved!

Sean, it was late for me last night. I wasn't thinking with a clear head. I hadn't installed Batch Metadata Tools - Web Interface.

Correct me if I'm wrong, but is the reason I was getting that error message because I didnt run the update tool? The instructions say to run that update tool before I install "any" plugins. I must have over 20 plugins installed before running that update. At least, I did uninstall BMT command-line/Web Interface before running the update and installing the BMT plugins again.

On a fresh install, installing bmt is as simple as installing the single bmt web plugin which installs all the dependencies. But, when you upgrade, and you have bmt installed, then ideally the best thing to do is to remove all plugins before you upgrade, but if you don't then running the tool i created will remove the old bmt and related libraries and enable it so that bmt can be installed via the plugin manager, the way it is supposed to be installed in V7.

Btw, too little too late... but I'm working on a complete user guide for BMT, so hopefully these issues will be addressed in the guide. I've been working on the guide for some time now, so far, i've put in about 80hours and I'm only about half done