Upgrade to 4.7beta 2 shafted?

[quatermass]

I've just upgraded my good old working (donated) Subsonic server from 4.6 (build 2583) to 4.7beta2 and wham - I now get :

Code: Select all

HTTP ERROR: 503

SERVICE_UNAVAILABLE

RequestURI=/index.view

Powered by jetty://

When I try to open the Subsonic web page in my Pc using localhost address on my own LAN.

The Subsonic control panel is running in my taskbar (Windows 7 Pro 32bit) with no error messages. But no web access any more!


Subsonic-service.exe.vmoptions file:

Code: Select all

-Xmx100m
-verbose:gc
-Dsubsonic.host=0.0.0.0
-Dsubsonic.port=80
-Dsubsonic.httpsPort=0
-Dsubsonic.contextPath=/
-Dsubsonic.home=f:/subsonic


Luckily I used System Restore to go back to 4.6....But I'd like to know if this is a known problem (yeah I know, it's a Beta

[GJ51]

Looks like the installation didn't go well. I have two 64 bit upgrades to 4.7b2 and one 32 bit - all are running fine.

Update to the latest Java and try again. Do a reboot just before the upgrade just to be sure everything is running OK.

The upgrade process isn't always as smooth as it should be, but 4.7b2 runs very nicely once it's installed properly.

If the upgrade path doesn't go well, I'd do a clean install.

[bushman4]

I'd guess you forgot to delete the work directory when you did the upgrade. stop the service, delete the work directory, and restart the service.

Glenn

[hakko]

Update to the latest Java and try again. Do a reboot just before the upgrade just to be sure everything is running OK.

Sorry if I'm a PITA now but the latest Java is 1.7 which Subsonic has compability issues with... right?

[GJ51]

The Windows latest download is 7.5.

It too has caused problems, but it can work. I had to do a clean reinstall last night to get one site back up. Similar issues to what others are reporting with 1.7 producing Java errors.

[GJ51]

I'd guess you forgot to delete the work directory when you did the upgrade. stop the service, delete the work directory, and restart the service.

Glenn

I'm not sure I understand what the "work" directory is. I did delete C:\Subsonic but there were SS files in other places on the C: drive that were retaining settings from the install. I'm just on a Windows standard install.

I did stop the service.

[bushman4]

I was talking about the OP, quatermass. I had a very similar problem as he describes in his OP once during an upgrade, and it was because I forgot to delete the "work" directory.

That directory is called something else in a Jetty install... \jetty\<some number>\webapp I think.

It is where the WAR file is unpacked into to run... since all versions of subsonic have the WAR somewhere, it needs to be unpacked so that whatever java servlet server you are running (be it Apache Tomcat, Jetty, or something else) can serve it up one file at a time.

HTH,

Glenn

[quatermass]

So why can't the upgrader installer look for the service running, stop it, look for this 'work folder', delete it?

P.S. How can I forget to delete this 'work folder' when the Installer didn't mention it? Am I missing something?

[BKKKPewsey]

P.S. How can I forget to delete this 'work folder' when the Installer didn't mention it? Am I missing something?

Nope - a normal install will stop the SS service and delete the "work" folder so something must have gone wrong.
Note I am installing under Windows server 2003 & vista but I doubt if Win7 is that different.

[GJ51]

I've had different degrees of success with the 4.7 upgade process, everything from total success to complete failure, and a few variations in between.

That's probably why it's called a beta.