From 6e533f223e85f6fb94263de93d911682de972f36 Mon Sep 17 00:00:00 2001 From: Johannes Meyer Date: Thu, 29 Jan 2015 17:12:59 +0100 Subject: [PATCH] Log warnings emitted by ldap_control_paged_result_response() as debug Such a warning is emitted as well in case it's not critical. That is passing an alternative overall result limit using ldap_search() to the server causes it being applied across pages so ldap_control_paged_result_response() does not indicate the "end" of the resultset just by adjusting the cookie but by emitting the warning as well. --- library/Icinga/Protocol/Ldap/Connection.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/Icinga/Protocol/Ldap/Connection.php b/library/Icinga/Protocol/Ldap/Connection.php index 7b1ca4567..37d8c4660 100644 --- a/library/Icinga/Protocol/Ldap/Connection.php +++ b/library/Icinga/Protocol/Ldap/Connection.php @@ -329,7 +329,7 @@ class Connection ldap_control_paged_result_response($this->ds, $this->lastResult, $this->pageCookie); } catch (Exception $e) { $this->pageCookie = ''; - Logger::error( + Logger::debug( 'Unable to request paged LDAP results. Does the server allow paged search requests? (%s)', $e->getMessage() );