I'm getting WSOD on several tests using the latest (unstable6) build.

Server Properties:

  • sid = idauth1
  • name = idauth1
  • status = 1
  • type = novell_edir
  • address = idauth1
  • port = 389
  • tls = 0
  • bind_method = 1
  • basedn = Array
  • binddn = cn=username,ou=Services,o=hfcc
  • user_dn_expression =
  • user_attr = cn
  • mail_attr = mail
  • ldap_to_drupal_user =
  • testing_drupal_username = webtest

Test Grid Summary, Mixed Mode:

  • LDAP_authen.MM.ULT.user1.goodpwd -- result: OK
  • LDAP_authen.MM.ULT.user1.badpwd -- result: OK
  • LDAP_authen.MM.ULT.drupal.goodpwd - result: WSOD
  • LDAP_authen.MM.ULT.drupal.badpwd - result: WSOD
  • LDAP_authen.MM.ULT.ldap.newaccount.goodpwd - result: OK
  • LDAP_authen.MM.ULT.ldap.newaccount.badpwd - result: WSOD
  • LDAP_authen.MM.ULT.existingacct.goodpwd - result: OK
  • LDAP_authen.MM.ULT.existingacct.badpwd - result: WSOD

Details of the test, including watchdog debug messages, are attached.

I'm not getting any specific errors in my web server's error log or in the watchdog, and I have error logging cranked as high as it will go. My local drupal user logs in fine when LDAP modules are disabled. I get the WSOD on both Chrome and IE, so it doesn't appear to be a browser-specific or caching issue.

CommentFileSizeAuthor
ldap-unstable6-mm-results.txt1.75 KBmicahw156

Comments

micahw156’s picture

micahw156
he/him/his
commented
Priority: Normal » Critical

Bumping priority on this. Really can't proceed with any other testing until this is resolved.

johnbarclay’s picture

johnbarclay commented

This was a bug in the logging which would have happened if you had detailed logging on. I'm applying the fix to head. That is what caused the WSODs. I cleaned up the error catching and logging a little and made it an issue for 7.2 to have more consistent approach to the logging. I went through the next set of tests successfully. This will be in head and should get rolled to -dev on the 17th.

LDAP_authen.EM.ULT.user1.goodpwd -- result: ok: Successful logon as user 1
LDAP_authen.EM.ULT.user1.badpwd -- result: ok: Drupal logon error message.
LDAP_authen.EM.ULT.drupal.goodpwd -- result: ok: Drupal logon error message.
LDAP_authen.EM.ULT.drupal.badpwd-- result: ok: Drupal logon error message.
LDAP_authen.EM.ULT.ldap.newaccount.goodpwd -- result: ok: Successful logon, with user record created and authmapped to ldap
LDAP_authen.EM.ULT.ldap.newaccount.badpwd -- result: ok: Drupal logon error message.
LDAP_authen.MM.ULT.existingacct.goodpw -- result: ok: Successful logon.
LDAP_authen.MM.ULT.existingacct.badpw -- result: ok: Drupal logon error message.

micahw156’s picture

micahw156
he/him/his
commented
Priority: Critical » Major

Did a quick test to confirm that this does work as expected with verbose logging disabled. Will test again when your patch lands.

Downgrading priority since it does work without verbose logging.

johnbarclay’s picture

johnbarclay commented
Status: Active » Fixed

I believe these are all fixed. I'm running with strict errors on my dev server now also.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.