Subsonic Forum

First, have to say, great application.
Have been using 3.5beta1 and it's really quite good. Well done.

The server has been running 3.5beta1 for a week or more now without issue.

Suddenly, today, I get.
HTTP ERROR: 503
SERVICE_UNAVAILABLE
RequestURI=/

Powered by jetty://
---------

I'm running Subsonic on Windows XP Pro on an older 1.3GHz Pentium with 512Mb or RAM.

I've restarted the PC, uninstalled, reinstalled Subsonic, uninstalled the 3.5beta1 and reinstalled with 3.4.

Whether I try to access across the network, or even localhost, I still get the HTTP ERROR: 503.

I hope this isn't some boneheaded thing I've done.
Looking forwarded to any help.

Thanks again, great app.

Sorry, I don't know what this is, but you can try to stop Subsonic, remove c:\subsonic (NOTE: You will loose all settings), and start it again.

Sindre

Just as a heads up, I ended up uninstalling the Beta, then crawling through the registry deleting all references to Subsonic, then deleting c:\subsonic as well.
After a reboot, I reinstalled the Beta and all works well.

Not the prettiest solution, but it's up and running.

Thanks for the quick response.

Again, very cool application.

Hi, I have the same problem as utbluesman. I've looked into the log files and event viewer. Below are the details. Maybe with that information you can find a solution, without me having the deinstall everything.

In c:\subsonic\subsonic.log:

[2009-02-14 08:18:36,020] ERROR DaoHelper - Failed to initialize database.
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: File input/output error: java.io.IOException: org.hsqldb.HsqlException: Unexpected token: [null]

I can send the detailed log file if you wish.

Regards
Joost

Sounds like a corrupt database. Yes, please send me the log file if you still have it.

Thanks,
Sindre

Sorry, I forgot about this.

The log file didn't reveal anything more. Can't think of any other work-around than resetting the database:

o Stop Subsonic.
o Remove c:\subsonic\db
o Start Subsonic.

You will of course loose your settings.

Thanks Sindre,

That indeed did the trick. I'm glad that I did not have to dive into the registry

Joost

Just ran into this on the standalone 3.7 beta1. I'm running on linux debian. I'll delete and try from scratch. Just a heads up

I just experienced this problem with 3.7 beta 1 on Ubuntu 9.04. I'd say it was due to an unclean reboot of the computer which caused the database to become corrupt.

Deleting the "db" folder and running Subsonic again fixed the problem. I've taken a backup of the "db" folder after setting all the settings again to safeguard against this next time.

same problem: HTTP ERROR: 503

deleted db, rerun subsonic.sh and same error.
completely deleted all subsonic files and reinstalled.. same error.

>:[

!?

I am having the same error on FreeBSD 7.2 tomcat6.
It ran after the install but would not play music in the web interface although the log files showed the song had started.
I would click the play icon and nothing would happen (tried different browsers/computers).
After a reboot I then started getting this error.

Moved subsonic.war file back to subsonic root and restarted tomcat, apache and subsonic and it all works including the play button.
I will be donating shortly.

Having the same problem on a Windows Vista machine. I can't locate the DB to delete it. Any clues?

mchyde wrote:Having the same problem on a Windows Vista machine. I can't locate the DB to delete it. Any clues?

I use Win7 x64 and the db folder by default was located at: C:\subsonic\db

I use 3.9 (build 1335) – February 9, 2010

I, too, had this 503 error after about a week of use and had to delete the db files to fix the problem. Hopefully this isn't a recurring issue because wiping settings every week or so to fix it would kinda suck.

I had a similar issue (Windows 7, 32 bit, Subsonic 4.4), and yes: deleting the directory made the trick. The failure came after a sudden reboot, so it's easy to see that Subsonic's db got damaged at that moment.

Seeing that this issue has happened to many, I'm thinking it might be a good idea to keep some sort of auto-backup of the db which would kick in should the dreaded error 503 happen. I know: the db regenerates automatically, but still, a) it takes time, and b) you also lose your configs.

What do you think, Sindre?