You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Splitting off from #5278 one smaller task.
Before 2.0 we should add, if possible, a clear warning if the version of RabbitMQ is incompatible. In this way, people know and fix this before starting to run in production with AiiDA, and discovering weeks later that there is an issue (and that is very hard to debug, because the error shows up as seemingly random "Channel is closed" errors.
Some sub-tasks:
check programmatically the version of RabbitMQ (to see how to do it)
add checks in all relevant places (definitely in verdi status and in verdi daemon start, possibly also in verdi shell if not too slow?)
The warning should point to a wiki page with more information (EDIT: here is the page). For now we put a general explanation of the problem and relevant links to issues, as well as some instructions on how to fix the issue. However, this page might improve in the future (e.g. if we also want to suggest to keep using the newer version, we need to explain:
how to change the RMQ configuration to a longer time
how to reset the permanent queues that might have been already created if the user already started using the profile (as these might have incompatible settings and RMQ would crash)
update the installation documentation. This should include both the system-wide installation and all other paths (conda, etc.). If appropriate, we can just highlight with some emphasis that version should be <=3.7, and link to the wiki page
I don't know if there is an easy way to get the version via the communicator, e.g. via KiwiPy or the underlying libraries. @muhrin do you have any idea if this is possible? (or @sphuber@chrisjsewell )
Let me have a look. I did try this some time ago but I think it wasn't trivial, let me see if the underlying library we use has made it any easier now...
At the moment, in Ubuntu 20.04, it seems to me that the simplest approach is to tell users to run RabbitMQ in a docker container, because even using the APT sources provided by RabbitMQ, they anyway provide only versions 3.8.x and 3.9.x.
@sphuber could you please add some comments on how to run with a recent version (or @chrisjsewell or anyone who tested this); I left some notes of things one might need to say
@chrisjsewell is there a way to select the version of rabbitmq with conda? If so, can you add a paragraph to the wiki? So we can then later also link to it (or update) the installation docs
Splitting off from #5278 one smaller task.
Before 2.0 we should add, if possible, a clear warning if the version of RabbitMQ is incompatible. In this way, people know and fix this before starting to run in production with AiiDA, and discovering weeks later that there is an issue (and that is very hard to debug, because the error shows up as seemingly random "Channel is closed" errors.
Some sub-tasks:
update the installation documentation. This should include both the system-wide installation and all other paths (conda, etc.). If appropriate, we can just highlight with some emphasis that version should be <=3.7, and link to the wiki pageLast point was split off to separate issue #5317
The text was updated successfully, but these errors were encountered: