If one of your check servers crashes/was hard rebooted and it is running MongoDB you will most likely need to resync the MongoDB replicaset since the 32bit version of MongoDB doesn't use journaling.
First, check to see if your MongoDB instance needs to be resynced, tail the /var/log/mongo/mongod.log and if you see the following you will need to perform a resync.
tail -n 100 /var/log/mongo/mongod.log
Unclean shutdown detected.
Please visit http://dochub.mongodb.org/core/repair for recovery instructions.
If you don't see a message about an unclean shutdown then your replica set is fine and doesn't need repaired.
If you do see this message, then ssh to the server that was rebooted and issue the following commands which backs up the existing replicaset data on that server, then removes it so it can be resynced. (If you have recovered this mongodb instance before you will need to use a different backup directory name instead of mongo-bk or remove the old mongo-bk before issuing the following commands).