Using 1.48 of SCM-Manager, we all of a sudden got this error:
HTTP ERROR: 503 Problem accessing /scm/. Reason: service unavailable powered by jetty://
After a lot of comparison against a clean config installation I noticed that the Repositories.xml file suddenly was 0 bytes in size and no longer a valid XML files. SCM-Manager does not seem to handle this very well since it refused to start up without any clear information of why.
So that should be addressed, but more importantly what can have caused the file to be completely empty?