Learn more about these different git repos.
Other Git URLs
When setting multiple celery workers,
I'm looking at,
Jan 14 08:55:32 qemu celery[26037]: 2019-01-14 08:55:32,083 [WARNING] celery.redirected: /opt/pag_01/pag_01-server/venv/lib/python3.5/site-packages/celery/app/control.py:52: DuplicateNodenameWarning: Received multiple replies from node name: celery@qemu. Jan 14 08:55:32 qemu celery[26037]: Please make sure you give each node a unique nodename using Jan 14 08:55:32 qemu celery[26037]: the celery worker `-n` option. Jan 14 08:55:32 qemu celery[26037]: pluralize(len(dupes), 'name'), ', '.join(sorted(dupes)), Jan 14 08:55:32 qemu celery[26037]: 2019-01-14 08:55:32,086 [INFO] celery.worker.consumer.mingle: mingle: all alone Jan 14 08:55:32 qemu celery[26037]: 2019-01-14 08:55:32,132 [INFO] celery.apps.worker: celery@qemu ready.
Maybe using a -n pagure_$name e.g. -n pagure_ci or -n pagure_gitoline
-n pagure_$name
-n pagure_ci
-n pagure_gitoline
For the systemd files would be a solution to it.
Metadata Update from @pingou: - Issue tagged with: RFE, easyfix
Metadata Update from @pingou: - Issue set to the milestone: Coming 3 months
Is somebody working on this issue? I would like to take it.
Metadata Update from @wombelix: - Issue assigned to wombelix
I'm working on a FreeBSD Port, used the systemd files as blueprint and came across the same problem, so I guess it's still a thing, I will verify it and add node names to the systemd service files if necessary.
Metadata Update from @wombelix: - Issue set to the milestone: 5.13 (was: Coming 3 months)
Metadata Update from @wombelix: - Issue set to the milestone: 6.0 (was: 5.13)
That's part of the master branch in the meantime and I think we also backport it into the upcoming 5.14 release. Fixed.
master
5.14
Metadata Update from @wombelix: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.