After every reboot: HTTP ERROR: 503 SERVICE_UNAVAILABLE

[fivestones]

The short:
HTTP ERROR: 503 SERVICE_UNAVAILABLE comes up after every reboot of my ubuntu system. To fix, have to delete the subsonic database and restart subsonic. Don't want to do this every time.

The long:
I'm running subsonic 4.4 on Ubuntu 10.04 and every time I reboot the computer I get HTTP ERROR: 503 SERVICE_UNAVAILABLE instead of subsonic when going to the subsonic page. There are several other posts about this (for example, http://forum.subsonic.org/forum/viewtopic.php?t=3054 and http://forum.subsonic.org/forum/viewtopic.php?p=10297 and many others) and after reading there I've found how to fix it (until the next reboot)--I just delete the database, and then sudo service subsonic restart. This makes it work again, but with all my settings gone. I've done this so many times now that I've started having my backup software back up every permutation of the subsonic database so that after a reboot I can restore the database from right before the reboot. This works but is a big hassle.

It seems that obviously the problem is due to a corrupted database which gets corrupted during rebooting somehow. So how is it getting corrupted? I don't know if this is a subsonic problem or an Ubuntu problem, but either way despite all the posts about this error (and the likelihood that a lot or all of them are also due to a corrupted database) I have yet to see any better solution than to delete the database and restart subsonic.

Any ideas anyone? Any other information I can bring to help someone help me figure out a solution?

...and, THANKS Sindre for the sweet software!

[fivestones]

Nobody? I know other people have had this same problem...did anyone ever figure out how to fix it or where the problem was stemming from?

Thanks!

[donpearson]

maybe a stupid question, but have you uninstalled subsonic rebooted and then reinstalled it?

[tmadison]

I'm having the same problem.

My config is Opensuse 11.4, w/ apache 2 and tomcat 6 running subsonic 4.4

The logs report that the database is still in use as the database lock file is there.

The first few times I fixed the problem by deleting the /var/subsonic folder, but now I have too much involved on the config. I undeployed the war file with tomcat and then reployed it. I also deleted the lock file. That seemed to work.