I was seeing the same behavior that Peter is seeing with a slight twist. Most of my recordings are made on my master backend (settop-2), my only slave backend was taking transcode jobs and failing with a 242 status like Peter is reporting. I changed the "jobs run only on host machine" setting for only my master backend. After restarting both backends it seems like now the recordings are being transcoded correctly for the master backend.
<br><br>Of course what I'd really like to see is myth to be able to be able to continue to run commflagging on non-busy remote backends and keep transcodes on the backend it was recorded on. Don't know if this is planned or possible given the current code base. (I'm running .20-147.)
<br><br>...Kevin<br><br><br>