I just recently noticed 'input error=-2' when running in debug mode, and in my logs (loglevel sync shell stats ber conns). It seems to occur (always) when the connection it closed. Anyone know what might cause this? Is it anything I should be concerned with? I am not sure when this started. I have made numerous changes over the past few weeks; too many to back out.
Thanks, Joe
From DEBUG::
ber_get_next on fd 25 failed errno=0 (Success) connection_read(25): input error=-2 id=20, closing. connection_closing: readying conn=20 sd=25 for close connection_close: conn=20 sd=25 =>ldap_back_conn_destroy: fetching conn 20 daemon: removing 25
Similarly in log: Jun 4 15:39:31 ldapserver slapd[7683]: daemon: read active on 16 Jun 4 15:39:31 ldapserver slapd[7683]: conn=150 op=2 UNBIND Jun 4 15:39:31 ldapserver slapd[7683]: connection_read(16): input error=-2 id=150, closing. Jun 4 15:39:31 ldapserver slapd[7683]: daemon: removing 16 Jun 4 15:39:31 ldapserver slapd[7683]: conn=150 fd=16 closed Jun 4 15:39:31 ldapserver slapd[7683]: daemon: epoll: listen=7 active_threads=0 tvp=zero Jun 4 15:39:31 ldapserver slapd[7683]: daemon: epoll: listen=8 active_threads=0 tvp=zero Jun 4 15:39:31 ldapserver slapd[7683]: daemon: activity on 1 descriptor Jun 4 15:39:31 ldapserver slapd[7683]: daemon: activity on:
_________________________________________________________________ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:W...
openldap-technical@openldap.org