" Activating pending operation messages " in LDAP trace.

  • 3309655
  • 13-Mar-2007
  • 26-Apr-2012

Environment

Novell Open Enterprise Server (Linux based)
Novell eDirectory 8.8 SP1 for Linux

Situation

The server is running Novell OES Linux SP1 with Samba and LUM. When running dstrace with the +LDAP flag the following messages are seen every few seconds:
>>> [2007/01/04 12:11:13] (10.100.100.112:32806)(0x0002:0x63) Activating pending
>>> operation 0x2:0x63 on connection 0x5706dd20
>>> [2007/01/04 12:11:13] (10.100.100.110:57405)(0x0002:0x63) Activating pending
>>> operation 0x2:0x63 on connection 0x47b93700
>>> [2007/01/04 12:11:13] (10.100.100.70:60946)(0x0002:0x63) Activating pending
>>> operation 0x2:0x63 on connection 0x4493a700
>>> [2007/01/04 12:11:13] (10.100.100.60:48394)(0x0002:0x63) Activating pending
>>> operation 0x2:0x63 on connection 0x5706dee0
>>> [2007/01/04 12:11:13] (10.100.100.40:9224)(0x0002:0x63) Activating pending
>>> operation 0x2:0x63 on connection 0x5692b540
>>> [2007/01/04 12:11:13] (10.100.100.10:17671)(0x0002:0x63) Activating pending
>>> operation 0x2:0x63 on connection 0x58d499a0

Resolution

The LUM service was configured for persistant search so that when a POSIX group or user was modified the group or user change would be cached locally by the server. To do this the LDAP service periodically polls the server to see if changes have occured. These messages are a normal effect of this persistant search and are no cause for alarm.
 
Novell recommends that LUM's persistent search be disabled.  Please refer to KB 7006086 for instructions on how to perform this step.  You must restart NDSD and NAMCD after disabling this parameter.  On new installations of OES2 SP3 it is off by default.
 
NOTE: these messages may still be seen after disabling a server's LUM setting.  This can be due to other server's still having persistent search turned on or another application in the environment is making persistent search calls.