Serviio

First of all, I would like to say this is an excellent program and my hats off to the Devs!
I am running the latest Serviio on my Linux Mint DE machine.
I recently removed a USB storage device and whenever I try to remove the folder from the console I get an error message "An unexpected error occurred (500) Check the log."
The log shows "2013-02-02 12:43:38,238 WARN [ServiioStatusService] PersistenceException occured. Returning error code 500 to the REST layer. Message: Cannot delete Repository with id = 3".
I tried a few things and I was able to delete other folders that were on the same device but this one just wont delete!
thxs

maybe one of the devs can offer a more elegant solution, but to get around this you can just wipe your library and let it recreate. You will will to redo all your settings however.

Can you post the whole log with the error?

Zip, sorry for not letting you have a chance to resolve the problem properly. I had too much time on my hands and I deleted the library.
Thanks again for a great product.
darco

I think I have a similar/related problem.

I have added several online sources before with no problem. I have just tried to add some more and remove some previously added sources and when I hit the save button ( on the php web-based console ) and the page reloads the changes haven't happened.

Here is the log that I have for when this error occurs:


Not sure what to make of it so I hope you can help

Ok, this seems to have fixed itself when I went pro and applied the license... I didn't think that the online sources were a pro feature but I'm not too worried as I was going pro anyway

It's probably a bug in the web UI related to the pro license handling.

I had this last night (not the WebUI bug). I wanted to remove my picture folder before upgrading the library, using the official console it just stopped responding when I pressed save, then using ServiiDroid/WebUI it timed out after a while with a connection error. Ofcourse I had to restart the server to turn on logging, at which point it was either OK, or had finished deleting the folder 10 min later, as it it took me a while to realise what was happening. I had various entires like this in the standard log, but I guess that was due to mutiple requests to delete the same folder.

I've seen this before when deleting large music libraries as well. Unfortunately because my server is quite slow, it takes a very long time to add 30GB of content just to remove it and re-add it.

When deleting a folder via the API, it looks like the method waits until the DB has been purged before returning/something blocks it, can it be pushed off to a new thread?

It could but I left it like this on purpose, as any consequent calls to get list of repositories would return the folders that are being removed. So in the console you click delete, but you'll still get them back. I guess I could mark then with a flag as being deleted and return immediately only those with the flag set to false. Will create a ticket.