Hello Everybody!
I've had a hard time getting LCG-2.4 to run on xen-2.0.5. And actually, I failed.
I was not able to start the slapd's listening on the 217* ports. Opposing to
the 2135 they're not using the globus version. Also they're using ldbm as a
backend. Running
/opt/openldap/sbin/slapadd -v -f /opt/lcg/bdii/var/marcus/lcg-bdii-slapd.conf
gives me these syslog entries:
Apr 22 19:20:02 xen-4-1 slapadd: ldbm: ==> unable to initialize mutex: Function not implemented
Apr 22 19:20:02 xen-4-1 slapadd: ldbm: ==> process-private: unable to initialize environment lock: Function not implemented
Apr 22 19:20:02 xen-4-1 slapadd: ldbm_initialize_env(): FATAL error in dbEnv->open() : Function not implemented (38)
These syslog entries do not appear when moving /lib/tls.disabled.for.xen to /lib/tls.
Unfortunately I cannot make sure if things work then, because my setup seems to be
infunctional yet.
However, the xen people do not suggest using /lib/tls, because it brings instabilities
as well as performance problems.
Is it necessary to use ldbm?
Is there any other way out?
Stephen: have you experienced similar problems?
Are you running a bdii on xen?
--
Marcus
|