RESOLVED: SERVICE_UNAVAILABLE after upgrade to v 4.7 fom 4.6

[bux]

Hi,
i've upgrade my version of subsonic from 4.6 to 4.7, with .deb Debian/Ubuntu installer. Bu now, subsonic seems to be not working ...
When i restart subsonic:

Code: Select all

sudo /etc/init.d/subsonic restart

/var/subsonic/subsonic.log

[2012-09-25 13:12:17,715] INFO DaoHelper - Checking database schema.
[2012-09-25 13:12:20,738] INFO DaoHelper - Done checking database schema.
[2012-09-25 13:12:20,898] INFO VersionService - Resolved local Subsonic version to: 4.7
[2012-09-25 13:12:21,574] INFO MediaScannerService - Automatic media library scanning scheduled to run every 7 day(s), starting at Wed Sep 26 04:00:00 CEST 2012
[2012-09-25 13:12:24,702] INFO NetworkService - Deleted port mapping for port 4040

/var/subsonic/subsonic_sh.log

[...]
5003 [main] INFO org.mortbay.log - Started SelectChannelConnector@0.0.0.0:4040
Subsonic running on: http://localhost:4040/
5097 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Looking for RMI registry at port '9412'
[GC 165387K->60562K(214976K), 0,0740130 secs]
5209 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Could not detect RMI registry - creating new one
5258 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Binding service 'SubsonicDeployerService' to RMI registry: RegistryImpl[UnicastServerRef [liveRef: [endpoint:[127.0.0.1:9412](local),objID:[0:0:0, 0]]]]

If i try to access to http://localhost:4040 :

HTTP/1.1 503 Service Unavailable

Do you have an idea ?

[BKKKPewsey]

There does appear to be a general issue with updating a 4.6 DB to 4.7
I also had the the same problem but only after a couple of days. (With a 4.7beta)
Like you I had no errors shown in the log
The general consensus seems to be that its best to do a clean install of 4.7
(Delete/Rename c:\subsonic folder before installing)

[bux]

Ok,
Is it possible to save/restore data ? (notations, comments, etc) ?

[BKKKPewsey]

Yes but I think it needs a bit of reading/writing of db via db.view.
Just copying the old db over will end up in the same situation as before eg 503 error. (Well in my case it did )
Do a forum search as there was a post here somewhere about copying the data eg playcounts/comments etc
Or await one of our SQL gurus to reply.

[jonnymnemo]

I don't know about the comments, but you can keep the users (with their password) and their settings.
They are kept in the subsonic.script file

1. stop subsonic service
2. rename the subsonic/db directory
3. start subsonic service : a new database is created.
4. open the old subsonic.script file (in the directory you renamed)
5. select the lines you want to keep (INSERT INTO MUSIC_FOLDER VALUES... INSERT INTO USER VALUES... INSERT INTO USER_ROLE VALUES ... INSERT INTO USER_SETTINGS VALUES ...)
6. in your subsonic webpage, replace "index.view" with "db.view"
7. paste the selected lines

Now you should have your old user settings

[bux]

Ok, thank's. I've:

1 - Stopped subsonic deamon
2 - Backuped subsonic/db/subsonic.script file (containing logical backup of database)
3 - Installed 4.7 form .deb package
4 - Copied somes lines from OLD subsonic/db/subsonic.script in NEW subsonic/db/subsonic.script
If i copy entire file: error; take care to copy cleanly lines what you want (for me, user, user_role, music path, rating, player, user parameters)
5 - Started subsonic deamon

Thank's guy's !!

[jonnymnemo]

You're welcome !

By the way, you can't import the starred albums or songs, because when you recreate the database, each song will have a new ID !!!

If you want to backup these BEFORE upgrading, there is a workaround :

- create a playlist with all your starred songs
- export the playlist

When you have to recreate the database, you will just have to import this playlist and star each song.

Same thing for the starred albums : you create a separate playlist, and put one song of each album, then star the album !

[bux]

I think i was lucky, i've my (and other user) starred albums
(No new music in mymusic folder, so same id i think )