Highlighted
Absent Member.
Absent Member.
1139 views

AFP "Hash List"?

What is the hash list that is referenced in the afptcp.log? Here is what it looks like:

Feb 10 10:15:56 d208 afptcpd[7382]: [debug] Ldap user name: cn=James***,ou=TECH,ou=CENTRAL,o=***
Feb 10 10:15:57 d208 afptcpd[7382]: [debug] UID: 600
Feb 10 10:16:00 d208 afptcpd[7382]: [error] Map GUID to DN returns -765
Feb 10 10:16:00 d208 afptcpd[7382]: UTF8 Name
Feb 10 10:16:00 d208 afptcpd[7382]: [error] Unable to open parent (ZID #127 <7f>) 20407 <4fb7> child is <mach_kernel>
Feb 10 10:16:00 d208 afptcpd[7382]: [error] FPGetFileDirParms: GetInfo call is failed with err 20407
Feb 10 10:16:00 d208 afptcpd[7382]: UTF8 Name
Feb 10 10:16:00 d208 afptcpd[7382]: [error] Unable to open parent (ZID #127 <7f>) 20407 <4fb7> child is <DCIM>

(...Lots more of this)

Feb 10 10:16:00 d208 afptcpd[7382]: [debug] entry 130 already exists in the hash table Feb 10 10:16:00 d208 afptcpd[7382]: [error] Failed to resolve user name .Help_Desk_Specialist.ou=ADMIN_SVCS.ou=CENTRAL.o=*** NWDSResolveName error: -601 - fffffda7
Feb 10 10:16:00 d208 afptcpd[7382]: [error] Failed to resolve user name .Help_Desk_Specialist.ou=BUSINESS.ou=CENTRAL.o=*** NWDSResolveName error: -601 - fffffda7

(...Lots more of this)

Feb 10 10:16:01 d208 afptcpd[7382]: [error] Unable to convert trustee GUID -1 <ffffffff>

That is NOT an attempted login. Dozens of these kinds of -601 errors follow for users not trying to login. Apparently they are somehow stuck in this "hash table"? The logs for a single login attempt will return over 13000 lines of these -601 errors coming from this hash table.

Any ideas what is going on here?
Labels (1)
0 Likes
1 Reply
Highlighted
Absent Member.
Absent Member.

Re: AFP "Hash List"?

Tha hash table is used as part of AFP Directory Cache. Cache entry handles get stored in hash tables. "entry 130 already exists in the hash table" says that file system object whose entry ID is 130 is already present in Cache. This is not an error.

We just need to worry about NWDSResolveName errors. Make sure all your users are present in the contexts that are mentioned on afpDircxt.conf file. Normally 601 error designate the entry not found error for eDirectory.

Other than generating huge log messages, are you facing any login problems for your users?

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.