New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: LDAP makes NC29 server unstable #45211
Comments
I understand you can't enable the app now, but can you expand on the initial issue:
"Crash" as in ... ? And maybe provided the associated log entry? I don't suppose you can provide some details about how you configured LDAP? |
Thank you for responding, crash as in literally server is not showing any gui and not accessible, showing "server is not able to complete your request",ldap backend was enabled after installing php-ldap on the system. I tried installing it (ldap backend) using occ via shell but it keeps breaking the server. When i install it from the app store on nc it prevents me and shows the screen attached. Logs actually show nothing regarding why server crashes or what happen after i install the ldap. I will provide you with them just when i am at office. Thank you |
At first it crashes after faulty config which I can't trace yet because AD management is not within my sight, we have another dept handling it, but now it just does that after enabling ldap backend |
So you're saying it initially crashed before you configured anything LDAP related? Please provide the entire stack trace from the first erroneous log entry (it'll likely include a stack trace) after you enabled the |
sorry for messy explanation, the exact process was: now team decided to revert to older snapshot so i don't have the old logs of theses processes, but i have the current logs, they still full of ldap errors |
Can you check the linux audit logs? you have dns errors and a few other things. Just to rule out selinux problems. (as you are running on rhel/centos) |
SElinux is set off by setenforce 0, unless there's another way? dns issue appeared after changing the dns because i thought it was the issue, so anyway we are rolling back to the old one |
since i got internal error again, these are the logs: Level App Message Time Error index Exception: LDAP Operations error at 2024-05-08T10:31:08+00:00
Warning user_ldap Bind failed: 49: Invalid credentials 2024-05-08T10:38:42+00:00 Error PHP ldap_search(): Search: Operations error at 2024-05-08T10:38:42+00:00 Error support Exception: LDAP Operations error at 2024-05-08T10:38:42+00:00
Warning support Can not determine user count for OCA\User_LDAP\User_Proxy 2024-05-08T10:38:42+00:00 Error PHP ldap_search(): Search: Operations error at 2024-05-08T10:38:42+00:00 Error index Exception: LDAP Operations error at 2024-05-08T10:38:42+00:00
Warning support Can not determine user count for OCA\User_LDAP\User_Proxy 2024-05-08T10:38:42+00:00 Error PHP ldap_search(): Search: Operations error at 2024-05-08T10:38:42+00:00 Error index Exception: LDAP Operations error at 2024-05-08T10:38:42+00:00
|
issue solved by providing the right creds. |
Bug description
LDAP enabled backend app causing server to crash after configurating it, now it is not allowed to be enabled on the server, and when installed from shell it causes gui to show internal server error
Steps to reproduce
1.install ldap server
2.configure it
3.server crashes
Expected behavior
Server works normally
Installation method
Community Web installer on a VPS or web space
Nextcloud Server version
29
Operating system
RHEL/CentOS
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: