I've got a client who's got a SuSE server and basically the slapd daemon is running, no problems reported in the logs yet it is not listening on port 389. Has anyone had a similar problem on any platform or version of Linux?
In this case the relevant errata for the SuSE product has been applied but it didn't change the outcome. Starting manually with /usr/lib/openldap/slapd -d 255 -h ldap://192.168.10.10 produces a lot of info, here's the relevant bit:- @(#) $OpenLDAP: slapd 2.1.4 (Mon Mar 24 14:47:47 UTC 2003) $ [EMAIL PROTECTED]:/usr/src/packages/BUILD/openldap-2.1.4/servers/slapd daemon_init: ldap:///192.168.10.10:389/ daemon_init: listen on ldap:///192.168.10.10:389/ daemon_init: 1 listeners to open... ldap_url_parse_ext(ldap:///192.168.10.10:389/) daemon: initialized ldap:///192.168.10.10:389/ daemon_init: 1 listeners opened slapd init: initiated server. slap_sasl_init: initialized! bdb_open: initialize BDB backend bdb_open: Sleepycat Software: Berkeley DB 4.0.14: (October 16, 2002) reading config file /etc/openldap/slapd.conf It then goes on to parse the config file & do database stuff & so forth, I'm not sure I should be giving out all that info but it ends with:- slapd startup: initiated. bdb_db_open: dc=in,dc=artedomus,dc=com bdb_db_open: dbenv_open(/var/lib/ldap) Of course since I stared it in debug mode I had to kill it off from another terminal with a kill -9. -- ---<GRiP>--- Grant Parnell - senior consultant EverythingLinux services - the consultant's backup & tech support. Web: http://www.everythinglinux.com.au/services We're also busybits.com.au and linuxhelp.com.au. Phone 02 8752 6622 to book service or discuss your needs. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
