I noticed that several errors are logged all with a similar content:
fatal: bad config line 1 in file C:/Continua/Rc/2e72daac/.git/modules/lib/CommonUtils/config
The actual repository changes, but up to now it affects sub modules only (seems also arbitrary ones).
The config files in question have different sizes, but all are filled with NUL bytes. I cannot say when that happened and why, but when in this state I constantly get these error messages.
Currently I can fix this by resetting the affected repositories, but after a while it usually happens again.
Continua doesn’t directly manipulate the config files - it calls the Git command-line for all repository operations. The corruption you are seeing, where the config file is filled with NUL bytes, generally indicates that a write to the file was interrupted. To begin with, we recommend checking that the latest stable version of Git is installed on the server, as older versions can occasionally have issues that are fixed in more recent releases.
Typically, files only become corrupt when something interrupts the write process. It’s worth reviewing earlier messages in the Continua Event Log for any errors or warnings that might point to a process failure or a problem when Git was writing to disk. Also consider possible external causes. Real-time antivirus software is a common culprit when I/O errors occur, so please make sure that C:\Continua is fully excluded from any real-time anti-virus protection. It’s also a good idea to check for hardware-related issues such as low disk space or disk errors by reviewing the Windows event log.
Could you post the complete error output, or send it to me directly, so that we can see exactly which Git command is reporting the problem? We’d also like to see any earlier errors in the event log, as these often reveal the point where the write failed. The simplest way to gather everything is to generate a diagnostics report from the Event Log page and send it to me directly or by email to support at finalbuilder.com.
Once we have the full error details and the related event log entries, we can determine whether it’s feasible for Continua to run additional Git commands to automatically detect and repair a damaged repository when this situation occurs.