Hi
I configure LDAP authentification.
All work find.
But when i look at log page i see lot of line like :
Error PHP ldap_control_paged_result_response(): No server controls in result at /var/www/html/nextcloud/apps/user_ldap/lib/LDAP.php#74
And i get lots of this line each LDAP connexion.
What can cause this problem? ( I read something about $cookie but nothing about how to debug this problem)
cordialy
Hi
Iām looking for a way to get value return by LDAP request to see why nextcloud show me this error, so i can give more information on this post about this problem.
Is there a debug mode?
Cordialy
Hi
I set 'loglevel' => 0,
in /nextcloud/config/config.php file.
It seems that i get the php error when i have this in ldap result :
limit 500 offset 0
How to avoid that?
cordialy
tflidd
December 22, 2017, 12:17pm
4
There was a report on owncloud:
opened 10:18AM - 16 Apr 16 UTC
closed 01:24PM - 12 Dec 17 UTC
Type:Bug
I just upgraded from owncloud 9.0 to owncloud 9.0.1.
Now, I get the following erā¦ rors by mail from the cron job:
[owncloud][PHP][3] ldap_control_paged_result_response(): No server controls in result at /usr/local/www/owncloud/apps/user_ldap/lib/ldap.php#70
[owncloud][PHP][3] ldap_control_paged_result_response(): No server controls in result at /usr/local/www/owncloud/apps/user_ldap/lib/ldap.php#70
[owncloud][PHP][3] ldap_control_paged_result_response(): No server controls in result at /usr/local/www/owncloud/apps/user_ldap/lib/ldap.php#70
[owncloud][PHP][3] ldap_control_paged_result_response(): No server controls in result at /usr/local/www/owncloud/apps/user_ldap/lib/ldap.php#70
Despite this, most things that I can see appear to work just fine.
I think I also had an error with the cron job when I upgraded to 9.0, which took me to patch one file, but I can't find the fix in the Internet now, and I can't tell if the error was the same.
**Operating system**: FreeBSD 10.3-RELEASE
**Web server:** Apache 2.4 (from ports)
**Database:** MariaDB 5.5 (pre-compiled pkg)
**PHP version:** 5.6.20 (pre-compiled pkg)
**ownCloud version:** 9.0.1 (from ports, 9.0.1_1)
**Updated from an older ownCloud or fresh install:** upgraded from 9.0
**Where did you install ownCloud from:** from FreeBSD ports, port revision 9.0.1_1
**Signing status (ownCloud 9.0 and above):**
```
No errors have been found.
```
#### LDAP configuration
```
+-------------------------------+---------------------------------------------------------------------------------------------------------+
| Configuration | |
+-------------------------------+---------------------------------------------------------------------------------------------------------+
| hasMemberOfFilterSupport | |
| hasPagedResultSupport | |
| homeFolderNamingRule | |
| lastJpegPhotoLookup | 0 |
| ldapAgentName | |
| ldapAgentPassword | *** |
| ldapAttributesForGroupSearch | |
| ldapAttributesForUserSearch | |
| ldapBackupHost | |
| ldapBackupPort | |
| ldapBase | dc=ramos,dc=link |
| ldapBaseGroups | dc=ramos,dc=link |
| ldapBaseUsers | dc=ramos,dc=link |
| ldapCacheTTL | 600 |
| ldapConfigurationActive | 1 |
| ldapDynamicGroupMemberURL | |
| ldapEmailAttribute | mail |
| ldapExperiencedAdmin | 0 |
| ldapExpertUUIDGroupAttr | |
| ldapExpertUUIDUserAttr | |
| ldapExpertUsernameAttr | uid |
| ldapGroupDisplayName | cn |
| ldapGroupFilter | (&(objectclass=posixGroup)(gidNumber>=2001)) |
| ldapGroupFilterGroups | |
| ldapGroupFilterMode | 1 |
| ldapGroupFilterObjectclass | posixGroup |
| ldapGroupMemberAssocAttr | memberUid |
| ldapHost | ldapi:/// |
| ldapIgnoreNamingRules | |
| ldapLoginFilter | (&(|(objectclass=inetOrgPerson))(|(uid=%uid)(|(cn=%uid)(displayName=%uid)(givenName=%uid)(mail=%uid)))) |
| ldapLoginFilterAttributes | cn;displayName;givenName;mail |
| ldapLoginFilterEmail | 0 |
| ldapLoginFilterMode | 0 |
| ldapLoginFilterUsername | 1 |
| ldapNestedGroups | 1 |
| ldapOverrideMainServer | |
| ldapPagingSize | 0 |
| ldapPort | 389 |
| ldapQuotaAttribute | |
| ldapQuotaDefault | |
| ldapTLS | 1 |
| ldapUserDisplayName | displayName |
| ldapUserDisplayName2 | |
| ldapUserFilter | (|(objectclass=inetOrgPerson)) |
| ldapUserFilterGroups | |
| ldapUserFilterMode | 0 |
| ldapUserFilterObjectclass | inetOrgPerson |
| ldapUuidGroupAttribute | auto |
| ldapUuidUserAttribute | auto |
| turnOffCertCheck | 0 |
| useMemberOfToDetectMembership | 1 |
+-------------------------------+---------------------------------------------------------------------------------------------------------+
```
I use OpenLDAP 2.4 and the core, inetorgperson schemas.
This is a family server, still small but growing.
Also, I changed recently to ldapi:/// where I used to have localhost.
Also, I've used both 500 and 0 for ldapPagingSize.
None of these changes anything.
Thank you,
Since itās unclear if it has been resolved, you could file a new bug report in Issues Ā· nextcloud/server Ā· GitHub and give more details about your setup. Make sure that you are running a current version of Nextcloud first (12.0.4 or 11.0.5).
Hi
Thanks for your answer.
Iāve read this bug report too.
But first i prefere to post on forum to know if the problem come from LDAP server or from Nextcloud.
I fellow advice present here https://github.com/nextcloud/server/issues/6613 and set āloglevelā => 4
But iām not sur itās a good idea and prefer to solve this error.
Iāll go open a github ticket.
cordialy
tflidd
December 22, 2017, 12:41pm
6
LDAP issue often remain unanswered as it is less popular by individual users and the developers and not all checking the topics here on a regular basis.
Hi
Thanks for your advise.
I create a issue here : https://github.com/nextcloud/server/issues/7610
cordialy
1 Like
Hi,
I come back on this problem that I solve.
Our LDAP donāt support ldap_control_paged_result_response().
So i disable the āldapPagingSizeā ldap parameter from default 500 value to 0 value.
And no more problem nor log of ldap_control_paged_result_response().
cordialely