Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47444
during ipa testing on el7, this error was logged to /var/log/messages:
Jul 19 23:21:16 dhcp207-172 ns-slapd: encoded packet size too big (599441 > 65536)
This error should have been logged to the directory server errors log. We need to ensure that sasl error messages are handled correctly. We are setting SASL_CB_LOG in ids_sasl_callbacks in sasl_server_init, so I don't know why this error wasn't handled.
I don't know if this is the right place to report this - but a ticket search on the error "ns-slapd: encoded packet size too big" matched perfectly
I ran into this problem using an IPA server as the LDAP source for a GitLab (Community Edition) server
Plain-vanilla installs of each, so it's very easy to replicate
To increase the packet size setting [nsslapd-sasl-max-buffer-size] -- I followed instructions from here: http://stackoverflow.com/questions/28627406/freeipa-no-host-replication
We run our IPA servers in a cluster, after 10mins or so the change had not replicated so I repeated my change on the 2nd IPA server
I know that the small packet size is not _technically_ an error, but I read some tickets that said that it was hard to reproduce -- it's not.
Now that Garrity and Barkeep are basically gone, gitlab seems to be the choice for SCM w/fork-merge-pull & code review -- and everyone should be running IPA anyway
The logged error gives these numbers: (232301 > 65536) so a bump up from 64K to 256K would do it
Thanks for your time
And thanks for IPA !!
Al;