Issue with Dell OpenManage 5.3 inventory under Xen Server 4.1

I wrote in this article how to install Dell OpenManage 5.3 on a Xen 4.1 Host. However, I noticed that when logging into the test systems' GUI that I wasn't seeing an inventory of hardware. Performing the installation again, I noticed a few errors I didn't see originally.

When first running setup.sh, there is a brief display of the following error:

Warning: The lockfile utility is not found in PATH or /usr/bin.
This utility prevents concurrent executions of setup.sh
which can lead to unexpected or invalid installation results.

This appeared again when starting the services

To resolve this, I decided to install lockfile via YUM. The problem is, YUM seems broken by default in 4.1.

Xen is using CentOS for their host OS, but they disable the CentOS repository and enable what appears to be a non-existent/functional Xen repository. Whenever you try to use Yum, it throws an error that the repository checksum is invalid:

http://updates.xensource.com/XenServer/4.0.96/domain0/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
Error: failure: repodata/primary.xml.gz from xensource: [Errno 256] No more mirrors to try.

To resolve this temporarily, and only on my test system, I edited /etc/yum.repos.d/XenSource.repo and changed the following line:

enabled=1

to:

enabled=0

I then edited /etc/yum/repos.d/CentOS-Base.repo and changed the following line under the top "[base]" section

enabled=0

to:

enabled=1

"yum whatprovides lockfile" now returned a bunch of results. It seems "lockfile" is part of the postfix package. To get this file I:

1. ran "yum install postfix"
2. copied "/usr/bin/lockfile" to a temporary location
3. ran "yum remove postfix"
4. copied "lockfile" back to "/usr/bin/lockfile"

Now starting the services ("/opt/dell/srvadmin/omil/supportscripts/srvadmin-services.sh restart") no longer shows an error and I can see the inventory in the GUI

To avoid this cumbersome process on our other Xen hosts I make a new tar.gz of the extracted and modified OpenManage installation which included this file, which I make sure to copy to /usr/bin prior to running "setup.sh" above.