Hide Forgot
Description of problem: For init scripts and troubleshooting the clmvd should return non-zero if it cannot be started. In this case the dlm module was not loaded. The only way (I can see) to get more info on this is by running it with the -d flag. [root@link-10 root]# clvmd [root@link-10 root]# echo $? 0 [root@link-10 root]# pidof clvmd [root@link-10 root]# clvmd -d Unable to create lockspace for CLVM Can't initialise cluster interface [root@link-10 root]# modprobe dlm [root@link-10 root]# clvmd [root@link-10 root]# echo $? 0 [root@link-10 root]# pidof clvmd 5000 [root@link-10 root]# Version-Release number of selected component (if applicable): [root@link-10 root]# clvmd -V Cluster LVM Daemon version 0.2.1 How reproducible: Steps to Reproduce: 1. Quorate cman cluster 2. Do not have the dlm module loaded 3. Start clvmd Actual results: clvmd did not start. returned 0. Expected results: Return non-zero on failure. Additional info:
This was because clvmd forked before trying to open the cluster manager socket. So what it was saying was "success...I've forked", then it failed whilst a daemon. I've moved the fork to later on in the startup sequence now so it can return error codes for the most basic problems. For others you'll just have to watch syslog :)
Verified: [root@link-12 root]# clvmd Unable to create lockspace for CLVM Can't initialise cluster interface [root@link-12 root]# echo $? 5 [root@link-12 root]#
Updating version to the right level in the defects. Sorry for the storm.