I'm the "author" of the AutoMongoDump tool on github (github.com/
micahwedemeyer/automongobackup). I basically took the very nice
AutoMySQLDump bash script and modified it for use with MongoDB.
Thanks, by the way, for making the mongodump CLI so similar to
mysqldump. I assume that wasn't an accident.

Anyways, it seems that every time mongodump runs, it writes some debug
output (like "connected to: 127.0.0.1:27017") to stderr. The
automysqldump script is set up to count anything written to stderr as
a serious error and alert the user that the dump has probably failed.
I've hacked around this for my mongo port, assuming that everything in
stderr is just warning messages, not fatal errors. I tried playing
with analyzing the output to stderr a little, but it seemed like a bad
road to head down.

I'd like to request that if anyone chooses to refactor or work on
mongodump, please modify it only write to stderr if a serious error
occurs. That way I can update the script to alert the user in case of
serious errors.