Description of problem: After an system reboot pulp_workers, pulp_celerybeat and pulp_resource_manager services is not started. Version-Release number of selected component (if applicable): # rpm -qa | grep pulp python-pulp-common-2.4.0-0.10.beta.el6.noarch createrepo-0.9.9-21.2.pulp.el6.noarch mod_wsgi-3.4-1.pulp.el6.x86_64 pulp-server-2.4.0-0.10.beta.el6.noarch pulp-selinux-2.4.0-0.10.beta.el6.noarch pulp-admin-client-2.4.0-0.10.beta.el6.noarch python-isodate-0.5.0-1.pulp.el6.noarch python-pulp-client-lib-2.4.0-0.10.beta.el6.noarch m2crypto-0.21.1.pulp-8.el6.x86_64 python-pulp-puppet-common-2.4.0-0.10.beta.el6.noarch pulp-puppet-plugins-2.4.0-0.10.beta.el6.noarch pulp-rpm-admin-extensions-2.4.0-0.10.beta.el6.noarch python-pulp-rpm-common-2.4.0-0.10.beta.el6.noarch python-kombu-3.0.15-4.pulp.el6.noarch pulp-rpm-plugins-2.4.0-0.10.beta.el6.noarch python-pulp-bindings-2.4.0-0.10.beta.el6.noarch pulp-puppet-admin-extensions-2.4.0-0.10.beta.el6.noarch How reproducible: Always Steps to Reproduce: 1. make sure all services is enabled. # chkconfig --list | grep pulp pulp_celerybeat 0:off 1:off 2:on 3:on 4:on 5:on 6:off pulp_resource_manager 0:off 1:off 2:on 3:on 4:on 5:on 6:off pulp_workers 0:off 1:off 2:on 3:on 4:on 5:on 6:off 2. reboot the system # shutdown -hr now 3. When the system is rebooted check the status on the services. # service pulp_workers status celery init v10.0. Using config script: /etc/default/pulp_workers cat: /var/run/pulp/*.pid: No such file or directory bad pid file (/var/run/pulp/*.pid) # service pulp_resource_manager status celery init v10.0. Using config script: /etc/default/pulp_resource_manager cat: /var/run/pulp/*.pid: No such file or directory bad pid file (/var/run/pulp/*.pid) Actual results: The services is not running and no tasks can be executed. Expected results: Additional info:
This ended up being a combination of two problems with the init scripts. See the pull request for more details: https://github.com/pulp/pulp/pull/957
Once the fix for this bug makes it into a build, you will need to "re-chkconfig" these services so that they get into a new startup order. Here's a oneliner that I didn't try out but might work: for s in {pulp_celerybeat,pulp_resource_manager;pulp_workers}; do sudo chkconfig $s off; sudo chkconfig $s on; done;
This was fixed by today's pulp-2.4.0-0.14.beta build.
verified [root@pulp-v2-server ~]# rpm -qa pulp-server pulp-server-2.4.0-0.23.beta.el6.noarch [root@pulp-v2-server ~]# [root@pulp-v2-server ~]# service pulp_workers status celery init v10.0. Using config script: /etc/default/pulp_workers node reserved_resource_worker-0 (pid 1947) is running... [root@pulp-v2-server ~]# service pulp_resource_manager status celery init v10.0. Using config script: /etc/default/pulp_resource_manager node resource_manager (pid 1833) is running... [root@pulp-v2-server ~]#
This has been fixed in Pulp 2.4.0-1.