I still didn’t find a place where the server could exit with code 0 without performing a proper shutdown and also no way how the command line usage hint would print without exiting immediately afterwards, so this part still remains a mystery. Is it possible that the output might somehow come from two different processes?
Image shaders not initialized. Falling back to CPU: Do you have set up any export collections? I just realized that export collections are currently also processed on the server, which really is unnecessary. This shouldn’t really be an issue, though, except for the performance degradation.
Failed to load metadata for getFileInformation API: Failed to locate file aspect-file and Failed to load metadata for 'aspect-file:: These are (unnecessary) warnings that can be caused by files that are in the catalog, but are missing in the file system (either missing properly or not present due to sync storage settings). This will be gone from the log in the next release, since it doesn’t add any value.
One thing in the current synchronization behavior of the server version that might lead to files being removed in the desktop library instance is that files deleted from the file system will automatically be removed from the catalog. If, for example, the contents of the library folder would get deleted while aspect-web is still running, this could result in all files being considered deleted. However, in this case, the files should still be found in the remotely-deleted folder on the desktop, since files will never actually be deleted during the synchronization process as a safety measure*.
But looking at this again, even though this also used to be the default behavior of the desktop version up to 1.0.0-rc.6, it doesn’t really make sense for the server version, since modifying the library on the server within the file system is not really considered a use case and the possibility to accidentally remove files this way is a rather strong argument against it. I’ll change this for the next release to always retain catalog entries.
* Having the files in remotely-deleted will also allow to implement the possibility to revert changes where files have been deleted (regarding the revision history feature request)