Finally tracked down the oddball valgrind warning that I could never figure

Finally tracked down the oddball valgrind warning that I could never figure
out :)

The check for one particular safety check was wrong (though something in the
server would have to go wrong to trigger this error).