GJ51 wrote:As much as I respect and appreciate all that Hakko does and I readily acknowledge that he is using a better database than what is native to Subsonic; don't be mislead into thinking that Subsonic is inherently unstable and cannot be set up to run dependably. To jump to the conclusion that your issues are an incurable flaw that can't be remiedied is illogical in lieu of the fact that many of us are not experiencing the same issues.
If you are having db stability issues you can try a few things.
Uncheck your media folders "Enabled" boxes and rescan then clean-up db which doesn't take very long when there's nothing to scan. Then re-enable the folders and rescan.
Your description of your problems is too vague to suggest anything else. A few more details might give us enough to suggest a few other things.
HTH
HTH
I do respect the extreme quality work of Subsonic and I never say the contrary. Since 4.7 update though, I still had 2 problems with the database. Please allow me to explain what happen. First, for the upgrade from 4.6 to 4.7, database went corrupted, the website was unavailable with a 500 internal server error I think, from jetty. I checked the logs, and I found that the cause of the problem. I googled the problem and found some solutions on the subsonic forum, which first told me, as the only possible solution, to start over from scratch, which I did (I can't retrieve the thread, sorry). So I deleted the "db" folder, and indeed, everything was working back.
The second time the same problem occurred, my Unix server had shut down unexpectedly, due to a storage problem on the physical machine. So when I restarted the server, the database was AGAIN corrupted. I didn't wanted to loose again all my settings, so I've searched again and found another thread on the subsonic forum of the existence of "db.view" page, which allowed me to recover some stuff quickly, but still, I lost some data.
What I'm saying here is, Subsonic is stable overall, but the database doesn't help at all. Each time the database was corrupted, I wasn't able to access the web interface, jetty couldn't work correctly because of the database error. I can't find logs anymore, but if it's happen again, I will be pleased to show you them. And yeah, so if jetty is unable to show me the web interface, I wasn't able to access the settings of subsonic. The only possible way to fix the problem for me was to directly access the server and fix the problem locally by modifying subsonic files.
