Warning: RabbitMQ v3.9.13 is not supported and will cause unexpected problems!

General Usage
1

Hi developers,
I came across this warning. I went to RabbitMQ version to use · aiidateam/aiida-core Wiki · GitHub and followed the instructions.

I created the rabbitmq.conf in the /etc/rabbitmq/ directory with content

# 1000 hours in milliseconds (increase if you expect your workflows to run longer)
consumer_timeout = 3600000000

And then restarted RabbitMQ via service rabbitmq-server restart

Will this fix this issue? There is a way to supress the warning via but real question is will there be any issue or is there other way I need to do to fix this?

verdi config set warnings.rabbitmq_version false

(aiida) rkarkee@RKARKEE:~$ verdi status
 ✔ version:     AiiDA v2.5.1
 ✔ config:      /home/rkarkee/.aiida
 ✔ profile:     rkee
 ✔ storage:     Storage for 'rkee' [open] @ postgresql://aiida:***@localhost:5432/aiidadb / DiskObjectStoreRepository: 493c766da9614dc5ac0c32fe379bef27 | /home/rkarkee/.aiida/repository/rkee/container
Warning: RabbitMQ v3.9.13 is not supported and will cause unexpected problems!
Warning: It can cause long-running workflows to crash and jobs to be submitted multiple times.
Warning: See https://github.com/aiidateam/aiida-core/wiki/RabbitMQ-version-to-use for details.
 ⏺ rabbitmq:    Incompatible RabbitMQ version detected! Connected to RabbitMQ v3.9.13 as amqp://guest:guest@127.0.0.1:5672?heartbeat=600
 ✔ daemon:      Daemon is running with PID 76997
2

Hi, indeed if you set the consumer_timeout correctly, you can just suppress the warning as you indicate and everything will work normally. If for any reason the setting wasn’t set correctly, what you will notice when you will run long workflows, they will stop after 30 minutes. If this should happen, double check if you set the consumer_timeout correctly. Otherwise, just silence the warning and everything will be OK!

4

If for any reason the setting wasn’t set correctly, what you will notice when you will run long workflows, they will stop after 30 minutes.

Small correction: they will not just stop, but you will see the workchains starting to except with all sorts of different exceptions. This requires more than 1 daemon worker being active however.

To check whether RabbitMQ properly picked up the configuration option, you can run the following command:

sudo rabbitmqctl environment | grep consumer_timeout

This should print the value you set if it is set correctly