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
Connection failure on second generation #18
Comments
Hi again! I was not able to replicate this issue. I'm using rabbitmq 3.6.10. It looks like a permissions issue. Have you followed the steps in: https://github.com/gmontamat/gentun#basic-rabbitmq-installation-and-setup ? It seems that the server user doesn't have enough permissions to clean up the job queue |
@ahmadmobeen to be more specific, try running:
To update permissions for the |
Actually this is not a permission problem. The real problem is that setup a new user named Line 20 in d852041
When the server instance of DistributedPopulation is created the default value of user guest is replated with test and first generation runs just fine. However, in subsequent generation the default values of credentials are not replaced by test user. We checked it by debugging these 2 places.
In Line 26 in d852041
In Line 95 in d852041
Both are initialized with default user |
@shehzi-khan thank you very much for reporting this bug. I overlooked this problem (will update tests to cover non-guest rabbitmq user). |
I tried this method and it worked for generation # 1.
got the following error in both cases:
Originally posted by @ahmadmobeen in #17 (comment)
The text was updated successfully, but these errors were encountered: