pagure

#2661 pagure_worker service fail: celery does not recognize autoreload argument
Closed: Fixed Opened by serafim.

Closed: Fixed
Reopen Issue

I am trying to configure a development enviroment and noticed that pagure_worker service did not start

-- The start-up result is done.
Oct 06 23:28:18 pagure-dev.example.com celery[9025]: usage: celery worker [options]
Oct 06 23:28:18 pagure-dev.example.com celery[9025]: celery: error: unrecognized arguments: --autoreload
Oct 06 23:28:18 pagure-dev.example.com systemd[1523]: pagure_worker.service: Main process     exited, code=exited, status=2/INVALIDARGUMENT

celery version 4.1.0 is installed in virtual environment but the --autoreload feature was removed in version 4.0 according to this page.

@pingou remember something ? :p

Which system is this running on?

@vivekanand1101 how did you fix this?
Edited by pingou

Metadata Update from @pingou:
- Issue tagged with: bug, easyfix

I am using vagrant and the example vagrantfile available on dev folder, as described on README.rst.

Ansible provisioning fails to enable the pagure services, as described on bug #2647.
So i use vagrant ssh to access the machine and then execute...

systemctl --user enable pagure_worker
systemctl --user start pagure_worker
journalctl -xe

...which allows me to see that error message

@serafim removing --autoreload from the ExecStart from both pagure_worker and gitolite worker should do

@vivekanand1101 thanks, I was able to get pagure_worker to start

Fixed in #2678

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
Metadata
None

bug easyfix

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.