Subsonic Forum

Hello All,

I decided to put a larger hard disk in my media server, so I made an image and restored it to my larger disk. Everything works (Vista) except Subsonic, I get an HTTP Error 503. I uninstalled subsonic and reinstalled it, now subsonic is working but as a virgin system.

I tired to copy my backed up db folder to the c:\subsonic folder but once I do this I again get the HTTP Error 503. Do I have to start setting this up from scratch again?

Alan.

I tried copying over the db folder and subsonic.properties but that has not worked

Can someone tell me what the subsonic.script file does?

If I dont copy that file over, i can copy my db, although I still have none of my old settings, the script file looks like a load of SQL commands to rebuild a database.

Any ideas?

Having lost all my album stats, album art, higest rated etc I am feeling pretty miffed. If I can't get to the bottom of this then I can't have any confidence running Subsonic long term.

Is anyone able to look at my database and tell me if it is corrupted?

Alan.

WildWalker wrote:Having lost all my album stats, album art, higest rated etc I am feeling pretty miffed. If I can't get to the bottom of this then I can't have any confidence running Subsonic long term.

Is anyone able to look at my database and tell me if it is corrupted?

Alan.

I don't run a windows version of it, but in Linux, I have found that you have to have the /var/subsonic dir as well. I could be wrong though.

Sorry, wish I knew more of the Windows side of things, but I just don't run it.

When upgrading you should backup the folder "database" and the subsonic.properties file in the subsonic folder. This should be enough to have your settings and your data carried over to the next installation. Try replacing just those two items and not the whole subsonic folder. I am using a tomcat installation, but I think it should be fairly similar in terms of backups.

ff

My best solution currently (I had the same issue after a full dist-upgrade) is to run subsonic first with sudo to allow it root permissions to create any directories it may need, and then to kill it and run it as a regular user. Not pretty, but it worked for me. Seemed heavily related to permissions assigned to folders, if you wanted to run it with root permissions all the time (not advisable) you could do it but there are no guarantees what will happen if its compromised.