namcd cores when refreshing cache

  • 3320420
  • 16-Nov-2007
  • 16-Mar-2012


Novell Open Enterprise Server (Linux based)


When namcd either creates cache or attempts to refresh cache, it will core.

/etc/nam.conf includes:

The core file produced by namcd shows a stack similar to the following:

#0 0x401e4d43 in strlen () from /lib/tls/

#1 0x0805bec4 in insertGidListIntoUserHash (value=0x8070518,

userFDN=0x8080a10"cn=Test,ou=foo,o=novell", passwdHash=0x0, gidlist=0x0,

gidcount=0xbffff0d0) at hash.c:1271

#2 0x08050693 in addOutOfBaseContextUsersToList (nss_priv=0x80667e0,

username=0x806b800"Test", fdn=0x8080a10 "cn=Test,ou=foo,o=novell")

at nss_ldap.c:6194

#3 0x08054ff0 in populate_groupHash_fromNDS (nss_privt=0x80667e0)

at nss_ldap.c:3901

#4 0x0804d02c in main (argc=1, argv=0xbffff4f4) at namcd.c:789

If the attributes/objectclass of the user cn=test,ou=foo,o=novell (in this example) are checked, they will be missing a required LUM attribute or objectclass.

The user can be examined by exporting the user using ldapsearch.

EXAMPLE: ldapsearch -h ipaddress -D adminFDN -w adminpwd -b searchbase cn=user

Here's an example using the specified user:

ldapsearch -h IP -D cn=admin,o=novell -w novell -b o=novell cn=testuser


1. Change the enable-persistent-cache to no and restart namcd
then either:
1. Export the problem user and determine which attributes are missing; then fix the user.
2. Delete the problem user

This issue has been reported to development.


Reported to Engineering