Issue upgrading from 4.1.2 to 4.4.4, Fails with ldap errors

Paul Benton January 19, 2012

I'm trying to do a manual upgrade as recommended by the docs. I've copied my osusers.xml file and when I start Jira to upgrade the data I get:

Exception thrown during upgrade: org.springframework.ldap.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-03151EFD, problem 2001 (NO_OBJECT), data 0, best match of

I've seen that using

<property name="java.naming.referral">follow</property>" has worked for some.
Although I am using a Global Catalog in order not to do forwarding/referals for multiple sub domains that arn't accessable from the jira server.
wondering if anyone has any ideas how to get the upgrader to like my ldap setup?
TIA


4 answers

0 votes
BernardoA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 11, 2012

Basically your issue is caused by a non-existent DN specified in the User Search field, so oou may be asked to define a DN so that a service can bind to it to authenticate.

0 votes
John Chin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 14, 2012

Hi Paul,

There is a KB for this issue, please refer here.

  1. https://confluence.atlassian.com/display/CONFKB/LDAP+Error+Code+32

Hope it helps.

John

0 votes
Paul Benton January 19, 2012

Didn't fit in the comments so can check it out here http://pastebin.com/wQBR8r9y

0 votes
Aspect Infra Team
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 19, 2012

can you please provide a little bigger part of log?

Suggest an answer

Log in or Sign up to answer