Rudder

Thansk Dennis, can you add the criteria you put in the regexp field ??

Thanks!

So, the problem is due to the number of software entries. In more details:

LDAP does not support regex matching on queries. So to handle them, we return all the entries to check for the regex and process the regex on the client side.

On the other hand, there is limits on the number of entries returned by the server.

The conjonction of the two factors lead to the error.

I think there is no reason to limit the number of returned entries, and we should just safe-guard with a time limit for requests.
An other solution is to pre-process the regex query to see if it can be more efficiently translated to a substring query, as it is the case here, so that we have far less response in the common cases.

An other think: we never ever delete software, meaning that their number is strictly rising and so that bug will appear at some point for any people using regex match on software.

I don't see any easy (i.e: without code in the webapp) workaround safe removing softwares from LDAP so that only actuall software will be re-added (and so that the total stay under the limit.

https://github.com/Normation/rudder/pull/608

Applied in changeset ff11035dc91c2385e9652b339d593691f276b18c.

This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:

• The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000038.html
• The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog27
• Download information: https://www.rudder-project.org/site/get-rudder/downloads/