Exceptions from automongobackup, yet script completes
Posted
by
chakram88
on Server Fault
See other posts from Server Fault
or by chakram88
Published on 2012-01-26T16:01:27Z
Indexed on
2012/03/24
23:31 UTC
Read the original article
Hit count: 197
I am using automongobackup to, well, automate the backups of mongodb.
output from the script (to STDERR) has the following exceptions (but the backup completes, and the dump files are created)
###### WARNING ######
STDERR written to during mongodump execution.
The backup probably succeeded, as mongodump sometimes writes to STDERR, but you may wish to scan the error log below:
exception: connect failed
exception: connect failed
exception: connect failed
exception: connect failed
exception: HostAndPort: bad port #
exception: connect failed
exception: connect failed
exception: connect failed
exception: connect failed
exception: connect failed
exception: connect failed
I know that the Host & Port are correct.
If I run mongodump --host=127.0.0.1:27017 --journal
(which is the effective command from automongobackup
based on the options set and my reading of the src code) everything runs clean without any error reporting and the dump files are created as expected.
Why would automongobackup
report connection errors, even tho it does create the dump files, yet a straight call to mongodump
does not?
- Debian 6.0 Lenny (from Linode image: Latest 3.2 (3.2.1-x86_64-linode23))
- AutoMongoBackup VER 0.9
- mongodb v 2.0.2
© Server Fault or respective owner