I'm actually getting a similar message right now. I've found some information that indicates this *might* be related to a "dirty" ssh connection, wherein some "junk" gets injected into the stdout or stderr, when the ssh connection should be silent.