Raise a critical if we can't read the replication status.

Exception handling introduced by 0c83e66e was completely broken.
find() was incorrectly used and matched all received error messages
reporting that was OK.
Also, there is no reason to respond OK, if we check a replication lag
and the node does not run with --replSet.
Use in to test the presence of a substring in a string.