I saw the problem you are having with the inability to start the openfiler service. I just recently installed OpenFiler following the same tutorial on this site and encountered the same error; however, I don't think it's really a problem, and perhaps maybe by design.
Is root@offsan1 your secondary node? If so, you won't be able to start the OpenFiler service. This is automatically started by Heartbeat after a failover has occurred.
For example, I am running both nodes in virtual machines, and after pausing my primary, the failover is initiated. On the secondary node, a message should be presented after the failover completes telling you "You have new mail in /var/spool/mail/root".
On the secondary node, drbd will look like this:
m:res cs ro ds p mounted fstype
0:cluster_metadata WFConnection Primary/Unknown UpToDate/DUnknown C /cluster_metadata ext3
1:vg0drbd WFConnection Primary/Unknown UpToDate/DUnknown C
The httpd service does not apply, because I believe the OpenFiler service is acting as a web service. At this point running service openfiler status
should return that the service is running, and you can access the node via the virtual IP you defined in the setup instructions. When you look at the Status page in the web UI, it should indicate that it is looking at your secondary node.
Finally, you can look at /opt/openfiler/etc/httpd/conf/httpd.conf, since now the file will exist.
I am a novice as well, but I hope this helps and represents accurate information.