Hmm, we've had one other user getting a
SIGTERM like this, but we haven't found the root cause yet. Part of the problem is just how vague the error message is.
Do you have any more information about what was happening when this error occurred? (Time since you launched, was this in the middle of an operation or while the server was idle?)