Hi, I've recently upgraded my ReviewBoard instance to version 3.0.3, from previously being on 2.5.x -- which proceeded without a hitch. I then moved on to setting up Review Bot, which was really the driver for the upgrade, being quite excited by this new functionality.
I followed the docs, plus a little googling, and got everything working. This mean installing the reviewboard extension, rabbitmq-server, and the worker extension, and manually running the worker to connect to rabbitmq. So far, so good. Then I started changing the configuration to try and make it production-worth, and hit a couple of snags. 1. Using a different broken URL resulted in "No worker nodes found." Exact setup was as follows: Server A runs ReviewBoard. Server B runs ReviewBot, RabbitMQ. New user created on RabbitMQ, following the Calery/RabbitMQ docs here: http://docs.celeryproject.org/en/latest/getting-started/brokers/rabbitmq.html Effectively this was: $ sudo rabbitmqctl add_user myuser mypassword $ sudo rabbitmqctl set_user_tags myuser mytag $ sudo rabbitmqctl set_permissions myuser ".*" ".*" ".*" Configure ReviewBoard, -bot extension to point to this, changing the guest:guest broken URL, to one of: amqp://myuser:mypassword@B// It connects to amqp, so that bit looks good. Now I start up the bot on server B, giving it the same URL: reviewbot worker -b "amqp://myuser:mypassword@B//" It connects, and prints out the usual stuff -- the same logging as I saw earlier when i twas running on server A. At this point I'm expecting it to work. However, all I see is "No worker nodes found.". I've tried looking through any logs I can find - server ones, ReviewBoard, etc. And haven't found anything. Things look the same as the successful case. I'm expecting this is some kind of RabbitMQ setup I've got wrong, but without an error in a log anywhere, I don't know how to go about debugging it. Any ideas? 2. The only way I can find to configure the broker URL on the worker is via the command-line This works, but means the password is shown on the command-line, so is not a secure setup. Server B in my setup is a shared-login build machine, so I'd really like to hide this. From reading the ReviewBot code, it doesn't obviously look to me like this can be configured any other way. Have I missed anything here? Is there any way to specify the broker url (which includes a password) other than via the command-line? Thanks for building such a great tool. - Sam -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "Review Board Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
