503 Service Unavailable - Corrupt DB?

[Xylex]

I have been using subsonic for a long time now, and I love it. I would like to continue using it for as long as its being developed.

I have a challenge now that I fear may cause me serious issues.
I added newly collected content when suddenly, subsonic stooped playing music I was listening to.
the page kept timing out. I restarted the service. And started getting 503 errors.
Yes I have searched the forums and found the same answer. Corrupt Database.

What I need to know, is there a reason why the database gets corrupted?
I have a very very large collection. I am concerned that my massive collection my be the cause of this failure.
If this is even a remote possibility of the cause, I would like a general idea of "Best Practices" for a collection as large as mine.

Side Note: I am aware of Music Cabinet, and I am not yet willing to move to it, as then I would rely upon two groups to keep the software up to date.

My current set up is as follows:
Susbonic VM Debian 7 x64 running on ESXi 5.5 with 4GBs RAM, and Dual Quad Xeons E5620I do appol
Storage NAS running FreeNAS 9.2.1.3 x64 with 64GBs DDR3 and Dual Hex core Xeons E5-2620
8 2TB Drives, in RAID1Z totaling 12TBs
These servers are located in a datacenter with no bandwidth cap.

Let me know what you all think.

Thanks

[alphawave7]

There seems to by a myriad of reasons a db gets corrupted, and without logs it's all a guess. If it's not too much trouble with the volume of your users, it's fastest to delete it and rebuild it.

[Xylex]

I decided to accept the loss of all the rated music I had and start the database over.
Unfortunately, even after renaming the db folder to something else, the server still gives me a 503 error.
From what the logs show, its seems like a successful connection.

What am I missing here?

[alphawave7]

I decided to accept the loss of all the rated music I had and start the database over.
Unfortunately, even after renaming the db folder to something else, the server still gives me a 503 error.
From what the logs show, its seems like a successful connection.

What am I missing here?

I believe you may need to delete the c:/subsonic directory to reinitialise a new db. I would also go ahead and delete Java, and reinstall. Sorry it's sucking so much!

[okieeagle]

I decided to accept the loss of all the rated music I had and start the database over.
Unfortunately, even after renaming the db folder to something else, the server still gives me a 503 error.
From what the logs show, its seems like a successful connection.

What am I missing here?

I believe you may need to delete the c:/subsonic directory to reinitialise a new db. I would also go ahead and delete Java, and reinstall. Sorry it's sucking so much!

I've done this. The service worked for a little while, then suddenly stopped working again, nothing changed, that I can think of. This is getting quite upsetting.

[alphawave7]

I decided to accept the loss of all the rated music I had and start the database over.
Unfortunately, even after renaming the db folder to something else, the server still gives me a 503 error.
From what the logs show, its seems like a successful connection.

What am I missing here?

I believe you may need to delete the c:/subsonic directory to reinitialise a new db. I would also go ahead and delete Java, and reinstall. Sorry it's sucking so much!

I've done this. The service worked for a little while, then suddenly stopped working again, nothing changed, that I can think of. This is getting quite upsetting.

It is usually a Java update and improper shutdown/reboot that is the root of the corrupt db issue. I always stop SS service, THEN update Java manually, reboot, and the SS service restarts on the new boot, and I haven't had a 503 error in ages.