When using tail to view the log on a problem with the server, the exception with string Config file could not be loaded. is deeply unhelpful, giving an impression of being a “computer says no” moment. Since if it is thrown there is also a more useful stack trace a little further up the stack, we should be handling things a bit better!
(The original problem that triggered this was an attempt to run two instances of spalloc_server on the same port, a configuration/operational issue and not a bug.)
When using
tailto view the log on a problem with the server, the exception with stringConfig file could not be loaded.is deeply unhelpful, giving an impression of being a “computer says no” moment. Since if it is thrown there is also a more useful stack trace a little further up the stack, we should be handling things a bit better!(The original problem that triggered this was an attempt to run two instances of
spalloc_serveron the same port, a configuration/operational issue and not a bug.)