Hello Maarten,
In fact the error message is:
[se2.egeode.org ~]# /etc/init.d/bdii start
Starting SLAPD: SLAPD failed to start [FAILED]
and when I run manually the command line from the /etc/init.d/bdii
script it works !
I have many errors in bdii-update.log file, but it does not seem to be
connected to the starting problem.
tail -500 /var/log/bdii/bdii-update.log
dpm_getspacetoken: No accessible space token
dpm_getspacetoken: No accessible space token
dpm_getspacetoken: No accessible space token
Is there a possibility to start bdii in debug mode ? Can I put a sort
of DEBUG=yes in /etc/init.d/bdii script ?
best regards, Jean-Bernard
On 01/25/2010 10:49 PM, [log in to unmask] wrote:
> Bonjour Jean-Bernard,
>
>
>> I've just installed with YAIM a new CREAM-CE (ce2.egeode.org) and a new
>> SE_DMP_mysql (se2.egeode.org)
>> and each time the local bdii is not starting. (OS = SL 5.4 x86_64 ) but
>> I can successfully start it
>> manually with command lines:
>>
>> For the CREAM-CE:
>> /usr/sbin/slapd -f /opt/bdii/etc/bdii-slapd.conf -h
>> ldap://ce2.egeode.org:2170 -u edguser
>> /opt/bdii/bin/bdii-update -d -c /opt/bdii/etc/bdii.conf
>>
>> For the SE_DMP_mysql:
>> /usr/sbin/slapd -f /opt/bdii/etc/bdii-slapd.conf -h
>> ldap://se2.egeode.org:2170 -u edguser
>> /opt/bdii/bin/bdii-update -d -c /opt/bdii/etc/bdii.conf
>>
> What happens when you run the standard command:
>
> /etc/init.d/bdii start
>
> Are there error messages?
>
>
>
|