Hi Laurence,
Yes !
That was the problem... Disabling SE Linux solved it !
Thanks a lot.
--
Luc
> -----Message d'origine-----
> De : Laurence Field [mailto:[log in to unmask]]
> Envoyé : lundi 4 avril 2011 15:49
> À : LHC Computer Grid - Rollout
> Cc : Santeramo Luc
> Objet : Re: [LCG-ROLLOUT] strange behavior with /etc/init.d/bdii
>
> Hi,
>
> Do you have SE Linux enabled?
>
> Laurence
>
> On 04/04/2011 12:13 PM, Santeramo Luc wrote:
> > Hello,
> >
> > I'm using bdii-5.0.9-1.noarch on SL5.5.
> >
> > If I try to start it with the default script (/etc/init.d/bdii), it does not want to :
> > [root@egi-se ~]# /etc/init.d/bdii start
> > Starting SLAPD: SLAPD failed to start [ÉCHOUÉ]
> >
> > As suggested by other people I tried following commands :
> > [root@egi-se ~]# service bdii start
> > Starting SLAPD: SLAPD failed to start [ÉCHOUÉ]
> >
> > [root@egi-se ~]# env -i bash
> > [root@egi-se root]# /etc/init.d/bdii start
> > Starting SLAPD: SLAPD failed to start [ÉCHOUÉ]
> >
> >
> > Looking to slapd start process, I can see following lines after activating debug
> :
> > Starting SLAPD: @(#) $OpenLDAP: slapd 2.3.43 (Mar 10 2011 18:51:22) $
> >
> > [log in to unmask]:/builddir/build/BUILD/openldap-2.3.43/openl
> > dap-2.3.43/build-servers/servers/slapd
> > daemon: bind(7) failed errno=13 (Permission denied) slapd stopped.
> > connections_destroy: nothing to destroy.
> >
> >
> > But If I try forcing bash interpreter, it works :
> > [root@egi-se ~]# bash /etc/init.d/bdii start
> > Starting SLAPD: [ OK ]
> >
> > Starting update process: [ OK ]
> >
> > If I had a # on the first line of the script, it works too (without forcing bash
> interpreter) :
> > [root@egi-se ~]# head /etc/init.d/bdii # #! /bin/bash # # BDII system
> > startup script # $Id: bdii,v 1.9 2009/06/18 14:26:52 lfield Exp $ #
> > chkconfig: 345 95 5 # description: BDII Service # config:
> > /opt/bdii/etc/bdii.conf shopt -s expand_aliases
> >
> >
> > [root@egi-se ~]# /etc/init.d/bdii start
> > Starting SLAPD: [ OK ]
> >
> > Starting update process: [ OK ]
> >
> > Why not... But, after system reboot, this "solution" is not working (with or
> without # on the first line).
> > The problem is the same on the SE and CE.
> > I can't find anything about this on ggus or lcg-rollout archives....
> >
> > Could somebody explain this please ?
> > Do you have a known workaround or do I have to dig further?
> >
> > Thanks.
> >
> > Regards,
> > Luc
> >
> ****************************************************************
> ******
> > ************************ Pensez a l'environnement avant d'imprimer ce
> > message Think Environment before printing
> >
> > Le contenu de ce mel et de ses pieces jointes est destine a l'usage
> > exclusif du (des) destinataire(s) designe
> > (s) comme tel(s).
> > En cas de reception par erreur, le signaler a son expediteur et ne pas en
> divulguer le contenu.
> > L'absence de virus a ete verifiee a l'emission, il convient neanmoins
> > de s'assurer de l'absence de contamination a sa reception.
> >
> > The contents of this email and any attachments are confidential. They
> > are intended for the named recipient
> > (s) only.
> > If you have received this email in error please notify the system
> > manager or the sender immediately and do not disclose the contents to
> anyone or make copies.
> > eSafe scanned this email for viruses, vandals and malicious content.
> >
> ****************************************************************
> ******
> > ************************
**********************************************************************************************
Pensez a l'environnement avant d'imprimer ce message
Think Environment before printing
Le contenu de ce mel et de ses pieces jointes est destine a l'usage exclusif du (des) destinataire(s) designe
(s) comme tel(s).
En cas de reception par erreur, le signaler a son expediteur et ne pas en divulguer le contenu.
L'absence de virus a ete verifiee a l'emission, il convient neanmoins de s'assurer de l'absence de
contamination a sa reception.
The contents of this email and any attachments are confidential. They are intended for the named recipient
(s) only.
If you have received this email in error please notify the system manager or the sender immediately and do
not disclose the contents to anyone or make copies.
eSafe scanned this email for viruses, vandals and malicious content.
**********************************************************************************************
|