-
Notifications
You must be signed in to change notification settings - Fork 24
mongoq: Authentication mechanism not supported #25
Comments
Hmm, using Please comment on this issue if authentication is still a problem. Thanks! |
Hi! Thanks a lot. Flag problem is solved by using earlier version of go-flags. I still have problems with authentication. I've forgotten to say that I'm using region eu-central-1. The command looks like this
I think that european servers require to use AWS v4 authentication (http://stackoverflow.com/questions/26533245/the-authorization-mechanism-you-have-provided-is-not-supported-please-use-aws4). Thanks again! |
Hi again, I've removed the region parameter "-R" and now I can access the extended mogoDB shell. In the other hand, I think I haven't configured something wrong, because I cannot see my backed up database, but I'll try to set it up again. Thanks! |
Ok. One suggestion is make sure that yas3fs is working by running |
Hi @AGFeldman, I could get mongoq working by runing yas3fs in a sepparated shell. I didn't undestand that I must have yas3fs running while running mongoq. I only still have a minor problem, but I tell you to know if it's intended or not. When I run mongoq, before taking a backup by id with command cb, all logs are bad intended and it's really difficult to read at logs. I show you an example here:
Thanks a lot for helping me run mongoq! 😃 |
I'm glad it seems to be working! That indentation is unfortunate. I don't recall coming across that issue :/ |
Hi,
I'm trying to use mongoq to browse my backups but I'm having some trouble. I think there's something wrong with mongoq. I hope anyone can help me.
The first problem is that I'm trying to run the command
./mongoq -b=all_backups -p=mongo-rocks -m=/path/to/desired/mountpoint
But mongoq says that flag "m" is unknown, so I cannot specify my S3 replica path.
unknown flag 'm'
If I don't specify the replica path, then mongoq says this:
Thanks for this great tools! I'm using strata for backup/restore and works like a charm 👍
The text was updated successfully, but these errors were encountered: