-
Notifications
You must be signed in to change notification settings - Fork 22
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
bad credential amqps://[email protected] #1328
Comments
I think it understands ... filling in the anonymous password for the anonymous user... but it incorrectly complains about a missing entry... have to reproduce the problem, then dream up some strategies to get around it. I confirm it should not result in data loss, or any delay though. |
Even if you put in the password, it still complains. |
When you say "put in the password" ... the place to put it would be in ~/.config/sr3/credentials.conf... The warning should go away if you have an entry like: amqps://anonymous:[email protected] in that file. I guess we can call that a work-around. |
Oh, by "put in the password", I mean putting |
Well if you try putting it in the credentials file... let me know if the error goes away. |
best practice is to put all passwords in the credentials files... and keep the configs password free... but it does work if you put the pw straight in the config... we don't want to be too stubborn about it. |
The error does go away if you have |
users should not need a "credentials.conf" file to exist... when you need credentials.conf... should be more explicit about pointing out the file name and format needed. |
work-around to prevent message... do not put the username in the url broker amqps://dd.weather.gc.ca Does not provoke the error... only when username is used. (is default anyways.) |
I've noticed recently that when I start up sr3, I get logs like this:
After that, sr3 is able to function in what appears to be a normal manner. Is this something that needs fixing?
Here's my config file:
The text was updated successfully, but these errors were encountered: