Red Hat Bugzilla – Bug 850861
ctdb+systemd problems
Last modified: 2014-06-18 03:42:45 EDT
There are a number of problems with the ctdb.service file: 1) it defines a PIDFile= directive, but ctdb doesn't create any sort of pidfile there. This makes the startup via systemd fail. Commenting that directive out works, but you probably need to think about how this should be monitored? 2) There is a problem with quoting in the /etc/ctdb/systemd/ctdb.systemd file. The "exec" line has $CTDB_OPTIONS in quotes, which makes it pass the whole thing as one giant argument. Those quotes need to be removed. 3) the startstop_nfslock() function in "functions" probably also needs updating for systemd-ized machines. Still looking at that piece. Patches forthcoming...
Created attachment 606315 [details] patch: fix up systemd integration goop
Comment on attachment 606315 [details] patch: fix up systemd integration goop This patch should fix most of the issues so that ctdb can at least start properly now. I've not touched the NFS integration parts yet, since I have my doubts as to whether that's safe anyway...
ctdb-1.2.39-5.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/ctdb-1.2.39-5.fc18
ctdb-1.2.39-5.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.