REST not responding (503 error)

[agent_kith]

Sorry, but I don't remember.
The only thing I know for sure is that if Snakeoil try to mount an non accessible NAS share it take 2 minutes before the REST starts and if I remove the NAS share in Snakeoil it take 5 seconds for the REST to start.

I will fix that first problem. With the new re-write mounting network shares is a blocking call. i.e. the whole Snakeoil API will do nothing but mount the drives, and proceed to do other tasks only after mounting shares has stopped. This is why you lost access for 2 minutes. 

Never seen this problem in my home setup before cause my NAS is always online.

That's an easy fix.. Just change it to an unblocking call. <- What this means is snakeoil will continue to mount the shares in the background, and continue to work on other tasks.

Let me know if you're listening to music halfway, and then music suddenly stop and resume... That is a sign that the API server has restarted.  <- This is the part I need to look at to make sure this restart is not happening on it's on.