Description of problem: 1. Installed Pulp (v0.109) on F14 x86_64. Did not have crontabs package installed. Installation proceeded with no issues. Error during service pulpd init: -bash-4.1# service pulpd init Starting mongod: [ OK ] sh: /usr/bin/crontab: No such file or directory sh: /usr/bin/crontab: No such file or directory sh: /usr/bin/crontab: No such file or directory sh: /usr/bin/crontab: No such file or directory database migration to version 1 complete Exception in thread Thread-1 (most likely raised during interpreter shutdown): Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 530, in __bootstrap_inner File "/usr/lib64/python2.7/threading.py", line 483, in run File "/usr/lib/python2.7/site-packages/pulp/server/tasking/queue/fifo.py", line 83, in _dispatch <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'critical' 2. yum install crontabs 3. service pulpd init -bash-4.1# service pulpd init no crontab for root data model in use matches the current version database migration to version 1 complete
commit 70bdb9d38fd24551a130917314f1625d1052659a tree e756d07133be2ed8a0bebd4df7bed17bfd96dbe8 661850 - Added crontabs as a dependency. It is used for scheduled events, such as repo syncs and auditing/consumer history culling. pulp.spec
Fixed in build 0.114.
Here is what I see, Please let me know if this is ok. [root@pulp2 ~]# yum install pulp --> Processing Dependency: crontabs for package: pulp-0.0.119-1.fc14.noarch [root@pulp2 ~]# rpm -q crontabs crontabs-1.11-1.20101115git.fc14.noarch [root@pulp2 ~]# rpm -q pulp pulp-0.0.119-1.fc14.noarch [root@pulp2 ~]# service pulp-server init Starting mongod: [ OK ] no crontab for root database migration to version 1 complete I see the no crontab for root message above [root@pulp2 ~]# service pulp-server start Starting Qpid AMQP daemon: [ OK ] Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 10.16.79.226 for ServerName [ OK ]
The "no crontab" message is only saying that there wasn't a crontab entry for root yet. If you see that, it means cron is installed and able to do that check. If you didn't have crontab installed, instead of that message you'd see an error that cron could not be found. The easiest way to verify this is to uninstall crontab and install pulp, checking that pulp installed it in the process. For completeness, it'd be ideal to test this on both RHEL 5 and Fedora 13/14 to make sure that the package is named correctly in both cases.
So, it helps if I pay attention when I read your comment. Looks like you already verified that "yum install pulp" pulls in crontabs as a dependency. The "no crontab" isn't an error and just a result of using cron.
Moving to verified as per the comments above in 119
Closing with Community Release 15 pulp-0.0.223-4.