search

snipe / snipe-it

A free open source IT asset/license management system
https://snipeitapp.com
GNU Affero General Public License v3.0
11.12k stars 3.19k forks source link

LDAP Whoops error after clicking Synchronize #8489

Closed pablom1776 closed 4 years ago

pablom1776 commented 4 years ago

Please confirm you have done the following before posting your bug report:

Describe the bug I do not know how to enable debug mode. I have looked everywhere to see if this was an issued someone else may have posted. I went to the LDAP in the settings. I ran a Test LDAP Sync and comes back as: Connection to LDAP server established! I ran a Test LDAP Login: User authentication against LDAP successfully! When I go to Synchronize in the People tab it takes me to a Whoops error message page, and no users actually sync. I am wondering if it can be the php. Please provide instructions

To Reproduce Steps to reproduce the behavior:

  1. Go to the People
  2. Click on Synchronize
  3. See error: Whoops, looks like something went wrong.

Expected behavior Normally I get a list of users that synced.

Screenshots image

image

image

Server (please complete the following information):

Desktop (please complete the following information): N/A

Smartphone (please complete the following information): N/A

Error Messages

Additional context

Add any other context about the problem here.

Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.

uberbrady commented 4 years ago

It definitely seems strange that the sync test works but the actual sync doesn't. Especially if nothing else changed.

To enable debug mode, set APP_DEBUG=true in your .env - then poke around in your storage/logs/laravel.log file and see what shows up.

One possibility is if your LDAP server has more than, say, a thousand or so users on it, and your LDAP server doesn't support paging, then we can run into problems - but usually those end up being different problems; a Whoops error is unusual.

Has anything else changed?

uberbrady commented 4 years ago

I've definitely seen something like this a while ago - where a customer had changed their OU structure (deleting some OU's), and they still had those OU's defined in the Locations. Later versions of Snipe-IT have better error reporting for that.

zsirmo commented 4 years ago

I have a same problem. I use(try) MS AD.

Log attached. laravel.log

pablom1776 commented 4 years ago

Hello uberbrady, There have been no changes that I know of. Are you able to send me the exact cmmd I need to run. I do not have a lot of experience with Linux. Thanks,

uberbrady commented 4 years ago

I have a same problem. I use(try) MS AD.

Log attached. laravel.log

@zsirmo - We fixed that issue in the latest v5 release - https://github.com/snipe/snipe-it/releases/tag/v5.0.0-beta-6-GM - can you give that one a try?

uberbrady commented 4 years ago

@pablom1776 it's less of a Snipe-IT issue, and more of a "How is your directory set up?" issue - if you've deleted an OU recently - or renamed one - Snipe-IT will still try to keep looking for it afterwards. We fixed that in a later v4.x release - you can certainly try v4.9.4 or 4.9.5 (though I would recommend 4.9.4 for now).

We had one customer who ended up putting back their old OU's and then running a sync, and only after that deleting the OU's. That seems excessive to me, though.

v5's sync system is completely rebuilt and shouldn't (emphasis on shouldn't) fall prey to the same problems, if you're feeling adventurous. It is not formally released yet, but the above-listed release is what we consider our "Golden Master", hopefully for later this week.

zsirmo commented 4 years ago

I have a same problem. I use(try) MS AD. Log attached. laravel.log

@zsirmo - We fixed that issue in the latest v5 release - https://github.com/snipe/snipe-it/releases/tag/v5.0.0-beta-6-GM - can you give that one a try?

Good job, working 👍

GitHub
Release v5.0.0-beta-6-GM · snipe/snipe-it
New from v5.0.0-beta-5 to v5.0.0-beta-6-GM This is the golden master for Snipe-IT v5. Primary in this release are some critical fixes for AD interoperability. IMPORTANT: This version of Snipe-IT re...
uberbrady commented 4 years ago

Please let us know if this is still a problem in the latest v5 - https://github.com/snipe/snipe-it/releases/tag/v5.0.4

GitHub
Release v5.0.4 · snipe/snipe-it
New in v5.0.4 This is a bug fix release that should handle some of the issues reported over the past few days. We'll be hitting them back as quickly as you can throw issues at us, so keep them comi...
pablom1776 commented 4 years ago

Thanks for your help everyone. I am good now. I am having an issue with the Backup and the QR code.

uberbrady commented 4 years ago

Please open a new issue for your Backup and QR code issues - I suspect they're probably permissions-related.