| View previous topic :: View next topic |
| Author |
Message |
moxica
Joined: 27 Sep 2008
Posts: 6
|
 Posted: Sat Sep 27, 2008 11:35 am Post subject: Installing 3.5.beta2 over 3.4 - not upgrading? |
 |
|
Hi, I've just started playing around with subsonic, started with 3.4 as the latest stable release, got it up and running fine, then decided to try the latest beta to get some of the newer features so have tried installing the beta, but when I connect to subsonic I still seem to be on version 3.4?
I've tried uninstalling and reinstalling, installing to a different directory, reinstalling without uninstalling, doesn't seem to make any difference...the 'about' page when I log in and click on the sub image tells me that there's a new beta to download, that I'm running 3.4 (build 530), and gives the following info:-
[9/27/08 8:48:24 PM CST] INFO DaoHelper Checking database schema.
[9/27/08 8:48:25 PM CST] INFO DaoHelper Done checking database schema.
[9/27/08 8:48:25 PM CST] INFO SearchService Automatic index creation scheduled to run every 1 day(s), starting at Sun Sep 28 03:00:00 CST 2008
[9/27/08 8:48:25 PM CST] INFO PodcastService Automatic Podcast update disabled.
[9/27/08 8:48:48 PM CST] INFO VersionService Resolved latest Subsonic final version to: 3.4
[9/27/08 8:48:48 PM CST] INFO VersionService Resolved latest Subsonic beta version to: 3.5.beta2
[9/27/08 8:48:48 PM CST] INFO VersionService Resolved local Subsonic version to: 3.4
Am I missing some step in the upgrade process?
Cheers! |
|
| Back to top |
|
 |
sindre_mehus
Joined: 29 Nov 2005
Posts: 1138
Location: Oslo, Norway
|
| Posted: Sat Sep 27, 2008 1:43 pm Post subject: |
|
|
Assuming you're using the Windows installer, you can try the following:
1. Stop Subsonic
2. Remove c:\subsonic\jetty
3. Start Subsonic
Hope this helps,
Sindre |
|
| Back to top |
|
|
Andreas
Joined: 26 Sep 2008
Posts: 22
Location: Kirkenes
|
| Posted: Sun Sep 28, 2008 12:31 am Post subject: |
|
|
| This worked for me. |
|
| Back to top |
|
|
moxica
Joined: 27 Sep 2008
Posts: 6
|
| Posted: Sun Sep 28, 2008 3:37 am Post subject: |
|
|
| sindre_mehus wrote: | Assuming you're using the Windows installer, you can try the following:
1. Stop Subsonic
2. Remove c:\subsonic\jetty
3. Start Subsonic
Hope this helps,
Sindre |
Brilliant, worked perfectly!
Thank you, both for the quick response, and the excellent software  |
|
| Back to top |
|
|
sindre_mehus
Joined: 29 Nov 2005
Posts: 1138
Location: Oslo, Norway
|
| Posted: Sun Sep 28, 2008 8:19 am Post subject: |
|
|
Wonderful! I'll modify the installer so that this happens automatically.
Thanks,
Sindre |
|
| Back to top |
|
|
henrik
Joined: 06 Nov 2008
Posts: 3
|
| Posted: Thu Nov 06, 2008 3:47 am Post subject: |
|
|
How would you do that for linux stand-alone? Just overwrite all files? Where are the settings stored? Do I have to change the port again?
thanks
_________________
I'd rather have a bottle in front of me than a frontal lobotomy |
|
| Back to top |
|
|
sindre_mehus
Joined: 29 Nov 2005
Posts: 1138
Location: Oslo, Norway
|
| Posted: Thu Nov 06, 2008 4:56 am Post subject: |
|
|
| henrik wrote: | | How would you do that for linux stand-alone? Just overwrite all files? Where are the settings stored? Do I have to change the port again? |
On Linux, that would be /var/subsonic/jetty. Settings are generally stored in /var/subsonic/db and will survive. The exceptions are port and context path, which are set in the subsonic.sh script. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
SmartFeed
Register
Profile
Log in to check your private messages
Log in
