Upgrade to 4.7 ==> 503 Service unavailable

[jflorance]

Problem Description: I upgraded from Subsonic 4.6 to 4.7 today . Installation ran with no errors but when trying to test using localhost or local IP, receive the message: HTTP ERROR: 503, SERVICE_UNAVAILABLE, RequestURI=/index.view.
I had been running Subsonic on this computer for about 2 years and wanted to pick up the previous version settings.

Troubleshooting Steps: Tried using the defaults as well as the current ports (8080) but continues to display the error message.
Playback Application and version: Chrome and IE, local and from another PC.
Subsonic Version: Can't access the web interface but believe I have 4.7, build 3106
Server Version: Same issue as above.
Hardware Platform: Windows 7 Pro 64 bit, Java version 1.6.0_37b06
Java Memory Limit: 150 megs
Problem Filename: N/A
Output from ffmpeg -i: (If you open a command prompt and type 'ffmpeg -i <filename>' what is the output? Ideally put this in a "code" block)
Last ten log file lines: From sonic-agent.log

Code: Select all

Executing: subsonic-service.exe -start
41726 [pool-1-thread-2] WARN org.springframework.remoting.rmi.RmiProxyFactoryBean - Could not connect to RMI service [rmi://localhost:9412/SubsonicDeployerService] - retrying
1645256 [pool-1-thread-2] WARN org.springframework.remoting.rmi.RmiProxyFactoryBean - Could not connect to RMI service [rmi://localhost:9412/SubsonicDeployerService] - retrying
Executing: subsonic-service.exe -stop
2528704 [pool-1-thread-2] WARN org.springframework.remoting.rmi.RmiProxyFactoryBean - Could not connect to RMI service [rmi://localhost:9412/SubsonicDeployerService] - retrying
Executing: subsonic-service.exe -start
Executing: subsonic-service.exe -stop
2947162 [pool-1-thread-2] WARN org.springframework.remoting.rmi.RmiProxyFactoryBean - Could not connect to RMI service [rmi://localhost:9412/SubsonicDeployerService] - retrying
Executing: subsonic-service.exe -start
6443147 [pool-1-thread-2] WARN org.springframework.remoting.rmi.RmiProxyFactoryBean - Could not connect to RMI service [rmi://localhost:9412/SubsonicDeployerService] - retrying
Executing: subsonic-service.exe -stop
6490276 [pool-1-thread-2] WARN org.springframework.remoting.rmi.RmiProxyFactoryBean - Could not connect to RMI service [rmi://localhost:9412/SubsonicDeployerService] - retrying
Executing: subsonic-service.exe -start
7558725 [pool-1-thread-2] WARN org.springframework.remoting.rmi.RmiProxyFactoryBean - Could not connect to RMI service [rmi://localhost:9412/SubsonicDeployerService] - retrying
Executing: subsonic-service.exe -start
Executing: subsonic-service.exe -start
Executing: subsonic-service.exe -stop
8728739 [pool-1-thread-1] WARN org.springframework.remoting.rmi.RmiProxyFactoryBean - Could not connect to RMI service [rmi://localhost:9412/SubsonicDeployerService] - retrying
Executing: subsonic-service.exe -start

I suspect it is a problem with the RMI service but that's beyond my skill set.
--John

[jflorance]

Update: Uninstalled Subsonic 4.7 through the Control Panel and installed 4.6. Everything seems to be working. Didn't touch Java. I think I will wait until someone can provide some direction. I'm just glad to have my music back.

[BKKKPewsey]

There does appear to be a problem with upgrading a 4.6 db to 4.7.
I know I had some issues with that - I think it is better to do a clean install of 4.7.
Since then I have had no errors (503) or otherwise with my 4.7 install.
(I still use 4.6 as my main SS - I prefer the playlist handling)

[GJ51]

Update: Uninstalled Subsonic 4.7 through the Control Panel and installed 4.6. Everything seems to be working. Didn't touch Java. I think I will wait until someone can provide some direction. I'm just glad to have my music back.

When you attemted the upgrade, did you manually shut down Subsonic before upgrading or did you attempt to do the upgrade while the service was running?

[jflorance]

[Correction: I stopped the Subsonic service first, then removed 4.7 using Control Panel and then installed 4.6.]

I have not tried uninstalling 4.6 and installing 4.7 but I may try that over the weekend now that I know my settings are not lost.

I'm assuming, on a Windows installation, settings are in the C:\subsonic folder. I am also assuming that Java 7 should still be avoided, at least for now.

John
---------------------------------------------------------------
Windows 7, 64 bit, 4 gig RAM
And only...
1,412 artists
864 albums
7,146 songs
95.20 GB (~ 1,478 hours)

[GJ51]

Version 4.8.beta2 (build 3280) – November 29, 2012 – (Moded by MadEvil)
Server Apache Tomcat/6.0.35, java 1.7.0_05, Windows Server 2008 (118.9 MB / 212.6 MB)

I've had no problems using the latest Java.

[FreeMan]

I'm also getting the 503 error.

Initially, I updated to 4.7 (just a couple of days ago), got the error and was slightly panicked! I did figure out to uninstall 4.7, reinstall 4.6 and all was good.

After reading through the issues others have had, I attempted to shutdown the SS service, then do the update, which still left me with a 503. Based on this thread, I uninstalled 4.6, then did a fresh install of 4.7, and am still getting a 503. I am running Oracle Java 7, which I understand isn't the most compatible with SS.

I'm not really looking to downgrade Java at the moment, so are there any other suggestions that might allow me to fix this? I do find it interesting that the 4.6 control panel indicates SS is using about 15MB RAM, while the 4.7 control panel indicated 22-25MB of RAM.

(OS: WinXP, SP3)

[labtopia]

i am also getting this same error for no reason at all. i had 4.7 running fine and now it has stopped working with this error.

any ideas? i am going to unistall the latest windows updates and see if that does something.

dave

[labtopia]

ok, i tried some of the suggestions on the forum like
viewtopic.php?f=2&t=10326&p=46403&hilit=service+unavailable#p46403

with no luck, first of all, nothing shows up in the script file mentioned, just blank lines.

then i remembered this happened before, solution= delete all the stuff in the DB folder and start over setting up your sources, users, and all the GD settings.

i am on windows, i do remember that the last time this happened, the machine had to be hard repowered as with this time and it is clear that subsonic is unable to recover it's data in this case,

so the above link may help those on other OS, but not windows

how about a setting for periodic DB snapshots so this doesnt happen. well there went an hour of time fixing and it's rescanning away.

not a happy fix but the only way i could get running again...

dave

[MaLaCoiD]

I just got the same problem on Win7 x64. About the time the problem was seen, I installed:
Security Update for Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (KB2538243)
Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.141.3314.0)

... that's only change I can think of. A cold boot didn't recover. In c:\subsonic, I have a db.backup folder with files from 2012-09-20. I renamed the folder to 'db' and moved the original 'db' to 'db.broke'. Now I'm back in business- will just have to update the library.

[GJ51]

I'm pretty convinced that these errors are most likely due to improper shutdowns that fail to close the db properly. This can occur sometimes even during the update process if the reboot doesn't close out the file properly before the restart.

My servers run on Windows Server 08R2 and are on 24/7. I haven't had a 503 error in a couple years now. Doing an occasional backup of C:\Subsonic and making sure the server is always shut down properly is the best way to deal with this issue.

[MaLaCoiD]

I'm pretty convinced that these errors are most likely due to improper shutdowns that fail to close the db properly. This can occur sometimes even during the update process if the reboot doesn't close out the file properly before the restart.

I'll admit that I hit "Restart Now" instead of waiting for everything to shut down.