[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: ldap server hungs after ldapadd of one record
> You can try first to kill -9 the process if you see it is hanging.
>
> Then start the ldap daemon and check with nmap that the port is open.
>
> Afterwards what is the error that appears when you do the ldapadd? Have you configure the .conf file for the dn and cn?
> Have you put any security measures?.
>
> Joaquin
>
> ----------
> From: Jose Antonio Gómez Muñoz
> Sent: Tuesday, June 10, 2003 2:34 PM
> To: openldap-software@OpenLDAP.org
> Subject: ldap server hungs after ldapadd of one record
>
> Hello,
>
> I'm new in openldap. I use
>
> Linux Suse 8.0
> openldap2-2.1.4-46
> openldap-lib-1.2.13
>
>
> I ran the next command:
>
> ldapadd -v -D 'cn=Manager,dc=Colegio Oficial de Arquitectos de Madrid, dc=es' -x -f invitado.ldif -w password
>
>
> The ldif file had only one record, but perhaps SOME EXTRA BLANK LINE, I'm not sure.
> A lot of times I have added records in this same way, but after trying to execute this command (this command didn't end with the root prompt) the CPU raised 100% with slapd.
>
> No more ldapsearch were posible, so I did
>
> /etc/init.d/ldap restart
>
> but now the ldap server starts, but doesn't open the port 389:
>
> ldapsearch -x -b 'uid=col690, ou=smb, dc=Colegio Oficial de Arquitectos de Madrid,dc=es'
> ldap_bind: Can't contact LDAP server (81)
>
>
> nmap localhost
>
> Starting nmap V. 2.54BETA30
> Interesting ports on localhost (127.0.0.1):
> (The 1539 ports scanned but not shown below are in state: closed)
> Port State Service
> 22/tcp open ssh
> 25/tcp open smtp
> 53/tcp open domain
> 80/tcp open http
> 111/tcp open sunrpc
> 139/tcp open netbios-ssn
> 515/tcp open printer
> 3128/tcp open squid-http
> 6000/tcp open X11
> 10000/tcp open snet-sensor-mgmt
>
> So I don't know what can I do. Any help will be appreciated. Thanks very much.
>
>