HTTP ERROR: 503

[da_am]

Just wanted to throw in my experience. I received this 503 after a bad shutdown. I reinstalled, deleted the DB folder, restarted the service and still nothing. Then I took a look at my system moniter and saw about 6 java processes running and sure enough they were started by subsonic. I ended all the processes and restarted the service. Voila - everything worked again. I was kicking myself for not looking at what was running originally.

[gogogo]

Hi to all,
I have solved restoring all /var/subsonic/ directory files to the last day backup using crashplan (free version) and rebooting the server, under ubuntu 32bit.

My problem was born installing "psyco" (a python booster)

Regards.

[TWeaK]

My experience:

I have a Windows 7 machine. My computer rebooted after a power surge and Subsonic would not work from then on. I tried reinstalling both Subsonic and Java, neither of which worked. Stopping Subsonic, Deleting C:/subsonic/db, and restarting Subsonic did the trick.

[GJ51]

That makes sense; when the power killed the PC the OS didn't have time to close the files properly.

[wisenuts]

Just wanted to throw in my experience. I received this 503 after a bad shutdown. I reinstalled, deleted the DB folder, restarted the service and still nothing. Then I took a look at my system moniter and saw about 6 java processes running and sure enough they were started by subsonic. I ended all the processes and restarted the service. Voila - everything worked again. I was kicking myself for not looking at what was running originally.

This worked for me.

ended up doing

service subsonic stop
top (to find there were still java processes running)
killall java
service subsonic start

bingo! streaming music once again.

[Dawg]

An old thread I know but i just had the 503 error, thought i would post my findings. Im running windows 7 ultimate. as far as i know there was not explanation for the crash, it happened while listening to music, grrr. I did find a backup of the DB files which must of happened automatically, I was running v5.0 as I HATE the new layout of the album artwork in 5.1. Replacing the DB with the backups had no effect, I didnt want to delete anything just yet so i installed 5.1, this did the trick, after seeing the album artwork in its new form again i thought NOOO, I would rather delete the DB. Instead I just reinstalled v5.0 and everything is back to normal, nothing lost! As this is over 2 years old I am surprised its still happening but I guess everyone now just backs up with success or starts again.

[CaddyGuy]

Kicking an old thread, but sharing my findings.
Running Windows 7 64 Bit
I am running 5.3 (build 4569), spare computer only used for serving my music and some movies to my phone mostly.
It was working fine yesterday, and this morning when I left for work It would not connect with a "Didn't understand the reply" error on my phone. When I got home I made sure port forwarding and what not didn't go wonky. I tried connecting to the local host on the machine itself and got the "HTTP ERROR: 503". After a bit of searching around and trying to uninstall a Windows Update that installed itself last night, I found this thread and took a look at the log. I saw those database issues. I opened up task manager and killed subsonic, then navigated to "C:\subsonic". I made a copy of the "db" folder and the "db.backup" folder for safe keeping. Then I deleted the "db" folder and renamed the "db.backup" folder to "db". Launched subsonic, tried to connect to local host, but it didn't go, so I opened the "Subsonic Control Panel" and stopped the service, waited a few seconds, then restarted the service and clicked the "Server address" link towards the bottom. The browser then popped right up to the Subsonic login screen. I tried my phone and it connected right up.

It turns out the computer installed a .net framework update last night. When it restarted it must have corrupted the database.

[jeremybear]

I had this issue with a fresh install on Ubuntu 16.1 AMD64 version.

"HTTP ERROR: 503
SERVICE_UNAVAILABLE
RequestURI=/"

Turns out that I had openjdk-8 and openjdk-9 installed. Uninstalling all the openjdk-9 components fixed the problem.