Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors generated incorrectly when not in replica set #12

Open
Pharkie opened this issue Mar 24, 2012 · 2 comments
Open

Errors generated incorrectly when not in replica set #12

Pharkie opened this issue Mar 24, 2012 · 2 comments

Comments

@Pharkie
Copy link

Pharkie commented Mar 24, 2012

When this is a single 'master' server that is not in a replicaset and the config is set to:

# Choose other Server if is Replica-Set Master 
REPLICAONSLAVE="yes"

The following errors are generated:

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

Please see my answer on ServerFault from 'Adam Knowles' at

http://serverfault.com/questions/353912/exceptions-from-automongobackup-yet-script-completes/373073#373073

@kwilczynski
Copy link
Contributor

Thank for bringing this on up. I will look into fixing it.

As per the feedback so far ... we need to improve documentation and make script more robust.

@rubyconvict
Copy link

script should be more verbose, and for now, a proper config is needed #18 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants