After a few more test, we can reproduce this error.
But we found that this error msg ONLY showed in the first few HTTP requests after your rebooting Seahub, after you have used Seahub GUI for a little time, this error This error no longer appears any more.
Is that the case for you?