Page 1 of 1

Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sat Jan 12, 2013 12:18 pm
by dbenyakar
However I did not upgrade at all.
I am running 4.7 and today, when I tried to access http://localhost:4040/, it refereed me to http://localhost:4040/index.view.
The error was:
HTTP ERROR: 503

SERVICE_UNAVAILABLE

RequestURI=/index.view

Powered by jetty://

In the log file is attached.

What can I do to resolve it?
Please help.

Re: Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sat Jan 12, 2013 12:33 pm
by hakko
Anyone running Subsonic or derivative software using the same database is exposed to the risk of this happening, sooner or later. Stop your service, rename C:\Subsonic (or equiv) to C:\Subsonic_backup (or equiv), start again and then read viewtopic.php?f=6&t=10338

Re: Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sun Jan 13, 2013 6:23 am
by dbenyakar
Thanks for this info.

I have few questions then.
1. What do you mean by "using the same database"? Are there other alternatives to minimize such corruption?
2. I have apparently saved the database 3 months ago. So I replaced the contents of the existing subsonic/db with the files in the backup. Subsonic was up and running again.
So I started entering the missing music folders again. However, when looked at the subsonic.data file, its size and date did not change. The date and size are still the same as they were when i took the backup. Why did they not change?
3. Is the process I have done above of restoring an old database is the correct process? Do I need to backup anything else in the future?

Regards
Danny

Re: Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sun Jan 13, 2013 5:56 pm
by hakko
1. You could either use Subsonic 4.6 or earlier, or check my highly modified Subsonic server (designed for audio listening, not video streaming) which stores library metadata in a PostgreSQL database instead of HSQLDB. viewtopic.php?f=11&t=10587
2. I think subsonic.data is only written to at certain checkpoints, but not sure as I tend to avoid it as much as possible
3. Saving C:\Subsonic is enough for backup purposes, no information is stored outside of that directory afaik

Re: Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sun Jan 13, 2013 6:49 pm
by BKKKPewsey
dbenyakar wrote:So I started entering the missing music folders again. However, when looked at the subsonic.data file, its size and date did not change. The date and size are still the same as they were when i took the backup. Why did they not change?

After adding the new media folders did you do a rescan?

:mrgreen:

Re: Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sun Jan 13, 2013 7:26 pm
by dbenyakar
BKKKPewsey wrote:
dbenyakar wrote:So I started entering the missing music folders again. However, when looked at the subsonic.data file, its size and date did not change. The date and size are still the same as they were when i took the backup. Why did they not change?

After adding the new media folders did you do a rescan?

:mrgreen:

Yes I did.

Re: Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sun Jan 13, 2013 7:40 pm
by dbenyakar
hakko wrote:1. You could either use Subsonic 4.6 or earlier, or check my highly modified Subsonic server (designed for audio listening, not video streaming) which stores library metadata in a PostgreSQL database instead of HSQLDB. viewtopic.php?f=11&t=10587
2. I think subsonic.data is only written to at certain checkpoints, but not sure as I tend to avoid it as much as possible
3. Saving C:\Subsonic is enough for backup purposes, no information is stored outside of that directory afaik

It looks great.
But how do I migrate the data from HSQLDB to PostgreSQL? and vise versa?
The reason I ask about migrating back to HSQLDB is in case I would like to start streaming videos and I would like to go back to Subsonic server.

Re: Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sun Jan 13, 2013 8:06 pm
by hakko
From HSQLDB to PostgreSQL is done automatically on install (users and settings are actually still stored in HSQLDB). On first usage of MusicCabinet, you have to scan your library to read meta data of all files and folders (similar to the way Subsonic 4.7 works), and as well when you're adding new data to detect the changes. All that metadata about your files, what artists are found and how they are related etc, is stored in PostgreSQL.

From PostgreSQL to HSQLDB is not possible. Make a backup of your current C:\Subsonic to go back to if you don't like it. I've made some changes (for example storing passwords as salted hash sums instead of clear text as in Subsonic) that simply makes it impossible to go back.

Video streaming is actually still there, it's just more hidden and clumsy as it is not the main purpose of this project.

Re: Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sun Jan 13, 2013 9:06 pm
by dbenyakar
Thanks for this hakko
I have a question regarding the installation.
It says in your site:
"Run the Windows installer, use the stand-alone version or the Tomcat war."
What are these installations?

Re: Another case of ERROR 503 - But not due to upgrade.

PostPosted: Sun Jan 13, 2013 9:11 pm
by hakko
The stand-alone contains necessary binaries and startup scripts for running on *ix platforms (Linux, Solaris, MacOSX, FreeBSD etc). The Tomcat war is for people who run Tomcat 6 or 7 instead of Jetty. It's basically the same code, built and bundled for different environments.